# Elasticsearch with warm nodes setup, kibana not yet ready **URL:** \ **Category:** Elasticsearch\ **Created:** [August 25, 2020, 4:20pm UTC](https://discuss.elastic.co/t/elasticsearch-with-warm-nodes-setup-kibana-not-yet-ready/246324 "2020-08-25T16:20:27Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![souji](https://avatars.discourse-cdn.com/v4/letter/s/65b543/32.png) [@souji](https://discuss.elastic.co/u/souji)\ **Post date:** [August 25, 2020, 4:20pm UTC](https://discuss.elastic.co/t/elasticsearch-with-warm-nodes-setup-kibana-not-yet-ready/246324/1 "2020-08-25T16:20:27Z")
Hi ```auto I setup the 7.8 version elastic search with 3 master, 3 client, 3 warm, 3 data nodes in amazon ec2 machines. ``` ```auto warm nodes: bootstrap.memory_lock: true node.name: ${HOSTNAME} action.destructive_requires_name: true indices.fielddata.cache.size: 1% # default is unbounded ``` ```auto Datanodes: bootstrap.memory_lock: true node.name: ${HOSTNAME} action.destructive_requires_name: true indices.fielddata.cache.size: 1% # default is unbounded ``` ```auto masternode: bootstrap.memory_lock: true node.name: ${HOSTNAME} action.destructive_requires_name: true indices.fielddata.cache.size: 1% # default is unbounded cluster.name: sfhlogging xpack.monitoring.enabled: true xpack.monitoring.collection.enabled: true path.data: /opt/elasticsearch/data path.logs: /var/log/elasticsearch xpack.security.enabled: false network.host: _ec2:privateIpv4_,localhost plugin.mandatory: discovery-ec2 cloud.node.auto_attributes: true cluster.routing.allocation.awareness.attributes: aws_availability_zone discovery: seed_providers: ec2 ec2.groups: sg-018af72f8a8e37ec4 ec2.host_type: private_ip ec2.tag.Cluster: dev-sfhlogging ec2.protocol: http # no need in HTTPS for internal AWS calls # manually set the endpoint because of auto-discovery issues # https://github.com/elastic/elasticsearch/issues/27464 ec2.endpoint: ec2.us-east-1.amazonaws.com node.master: true node.data: false node.ingest: false ``` ```auto clientnodes: bootstrap.memory_lock: true node.name: ${HOSTNAME} action.destructive_requires_name: true indices.fielddata.cache.size: 1% # default is unbounded cluster.name: sfhlogging xpack.monitoring.enabled: true xpack.monitoring.collection.enabled: true path.data: /opt/elasticsearch/data path.logs: /var/log/elasticsearch xpack.security.enabled: false network.host: _ec2:privateIpv4_,localhost plugin.mandatory: discovery-ec2 cloud.node.auto_attributes: true cluster.routing.allocation.awareness.attributes: aws_availability_zone discovery: seed_providers: ec2 ec2.groups: sg-018af72f8a8e37ec4 ec2.host_type: private_ip ec2.tag.Cluster: dev-sfhlogging ec2.protocol: http # no need in HTTPS for internal AWS calls # manually set the endpoint because of auto-discovery issues # https://github.com/elastic/elasticsearch/issues/27464 ec2.endpoint: ec2.us-east-1.amazonaws.com node.master: false node.data: false node.ingest: false ``` I am able to access elasticsearch, grafana, cerebro. I am getting Kibana not yet ready message. I mentioned the issue in below and got redirected here. > [@While spinning up elastic search on ec2 machines with warm nodes, kibana not yet ready message](https://discuss.elastic.co/t/while-spinning-up-elastic-search-on-ec2-machines-with-warm-nodes-kibana-not-yet-ready-message/246147): > > Hi, I am new self hosted elastic search, for poc I started spinning the self hosted es with data nodes, client nodes set up worked fine. I added the warm nodes I am seeing message kibana not yet ready. Elasticsearch.yml bootstrap.memory\_lock: true node.name: ${HOSTNAME} action.destructive\_requires\_name: true indices.fielddata.cache.size: 1% # default is unbounded cluster.name: sfhlogging xpack.monitoring.enabled: true xpack.monitoring.collection.enabled: true path.data: /opt/elasticsearch/da… ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [August 26, 2020, 4:32am UTC](https://discuss.elastic.co/t/elasticsearch-with-warm-nodes-setup-kibana-not-yet-ready/246324/2 "2020-08-26T04:32:34Z")
> [@souji](#): > > I am able to access elasticsearch, grafana, cerebro. I am getting Kibana not yet ready message. Is there anything in your Elasticsearch logs that mentions the `.kibana` index? What is the output from the `_cat/health?v` API? ---
**Author:** ![souji](https://avatars.discourse-cdn.com/v4/letter/s/65b543/32.png) [@souji](https://discuss.elastic.co/u/souji)\ **Post date:** [August 26, 2020, 3:37pm UTC](https://discuss.elastic.co/t/elasticsearch-with-warm-nodes-setup-kibana-not-yet-ready/246324/3 "2020-08-26T15:37:11Z")
> [@warkolm](#): > > \_cat/health?v ```auto epoch timestamp cluster status node.total node.data shards pri relo init unassign pending_tasks max_task_wait_time active_shards_percent 1598455778 15:29:38 sfhlogging red 6 0 0 0 0 0 7 0 - 0.0% ``` ```auto journalctl -u elasticsearch -- Logs begin at Fri 2020-07-24 00:11:43 UTC, end at Wed 2020-08-26 15:27:28 UTC. -- Aug 18 22:34:49 ip-10-128-44-63 systemd[1]: Starting Elasticsearch... Aug 18 22:36:12 ip-10-128-44-63 systemd[1]: Started Elasticsearch. ``` ```auto Aug 24 19:41:48 ip-10-128-44-63 kibana[16069]: {"type":"log","@timestamp":"2020-08-24T19:41:48Z","tags":["info","plugins","watcher"],"pid":16069,"message":"Your basic license does not support watcher. Please upgrade your license."} Aug 24 19:41:48 ip-10-128-44-63 kibana[16069]: {"type":"log","@timestamp":"2020-08-24T19:41:48Z","tags":["info","plugins","monitoring","monitoring","kibana-monitoring"],"pid":16069,"message":"Starting monitoring stats collection"} Aug 24 19:41:48 ip-10-128-44-63 kibana[16069]: {"type":"log","@timestamp":"2020-08-24T19:41:48Z","tags":["info","savedobjects-service"],"pid":16069,"message":"Starting saved objects migrations"} Aug 24 19:41:48 ip-10-128-44-63 kibana[16069]: {"type":"log","@timestamp":"2020-08-24T19:41:48Z","tags":["info","savedobjects-service"],"pid":16069,"message":"Creating index .kibana_task_manager_1."} Aug 24 19:41:48 ip-10-128-44-63 kibana[16069]: {"type":"log","@timestamp":"2020-08-24T19:41:48Z","tags":["info","savedobjects-service"],"pid":16069,"message":"Creating index .kibana_1."} Aug 24 19:42:18 ip-10-128-44-63 kibana[16069]: {"type":"log","@timestamp":"2020-08-24T19:42:18Z","tags":["warning","savedobjects-service"],"pid":16069,"message":"Unable to connect to Elasticsearch. Error: Request Timeout after 30000ms"} Aug 24 19:42:20 ip-10-128-44-63 kibana[16069]: {"type":"log","@timestamp":"2020-08-24T19:42:20Z","tags":["warning","savedobjects-service"],"pid":16069,"message":"Unable to connect to Elasticsearch. Error: [resource_already_exists_exception] index [.kibana_task_manager_1/XSCzMemTSza0BDR2fdGNtA] already exists, with { index_uuid=\"XSCzMemTSza0BDR2fdGNtA\" & index=\".kibana_task_manager_1\" }"} Aug 24 19:42:20 ip-10-128-44-63 kibana[16069]: {"type":"log","@timestamp":"2020-08-24T19:42:20Z","tags":["warning","savedobjects-service"],"pid":16069,"message":"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."} Aug 24 19:42:20 ip-10-128-44-63 kibana[16069]: {"type":"log","@timestamp":"2020-08-24T19:42:20Z","tags":["warning","savedobjects-service"],"pid":16069,"message":"Unable to connect to Elasticsearch. Error: [resource_already_exists_exception] index [.kibana_1/k_twoA66Shm9QWXZEsDibg] already exists, with { index_uuid=\"k_twoA66Shm9QWXZEsDibg\" & index=\".kibana_1\" }"} Aug 24 19:42:20 ip-10-128-44-63 kibana[16069]: {"type":"log","@timestamp":"2020-08-24T19:42:20Z","tags":["warning","savedobjects-service"],"pid":16069,"message":"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_1 and restarting Kibana."} ``` ```auto I stopped kibana and I deleted .kibana related indices. And restarted the kibana. ``` ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [September 23, 2020, 3:37pm UTC](https://discuss.elastic.co/t/elasticsearch-with-warm-nodes-setup-kibana-not-yet-ready/246324/4 "2020-09-23T15:37:17Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.