Skip to content
This repository has been archived by the owner on May 16, 2023. It is now read-only.

[elasticsearch] Tweak the 'readinessProbe' command to verify that master nodes are available. #380

Merged
merged 1 commit into from
Nov 21, 2019
Merged

[elasticsearch] Tweak the 'readinessProbe' command to verify that master nodes are available. #380

merged 1 commit into from
Nov 21, 2019

Commits on Nov 20, 2019

  1. [elasticsearch] Tweak the 'readinessProbe' command to verify that master 

    nodes are available.

The behaviour of the `/` endpoint changed[0] between 6.x and 7.x, whereby
previously it would return a HTTP `503` response when the cluster was
blocked, it now returns a HTTP `200` response even if there are no masters
available.

This change updates the behaviour of the `readinessProbe` command during
normal running to verify that the local node is responding and that there
are master nodes available. [1]

The desired behaviour here is that if the data nodes are unable to talk to
their master nodes for whatever reason, then the data nodes will become
`Unready` and therefore be removed from the Service load-balancer until
the master nodes are available again.

Refs:
[0] elastic/elasticsearch#29045
[1] elastic/elasticsearch#34897 (comment)
    Gavin Williams committed Nov 20, 2019
    Configuration menu
    Copy the full SHA
    7af11b1 View commit details
    Browse the repository at this point in the history