Skip to content

Revert "Use read/write engine lock to guard operations against resets" #125915

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Mar 31, 2025
Merged

Revert "Use read/write engine lock to guard operations against resets" #125915

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion server/src/main/java/org/elasticsearch/index/engine/Engine.java
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2371,7 +2371,7 @@ public record FlushResult(boolean flushPerformed, long generation) {
}

/**
* Ensures the engine is in a state that it can be closed by a call to {@link IndexShard#resetEngine(Consumer<Engine>)}.
* Ensures the engine is in a state that it can be closed by a call to {@link IndexShard#resetEngine()}.
*
* In general, resetting the engine should be done with care, to consider any
* in-progress operations and listeners (e.g., primary term and generation listeners).
Expand Down
Loading