-
Notifications
You must be signed in to change notification settings - Fork 25.2k
No core value reported for scaling thread pool type #29113
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
Comments
We report the same thread pool info for all thread pools. That is, all thread pools, regardless of type, report a |
So the thing is that in settings part you say |
Yeah, I am sorry for the confusion, it is something that has bothered be that we use this single thread pool info class to represent the underlying information regardless of the thread pool type. I looked into it once before and walked away because I did not see a clean way to refactor this. |
On second thought, I think we can change this on the display side only without having to endure a wider refactoring. |
Pinging @elastic/es-core-infra |
I opened #29123. Now we get: {
"_nodes" : {
"total" : 1,
"successful" : 1,
"failed" : 0
},
"cluster_name" : "elasticsearch",
"nodes" : {
"TQM_SNpDSsaYROQly2-KgQ" : {
"name" : "TQM_SNp",
"transport_address" : "127.0.0.1:9300",
"host" : "127.0.0.1",
"ip" : "127.0.0.1",
"version" : "7.0.0-alpha1",
"build_hash" : "2f21dc7",
"roles" : [
"master",
"data",
"ingest"
],
"thread_pool" : {
"force_merge" : {
"type" : "fixed",
"size" : 1,
"queue_size" : -1
},
"fetch_shard_started" : {
"type" : "scaling",
"core" : 1,
"max" : 16,
"keep_alive" : "5m",
"queue_size" : -1
},
"listener" : {
"type" : "fixed",
"size" : 4,
"queue_size" : -1
},
"index" : {
"type" : "fixed",
"size" : 8,
"queue_size" : 200
},
"refresh" : {
"type" : "scaling",
"core" : 1,
"max" : 4,
"keep_alive" : "5m",
"queue_size" : -1
},
"generic" : {
"type" : "scaling",
"core" : 4,
"max" : 128,
"keep_alive" : "30s",
"queue_size" : -1
},
"warmer" : {
"type" : "scaling",
"core" : 1,
"max" : 4,
"keep_alive" : "5m",
"queue_size" : -1
},
"search" : {
"type" : "fixed_auto_queue_size",
"size" : 13,
"queue_size" : 1000
},
"flush" : {
"type" : "scaling",
"core" : 1,
"max" : 4,
"keep_alive" : "5m",
"queue_size" : -1
},
"fetch_shard_store" : {
"type" : "scaling",
"core" : 1,
"max" : 16,
"keep_alive" : "5m",
"queue_size" : -1
},
"management" : {
"type" : "scaling",
"core" : 1,
"max" : 5,
"keep_alive" : "5m",
"queue_size" : -1
},
"get" : {
"type" : "fixed",
"size" : 8,
"queue_size" : 1000
},
"bulk" : {
"type" : "fixed",
"size" : 8,
"queue_size" : 200
},
"snapshot" : {
"type" : "scaling",
"core" : 1,
"max" : 4,
"keep_alive" : "5m",
"queue_size" : -1
}
}
}
}
} |
Elasticsearch version (
bin/elasticsearch --version
): >= 5.xDescription of the problem including expected versus actual behavior:
This is probably documentation related issue. There are a few places where the documentation mentions that the scaling thread pool uses the
core
value for the minimum value. For example:core
andmax
parameters"min
tocore
"However, in the output I see only
min
value where thecore
should be expected:The text was updated successfully, but these errors were encountered: