-
Notifications
You must be signed in to change notification settings - Fork 24.6k
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
Internal: Wait until engine has started up when acquiring searcher #7455
Labels
Comments
s1monw
added a commit
to s1monw/elasticsearch
that referenced
this issue
Aug 26, 2014
Today we have a small window where a searcher can be acquired but the engine is in the state of starting up. This causes a NPE triggering a shard failure if we are fast enough. This commit fixes this situation gracefully. Closes elastic#7455
s1monw
added a commit
that referenced
this issue
Aug 26, 2014
Today we have a small window where a searcher can be acquired but the engine is in the state of starting up. This causes a NPE triggering a shard failure if we are fast enough. This commit fixes this situation gracefully. Closes #7455
s1monw
added a commit
that referenced
this issue
Aug 26, 2014
Today we have a small window where a searcher can be acquired but the engine is in the state of starting up. This causes a NPE triggering a shard failure if we are fast enough. This commit fixes this situation gracefully. Closes #7455
spinscale
changed the title
Node startup: NPE triggers failed shard
Engine: Wait until engine is started up when acquiring searcher
Aug 27, 2014
clintongormley
changed the title
Engine: Wait until engine is started up when acquiring searcher
Internal: Wait until engine has started up when acquiring searcher
Sep 8, 2014
s1monw
added a commit
that referenced
this issue
Sep 8, 2014
Today we have a small window where a searcher can be acquired but the engine is in the state of starting up. This causes a NPE triggering a shard failure if we are fast enough. This commit fixes this situation gracefully. Closes #7455
mute
pushed a commit
to mute/elasticsearch
that referenced
this issue
Jul 29, 2015
Today we have a small window where a searcher can be acquired but the engine is in the state of starting up. This causes a NPE triggering a shard failure if we are fast enough. This commit fixes this situation gracefully. Closes elastic#7455
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This exception happened after a node restart and a delete-by-query hits the node immediately. Happened on 1.3.1
The text was updated successfully, but these errors were encountered: