# ES Cluster stopped working **URL:** \ **Category:** Elasticsearch\ **Created:** [November 7, 2024, 4:01am UTC](https://discuss.elastic.co/t/es-cluster-stopped-working/370147 "2024-11-07T04:01:40Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![Techiebee](https://avatars.discourse-cdn.com/v4/letter/t/67e7ee/32.png) [@Techiebee](https://discuss.elastic.co/u/Techiebee)\ **Post date:** [November 7, 2024, 4:01am UTC](https://discuss.elastic.co/t/es-cluster-stopped-working/370147/1 "2024-11-07T04:01:41Z")
My ES cluster is a 3 node setup cluster running on ES 7.17 , lately its giving alot of issues, So i had to made a single node setup removing the nodes and re-indexed from the application console. Now if I revert back to the cluster from single node what should I do to re-enable my cluster back and how to make sure the new nodes autojoins the cluster? Also I could see the health of single node as yellow and there are some recoveries not sure how to assign them back curl -k -X GET "[https://localhost:9200/\_cat/health](https://localhost:9200/_cat/health)" 1730951810 03:56:50 Prod yellow 1 1 9 9 0 0 7 0 - 56.3% curl -k -X GET "[https://localhost:9200/\_cat/recovery?pretty](https://localhost:9200/_cat/recovery?pretty)" defect 0 207ms empty\_store done n/a n/a 10.X.X.X xxx.xxx.com.au n/a n/a 0 0 0.0% 0 0 0 0.0% 0 0 0 100.0% build 0 85ms empty\_store done n/a n/a 10.X.X.X xxx.xxx.com.au n/a n/a 0 0 0.0% 0 0 0 0.0% 0 0 0 100.0% testsuite 0 69ms empty\_store done n/a n/a 10.X.X.X xxx.xxx.com.au n/a n/a 0 0 0.0% 0 0 0 0.0% 0 0 0 100.0% release 0 127ms empty\_store done n/a n/a 10.X.X.X xxx.xxx.com.au n/a n/a 0 0 0.0% 0 0 0 0.0% 0 0 0 100.0% requirement 0 168ms empty\_store done n/a n/a 10.X.X.X xxx.xxx.com.au n/a n/a 0 0 0.0% 0 0 0 0.0% 0 0 0 100.0% testcaserun 0 77ms empty\_store done n/a n/a 10.X.X.X xxx.xxx.com.au n/a n/a 0 0 0.0% 0 0 0 0.0% 0 0 0 100.0% testcase 0 98ms empty\_store done n/a n/a 10.X.X.X xxx.xxx.com.au n/a n/a 0 0 0.0% 0 0 0 0.0% 0 0 0 100.0% please help ---
**Author:** ![carly.richmond](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/carly.richmond/32/104935_2.png) [@carly.richmond](https://discuss.elastic.co/u/carly.richmond)\ **Post date:** [November 7, 2024, 3:42pm UTC](https://discuss.elastic.co/t/es-cluster-stopped-working/370147/2 "2024-11-07T15:42:34Z")
Hi @Techiebee, A yellow cluster status suggests you have unassigned replicas. Have you followed the [troubleshooting steps in the documentation](https://www.elastic.co/guide/en/elasticsearch/reference/current/red-yellow-cluster-status.html)? Can you check the unassigned shards using the commands [documented here](https://www.elastic.co/guide/en/elasticsearch/reference/current/red-yellow-cluster-status.html#diagnose-cluster-status), and also the [allocation settings](https://www.elastic.co/guide/en/elasticsearch/reference/current/red-yellow-cluster-status.html#fix-cluster-status-reenable-allocation)? Hope that helps! ---
**Author:** ![Sean\_Story](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sean_story/32/69987_2.png) [@Sean\_Story](https://discuss.elastic.co/u/Sean_Story)\ **Post date:** [November 7, 2024, 7:17pm UTC](https://discuss.elastic.co/t/es-cluster-stopped-working/370147/3 "2024-11-07T19:17:58Z")
Category updated on November 7, 2024, 7:17pm UTC From #Elastic Search to #Elasticsearch ---
**Author:** ![Sean\_Story](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sean_story/32/69987_2.png) [@Sean\_Story](https://discuss.elastic.co/u/Sean_Story)\ **Post date:** [November 7, 2024, 7:17pm UTC](https://discuss.elastic.co/t/es-cluster-stopped-working/370147/4 "2024-11-07T19:17:58Z")
Tags updated on November 7, 2024, 7:17pm UTC Removed #elastic-app-search ---
**Author:** ![Techiebee](https://avatars.discourse-cdn.com/v4/letter/t/67e7ee/32.png) [@Techiebee](https://discuss.elastic.co/u/Techiebee)\ **Post date:** [November 9, 2024, 10:37am UTC](https://discuss.elastic.co/t/es-cluster-stopped-working/370147/5 "2024-11-09T10:37:34Z")
I have started the cluster, and all the indicies have become green, still my cluster isnt working Suppressed: shaded.qasymphony.org.elasticsearch.client.ResponseException: method [PUT], host [[https://xxxx:9200](https://xxxx:9200)], URI [/requirement/\_mapping], status line [HTTP/1.1 400 Bad Request] {"error":{"root\_cause":[{"type":"illegal\_argument\_exception","reason":"mapper [externalSystemRequirementSystemField] cannot be changed from type [text] to [keyword]"}],"type":"illegal\_argument\_exception","reason":"mapper [externalSystemRequirementSystemField] cannot be changed from type [text] to [keyword]"},"status":400} at shaded.qasymphony.org.elasticsearch.client.RestClient.convertResponse(RestClient.java:283) at shaded.qasymphony.org.elasticsearch.client.RestClient.performRequest(RestClient.java:261) at shaded.qasymphony.org.elasticsearch.client.RestClient.performRequest(RestClient.java:235) at shaded.qasymphony.org.elasticsearch.client.RestHighLevelClient.internalPerformRequest(RestHighLevelClient.java:1514) ... 59 more 09-Nov-2024 22:51:09.269 INFO [main] org.apache.catalina.core.ApplicationContext.log Closing Spring root WebApplicationContext this was intial error due to which I had to switch to single node from cluster and re-index data, but now when i switch back to cluster its the same ---
**Author:** ![gokadroid](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/gokadroid/32/139076_2.png) [@gokadroid](https://discuss.elastic.co/u/gokadroid)\ **Post date:** [November 10, 2024, 12:05am UTC](https://discuss.elastic.co/t/es-cluster-stopped-working/370147/6 "2024-11-10T00:05:36Z")
```auto [PUT], host [[https://xxxx:9200](https://xxxx:9200/)], URI [/requirement/_mapping], status line [HTTP/1.1 400 Bad Request] : "mapper [externalSystemRequirementSystemField] cannot be changed from type [text] to [keyword]"},"status":400} ``` - Does index already exist with data in it? Changing the mappings of an existing index with data in it could be one of the reason for this error. - externalSystemRequirementSystemField is being modified from [text] to [keyword] ---
**Author:** ![Techiebee](https://avatars.discourse-cdn.com/v4/letter/t/67e7ee/32.png) [@Techiebee](https://discuss.elastic.co/u/Techiebee)\ **Post date:** [November 10, 2024, 11:23pm UTC](https://discuss.elastic.co/t/es-cluster-stopped-working/370147/7 "2024-11-10T23:23:40Z")
I haven't changed any thing, there is already existing data , I have tried re-indexing it , but it still throws the same error when started as cluster, but with single node its not causing issue ---
**Author:** ![Tortoise](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tortoise/32/147587_2.png) [@Tortoise](https://discuss.elastic.co/u/Tortoise)\ **Post date:** [November 11, 2024, 6:31pm UTC](https://discuss.elastic.co/t/es-cluster-stopped-working/370147/8 "2024-11-11T18:31:19Z")
Could you please confirm when you say single node you are able to start elasticsearch on all 3 nodes ? i mean single node is working only for specific node or all 3 nodes? this can help to understand the issue if the data is up to date on all the 3 elasticnodes or not? ---
**Author:** ![Techiebee](https://avatars.discourse-cdn.com/v4/letter/t/67e7ee/32.png) [@Techiebee](https://discuss.elastic.co/u/Techiebee)\ **Post date:** [November 12, 2024, 1:05am UTC](https://discuss.elastic.co/t/es-cluster-stopped-working/370147/9 "2024-11-12T01:05:12Z")
Single node is a single server/EC2 running one elasticsearch service, 3 nodes in the above context meaning 3 servers/ec2's as one cluster ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [December 10, 2024, 1:06am UTC](https://discuss.elastic.co/t/es-cluster-stopped-working/370147/10 "2024-12-10T01:06:03Z")
Closed on December 10, 2024, 1:06am UTC This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.