[GitHub] [ozone] kaijchen commented on pull request #3361: HDDS-6582. ContainerRecoveryStore for ec containers under recovery.

[GitBox <gi...@apache.org>]

kaijchen commented on PR #3361:
URL: https://github.com/apache/ozone/pull/3361#issuecomment-1117408736

   > If we stream the container content to avoid local storage consumption, the failure probability is more as we may have longer time spending in NW IO ( prone to failures). Where if we generate them locally, we can transfer the whole container as single step and even if failed to transfer, we could retry. So, it would be good idea to start with generating container locally and transfer them once all recovery done.
   
   I think we can cache the reconstructed data and allow retry in a sliding window when streaming data to TargetDNs.
   However, if any TargetDN fails and needs to be replaced, we have to start over.
   
   Overall, I agree with implementing the simple approach first, and do optimizations later.


-- 
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: issues-unsubscribe@ozone.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org