If you have local SSDs I am not sure what could be causing this. What OS and JVM are you using? What does your cluster setup and configuration look like?
Can please share what is the usual scenarios where the chances of "shard lock" are high or can be the root cause. Anything you want to suggest how to analyse or find the root cause or how to tackle "shard lock" situation.
Or any best practice that you want to share to avoid such situation
I have not come across this before, but did look through issues on the Elasticsearch GitHub repo and found this. It does however relate to older versions. It may be worthwhile looking through this and see if any of the potential causes apply to your cluster. If not, I would recommend you open a new issue with as much information about your cluster and work load as possible.
if you have in red, in my case I became to resove it by deleting some red indexes from linux command line :
sudo curl XDELETE http://ipaddress:9200/_cat/<indexe_name>
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.