You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
mgodwan opened this issue
Sep 14, 2023
· 0 comments
· May be fixed by #17495
Labels
bugSomething isn't workingdiscussIssues intended to help drive brainstorming and decision makingIndexingIndexing, Bulk Indexing and anything related to indexing
Describe the bug
There are a few settings which were introduced in OpenSearch to provide more control over the merge on refresh/commit feature in Lucene. These settings are provided to IndexWriter during initialization but when the settings are updated through PUT <index>/_settings API, the updated settings are not used by IndexWriter until the index is closed and reopened.
Expected behavior
Since the dynamic behavior is not honored as expected, should this setting remain dynamic as this may confuse customers?
One of the advantage of keeping this dynamic may be that in case the shards are moved and restarted on another node, the setting will start to be honored without any need to explicitly close/open the index.
The text was updated successfully, but these errors were encountered:
bugSomething isn't workingdiscussIssues intended to help drive brainstorming and decision makingIndexingIndexing, Bulk Indexing and anything related to indexing
Describe the bug
There are a few settings which were introduced in OpenSearch to provide more control over the merge on refresh/commit feature in Lucene. These settings are provided to IndexWriter during initialization but when the settings are updated through
PUT <index>/_settings
API, the updated settings are not used by IndexWriter until the index is closed and reopened.Expected behavior
Since the dynamic behavior is not honored as expected, should this setting remain dynamic as this may confuse customers?
One of the advantage of keeping this dynamic may be that in case the shards are moved and restarted on another node, the setting will start to be honored without any need to explicitly close/open the index.
The text was updated successfully, but these errors were encountered: