Details
-
Sub-task
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
Reviewed
Description
Current delete container API seems can be possibly running into inconsistent state. SCM maintains a mapping of container to nodes, datanode maintains the actual container's data. When deletes a container, we need to make sure db is removed as well as the mapping in SCM also gets updated. What if the datanode failed to remove stuff for a container, do we update the mapping? We need to revisit the implementation and get these issues addressed. See more discussion here.