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

Possible failure when using TransportClient (with sniffing) #923

Closed
kimchy opened this issue May 10, 2011 · 0 comments

Comments

@kimchy
Copy link
Member

commented May 10, 2011

Possible failure when using TransportClient (with sniffing) when failing to connect to sniffed nodes (removing from a set that is being iterated on).

@kimchy kimchy closed this in 176f359 May 10, 2011

ofavre pushed a commit to yakaz/elasticsearch that referenced this issue Jul 18, 2011
mute pushed a commit to mute/elasticsearch that referenced this issue Jul 29, 2015
martijnvg added a commit to martijnvg/elasticsearch that referenced this issue Jan 31, 2018
Persistent Tasks: require correct allocation id for status updates (e…
…lastic#923)

In order to prevent tasks state updates by stale executors, this commit adds a check for correct allocation id during status update operation.
martijnvg added a commit that referenced this issue Feb 5, 2018
Persistent Tasks: require correct allocation id for status updates (#923
)

In order to prevent tasks state updates by stale executors, this commit adds a check for correct allocation id during status update operation.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant
You can’t perform that action at this time.