sadanand48 opened a new pull request, #12060:
URL: https://github.com/apache/ozone/pull/12060

   ## What changes were proposed in this pull request?
   A datanode can get stuck in HEARTBEAT against one SCM endpoint after 
repeated heartbeat failures. In observed cases, SCM asks the DN to re-register, 
but the failing endpoint may continue retrying heartbeat and not re-enter full 
handshake until DN restart.
   
   This change adds endpoint-scoped recovery for prolonged heartbeat failures:
   
   - after a configurable number of consecutive failures, reset only the 
affected SCM endpoint to GETVERSION
   - continue through normal GETVERSION -> REGISTER -> HEARTBEAT flow
   - clear queued command-status/delete-ACK reports for that endpoint during 
reset (to mimic DN restart behavior for stuck ACK backlog)
   - do not reset healthy SCM endpoints
   - do not reset global datanode state
   - keep passive endpoints (Recon) unchanged
   - avoid resetting on every failure via threshold gating
   - reset missed-failure counter on successful heartbeat (existing behavior)
   
   Configuration:
   existing (unchanged purpose):
   hdds.heartbeat.address.refresh.missed-count-threshold (default 3)
   used for DNS/address refresh path
   new (this recovery path):
   hdds.heartbeat.re-register.missed-count-threshold (default 100)
   used for endpoint re-registration reset path
   
   ## What is the link to the Apache JIRA
   https://issues.apache.org/jira/browse/HDDS-17831
   
   ## 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]

Reply via email to