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.

Sign up for GitHub

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

Jump to bottom

Zen Disco join/leave should have higher than URGENT priority #5062

Closed
kimchy opened this issue Feb 10, 2014 · 5 comments
Closed

Zen Disco join/leave should have higher than URGENT priority #5062

kimchy opened this issue Feb 10, 2014 · 5 comments
Labels
>enhancement v1.1.0 v2.0.0-beta1

Comments

@kimchy
Copy link
Member

kimchy commented Feb 10, 2014

When processing node joining and leaving, we should have the utmost priority for it, higher than URGENT. We need another level of fine grained events.
@kimchy
Copy link
Member Author

kimchy commented Feb 10, 2014

probably also cluster update settings, and reroute

@bleskes
Copy link
Contributor

bleskes commented Feb 10, 2014

+1 on these extra 2. Should apply to all manually initiated API calls. DevOps need to be able to intervene,even/especially when the queues are full.

@uboness
Copy link
Contributor

uboness commented Feb 10, 2014

I can have a look at it.. not sure we should push it to 1.0.0 though

@s1monw
Copy link
Contributor

s1monw commented Feb 10, 2014

I'd also want to move this to 1.1 though - this is really something that should bake in

@kevinkluge
Copy link
Member

Simon, Uri and I discussed -- pushing to 1.1.

@kevinkluge kevinkluge removed the v1.0.0 label Feb 11, 2014
@javanna javanna removed the v0.90.12 label Feb 11, 2014
@uboness uboness mentioned this issue Feb 12, 2014
Closed
uboness added a commit that referenced this issue Mar 6, 2014
@uboness
Introduced a new IMMEDIATE priority - higher than URGENT
67cdda2 
* applied to cluster update settings, reroute, node join/leave events, node failure

Closes #5062
@uboness uboness closed this as completed in da938a6 Mar 6, 2014
dakrone added a commit that referenced this issue Jan 6, 2020
@dakrone
[7.x] Add aditional logging for ILM history store tests (#5062… (#50678)
552edd8 
* Add aditional logging for ILM history store tests (#50624)

These tests use the same index name, making it hard to read logs when
diagnosing the failures. Additionally more information about the current
state of the index could be retrieved when failing.

This changes these two things in the hope of capturing more data about
why this fails on some CI nodes but not others.

Relates to #50353
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
>enhancement v1.1.0 v2.0.0-beta1
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Introduced a new IMMEDIATE priority - higher than URGENT
7 participants
@kimchy @uboness @kevinkluge @spinscale @javanna @s1monw @bleskes