ChenSammi commented on PR #7877:
URL: https://github.com/apache/ozone/pull/7877#issuecomment-2667696579

   > @ChenSammi This change is not able to handle below case,
   > 
   >     1. if container folder is removed first, and then DN crashed / 
restarted, the DB entry remains orphan.
   > 
   > 
   > Currently this is never reported / cleaned. The reason for this is, during 
startup, preference is given to directory structure and those containers are 
loaded.
   > 
   > So if container is not loaded, its never going to report to SCM Or DN 
internal, and no way to know container entry as orphan.
   > 
   > This may have further impact, if next time, container is imported again, 
it will not clean old entry and try to overwrite. There can be some orphan 
entries in table which may impact functionality.
   
   There is possibility that container meta data will be left in DB if DN 
crashes before meta data cleanup get executed.  Except the orphan entries in 
the DB,  it shall not impact container function, as they are orphan entries, no 
logic will try to access then. Next time, If the same container is re-imported, 
and succeeded,  the container's meta data in DB will be overwritten with the 
new value, and they will be no longer orphan after that.


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

Reply via email to