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

Bulk process of shard started/failed should not execute on already processed events #5061

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

Bulk process of shard started/failed should not execute on already processed events #5061

kimchy opened this issue Feb 10, 2014 · 0 comments
Labels
:Distributed/Distributed A catch all label for anything in the Distributed Area. If you aren't sure, use this one. >enhancement v0.90.12 v1.0.0 v1.1.0 v2.0.0-beta1

Comments

@kimchy
Copy link
Member

kimchy commented Feb 10, 2014

This can lead to a starvation, where each new shard started event will cause the full queue to be drained, and not allowing other URGENT events to get in.
@kimchy kimchy closed this as completed in 152edd1 Feb 10, 2014
kimchy added a commit that referenced this issue Feb 10, 2014
@kimchy
Bulk process of shard started/failed should not execute on already pr…
a881d89 
…ocessed events

closes #5061
kimchy added a commit that referenced this issue Feb 10, 2014
@kimchy
Bulk process of shard started/failed should not execute on already pr…
3379e4f 
…ocessed events

closes #5061
kimchy added a commit that referenced this issue Feb 10, 2014
@kimchy
Bulk process of shard started/failed should not execute on already pr…
83b09d2 
…ocessed events

closes #5061
mute pushed a commit to mute/elasticsearch that referenced this issue Jul 29, 2015
@kimchy
Bulk process of shard started/failed should not execute on already pr…
2e0165b 
…ocessed events

closes elastic#5061
mute pushed a commit to mute/elasticsearch that referenced this issue Jul 29, 2015
@kimchy
Bulk process of shard started/failed should not execute on already pr…
2b65064 
…ocessed events

closes elastic#5061
@clintongormley clintongormley added :Distributed/Distributed A catch all label for anything in the Distributed Area. If you aren't sure, use this one. and removed :Cluster labels Feb 13, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
:Distributed/Distributed A catch all label for anything in the Distributed Area. If you aren't sure, use this one. >enhancement v0.90.12 v1.0.0 v1.1.0 v2.0.0-beta1
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@kimchy @clintongormley