aswinshakil opened a new pull request, #10702: URL: https://github.com/apache/ozone/pull/10702
## What changes were proposed in this pull request? During EC offline reconstruction, the coordinator creates a RECOVERING replica on a spare DataNode and writes blocks over time. If reconstruction stalls (e.g. slow block-group processing) longer than `ozone.recovering.container.timeout` (~20m, measured from creation, not last write), the DN scrubber marks the replica UNHEALTHY and SCM force-deletes it. The coordinator may still be running. The next `WriteChunk` finds no container; `HddsDispatcher` auto-creates a new OPEN container instead of failing. The coordinator continues and closes that replica shortly after, leaving a partial container (fewer blocks/chunks than the reference) that SCM can accept as CLOSED — silent data loss. This PR fixes the issue my not allowing create container during `WriteChunk` for RECOVERING containers. Also update the recovering container timeout based on the last write to the container. ## What is the link to the Apache JIRA [HDDS-15791](https://issues.apache.org/jira/browse/HDDS-15791) ## How was this patch tested? Added 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]
