# Can't join node after upgrade **URL:** \ **Category:** Elasticsearch\ **Created:** [October 9, 2018, 5:20pm UTC](https://discuss.elastic.co/t/cant-join-node-after-upgrade/151693 "2018-10-09T17:20:46Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![McElroy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mcelroy/32/24639_2.png) [@McElroy](https://discuss.elastic.co/u/McElroy)\ **Post date:** [October 9, 2018, 5:20pm UTC](https://discuss.elastic.co/t/cant-join-node-after-upgrade/151693/1 "2018-10-09T17:20:46Z")
I can't join my upgraded node to my cluster again. ``` [2018-10-09T19:21:39,386][WARN][r.suppressed] path: /se-tcj-al-2018-10-09/log/c309f128- 9c17-4848-9fb0-1c2ae3a835c5, params: {index=se-tcj-al-2018-10-09, id=c309f128-9c17-4848-9fb0-1c2ae3a835c5, type=log} org.elasticsearch.cluster.block.ClusterBlockException: blocked by: [SERVICE_UNAVAILABLE/1/state not recovered / initialized];[SERVICE_UNAVAILABLE/2/no master]; at org.elasticsearch.cluster.block.ClusterBlocks.globalBlockedException(ClusterBlocks.java:166) ~[elasticsearch-6.3.0.jar:6.3.0] at org.elasticsearch.action.bulk.TransportBulkAction$BulkOperation.handleBlockExceptions(TransportBulkAction.java:386) [elasticsearch-6.3.0.jar:6.3.0] at org.elasticsearch.action.bulk.TransportBulkAction$BulkOperation.doRun(TransportBulkAction.java:272) [elasticsearch-6.3.0.jar:6.3.0] at org.elasticsearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:37) [elasticsearch-6.3.0.jar:6.3.0] at org.elasticsearch.action.bulk.TransportBulkAction$BulkOperation$2.onTimeout(TransportBulkAction.java:420) [elasticsearch-6.3.0.jar:6.3.0] at org.elasticsearch.cluster.ClusterStateObserver$ContextPreservingListener.onTimeout(ClusterStateObserver.java:317) [elasticsearch-6.3.0.jar:6.3.0] at org.elasticsearch.cluster.ClusterStateObserver$ObserverClusterStateListener.onTimeout(ClusterStateObserver.java:244) [elasticsearch-6.3.0.jar:6.3.0] at org.elasticsearch.cluster.service.ClusterApplierService$NotifyTimeout.run(ClusterApplierService.java:576) [elasticsearch-6.3.0.jar:6.3.0] at org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingRunnable.run(ThreadContext.java:625) [elasticsearch-6.3.0.jar:6.3.0] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [?:1.8.0_05] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [?:1.8.0_05] at java.lang.Thread.run(Thread.java:745) [?:1.8.0_05] Suppressed: org.elasticsearch.discovery.MasterNotDiscoveredException at org.elasticsearch.action.support.master.TransportMasterNodeAction$AsyncSingleAction$4.onTimeout(TransportMasterNodeAction.java:223) ~[elasticsearch-6.3.0.jar:6.3.0] at org.elasticsearch.cluster.ClusterStateObserver$ContextPreservingListener.onTimeout(ClusterStateObserver.java:317) [elasticsearch-6.3.0.jar:6.3.0] at org.elasticsearch.cluster.ClusterStateObserver$ObserverClusterStateListener.onTimeout(ClusterStateObserver.java:244) [elasticsearch-6.3.0.jar:6.3.0] at org.elasticsearch.cluster.service.ClusterApplierService$NotifyTimeout.run(ClusterApplierService.java:576) [elasticsearch-6.3.0.jar:6.3.0] at org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingRunnable.run(ThreadContext.java:625) [elasticsearch-6.3.0.jar:6.3.0] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [?:1.8.0_05] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [?:1.8.0_05] at java.lang.Thread.run(Thread.java:745) [?:1.8.0_05] [2018-10-09T19:21:39,565][DEBUG][o.e.a.a.i.c.TransportCreateIndexAction] [myhost] timed out while retrying [indices:admin/create] after failure (timeout [1m]) [2018-10-09T19:21:39,759][DEBUG][o.e.a.a.i.t.g.TransportGetIndexTemplatesAction] [myhost] no known master node, scheduling a retry [2018-10-09T19:21:40,081][DEBUG][o.e.a.a.i.c.TransportCreateIndexAction] [myhost] timed out while retrying [indices:admin/create] after failure (timeout [1m]) [2018-10-09T19:21:40,200][DEBUG][o.e.a.a.i.c.TransportCreateIndexAction] [myhost] no known master node, scheduling a retry [2018-10-09T19:21:41,841][INFO][o.e.d.z.ZenDiscovery] [myhost] failed to send join request to master [{anotherhost}{nk1EByLST2GRnjggABJI2w}{zYlpKPhiQDuyhoGE0HU-Ng}{xxx.xxx.xxx.xxx}{xxx.xxx.xxx.xxx:9300}], reason [RemoteTransportException[[anotherhost][xxx.xxx.xxx.xxx:9300][internal:discovery/zen/join]]; nested: IllegalStateException[index [.marvel-es-1-2016.06.15/VlY3XavpTNK5JoVeAciDfQ] version not supported: 2.3.2 minimum compatible index version is: 5.0.0]; ] [2018-10-09T19:21:42,200][DEBUG][o.e.a.a.i.c.TransportCreateIndexAction] [myhost] timed out while retrying [indices:admin/create] after failure (timeout [1m]) [2018-10-09T19:21:43,690][DEBUG][o.e.a.a.i.c.TransportCreateIndexAction] [myhost] timed out while retrying [indices:admin/create] after failure (timeout [1m]) [2018-10-09T19:21:44,077][DEBUG][o.e.a.a.i.c.TransportCreateIndexAction] [myhost] no known master node, scheduling a retry ``` I try to upgrade from 5.6.1 to 6.3. Any ideas why? ---
**Author:** ![McElroy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mcelroy/32/24639_2.png) [@McElroy](https://discuss.elastic.co/u/McElroy)\ **Post date:** [October 10, 2018, 6:42am UTC](https://discuss.elastic.co/t/cant-join-node-after-upgrade/151693/2 "2018-10-10T06:42:45Z")
bump ---
**Author:** ![McElroy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mcelroy/32/24639_2.png) [@McElroy](https://discuss.elastic.co/u/McElroy)\ **Post date:** [October 15, 2018, 5:37am UTC](https://discuss.elastic.co/t/cant-join-node-after-upgrade/151693/3 "2018-10-15T05:37:42Z")
bump ---
**Author:** ![TimV](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/timv/32/13162_2.png) [@TimV](https://discuss.elastic.co/u/TimV)\ **Post date:** [October 15, 2018, 6:42am UTC](https://discuss.elastic.co/t/cant-join-node-after-upgrade/151693/4 "2018-10-15T06:42:16Z")
It looks like your node has an index (`.marvel-es-1-2016.06.15`) that was created in Elasticsearch `2.3.2` ES 6.x cannot read indices from 2.x, you need to use the reindex API to convert them to a newer format, or delete them from the cluster. See: [https://www.elastic.co/guide/en/elasticsearch/reference/6.3/setup-upgrade.html#reindexfn](https://www.elastic.co/guide/en/elasticsearch/reference/6.3/setup-upgrade.html#reindexfn) ---
**Author:** ![McElroy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mcelroy/32/24639_2.png) [@McElroy](https://discuss.elastic.co/u/McElroy)\ **Post date:** [October 15, 2018, 7:00am UTC](https://discuss.elastic.co/t/cant-join-node-after-upgrade/151693/5 "2018-10-15T07:00:12Z")
I deleted that one, therefore I am a bit startled about the message. ---
**Author:** ![McElroy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mcelroy/32/24639_2.png) [@McElroy](https://discuss.elastic.co/u/McElroy)\ **Post date:** [October 22, 2018, 11:17am UTC](https://discuss.elastic.co/t/cant-join-node-after-upgrade/151693/6 "2018-10-22T11:17:14Z")
I tried it again today and got the same message. ![image](https://us1.discourse-cdn.com/elastic/original/3X/b/c/bc4c8ae5cab5264c27b008f6d90593c70563f95a.png) Sorry for the ugly screenshot. Any ideas how to prevent this? ---
**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\ **Post date:** [October 23, 2018, 11:14am UTC](https://discuss.elastic.co/t/cant-join-node-after-upgrade/151693/7 "2018-10-23T11:14:32Z")
Not quite the same message - this is now saying that the `.kibana` index was created in Elasticsearch 2.3.2. ---
**Author:** ![McElroy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mcelroy/32/24639_2.png) [@McElroy](https://discuss.elastic.co/u/McElroy)\ **Post date:** [October 23, 2018, 11:26am UTC](https://discuss.elastic.co/t/cant-join-node-after-upgrade/151693/8 "2018-10-23T11:26:56Z")
Basically the same thing. Both indices were created with Elasticsearch 2.3.2. ---
**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\ **Post date:** [October 23, 2018, 5:51pm UTC](https://discuss.elastic.co/t/cant-join-node-after-upgrade/151693/9 "2018-10-23T17:51:07Z")
I don't really understand what you're asking. There are indices in your data directory that were created with Elasticsearch 2.3.2; Elasticsearch 6.x does not support such indices. You must reindex these into new indices and delete the old indices before you upgrade. You said that you'd deleted the `.marvel-es-1-2016.06.15` index and then received a similar message about the `.kibana` index. You have to do this for all your 2.x indices before upgrading. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [November 20, 2018, 5:51pm UTC](https://discuss.elastic.co/t/cant-join-node-after-upgrade/151693/10 "2018-11-20T17:51:09Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.