I have a setup of ELK stack with redis as a broker and a cluster of 2
Elasticsearch Nodes. The stack was running good and suddenly I started
facing the following error and warning messages at different levels of the
stack.
If I restart the redis broker, Logstash and the Elasticsearch node showing
error message, the stack comes back, with Redis-broker performing well,
able to allocate memory but I have been seeing the same error messages for
E.S and Logstash after the restart. Because of which the redis-broker start
buffering the logs in memory and eventually goes out of memory as E.S and
logstash stop indexing the data.
I am trying out figure out what might be the possible cause of this, any
help will be really appreciated. Please let me know if there is any
confusion understanding the situation.
I have a setup of ELK stack with redis as a broker and a cluster of 2
Elasticsearch Nodes. The stack was running good and suddenly I started
facing the following error and warning messages at different levels of the
stack.
If I restart the redis broker, Logstash and the Elasticsearch node showing
error message, the stack comes back, with Redis-broker performing well,
able to allocate memory but I have been seeing the same error messages for
E.S and Logstash after the restart. Because of which the redis-broker start
buffering the logs in memory and eventually goes out of memory as E.S and
logstash stop indexing the data.
I am trying out figure out what might be the possible cause of this, any
help will be really appreciated. Please let me know if there is any
confusion understanding the situation.
On 20 September 2014 04:33, shriyansh jain <shriyan...@gmail.com
<javascript:>> wrote:
I have a setup of ELK stack with redis as a broker and a cluster of 2
Elasticsearch Nodes. The stack was running good and suddenly I started
facing the following error and warning messages at different levels of the
stack.
If I restart the redis broker, Logstash and the Elasticsearch node
showing error message, the stack comes back, with Redis-broker performing
well, able to allocate memory but I have been seeing the same error
messages for E.S and Logstash after the restart. Because of which the
redis-broker start buffering the logs in memory and eventually goes out of
memory as E.S and logstash stop indexing the data.
I am trying out figure out what might be the possible cause of this, any
help will be really appreciated. Please let me know if there is any
confusion understanding the situation.
On 20 September 2014 04:33, shriyansh jain <shriyan...@gmail.com
<javascript:>> wrote:
I have a setup of ELK stack with redis as a broker and a cluster of 2
Elasticsearch Nodes. The stack was running good and suddenly I started
facing the following error and warning messages at different levels of the
stack.
If I restart the redis broker, Logstash and the Elasticsearch node
showing error message, the stack comes back, with Redis-broker performing
well, able to allocate memory but I have been seeing the same error
messages for E.S and Logstash after the restart. Because of which the
redis-broker start buffering the logs in memory and eventually goes out of
memory as E.S and logstash stop indexing the data.
I am trying out figure out what might be the possible cause of this, any
help will be really appreciated. Please let me know if there is any
confusion understanding the situation.
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.