Jialiang Cai created AMBARI-26640:
-------------------------------------
Summary: Prevent auto-recovery from blocking cluster start
operations
Key: AMBARI-26640
URL: https://issues.apache.org/jira/browse/AMBARI-26640
Project: Ambari
Issue Type: Bug
Reporter: Jialiang Cai
Agent-side auto-recovery commands are hidden from users and share the action
queue with server-issued operations. When recovery work is queued or running,
Start All Services can appear stuck without showing the blocking task.
Auto-recovery also evaluates only local component state. It can restart a
component before the transitive RoleCommandOrder dependencies are ready,
particularly after server or agent restarts when cached component status is
stale.
Auto-recovery should yield to server-issued commands and follow a versioned,
stateful cluster startup topology. Component state freshness must be tied to
the active agent session and invalidated on registration or heartbeat loss so
stale or out-of-order topology snapshots cannot trigger recovery.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
