Skip to content
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

Never throttle creation of compound files. #12070

Merged
merged 2 commits into from
Jan 11, 2023

Conversation

jpountz
Copy link
Contributor

@jpountz jpountz commented Jan 10, 2023

ConcurrentMergeScheduler uses the rate at which a merge writes bytes as a proxy for CPU usage, in order to prevent merging from disrupting searches too much. However creating compound files are lightweight CPU-wise and do not need throttling.

Closes #12068

`ConcurrentMergeScheduler` uses the rate at which a merge writes bytes as a
proxy for CPU usage, in order to prevent merging from disrupting searches too
much. However creating compound files are lightweight CPU-wise and do not need
throttling.

Closes apache#12068
Copy link
Member

@rmuir rmuir left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

makes sense to me. I think its an oversight that CFS/CFE was going thru this throttled directory.

jpountz added a commit to jpountz/elasticsearch that referenced this pull request Jan 10, 2023
This reverts commit 378cefe.

@DJRickyB observed an increase in merge throttling after elastic#92659 was merged,
which is due to the fact that creation of CFS files is throttled using the same
mechanism as merges. However after checking on the Lucene side, it does not
look like throttling the creation of CFS files is intentional:
apache/lucene#12070. I will re-introduce this change when we upgrade to a new
Lucene version that no longer throttles creation of CFS files.
@jpountz jpountz merged commit a8ef03d into apache:main Jan 11, 2023
@jpountz jpountz deleted the cfs_merge_throttling branch January 11, 2023 08:57
@jpountz jpountz added this to the 9.5.0 milestone Jan 11, 2023
jpountz added a commit that referenced this pull request Jan 11, 2023
`ConcurrentMergeScheduler` uses the rate at which a merge writes bytes as a
proxy for CPU usage, in order to prevent merging from disrupting searches too
much. However creating compound files are lightweight CPU-wise and do not need
throttling.

Closes #12068
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Is it right to throttle the creation of compound files?
2 participants