Add wait no initializing shards #26578
Conversation
|
Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually? |
|
Sure, this looks good so far. It still needs adaptions on the REST layer, tests and all that. |
| @@ -221,6 +224,10 @@ private boolean prepareResponse(final ClusterHealthRequest request, final Cluste | |||
| if (request.waitForNoRelocatingShards() && response.getRelocatingShards() == 0) { | |||
| waitForCounter++; | |||
| } | |||
| if (request.waitForNoInitializingShards() && !clusterState.getRoutingNodes().hasInactivePrimaries() && | |||
There was a problem hiding this comment.
you can use the same approach as for the waitForNoRelocatingShards a few lines above, i.e. request.waitForNoInitializingShards() && response.getInitializingShards() == 0
|
@matarrese any updates on this? I'll close the PR due to inactivity. Please let us know if you still want to work on this. |
|
Hi @ywelsch , happy to go back working on this. Is it possible to open the pull request? |
|
This was addressed in #27489. |
Hello, I don't know if @Hogusong is still working on this issue, so I decided to bring it up and send you a pull request. It is not intended to be ready to be tested, as it is failing some tests. I am just asking if it's possible to have a review and understand if it goes in the right direction. If other people working on this, please feel free to close it.
Closes #25623