-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
[Feature Request] Separation of Merges #12726
Comments
[Triage - attendees 1 2 3 4 5 6] |
My bad, i forgot to remove the label. Thanks for removing it! Also, I've added some details here which was definitely missing earlier. This will get more details as we progress further and bring more clarity after exploration |
Is your feature request related to a problem? Please describe
Most of the codebase for Opensearch today exists as a Monolith in :server hosting code related to various background tasks, including Merge. Segment Merges are run from within the Engine and are triggered only on the data node where a particular Shard is assigned.
It would be an anti-pattern to build entire :sever jar and host on Offline Node, which is just responsible for performing Merges.
Current Merge Flow
Once IndexWriter triggers a merge, following Merge Component come into play
Describe the solution you'd like
While maintaining the Status Quo, we need a way to separate out individual components like “Merge” and be able to run separately on Offline Fleet.
Related component
Storage
Describe alternatives you've considered
No response
Additional context
#12361
#12725
#5910
The text was updated successfully, but these errors were encountered: