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
Cluster State Update APIs (master node) to respect master_timeout better #3365
Labels
Comments
kimchy
added a commit
that referenced
this issue
Jul 22, 2013
Currently, the master node might be processing too many cluster state events, and then be blocked on waiting for its respective even to be processed. We can use the new cluster state update timeout support to use the master_timeout value and respect it. closes #3365
kimchy
added a commit
that referenced
this issue
Jul 22, 2013
Currently, the master node might be processing too many cluster state events, and then be blocked on waiting for its respective even to be processed. We can use the new cluster state update timeout support to use the master_timeout value and respect it. closes #3365
kimchy
added a commit
that referenced
this issue
Jul 22, 2013
also respect the timeout when trying to obtain the md lock relates #3365
kimchy
added a commit
that referenced
this issue
Jul 22, 2013
also respect the timeout when trying to obtain the md lock relates #3365
mute
pushed a commit
to mute/elasticsearch
that referenced
this issue
Jul 29, 2015
Currently, the master node might be processing too many cluster state events, and then be blocked on waiting for its respective even to be processed. We can use the new cluster state update timeout support to use the master_timeout value and respect it. closes elastic#3365
mute
pushed a commit
to mute/elasticsearch
that referenced
this issue
Jul 29, 2015
Currently, the master node might be processing too many cluster state events, and then be blocked on waiting for its respective even to be processed. We can use the new cluster state update timeout support to use the master_timeout value and respect it. closes elastic#3365
mute
pushed a commit
to mute/elasticsearch
that referenced
this issue
Jul 29, 2015
also respect the timeout when trying to obtain the md lock relates elastic#3365
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, the master node might be processing too many cluster state events, and then be blocked on waiting for its respective even to be processed. We can use the new cluster state update timeout support to use the master_timeout value and respect it.
The text was updated successfully, but these errors were encountered: