# Just Pushed: Expected nodes setting in gateway recovery **URL:** \ **Category:** Elasticsearch\ **Created:** [October 4, 2010, 2:21pm UTC](https://discuss.elastic.co/t/just-pushed-expected-nodes-setting-in-gateway-recovery/3405 "2010-10-04T14:21:50Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [October 4, 2010, 2:21pm UTC](https://discuss.elastic.co/t/just-pushed-expected-nodes-setting-in-gateway-recovery/3405/1 "2010-10-04T14:21:50Z")
Hi, Stemmed from a discussion I had with /ask a couple of mails back in the mailing list, I added the following feature: [http://github.com/elasticsearch/elasticsearch/issues/issue/404](http://github.com/elasticsearch/elasticsearch/issues/issue/404). Here is the desc in the feature: Currently, one can set gateway.recover\_after\_nodes setting to control after how many nodes within the cluster recovery will start. The gateway.recover\_after\_time sets the time to wait till recovery happens once the nodes are met. The missing setting in this scenario is the ability to set how many nodes are "expected" to be in the cluster. For example, setting: gateway: recover\_after\_nodes: 1 recover\_after\_time: 5m expected\_nodes: 2 In an expected 2 nodes cluster will cause recovery to start 5 minutes after the first node is up, but once there are 2 nodes in the cluster, recovery will begin immediately (without waiting). -shay.banon ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 4:18am UTC](https://discuss.elastic.co/t/just-pushed-expected-nodes-setting-in-gateway-recovery/3405/2 "2017-07-06T04:18:29Z")