umamaheswararao commented on PR #3361: URL: https://github.com/apache/ozone/pull/3361#issuecomment-1116713273
There two things we discussed: Generating containers locally first and transfer them to the remaining targets. This will give some advantage on failure handling side. Me and Arpit had a short discussion on this. 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. So, the next question for discussion here, while generating locally, whether to use existing protocols and have different container state or use this patch proposed new interfaces. -- 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]
