Skip to content

Switch back to ConcurrentMergeScheduler #5818

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

Merged
merged 2 commits into from
Apr 15, 2014
Merged

Conversation

s1monw
Copy link
Contributor

@s1monw s1monw commented Apr 15, 2014

Load tests showed that SerialMS has problems to keep up with
the merges under high load. We should switch back to CMS
until we have a better story to balance merge
threads / efforts across shards on a single node.

Closes #5817

@kimchy
Copy link
Member

kimchy commented Apr 15, 2014

LGTM

s1monw added 2 commits April 15, 2014 16:42
Load tests showed that SerialMS has problems to keep up with
the merges under high load. We should switch back to CMS
until we have a better story to balance merge
threads / efforts across shards on a single node.

Closes elastic#5817
@s1monw s1monw merged commit 9898eed into elastic:master Apr 15, 2014
@s1monw s1monw deleted the issues/5817 branch April 15, 2014 14:59
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.

Switch back to ConcurrentMergeScheduler as the default
2 participants