# Elastic migrating from 6.8.8 to 7.10.2 in cluster mode : 1st node not starting until 2nd node starts in earlier version this was not the case **URL:** \ **Category:** Elasticsearch\ **Created:** [November 18, 2021, 2:40pm UTC](https://discuss.elastic.co/t/elastic-migrating-from-6-8-8-to-7-10-2-in-cluster-mode-1st-node-not-starting-until-2nd-node-starts-in-earlier-version-this-was-not-the-case/289610 "2021-11-18T14:40:06Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![cssingh](https://avatars.discourse-cdn.com/v4/letter/c/34f0e0/32.png) [@cssingh](https://discuss.elastic.co/u/cssingh)\ **Post date:** [November 18, 2021, 2:40pm UTC](https://discuss.elastic.co/t/elastic-migrating-from-6-8-8-to-7-10-2-in-cluster-mode-1st-node-not-starting-until-2nd-node-starts-in-earlier-version-this-was-not-the-case/289610/1 "2021-11-18T14:40:06Z")
I am making 3 node cluster. Below is my elastic.yml file cluster.name: SpectrumCluster node.name: node-1 cluster.initial\_master\_nodes: 10.2.107.14:9300,172.30.6.22:9300,172.30.5.255:9300 discovery.seed\_hosts: 10.2.107.14:9300,172.30.6.22:9300,172.30.5.255:9300 ## When I am starting all three node simultaneously then its working fine. But when I only start node 1 and dont start node 2 and node 3. Then even node 1 does not initialized and get below error ## [2021-11-18T08:49:28,273][DEBUG][o.e.d.PeerFinder] [node-1] Peer{transportAddress=172.30.5.255:9300, discoveryNode=null, peersRequestInFlight=false} connection failed org.elasticsearch.transport.ConnectTransportException: [172.30.5.255:9300] connect\_exception at org.elasticsearch.transport.TcpTransport$ChannelsConnectedListener.onFailure(TcpTransport.java:978) ~[elasticsearch-7.10.2.jar:7.10.2] at org.elasticsearch.action.ActionListener.lambda$toBiConsumer$2(ActionListener.java:198) ~[elasticsearch-7.10.2.jar:7.10.2] at org.elasticsearch.common.concurrent.CompletableContext.lambda$addListener$0(CompletableContext.java:42) ~[elasticsearch-core-7.10.2.jar:7.10.2] This was not the case with previous version 6.8.8 where 1st node was starting gracefully even if 2nd node is down. Is there way in 7.10.2 where we can start 1st node gracefully even if 2nd node down ---
**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\ **Post date:** [November 18, 2021, 2:49pm UTC](https://discuss.elastic.co/t/elastic-migrating-from-6-8-8-to-7-10-2-in-cluster-mode-1st-node-not-starting-until-2nd-node-starts-in-earlier-version-this-was-not-the-case/289610/2 "2021-11-18T14:49:28Z")
If your 6.8 cluster started up correctly with only 1 of 3 master eligible nodes present it was misconfigured and did not have `minimum_master_nodes` correctly set to `2`. This can lead to data loss. A 3 node cluster shoule always need a majority of master eligible nodes available in order to elect a master (in this case 2) and Elasticsearch 7.x now enforces this and no longer allows this quite common misconfiguration. Have a look at [these docs](https://www.elastic.co/guide/en/elasticsearch/reference/7.15/high-availability-cluster-small-clusters.html) for more information. ---
**Author:** ![cssingh](https://avatars.discourse-cdn.com/v4/letter/c/34f0e0/32.png) [@cssingh](https://discuss.elastic.co/u/cssingh)\ **Post date:** [November 18, 2021, 4:42pm UTC](https://discuss.elastic.co/t/elastic-migrating-from-6-8-8-to-7-10-2-in-cluster-mode-1st-node-not-starting-until-2nd-node-starts-in-earlier-version-this-was-not-the-case/289610/3 "2021-11-18T16:42:14Z")
I agree with you I might configured wrongly in 6.8 but our application is work in such a way that initially elastic 1st node should start and later it will join that other node 1 and node 2. As 7.x .x not allowing one node to start until it join 2nd node. I am looking for some hacky way so that it does not became blocker to me. ---
**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\ **Post date:** [November 18, 2021, 6:03pm UTC](https://discuss.elastic.co/t/elastic-migrating-from-6-8-8-to-7-10-2-in-cluster-mode-1st-node-not-starting-until-2nd-node-starts-in-earlier-version-this-was-not-the-case/289610/4 "2021-11-18T18:03:56Z")
There is as far as I know no hacky way around this. It was specifically designed to prevent this type of misconfiguration as it can cause silent data loss. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [December 16, 2021, 6:04pm UTC](https://discuss.elastic.co/t/elastic-migrating-from-6-8-8-to-7-10-2-in-cluster-mode-1st-node-not-starting-until-2nd-node-starts-in-earlier-version-this-was-not-the-case/289610/5 "2021-12-16T18:04:48Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.