-
Notifications
You must be signed in to change notification settings - Fork 25.2k
[CI] IndexShardIT.testShardHasMemoryBufferOnTranslogRecover failure #37111
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
Labels
:Distributed Indexing/Engine
Anything around managing Lucene and the Translog in an open shard.
>test-failure
Triaged test failures from CI
Comments
Pinging @elastic/es-distributed |
s1monw
added a commit
to s1monw/elasticsearch
that referenced
this issue
Jan 4, 2019
We don't want two FSDirectories manage pending deletes separately and optimze file listing. This confuses IndexWriter and causes exceptions when files are deleted twice but are pending for deletion. This change move to using a NIOFS subclass that only delegates to MMAP for opening files all metadata and pending deletes are managed on top. Closes elastic#37111 Relates to elastic#36668
s1monw
added a commit
that referenced
this issue
Jan 5, 2019
We don't want two FSDirectories manage pending deletes separately and optimize file listing. This confuses IndexWriter and causes exceptions when files are deleted twice but are pending for deletion. This change move to using a NIOFS subclass that only delegates to MMAP for opening files all metadata and pending deletes are managed on top. Closes #37111 Relates to #36668
s1monw
added a commit
that referenced
this issue
Jan 5, 2019
We don't want two FSDirectories manage pending deletes separately and optimize file listing. This confuses IndexWriter and causes exceptions when files are deleted twice but are pending for deletion. This change move to using a NIOFS subclass that only delegates to MMAP for opening files all metadata and pending deletes are managed on top. Closes #37111 Relates to #36668
s1monw
added a commit
that referenced
this issue
Jun 12, 2019
We are still using `FileSwitchDirectory` in the case a user configures file based pre-load of mmaps. This is trappy for multiple reasons if the both directories used by `FileSwitchDirectory` point to the same filesystem directory. One issue is LUCENE-8835 that cause issues like #37111 - unless LUCENE-8835 isn't fixed we should not use it in elasticsearch. Instead we use a similar trick as we use for HybridFS and subclass mmap directory directly.
s1monw
added a commit
that referenced
this issue
Jun 12, 2019
We are still using `FileSwitchDirectory` in the case a user configures file based pre-load of mmaps. This is trappy for multiple reasons if the both directories used by `FileSwitchDirectory` point to the same filesystem directory. One issue is LUCENE-8835 that cause issues like #37111 - unless LUCENE-8835 isn't fixed we should not use it in elasticsearch. Instead we use a similar trick as we use for HybridFS and subclass mmap directory directly.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
:Distributed Indexing/Engine
Anything around managing Lucene and the Translog in an open shard.
>test-failure
Triaged test failures from CI
This reproduces on master:
The resulting error is:
FileSwitchDirectory
makes me think this is related to the addition ofhybridfs
, especially given that this only started failing yesterday afternoon, after #36668 was merged.The text was updated successfully, but these errors were encountered: