• Matthew Oliver's avatar
    Sharding: Use the metadata timestamp as last_modified · 370ac4cd
    Matthew Oliver authored
    This is a follow up patch from the cleaning up cleave context's patch
    (patch 681970). Instead of tracking a last_modified timestamp, and storing
    it in the context metadata, use the timestamp we use when storing any
    metadata.
    
    Reducing duplication is nice, but there's a more significant reason to
    do this: affected container DBs can start getting cleaned up as soon as
    they're running the new code rather than needing to wait for an
    additional reclaim_age.
    
    Change-Id: I2cdbe11f06ffb5574e573c4a60ba4e5d41a00c50
    370ac4cd
test_manage_shard_ranges.py 15.9 KB