An easy way to cycle EC2 instances where we have an elasticsearch cluster running. As an example target we have,
No words go here
No words go here
An easy way to cycle EC2 instances where we have an elasticsearch cluster running. As an example target we have,
Currently I’m using the logging setup of Beaver shipping logs into an ELK stack, and metrics with collectd shipping metrics into a Graphite stack. Now that Elastic have Beats that do both logging and metrics, its worth exploring further.
Quick walkthrough of a problem on a 3 node elasticsearch cluster first noticed with the generic yellow/red cluster warning. The chain of events causing the problem looks like…