-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Make multiple settings dynamic for Merge on Flush #17495
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
base: main
Are you sure you want to change the base?
Conversation
6adb78d
to
bbb906f
Compare
❌ Gradle check result for bbb906f: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
❕ Gradle check result for cf7e975: UNSTABLE Please review all flaky tests that succeeded after retry and create an issue if one does not already exist to track the flaky failure. |
❌ Gradle check result for c77e86d: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
IndexActionIT.testAutoGenerateIdNoDuplicates #16576 |
c77e86d
to
cb4b0f1
Compare
❌ Gradle check result for cb4b0f1: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
❌ Gradle check result for 11587de: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
@msfroh Could you please continue to review in your spare time? Thank you very much. |
this.indexWriterConfig = getIndexWriterConfig(); | ||
writer = createWriter(indexWriterConfig); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just to confirm -- this change will only be "semi-dynamic".
That is, you need to restart the Engine
to recreate the IndexWriterConfig
and recreate the IndexWriter
, right? Is that intentional?
If you call the getIndexWriterConfig()
method on InternalEngine
, you get a copy of the LiveIndexWriterConfig
which affects the current IndexWriter
.
I think it might be better to call getIndexWriterConfig()
from the onSettingsChanged
method to update the LiveIndexWriterConfig
. What do you think, @kkewwei?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
By the change, we can dynamic change the settings without restarting the Engine.
…lush_merge_wait_time`, `index.merge_on_flush.policy`, `index.check_pending_flush.enabled` dynamic Signed-off-by: kkewwei <kewei.11@bytedance.com> Signed-off-by: kkewwei <kkewwei@163.com>
Signed-off-by: kkewwei <kewei.11@bytedance.com>
❌ Gradle check result for ab353dc: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
Description
index.merge_on_flush.enabled
index.merge_on_flush.max_full_flush_merge_wait_time
index.merge_on_flush.policy
index.check_pending_flush.enabled
.Related Issues
Resolves #10048
Check List
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.