Ethan Rose

Hi @Xushaohong, I don't think we want to be deleting containers with all replicas unhealthy automatically, because this will cause divergence between the OM's metadata and the corresponding block storage....

Thanks for raising the issue @Xushaohong. Handling containers where all replicas are in a degenerate state is definitely something the system should improve on. Adding to @kerneltime's response based on...

Thanks for the proposal Symious. I agree we should not use /tmp for intermediate datanode operations like container import. I have a few questions. 1. Why is this be behind...

Thanks for the input @ChenSammi. The subtasks in [HDDS-6449](https://issues.apache.org/jira/browse/HDDS-6449) were actually created before we had design discussions. There won't need to be a background service which greatly simplifies the task...

> how do we verify that datanode downgrade will be impacted or not? The docker based upgrade/downgrade tests run a downgrade and upgrade back to the previous release as part...

Oops should be fixed now.

Thanks for the review @smengcl

The cluster ID directory on the datanode has a complicated history, but it is not related to schema V3. For a detailed look see HDDS-5432 and the design document linked...

One other thing to check is what happens with schema V3 when the container is moved to the tmp dir but the RocksDB update fails. Will the datanode restart cleanly?...

I've looked through the existing code, and if the RocksDB update fails for schema v3 I think we will be ok with a minor improvement in the current design. The...