# Index operation rejected with Service Not Available error / Master Node Failed in logs **URL:** \ **Category:** Elasticsearch\ **Created:** [July 14, 2021, 12:25pm UTC](https://discuss.elastic.co/t/index-operation-rejected-with-service-not-available-error-master-node-failed-in-logs/278657 "2021-07-14T12:25:09Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![Steve\_Robinson](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/steve_robinson/32/45707_2.png) [@Steve\_Robinson](https://discuss.elastic.co/u/Steve_Robinson)\ **Post date:** [July 14, 2021, 12:25pm UTC](https://discuss.elastic.co/t/index-operation-rejected-with-service-not-available-error-master-node-failed-in-logs/278657/1 "2021-07-14T12:25:09Z")
We noticed an index op fail with the error: `{"ok":false,"message":"The requested resource is currently unavailable."}` today. When investigating the server logs during this time, it appears as if the master node in our cluster has for whatever reason become unreachable and there was some kind of a recovery workflow happening (Apologies, I'm new to operating Elasticsearch, still learning the ropes). Here are all the server logs from that time: [ES Prod Logs ยท GitHub](https://gist.github.com/steverob/2f7cb2e9c06f46950d8d82bd0b67acaa) Looking for suggestions for where to look to investigate what happened or to know if this something that typically happens and for insights from the logs. We're using Elastic Cloud with a 3 node cluster. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [August 11, 2021, 12:25pm UTC](https://discuss.elastic.co/t/index-operation-rejected-with-service-not-available-error-master-node-failed-in-logs/278657/2 "2021-08-11T12:25:12Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.