# Cluster reovery failed and data node is not reachability
**URL:** https://discuss.elastic.co/t/cluster-reovery-failed-and-data-node-is-not-reachability/304630
**Category:** Elasticsearch
**Created:** [May 13, 2022, 2:02am UTC](https://discuss.elastic.co/t/cluster-reovery-failed-and-data-node-is-not-reachability/304630 "2022-05-13T02:02:26Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@liuhuang9492](https://discuss.elastic.co/u/liuhuang9492)
#### Post date: [May 13, 2022, 2:02am UTC](https://discuss.elastic.co/t/cluster-reovery-failed-and-data-node-is-not-reachability/304630/1 "2022-05-13T02:02:26Z")
hi,
I have run a Elasticsearch cluster in prd. it has 3 master node and 4 data node for version 2.1.1
it has a big index ,about 2.5TB and it only has 5 shards. The index is in translog state for a long time during index recovery.The JVM memory usage is very high, and then the GC is repeated, causing the data node to leave the cluster.
```auto
{data=false, master=true}], reason [failed to ping, tried [3] times, each with maximum [30s] timeout]
```
and I tried to modify the parameter discovery.ze.fd.ping\_timeout to 600s, but found the same error
```auto
{data=false, master=true}], reason [failed to ping, tried [3] times, each with maximum [10m] timeout
```
Is there a way to recover ?
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [June 10, 2022, 2:03am UTC](https://discuss.elastic.co/t/cluster-reovery-failed-and-data-node-is-not-reachability/304630/2 "2022-06-10T02:03:19Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.