I've read several answers on the topic around unassigned shards, from data about thread pools to checking how many replicas are configured but none of those seem to have answers.
I've literally just built a brand new elasticsearch 6.3 node (for home use) with logstash and kibana on top. It currently has 1 filebeat client feeding data into logstash and with output to elastic.
I have 3 unassigned shards. The instance is not clustered, it is single node, it has plenty of RAM and heap available and it's been an hour. I am imagining these 3 unassigned shards are due to 3 being the default number of shards from filebeat.
What I want to know is how can I already have unassigned shards? I'd rather resolve this now before I start having other filebeats starting to deliver logs.
Please let me know any config I might need to post here.
In case anyone is wondering (there is a lot of information out there about earlier versions of elastic and the error information printed by elastic starting up didnt work for me) you can't do it in the elasticsearch.yml but this works:
Note that you might have a template created by filebeat so it would be better to modify the template as well so next day, you'll start with the right values.
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.