# ECK Master not discovered issue **URL:** \ **Category:** Elastic Cloud on Kubernetes (ECK)\ **Created:** [May 19, 2022, 8:58am UTC](https://discuss.elastic.co/t/eck-master-not-discovered-issue/305147 "2022-05-19T08:58:57Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Sagar\_Dalvi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sagar_dalvi/32/71609_2.png) [@Sagar\_Dalvi](https://discuss.elastic.co/u/Sagar_Dalvi)\ **Post date:** [May 19, 2022, 8:58am UTC](https://discuss.elastic.co/t/eck-master-not-discovered-issue/305147/1 "2022-05-19T08:58:57Z")
We have deployed Elasticsearch on Openshift Cluster using ECK Operator. We were facing some sharding issue for Elasticsearch cluster after which we have restarted Elasticsearch operator and runtime pods. After restart we are seeing master not discovered error and cluster itself is not coming up. We have Production Data on cluster. We need help to recover Elasticsearch cluster or atleast data. ---
**Author:** ![framsouza](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/framsouza/32/95958_2.png) [@framsouza](https://discuss.elastic.co/u/framsouza)\ **Post date:** [May 24, 2022, 1:19pm UTC](https://discuss.elastic.co/t/eck-master-not-discovered-issue/305147/2 "2022-05-24T13:19:31Z")
Any specific reason why you had to restart the ECK operator? Which operator version are you using? Can you please share the ECK output logs and the ES logs? ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [June 21, 2022, 1:19pm UTC](https://discuss.elastic.co/t/eck-master-not-discovered-issue/305147/3 "2022-06-21T13:19:33Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.