Race condition between flushing and closing index #3909
Closed
Comments
This happens when you rotate the active write index and after that close the previous write index. The |
bernd
added a commit
that referenced
this issue
Jun 22, 2017
Also add that check to other jobs that could fail if an index is already closed. Fixes #3909
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The effects are probably harmless (because I guess closing an index will internally flush any changes to it anyway), but the error looks dangerous:
The text was updated successfully, but these errors were encountered: