Prior to this PR we would exit 0 with the message "Elasticsearch up!" even if the cluster status was red.
This PR changes the elastic_status command to target the cluster health API using the param wait_for_status=yellow
One easy way to cause a red status is to start an elasticsearch server on top of an index which was created with a previous version and is no longer compatible.
Prior to this PR we would exit 0 with the message "Elasticsearch up!" even if the cluster status was red.
This PR changes the
elastic_status
command to target the cluster health API using the paramwait_for_status=yellow
One easy way to cause a red status is to start an elasticsearch server on top of an index which was created with a previous version and is no longer compatible.