Description
SCM losses its state once being restarted. This issue can be found by a simple test with following steps
- Start NN, DN, SCM
- Create several containers via SCM CLI
- Restart DN
- Get existing container info via SCM CLI, this step will fail with container doesn't exist error.
ContainerManagerImpl maintains a cache of container mapping containerMap, if DN is restarted, this information is lost. We need a way to restore the state from DB in a background thread.
Attachments
Issue Links
- relates to
-
HDFS-12016 Ozone: SCM: Container metadata are not loaded properly after datanode restart
- Resolved