X-PACK 5.6.3out put time out when collecting data how to change the time of collecting data. ES 5.6.3

[2017-11-01T07:46:50,053][ERROR][o.e.x.m.c.i.IndexStatsCollector] [xxxxxxxxxxxxxxxxxxxxx] collector [index-stats] timed out when collecting data
[2017-11-01T07:50:19,540][ERROR][o.e.x.m.c.i.IndexStatsCollector] [xxxxxxxxxxxxxxxxxxxxx] collector [index-stats] timed out when collecting data
[2017-11-01T12:38:50,004][ERROR][o.e.x.m.c.i.IndexStatsCollector] [xxxxxxxxxxxxxxxxxxxxx] collector [index-stats] timed out when collecting data
[2017-11-01T12:41:30,006][ERROR][o.e.x.m.c.i.IndexStatsCollector] [xxxxxxxxxxxxxxxxxxxxx] collector [index-stats] timed out when collecting data
[2017-11-01T12:42:00,021][ERROR][o.e.x.m.c.i.IndexStatsCollector] [xxxxxxxxxxxxxxxxxxxxx] collector [index-stats] timed out when collecting data
[2017-11-01T12:47:20,046][ERROR][o.e.x.m.c.i.IndexStatsCollector] [xxxxxxxxxxxxxxxxxxxxx] collector [index-stats] timed out when collecting data
[2017-11-01T12:50:10,042][ERROR][o.e.x.m.c.i.IndexStatsCollector] [xxxxxxxxxxxxxxxxxxxxx] collector [index-stats] timed out when collecting data
[2017-11-01T12:51:40,050][ERROR][o.e.x.m.c.i.IndexStatsCollector] [xxxxxxxxxxxxxxxxxxxxx] collector [index-stats] timed out when collecting data
[2017-11-01T12:54:10,055][ERROR][o.e.x.m.c.i.IndexStatsCollector] [xxxxxxxxxxxxxxxxxxxxx] collector [index-stats] timed out when collecting data
[2017-11-01T12:55:00,046][ERROR][o.e.x.m.c.i.IndexStatsCollector] [xxxxxxxxxxxxxxxxxxxxx] collector [index-stats] timed out when collecting data
[2017-11-01T12:56:40,089][ERROR][o.e.x.m.c.i.IndexStatsCollector] [xxxxxxxxxxxxxxxxxxxxx] collector [index-stats] timed out when collecting data
[2017-11-01T12:57:10,040][ERROR][o.e.x.m.c.i.IndexStatsCollector] [xxxxxxxxxxxxxxxxxxxxx] collector [index-stats] timed out when collecting data
[2017-11-01T12:58:20,055][ERROR][o.e.x.m.c.i.IndexStatsCollector] [xxxxxxxxxxxxxxxxxxxxx] collector [index-stats] timed out when collecting data

how to settings the x-pack monitoring time about es in es 5.6.3

There seems to be a problem collecting monitoring data. What does your configuration look like? What is the full output of the cluster stats API?

see the flow
@Christian_Dahlqvist
{
"_nodes" : {
"total" : 54,
"successful" : 54,
"failed" : 0
},
"cluster_name" : "C1",
"timestamp" : 1509597366660,
"status" : "green",
"indices" : {
"count" : 214,
"shards" : {
"total" : 21072,
"primaries" : 7041,
"replication" : 1.9927567106945037,
"index" : {
"shards" : {
"min" : 2,
"max" : 216,
"avg" : 98.46728971962617
},
"primaries" : {
"min" : 1,
"max" : 72,
"avg" : 32.901869158878505
},
"replication" : {
"min" : 1.0,
"max" : 2.0,
"avg" : 1.8738317757009346
}
}
},
"docs" : {
"count" : 91972939129,
"deleted" : 1043473
},
"store" : {
"size" : "66.2tb",
"size_in_bytes" : 72849634123756,
"throttle_time" : "0s",
"throttle_time_in_millis" : 0
},
"fielddata" : {
"memory_size" : "172.7kb",
"memory_size_in_bytes" : 176920,
"evictions" : 0
},
"query_cache" : {
"memory_size" : "395.3mb",
"memory_size_in_bytes" : 414568535,
"total_count" : 241111,
"hit_count" : 38071,
"miss_count" : 203040,
"cache_size" : 2154,
"cache_count" : 8148,
"evictions" : 5994
},
"completion" : {
"size" : "0b",
"size_in_bytes" : 0
},
"segments" : {
"count" : 136973,
"memory" : "140.3gb",
"memory_in_bytes" : 150748200794,
"terms_memory" : "81.9gb",
"terms_memory_in_bytes" : 88012542640,
"stored_fields_memory" : "44.9gb",
"stored_fields_memory_in_bytes" : 48293355704,
"term_vectors_memory" : "0b",
"term_vectors_memory_in_bytes" : 0,
"norms_memory" : "5.2mb",
"norms_memory_in_bytes" : 5465280,
"points_memory" : "13.2gb",
"points_memory_in_bytes" : 14177428374,
"doc_values_memory" : "247.3mb",
"doc_values_memory_in_bytes" : 259408796,
"index_writer_memory" : "49.2gb",
"index_writer_memory_in_bytes" : 52918402118,
"version_map_memory" : "11.4gb",
"version_map_memory_in_bytes" : 12337476905,
"fixed_bit_set" : "14.7gb",
"fixed_bit_set_memory_in_bytes" : 15844183936,
"max_unsafe_auto_id_timestamp" : 1509580805844,
"file_sizes" : { }
}
},
"nodes" : {
"count" : {
"total" : 54,
"data" : 36,
"coordinating_only" : 1,
"master" : 4,
"ingest" : 13
},
"versions" : [
"5.6.3"
],
"os" : {
"available_processors" : 2592,
"allocated_processors" : 2592,
"names" : [
{
"name" : "Linux",
"count" : 54
}
],
"mem" : {
"total" : "19.9tb",
"total_in_bytes" : 21895598039040,
"free" : "181.3gb",
"free_in_bytes" : 194705154048,
"used" : "19.7tb",
"used_in_bytes" : 21700892884992,
"free_percent" : 1,
"used_percent" : 99
}
},
"process" : {
"cpu" : {
"percent" : 419
},
"open_file_descriptors" : {
"min" : 2130,
"max" : 4086,
"avg" : 3372
}
},
"jvm" : {
"max_uptime" : "8d",
"max_uptime_in_millis" : 694623145,
"versions" : [
{
"version" : "1.8.0_121",
"vm_name" : "Java HotSpot(TM) 64-Bit Server VM",
"vm_version" : "25.121-b13",
"vm_vendor" : "Oracle Corporation",
"count" : 54
}
],
"mem" : {
"heap_used" : "939.7gb",
"heap_used_in_bytes" : 1009021155840,
"heap_max" : "1.6tb",
"heap_max_in_bytes" : 1855425871872
},
"threads" : 23611
},
"fs" : {
"total" : "38.8tb",
"total_in_bytes" : 42740078292992,
"free" : "25.6tb",
"free_in_bytes" : 28197911846912,
"available" : "25.6tb",
"available_in_bytes" : 28197911846912,
"spins" : "true"
},
"plugins" : [
{
"name" : "x-pack",
"version" : "5.6.3",
"description" : "Elasticsearch Expanded Pack Plugin",
"classname" : "org.elasticsearch.xpack.XPackPlugin",
"has_native_controller" : true
}
],
"network_types" : {
"transport_types" : {
"netty4" : 54
},
"http_types" : {
"netty4" : 54
}
}
}
}

with x-pack 5.6.3 how to change the time of collecting data
thanks/.

update

Is your cluster under heavy load? Do you see anything else in the logs across the cluster, e.g. long GC, that could impact collection latency?

not reload. in cluster log , only show the timeout about cro data
how to change the default timeout about cro data?

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.