# Rolling upgrade from 2.1.0 to 2.1.1 failed. please help to identify the probelm **URL:** \ **Category:** Elasticsearch\ **Created:** [December 25, 2015, 3:03am UTC](https://discuss.elastic.co/t/rolling-upgrade-from-2-1-0-to-2-1-1-failed-please-help-to-identify-the-probelm/37963 "2015-12-25T03:03:44Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![makeyang](https://avatars.discourse-cdn.com/v4/letter/m/f05b48/32.png) [@makeyang](https://discuss.elastic.co/u/makeyang)\ **Post date:** [December 25, 2015, 3:03am UTC](https://discuss.elastic.co/t/rolling-upgrade-from-2-1-0-to-2-1-1-failed-please-help-to-identify-the-probelm/37963/1 "2015-12-25T03:03:44Z")
stop one of them, upgrade it and restart it. below is discovery log and it seems the server can connected to all of other nodes. [2015-12-25 10:57:00,313][TRACE][discovery.zen.ping.unicast] [192.168.200.190] [119] received response from {#zen\_unicast\_3#}{192.168.200.196}{192.168.200.196:9390}: [ping\_response{node [{192.168.200.190}{QDVnI6x7RQ2u3T3zBsKQgw}{192.168.200.190}{192.168.200.190:9390}{max\_local\_storage\_nodes=20, master=false}], id[351], master [null], hasJoinedOnce [false], cluster\_name[21test]}, ping\_response{node [{192.168.200.190}{QDVnI6x7RQ2u3T3zBsKQgw}{192.168.200.190}{192.168.200.190:9390}{max\_local\_storage\_nodes=20, master=false}], id[352], master [null], hasJoinedOnce [false], cluster\_name[21test]}, ping\_response{node [{192.168.200.190}{QDVnI6x7RQ2u3T3zBsKQgw}{192.168.200.190}{192.168.200.190:9390}{max\_local\_storage\_nodes=20, master=false}], id[353], master [null], hasJoinedOnce [false], cluster\_name[21test]}, ping\_response{node [{192.168.200.190}{QDVnI6x7RQ2u3T3zBsKQgw}{192.168.200.190}{192.168.200.190:9390}{max\_local\_storage\_nodes=20, master=false}], id[354], master [null], hasJoinedOnce [false], cluster\_name[21test]}, ping\_response{node [{192.168.200.190}{QDVnI6x7RQ2u3T3zBsKQgw}{192.168.200.190}{192.168.200.190:9390}{max\_local\_storage\_nodes=20, master=false}], id[355], master [null], hasJoinedOnce [false], cluster\_name[21test]}, ping\_response{node [{192.168.200.190}{QDVnI6x7RQ2u3T3zBsKQgw}{192.168.200.190}{192.168.200.190:9390}{max\_local\_storage\_nodes=20, master=false}], id[356], master [null], hasJoinedOnce [false], cluster\_name[21test]}, ping\_response{node [{192.168.200.196}{FzxGsQclQ22izuwoi-wTpQ}{192.168.200.196}{192.168.200.196:9390}], id[1081], master [{192.168.200.196}{FzxGsQclQ22izuwoi-wTpQ}{192.168.200.196}{192.168.200.196:9390}], hasJoinedOnce [true], cluster\_name[21test]}] but it keep logging: [DEBUG][action.admin.indices.create] [192.168.200.190] no known master node, scheduling a retry ---
**Author:** ![makeyang](https://avatars.discourse-cdn.com/v4/letter/m/f05b48/32.png) [@makeyang](https://discuss.elastic.co/u/makeyang)\ **Post date:** [December 25, 2015, 3:05am UTC](https://discuss.elastic.co/t/rolling-upgrade-from-2-1-0-to-2-1-1-failed-please-help-to-identify-the-probelm/37963/2 "2015-12-25T03:05:46Z")
cluster toplogy: 4 nodes, three of them are master&data node, the other is data node. the config is below: [cluster.name](http://cluster.name): 21test [node.name](http://node.name): 192.168.200.190 node.master: false node.data: true path.data: /export/Data/elasticsearch/es219290 path.logs: /export/Logs/elasticsearch/es219290 path.plugins: /export/plugins/elasticsearch/es219290 bootstrap.mlockall: true network.host: 192.168.200.190 http.port: 9290 transport.tcp.port: 9390 discovery.zen.ping.unicast.hosts: ["192.168.200.191:9390","192.168.200.192:9390","192.168.200.196:9390"] discovery.zen.minimum\_master\_nodes: 3 indices.memory.index\_buffer\_size: 20% script.engine.groovy.inline.aggs: on index.translog.sync\_interval: 30s index.translog.durability: async index.refresh\_interval: 180s index.max\_merged\_segment: 1g node.max\_local\_storage\_nodes: 20 ---
**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:** [December 25, 2015, 10:07pm UTC](https://discuss.elastic.co/t/rolling-upgrade-from-2-1-0-to-2-1-1-failed-please-help-to-identify-the-probelm/37963/3 "2015-12-25T22:07:13Z")
> [@makeyang](#): > > discovery.zen.minimum\_master\_nodes: 3 If you have 3 master eligible nodes in the cluster, minimum\_master\_nodes should be set to 2, not 3. 3 would however be the correct setting if all 4 nodes were master eligible. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 5, 2017, 11:28pm UTC](https://discuss.elastic.co/t/rolling-upgrade-from-2-1-0-to-2-1-1-failed-please-help-to-identify-the-probelm/37963/4 "2017-07-05T23:28:35Z")