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

Randomize MergeScheduler Settings #6194

Closed
s1monw opened this issue May 15, 2014 · 0 comments · Fixed by #6195
Closed

Randomize MergeScheduler Settings #6194

s1monw opened this issue May 15, 2014 · 0 comments · Fixed by #6195
Assignees
Labels
>test Issues or PRs that are addressing/adding tests v1.2.0 v2.0.0-beta1

Comments

@s1monw
Copy link
Contributor

s1monw commented May 15, 2014

ConcurrentMS has settings we should randomize in the index template just like LuceneTestCase does.

@s1monw s1monw self-assigned this May 15, 2014
s1monw added a commit to s1monw/elasticsearch that referenced this issue May 15, 2014
This commit adds randomization for:
 * `index.merge.scheduler.max_thread_count`
 * `index.merge.scheduler.max_merge_count`

This commit also moves to use
EsExecutors#boundedNumberOfProcessors(Settings) to default
configure the default `max_thread_count` for better reproducibility

Closes elastic#6194
s1monw added a commit that referenced this issue May 15, 2014
This commit adds randomization for:
 * `index.merge.scheduler.max_thread_count`
 * `index.merge.scheduler.max_merge_count`

This commit also moves to use
EsExecutors#boundedNumberOfProcessors(Settings) to default
configure the default `max_thread_count` for better reproducibility

Closes #6194
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
>test Issues or PRs that are addressing/adding tests v1.2.0 v2.0.0-beta1
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant