ELK data note index creating taking to much time


(sateesh) #1

Hi,

After restarting elastic search data node, it is taking to much time for creating index, in kibana dash board getting request time out.

almost 28hr over still shows red.
{
"cluster_name" : "elk-stack",
"status" : "red",
"timed_out" : false,
"number_of_nodes" : 8,
"number_of_data_nodes" : 3,
"active_primary_shards" : 791,
"active_shards" : 978,
"relocating_shards" : 0,
"initializing_shards" : 4,
"unassigned_shards" : 820,
"delayed_unassigned_shards" : 0,
"number_of_pending_tasks" : 0,
"number_of_in_flight_fetch" : 854,
"task_max_waiting_in_queue_millis" : 0,
"active_shards_percent_as_number" : 54.27302996670367

Regards
Sateesh


(David Pilato) #2

Which version?
Probably too many shards for only 3 data nodes which creates very big cluster state.


(sateesh) #3

Version -lucene_version" : "5.5.4


(David Pilato) #4

Elasticsearch version?


(sateesh) #5

Elastic search -
"version" : {
"number" : "2.4.6",


(David Pilato) #6

Could you run:

GET /_cat/nodes?v&h=*

(sateesh) #7

I am seeing below error in logs and status shows red.

nested: ElasticsearchTimeoutException[no activity after [30m]];
at org.elasticsearch.indices.recovery.RecoveriesCollection$RecoveryMonitor.doRun(RecoveriesCollection.java:235)
at org.elasticsearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:37)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: ElasticsearchTimeoutException[no activity after [30m]]
... 5 more


(David Pilato) #8

Is this the output of what I asked for?

GET /_cat/nodes?v&h=*

Do you mean this command is failing?


(sateesh) #9

it failed to fetch the data, even after install GET package.

-bash: GET: command not found

One information required, below query is health check output
"status" : "red",
"timed_out" : false,
"number_of_nodes" : 8,
"number_of_data_nodes" : 3,
"active_primary_shards" : 883,
"active_shards" : 1131,
"relocating_shards" : 0,
"initializing_shards" : 6,
"unassigned_shards" : 685,
"delayed_unassigned_shards" : 0,
"number_of_pending_tasks" : 0,
"number_of_in_flight_fetch" : 543,
"task_max_waiting_in_queue_millis" : 0,
"active_shards_percent_as_number" : 62.07464324917673

after how much percentage it shows red to yellow and green


(David Pilato) #10

It's a shortcut for the equivalent curl command.
Please run the curl command.


(system) #11

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