Ethan Rose

Hi @JyotinderSingh, can you merge master back in to this PR to pick up #3487 and check the compat acceptance test failure?

Hi @symious, my understanding of the change here is that containers that have been deleted will not need individual blocks deleted anymore. However, the requirement for a container to be...

Right, I believe the reason there is no removal for deleted containers from being processed for block deletes is that a container cannot be deleted until all blocks from all...

Sorry for the late response here. It's good to hear that this patch resolves the observed issue, but we should really try to understand why deleted containers are ending up...

@swamirishi will be looking at a way to reproduce this issue.

Thanks for the analysis @swamirishi. Coordinating between the deleted block log and replication manager will be challenging so I think removing DELETED containers from the deleted block log when they...

Ozone audit logs and system logs use log4j for the configuration, so I think log4j config docs are the better reference for that rather than duplicating the info in our...

Thanks for reviewing this @kerneltime. Let's put this on hold for now while re-evaluate our approach to not closing pipelines during finalization.

@JacksonYao287 what is the motivation behind this change? Maintaining a record of all deleted containers in SCM has the following benefits: - If a dead node comes back online after...

Hi @JacksonYao287 @sodonnel I still have some concerns about the way this change is implemented. ## No clear problem statement Is the motive to reduce memory usage or RocksDB usage...