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.

Sign up for GitHub

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

Jump to bottom

Thread pool size should not be a global (cluster update API) setting #15866

Closed
mikemccand opened this issue Jan 8, 2016 · 1 comment
Closed

Thread pool size should not be a global (cluster update API) setting #15866

mikemccand opened this issue Jan 8, 2016 · 1 comment
Assignees
@jasontedor
Labels
:Core/Infra/Core Core issues without another label >enhancement good first issue low hanging fruit

Comments

@mikemccand
Copy link
Contributor

Spinoff from #15585

Today you can e.g. set threadpool.bulk.size across the cluster, but this is dangerous, because it really should be node level setting instead (maybe you have "hot" nodes with many cores, and "cold" nodes with fewer cores).
@mikemccand mikemccand added :Core/Infra/Core Core issues without another label v5.0.0-alpha1 labels Jan 8, 2016
@clintongormley clintongormley added the good first issue low hanging fruit label May 3, 2016
@jasontedor jasontedor self-assigned this Jun 2, 2016
@jasontedor jasontedor mentioned this issue Jun 2, 2016
Open
7 tasks
@jasontedor
Copy link
Member

Closed in favor of #18613

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jasontedor jasontedor

Labels
:Core/Infra/Core Core issues without another label >enhancement good first issue low hanging fruit
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@clintongormley @mikemccand @jasontedor