You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by GitBox <gi...@apache.org> on 2019/12/03 22:19:54 UTC

[GitHub] [hadoop-ozone] xiaoyuyao edited a comment on issue #214: HDDS-2534. scmcli container delete not working

xiaoyuyao edited a comment on issue #214: HDDS-2534. scmcli container delete not working
URL: https://github.com/apache/hadoop-ozone/pull/214#issuecomment-561383295
 
 
   Yes, the current patch delete container from SCM DB, container state manager still has the deleted container info in memory. Here are the issues:
   1. ContainerReportHandler will not hit ContainerNotFoundException.
   2. Container state manager won't get deleted container removed from in-memory map until a restart/reload. 
   3. In-memory container state inconsistent with the SCM DB.
   
   To solve this, we will need to keep track of the deleting status in SCM until the heartbeat from Dn confirm the deletion cmd execution on three datanodes. This will be similar to what we did for the block deletion log in SCM. 
   
   

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

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