Anyone can help me on that? It's pretty weird. I'm using a simple architecture: Filebeat -> Logstash -> Elasticsearch. Besides, only one instance of logstash and elasticsearch. When I started them, they worked well. However for a while, there were many error information in logstash. {:timestamp=>…

Unavailable_shards_exception, reason: primary shard is not active

Topic		Replies	Views
Unavailable_shards_exception reason=> filebeat primary shard is not active Logstash	4	11124	October 4, 2017
Unavailable_shards_exception primary shard is not active Logstash	2	3707	June 5, 2018
Retrying failed action with response code: 503 unavailable_shards_exception, reason => logstash primary shard is not active Logstash	4	1559	May 3, 2020
Primary shard is not active Logstash	1	444	August 22, 2019
Retrying failed action with response code: 503 unavailable_shards_exception, reason - logstash primary shard is not active Elasticsearch	6	10233	May 4, 2020