Yes, at a *minimum* we should document best practices on the reclaim ages of objects, containers & accounts!
Yes, I would expect if traversing the container tree on all nodes is a viable option in your cluster removing the database (or moving to an out of the datadir directory) would allow everything to process cleanly.
... although fixing the bug would be even better <grrr>
There's some concern that entirety of the problem and the ramifications aren't fully understood - but if you recently encountered this situation in a production environment you might be able to provide additional forensics? Like what settings you were running for the reclaim ages - how many containers you found in this state - if all replicas of the containers reflected the same last update values - anything else that seems relevant...
@Juan
Yes, at a *minimum* we should document best practices on the reclaim ages of objects, containers & accounts!
Yes, I would expect if traversing the container tree on all nodes is a viable option in your cluster removing the database (or moving to an out of the datadir directory) would allow everything to process cleanly.
... although fixing the bug would be even better <grrr>
There's some concern that entirety of the problem and the ramifications aren't fully understood - but if you recently encountered this situation in a production environment you might be able to provide additional forensics? Like what settings you were running for the reclaim ages - how many containers you found in this state - if all replicas of the containers reflected the same last update values - anything else that seems relevant...