sadanand48 opened a new pull request, #10862: URL: https://github.com/apache/ozone/pull/10862
## What changes were proposed in this pull request? Current logic rejects checkpoint requests with 503 unless isLeaderReady() is true. In a degraded cluster (e.g., one OM down, one follower far behind), this creates a loop: Lagging follower needs checkpoint to catch up. Follower requests /v2/dbCheckpoint from leader. Leader is LEADER_AND_NOT_READY and returns 503 due to isLeaderReady() check. Follower cannot catch up, so leader readiness does not progress. System remains stuck until another OM is brought back. Checkpoint creation already has consistency barriers: awaitDoubleBufferFlush() bootstrap write lock (BOOTSTRAP_LOCK) So requiring LEADER_AND_READY here is stricter than necessary and can block recovery. instead only reject if NOT_LEADER ## What is the link to the Apache JIRA https://issues.apache.org/jira/browse/HDDS-15962 ## How was this patch tested? Unit tests -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
