looks like that node has a disk full enough to trigger the storage watermarks, so no new shards will get allocated there. The elasticsearch log on the master node is likely reporting this.
You can also see what's up by manually rerouting a shard to that node using the cluster reroute API with the explain parameter set. Way at the bottom of the response JSON, you will see the reason why it refuses.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.