[ 
https://issues.apache.org/jira/browse/HDDS-6582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17523478#comment-17523478
 ] 

Mark Gui edited comment on HDDS-6582 at 4/18/22 4:04 AM:
---------------------------------------------------------

Hi [~umamaheswararao] [~adoroszlai] , this idea is very good and briefly stated 
in the design doc.

Actually we are also learning and discussing about the Offline Recovery, and 
actually I've got a design and a offline prototype implementation of this temp 
store, could I take this issue and we could discuss about the details?

The design doc for a possible implementation: 
https://docs.google.com/document/d/1CW73NSIWmrzobVyMvtGQtj6-mLyLlpNennQE8yYMM4I/edit?usp=sharing


was (Author: markgui):
Hi [~umamaheswararao] [~adoroszlai] , this idea is very good and briefly stated 
in the design doc.

Actually we are also learning and discussing about the Offline Recovery, and 
actually I've got a design and a offline prototype implementation of this temp 
store, could I take this issue and we could discuss about the details?

 

> EC: DN ability to create container in temp location and write blocks to it.
> ---------------------------------------------------------------------------
>
>                 Key: HDDS-6582
>                 URL: https://issues.apache.org/jira/browse/HDDS-6582
>             Project: Apache Ozone
>          Issue Type: Sub-task
>            Reporter: Uma Maheswara Rao G
>            Assignee: Attila Doroszlai
>            Priority: Major
>
> This task is to analyze and provide option to create the container in 
> specified temp location in same drive. 
> This will be useful when we recover the EC containers, we can use this to 
> store the container in temp location, so that this will not be considered for 
> reporting purposes.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to