Did you start out with this disk configuration before adding data to the cluster or change after data was already indexed? Is this imbalance causing any performance problems?
I don't believe Elasticsearch will move shards between paths once they are placed, so if the path was initially incorrect, it would expect the imbalance. I would expect this to even out as you add additional indices/shards.
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.