# ES marking and sending shard failed due to failed recovery in enabling replication

**URL:** <https://discuss.elastic.co/t/es-marking-and-sending-shard-failed-due-to-failed-recovery-in-enabling-replication/41742>\
**Category:** Elasticsearch\
**Created:** [February 15, 2016, 6:44am UTC](https://discuss.elastic.co/t/es-marking-and-sending-shard-failed-due-to-failed-recovery-in-enabling-replication/41742 "2016-02-15T06:44:40Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![r.ganeshbabu](https://avatars.discourse-cdn.com/v4/letter/r/4da419/32.png) [@r.ganeshbabu](https://discuss.elastic.co/u/r.ganeshbabu)\
**Post date:** [February 24, 2016, 6:02am UTC](https://discuss.elastic.co/t/es-marking-and-sending-shard-failed-due-to-failed-recovery-in-enabling-replication/41742/7 "2016-02-24T06:02:18Z")

</div>

Thanks for your response @abeyad

Basically we have 3 physical server and below is the node setup details,  
Server name -- Node Setup  
tparhdetmi003 -- Master, Data, Data2, Client  
tparhdetmi004 -- Master, Data, Data2  
tparhdetmi005 -- Master, Data, Data2

Below is the disk usage of the server ( tparhdetmi003)

Filesystem Size Used Avail Use% Mounted on  
/dev/mapper/sysvg-root.vol  
3.9G 488M 3.2G 14% /  
tmpfs 127G 0 127G 0% /dev/shm  
/dev/sda1 976M 50M 875M 6% /boot  
/dev/mapper/sysvg-home.vol  
2.0G 558M 1.3G 31% /home  
/dev/mapper/sysvg-opt.vol  
20G 5.4G 14G 29% /opt  
/dev/mapper/sysvg-tmp.vol  
20G 45M 19G 1% /tmp  
/dev/mapper/sysvg-usr.vol  
4.9G 2.6G 2.1G 57% /usr  
/dev/mapper/sysvg-var.vol  
197G 1.3G 186G 1% /var  
/dev/sdb 1.1T 362G 682G 35% /app/data1  
/dev/sdc 1.1T 270G 774G 26% /app/data2  
/dev/sdd 1.1T 278G 766G 27% /app/data3  
/dev/sde 1.1T 426G 618G 41% /app/data4  
/dev/sdf 1.1T 439G 605G 43% /app/data5  
/dev/sdg 1.1T 443G 601G 43% /app/data6  
/dev/sdh 1.1T 71M 1.1T 1% /app/data7  
/dev/sdi 1.1T 276G 769G 27% /app/data8  
/dev/sdj 1.1T 71M 1.1T 1% /app/data9  
/dev/sdk 1.1T 72M 1.1T 1% /app/data10  
/dev/sdl 1.1T 72M 1.1T 1% /app/data11  
/dev/sdm 1.1T 72M 1.1T 1% /app/data12  
/dev/sdn 1.1T 331M 1.1T 1% /app/data13  
/dev/sdo 1.1T 336M 1.1T 1% /app/data14  
/dev/sdp 1.1T 340M 1.1T 1% /app/data15  
/dev/sdq 1.1T 71M 1.1T 1% /app/data16  
/dev/sdr 1.1T 71M 1.1T 1% /app/data17  
/dev/sds 1.1T 71M 1.1T 1% /app/data18  
/dev/sdt 1.1T 71M 1.1T 1% /app/data19  
/dev/sdu 1.1T 71M 1.1T 1% /app/data20  
/dev/sdv 1.1T 71M 1.1T 1% /app/data21  
/dev/sdw 1.1T 71M 1.1T 1% /app/data22  
/dev/mapper/sysvg-opt--app.vol  
99G 2.7G 91G 3% /opt/app  
cm\_processes 127G 72M 127G 1% /var/run/cloudera-scm-agent/process

Definitely I will use shard recovery thresholds settings & Hot Threads during testing of replications

Regards,  
Ganeshbabu R

---

_[View the full topic](https://discuss.elastic.co/t/es-marking-and-sending-shard-failed-due-to-failed-recovery-in-enabling-replication/41742)._