Terminal blocked on [2020-01-24T15:37:25,971][INFO ][o.e.c.r.a.AllocationService] [LAPTOP-TRA6NOPS] Cluster health status changed from [RED] to [GREEN] (reason: [shards started [[.kibana_task_manager_1][0], [.kibana_1][0]]])

Hello, i just set up elastic search 7.5.2 on my computer and when runnning on the terminal comand elastic search on windows the terminal stops at this sentence:
[2020-01-24T15:37:25,971][INFO ][o.e.c.r.a.AllocationService] [LAPTOP-TRA6NOPS] Cluster health status changed from [RED] to [GREEN] (reason: [shards started [[.kibana_task_manager_1][0], [.kibana_1][0]]]).

In the meantime, i checked on a web page if ES was running and this is what i get:
with {
"name" : "LAPTOP-TRA6NOPS",
"cluster_name" : "elasticsearch",
"cluster_uuid" : "z7EChdjwQD2-j9s73mtUBA",
"version" : {
"number" : "7.5.2",
"build_flavor" : "default",
"build_type" : "zip",
"build_hash" : "8bec50e1e0ad29dad5653712cf3bb580cd1afcdf",
"build_date" : "2020-01-15T12:11:52.313576Z",
"build_snapshot" : false,
"lucene_version" : "8.3.0",
"minimum_wire_compatibility_version" : "6.8.0",
"minimum_index_compatibility_version" : "6.0.0-beta1"
"tagline" : "You Know, for Search"

When checking the indices with curl "localhost:9200/_cat/indices?v":

health status index uuid pri rep docs.count docs.deleted store.size pri.store.size
green open .kibana_task_manager_1 rfLqgEEWTQuWpFcxYr4xLg 1 0 0 0 283b 283b
green open .kibana_1 zDVSq4pGTjGKvtPEPXh9Bg 1 0 0 0 283b 283b

Can anyone can help me please?
Best regards
Pierre Jutard

Everything you describe is normal behaviour for a healthy, happy cluster. Can you explain what help you need?

Is it normal that when running ES, the terminal stays in the line i mentionned?


Because when runnning kibana in the meantime, it stays on this line:
log [15:19:49.007] [warning][migrations] Another Kibana instance appears to be migrating the index. Waiting for that migration to complete. If no other Kibana instance is attempting migrations, you can get past this message by deleting index .kibana_task_manager_1 and restarting Kibana.


The Kibana question looks like https://github.com/elastic/kibana/issues/25464 but it might be best to take that question to the Kibana forum instead. Everything looks good from the Elasticsearch side.

Alright thanks for your quick help david!

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