Nhat Nguyen created LUCENE-10658:
------------------------------------
Summary: Merges should periodically check for abort
Key: LUCENE-10658
URL: https://issues.apache.org/jira/browse/LUCENE-10658
Project: Lucene - Core
Issue Type: Bug
Components: core/index
Affects Versions: 9.3
Reporter: Nhat Nguyen
Rolling back an IndexWriter without committing shouldn't take long (i.e., less
than several seconds), and Elasticsearch cluster coordination [relies
on|https://github.com/elastic/elasticsearch/issues/88055] this assumption. If
some merges are taking place, the rollback can take several minutes as merges
only check for abort when writing to files via
[MergeRateLimiter|https://github.com/apache/lucene/blob/3d7d85f245381f84c46c766119695a8645cde2b8/lucene/core/src/java/org/apache/lucene/index/MergeRateLimiter.java#L117-L119].
Merging a completion field, for example, can take a long time without touching
output files. Another reason merges should periodically check for abort is its
outputs will be discarded.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
