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

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

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

   @guihecheng This API seems be locally creating container and writing to it. But transferring remotely still need to expose them throw different protocol. 
   
   Other hand @sodonnel has a point to have recovery state and create in the same directory. Can we discuss this option as well?
   
   Looks like SCM needs to handle recovery state little differently, but that seems not difficult though. 
   When SCM smartly handle this different state, we don't need to worry about temp store though, it can be in actual dir itself. If we just wanted to move ahead with temp store, I feel it's too early to discard that idea. 
   I am thinking a bit about this: mainly handling failure cases. Is it is easy to change the state of container? example we created recovery state containers and coordinator crashed. Then we will have left out recovery state containers. Then when they can be cleared. cc: @sodonnel 
   


-- 
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