# Elastic upgrade from 6.2.3 to 6.6.1

**URL:** <https://discuss.elastic.co/t/elastic-upgrade-from-6-2-3-to-6-6-1/171848>\
**Category:** Elasticsearch\
**Created:** [March 12, 2019, 1:55am UTC](https://discuss.elastic.co/t/elastic-upgrade-from-6-2-3-to-6-6-1/171848 "2019-03-12T01:55:15Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![sharma](https://avatars.discourse-cdn.com/v4/letter/s/ebca7d/32.png) [@sharma](https://discuss.elastic.co/u/sharma)\
**Post date:** [March 12, 2019, 1:55am UTC](https://discuss.elastic.co/t/elastic-upgrade-from-6-2-3-to-6-6-1/171848/1 "2019-03-12T01:55:15Z")

</div>

Hi,

I've recently upgraded our Elastic cluster from 6.2.3 to 6.6.1, out of the three nodes one of the node`Preformatted text` is not connecting to the cluster and rest of the nodes are working fine.

Here are the health of the 3 nodes.

root@data-1:~# curl -XGET [https://localhost:9200/\_cluster/health?pretty](https://localhost:9200/_cluster/health?pretty) -k

Node0:

root@data-0:/home/usgaadmin# curl -XGET [https://localhost:9200/\_cluster/health?pretty](https://localhost:9200/_cluster/health?pretty) -k  
{  
"cluster\_name" : "rsi-rm-es-plt",  
"status" : "green",  
"timed\_out" : false,  
"number\_of\_nodes" : 2,  
"number\_of\_data\_nodes" : 2,  
"active\_primary\_shards" : 5806,  
"active\_shards" : 11612,  
"relocating\_shards" : 0,  
"initializing\_shards" : 0,  
"unassigned\_shards" : 0,  
"delayed\_unassigned\_shards" : 0,  
"number\_of\_pending\_tasks" : 1,  
"number\_of\_in\_flight\_fetch" : 0,  
"task\_max\_waiting\_in\_queue\_millis" : 0,  
"active\_shards\_percent\_as\_number" : 100.0  
}

Node1:

{  
"error" : {  
"root\_cause" : [  
{  
"type" : "master\_not\_discovered\_exception",  
"reason" : null  
}  
],  
"type" : "master\_not\_discovered\_exception",  
"reason" : null  
},  
"status" : 503  
}

Node2:

root@data-2:~# curl -XGET [https://localhost:9200/\_cluster/health?pretty](https://localhost:9200/_cluster/health?pretty) -k  
{  
"cluster\_name" : "rsi-rm-es-plt",  
"status" : "green",  
"timed\_out" : false,  
"number\_of\_nodes" : 2,  
"number\_of\_data\_nodes" : 2,  
"active\_primary\_shards" : 5820,  
"active\_shards" : 11640,  
"relocating\_shards" : 0,  
"initializing\_shards" : 0,  
"unassigned\_shards" : 0,  
"delayed\_unassigned\_shards" : 0,  
"number\_of\_pending\_tasks" : 6,  
"number\_of\_in\_flight\_fetch" : 0,  
"task\_max\_waiting\_in\_queue\_millis" : 3227,  
"active\_shards\_percent\_as\_number" : 100.0  
}

Kibana is also not working when upgraded from 6.2.3 to 6.6.1:

UI is showing

Kibana server is not ready yet since from the beginning.

Here are the logs from the dead node:

```
[2019-03-12T00:51:56,193][DEBUG][o.e.a.a.i.g.TransportGetIndexAction] [data-1] timed out while retrying [indices:admin/get] after failure (timeout [30s])
[2019-03-12T00:51:56,193][WARN][r.suppressed] [data-1] path: /.kibana, params: {index=.kibana}
org.elasticsearch.discovery.MasterNotDiscoveredException: null
        at org.elasticsearch.action.support.master.TransportMasterNodeAction$AsyncSingleAction$4.onTimeout(TransportMasterNodeAction.java:262) [elasticsearch-6.6.1.jar:6.6.1]
        at org.elasticsearch.cluster.ClusterStateObserver$ContextPreservingListener.onTimeout(ClusterStateObserver.java:322) [elasticsearch-6.6.1.jar:6.6.1]
        at org.elasticsearch.cluster.ClusterStateObserver$ObserverClusterStateListener.onTimeout(ClusterStateObserver.java:249) [elasticsearch-6.6.1.jar:6.6.1]
        at org.elasticsearch.cluster.service.ClusterApplierService$NotifyTimeout.run(ClusterApplierService.java:564) [elasticsearch-6.6.1.jar:6.6.1]
        at org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingRunnable.run(ThreadContext.java:660) [elasticsearch-6.6.1.jar:6.6.1]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_161]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_161]
        at java.lang.Thread.run(Thread.java:748) [?:1.8.0_161]
[2019-03-12T01:35:54,412][DEBUG][o.e.a.a.c.h.TransportClusterHealthAction] [data-1] no known master node, scheduling a retry
[2019-03-12T01:36:24,413][DEBUG][o.e.a.a.c.h.TransportClusterHealthAction] [data-1] timed out while retrying [cluster:monitor/health] after failure (timeout [30s])
[2019-03-12T01:36:24,413][WARN][r.suppressed] [data-1] path: /_cluster/health, params: {pretty=}
org.elasticsearch.discovery.MasterNotDiscoveredException: null
        at org.elasticsearch.action.support.master.TransportMasterNodeAction$AsyncSingleAction$4.onTimeout(TransportMasterNodeAction.java:262) [elasticsearch-6.6.1.jar:6.6.1]
        at org.elasticsearch.cluster.ClusterStateObserver$ContextPreservingListener.onTimeout(ClusterStateObserver.java:322) [elasticsearch-6.6.1.jar:6.6.1]
        at org.elasticsearch.cluster.ClusterStateObserver$ObserverClusterStateListener.onTimeout(ClusterStateObserver.java:249) [elasticsearch-6.6.1.jar:6.6.1]
        at org.elasticsearch.cluster.service.ClusterApplierService$NotifyTimeout.run(ClusterApplierService.java:564) [elasticsearch-6.6.1.jar:6.6.1]
        at org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingRunnable.run(ThreadContext.java:660) [elasticsearch-6.6.1.jar:6.6.1]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_161]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_161]
        at java.lang.Thread.run(Thread.java:748) [?:1.8.0_161]
```

---

<div class="post-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 9, 2019, 1:55am UTC](https://discuss.elastic.co/t/elastic-upgrade-from-6-2-3-to-6-6-1/171848/2 "2019-04-09T01:55:17Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.