Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add timeouts to refresh, flush and optimize apis #9997

Closed
martijnvg opened this issue Mar 5, 2015 · 2 comments
Closed

Add timeouts to refresh, flush and optimize apis #9997

martijnvg opened this issue Mar 5, 2015 · 2 comments
Labels
:Data Management/Indices APIs APIs to create and manage indices and templates >enhancement help wanted adoptme

Comments

@martijnvg
Copy link
Member

At the moment when the refresh, flush and optimize apis are executed and there is a cluster block (for example no master block) then these apis fail immediately. It would be nicer if those apis would wait for a defined timeout period and see if the cluster block is resolved within that period. This should be similar in how deal with cluster blocks in the index, update and delete apis (which have a timeout parameter).

@martijnvg martijnvg added >enhancement :Core/Infra/Core Core issues without another label labels Mar 5, 2015
@clintongormley clintongormley added the help wanted adoptme label Mar 9, 2015
@clintongormley
Copy link

These requests do now wait instead of failing immediately, but the timeout is not configurable.

@clintongormley clintongormley added :Data Management/Indices APIs APIs to create and manage indices and templates and removed :Core/Infra/Core Core issues without another label labels Dec 5, 2015
@clintongormley clintongormley changed the title Refresh, flush and optimize apis should wait on a clusterblock Add timeouts to refresh, flush and optimize apis Nov 26, 2016
@hub-cap
Copy link
Contributor

hub-cap commented Mar 21, 2018

This feature request is an interesting idea but since its opening we have not seen enough feedback that it is a feature we should pursue. We prefer to close this issue as a clear indication that we are not going to work on this at this time. We are always open to reconsidering this in the future based on compelling feedback; despite this issue being closed please feel free to leave feedback on the proposal (including +1s).

@hub-cap hub-cap closed this as completed Mar 21, 2018
fixmebot bot referenced this issue in VectorXz/elasticsearch Apr 22, 2021
fixmebot bot referenced this issue in VectorXz/elasticsearch May 28, 2021
fixmebot bot referenced this issue in VectorXz/elasticsearch Aug 4, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Data Management/Indices APIs APIs to create and manage indices and templates >enhancement help wanted adoptme
Projects
None yet
Development

No branches or pull requests

3 participants