Load Balance Health check with Search guard

How do I configure health check with AWS ELB with Searchguard as it doesn’t support authenticated health check requests.

For now yu have to go with TCP based health check or tweak "Success codes" to be 401 instead of 200

We will add a proper health check in SG 6

···

Am 06.11.2017 um 12:27 schrieb Mitesh Bulsara <mitbulsara@gmail.com>:

How do I configure health check with AWS ELB with Searchguard as it doesn't support authenticated health check requests.

--
You received this message because you are subscribed to the Google Groups "Search Guard Community Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email to search-guard+unsubscribe@googlegroups.com.
To post to this group, send email to search-guard@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/search-guard/7035cc66-5f0b-4b82-9e21-56790457af86%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Thanks for the update. Will love to have unauthenticated health check requests.

This came up because we faced a strange issue few days back. We already had TCP health check. We had a 5 nodes ES cluster running nicely for few days. Every evening the ES nodes are stopped and started next morning for cost saving.

One morning, one of the nodes didn’t join the cluster. On diagnosis, we found it said “Searchguard not initialized”. Because TCP 9200 port was good, the health check passed and Load balancer kept forwarding request to this bad node. So, our requests were failing intermittently.

Any thoughts on this issue.

···

On Tuesday, 7 November 2017 00:21:12 UTC+5:30, Search Guard wrote:

For now yu have to go with TCP based health check or tweak “Success codes” to be 401 instead of 200

We will add a proper health check in SG 6

Am 06.11.2017 um 12:27 schrieb Mitesh Bulsara mitbu...@gmail.com:

How do I configure health check with AWS ELB with Searchguard as it doesn’t support authenticated health check requests.


You received this message because you are subscribed to the Google Groups “Search Guard Community Forum” group.

To unsubscribe from this group and stop receiving emails from it, send an email to search-guard...@googlegroups.com.

To post to this group, send email to search...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/search-guard/7035cc66-5f0b-4b82-9e21-56790457af86%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

Thanks for the update and feedback. I am also impacted by this issue.

···

On Monday, November 6, 2017 at 10:42:18 PM UTC-6, Mitesh Bulsara wrote:

Thanks for the update. Will love to have unauthenticated health check requests.

This came up because we faced a strange issue few days back. We already had TCP health check. We had a 5 nodes ES cluster running nicely for few days. Every evening the ES nodes are stopped and started next morning for cost saving.

One morning, one of the nodes didn’t join the cluster. On diagnosis, we found it said “Searchguard not initialized”. Because TCP 9200 port was good, the health check passed and Load balancer kept forwarding request to this bad node. So, our requests were failing intermittently.

Any thoughts on this issue.

On Tuesday, 7 November 2017 00:21:12 UTC+5:30, Search Guard wrote:

For now yu have to go with TCP based health check or tweak “Success codes” to be 401 instead of 200

We will add a proper health check in SG 6

Am 06.11.2017 um 12:27 schrieb Mitesh Bulsara mitbu...@gmail.com:

How do I configure health check with AWS ELB with Searchguard as it doesn’t support authenticated health check requests.


You received this message because you are subscribed to the Google Groups “Search Guard Community Forum” group.

To unsubscribe from this group and stop receiving emails from it, send an email to search-guard...@googlegroups.com.

To post to this group, send email to search...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/search-guard/7035cc66-5f0b-4b82-9e21-56790457af86%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.