Yida Wu created IMPALA-15575:
--------------------------------
Summary: Statestore subscriber leaves the standby statestored
marked active after a stale active claim during registration
Key: IMPALA-15575
URL: https://issues.apache.org/jira/browse/IMPALA-15575
Project: IMPALA
Issue Type: Bug
Components: Backend
Reporter: Yida Wu
With statestored HA, if the statestore service fails over while a subscriber
registers with the two statestoreds, StatestoreSubscriber::Start() keeps the
active and standby statestoreds set by UpdateStatestoredRole(). It swaps them
only if the standby statestored reported itself as active with a newer active
version.
IMPALA-15553 fixed Start() overwriting these roles with the stale ones from the
registration responses, which could leave the subscriber following the standby
statestored. However, if the standby statestored reported itself as active with
the same or an older version, the subscriber correctly keeps the current active
statestored, but the StatestoreStub referenced by standby_statestore_ still
keeps the active flag true. Metrics for both statestored then may show true on
that daemon. So this flag should be better to reset in this case.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
