# Rolling upgrade problem **URL:** \ **Category:** Elasticsearch\ **Created:** [March 14, 2019, 6:56pm UTC](https://discuss.elastic.co/t/rolling-upgrade-problem/172408 "2019-03-14T18:56:13Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![kb2295](https://avatars.discourse-cdn.com/v4/letter/k/4491bb/32.png) [@kb2295](https://discuss.elastic.co/u/kb2295)\ **Post date:** [March 14, 2019, 6:56pm UTC](https://discuss.elastic.co/t/rolling-upgrade-problem/172408/1 "2019-03-14T18:56:13Z")
Hi, I'm trying to perform a rolling upgrade (5.6 to 6.6) on 3 nodes. I successfully upgraded the first node according to the instructions in: [https://www.elastic.co/guide/en/elasticsearch/reference/current/rolling-upgrades.html](https://www.elastic.co/guide/en/elasticsearch/reference/current/rolling-upgrades.html) I also started the new version of kibana on that node (node 1). Now, I'm trying to upgrade the next node. I see that it is shutdown, so i cant disable shard allocation on it. When I try to directly start elasticsearch 6.6 on this node (using the SAME config as the prev node), i get this error: ``` [2019-03-14T15:03:23,618][WARN][o.e.g.DanglingIndicesState] [vm-b4cc-2505.nam.nsroot.net] [[.watcher-history-6-2019.03.01/0ZnUwEH9Qjy3jA7StVyspw]] can not be imported as a dangling index, as index with same name already exists in cluster metadata [2019-03-14T15:03:27,568][WARN][o.e.g.DanglingIndicesState] [vm-b4cc-2505.nam.nsroot.net] [[.watcher-history-6-2019.03.01/0ZnUwEH9Qjy3jA7StVyspw]] can not be imported as a dangling index, as index with same name already exists in cluster metadata ``` ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [April 11, 2019, 6:56pm UTC](https://discuss.elastic.co/t/rolling-upgrade-problem/172408/2 "2019-04-11T18:56:20Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.