Closed benwtrent closed 1 week ago
Pinging @elastic/es-distributed (Team:Distributed)
I wanted to mark as blocker, but this is only in the lucene snapshot branch. My concern is that since that branch is long lived, we will forget about this :/
Actually, this "access from the wrong thread" is causing other tests to fail as well.
Pinging @elastic/es-search (Team:Search)
I've looked at the the test and it doesn't seem that we do anything non-standard in that test, RecoverySourceHandler
just closes opened resources, including MemorySegmentIndexInput
. I feel that the issue on Lucene's side in the implementation of MemorySegmentIndexInput
and how it uses the foreign-memaccess
API.
This issue has been closed because it has been open for too long with no activity.
Any muted tests that were associated with this issue have been unmuted.
If the tests begin failing again, a new issue will be opened, and they may be muted again.
CI Link
https://gradle-enterprise.elastic.co/s/b77e65ulskhjg
Repro line
./gradlew ":x-pack:plugin:frozen-indices:test" --tests "org.elasticsearch.index.engine.frozen.FrozenIndexShardTests.testRecoverFromFrozenPrimary" -Dtests.seed=2B3BFA46A5FBD920 -Dtests.locale=es-BO -Dtests.timezone=America/North_Dakota/New_Salem -Druntime.java=22
Does it reproduce?
Yes
Applicable branches
lucene_snapshot
Failure history
No response
Failure excerpt