Sorry i wasnt able to find any stack trace in the elastic logs.
for that node ID hn3cgxthRmyYMn-ZbOmuRw the only other logs i see except for the "failed to list shard for shard_store on node", are the normal cluster joinging logs
i.e. added {{.....internal}{hn3cgxthRmyYMn-ZbOmuRw}{3i8y7MXaQR-kBQLVslvaaA}{.....}{....:9300}.... ml.machine_memory=32891092992, scaling=false, xpack.installed=true, ml.max_open_jobs=20, ml.enabled=true} committed version [282] source [zen-disco-node-join]])
I looked up the source of this message and it's here (in v6.3.2):
The , failure); at the end means Elasticsearch definitely tried to log a stack trace. Also this message only appears in logs, so the text quoted in the OP must be the result of some post-processing of these logs. What is happening to the logs after they leave Elasticsearch? Can you get hold of the raw logs?
FailedNodeException is a very general exception that wraps around many different things, so without the stack trace showing the inner exceptions it's not really possible to describe what's going on.
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.