empty shards fail audit with reclaimed root db

Bug #1911232 reported by clayg on 2021-01-12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Object Storage (swift)
Matthew Oliver

Bug Description

When a sharded database is empty, it can be deleted - but the empty shards do not appear to be marked as deleted. When a non-deleted shard is unable to find (404) the root db, it logs a warning. Even if the shard is empty; once the deleted root db is reclaimed it creates a storm of log warnings and won't ever fix itself.

To work around manually you can issue DELETE requests to the shard containers in the .shard_AUTHXXX account

clayg (clay-gerrard) wrote :

having talked it through with Al & Tim - they think it might be reasonable for the sharder, during audit to detect the root db has reclaimed (404 w/o a backend-timestamp) and then mark itself as deleted

Matthew Oliver (matt-0) wrote :

in an ideal world, aka a world of auto-sharding I'd hope the empty shard containers would shrink and callapse back into the root container before reclaim_age. But yeha we need a backup to make sure they don't stick around.

Matthew Oliver (matt-0) on 2021-01-13
Changed in swift:
assignee: nobody → Matthew Oliver (matt-0)
Matthew Oliver (matt-0) on 2021-01-13
Changed in swift:
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers