openstack
/
openstack
Code Issues Proposed changes

Update git submodules 

* Update swift from branch 'master'
  to c3aa1ce66c20c0c9148a4d3e22d3ff5bcd12bfdb
  - Merge "sharder: always set state to CLEAVED after cleaving"
  - sharder: always set state to CLEAVED after cleaving
    
    During cleaving, if the sharder finds that zero object rows are copied
    from the parent retiring DB to a cleaved shard DB, and if that shard
    DB appears have been freshly created by the cleaving process, then the
    sharder skips replicating that shard DB and does not count the shard
    range as part of the batch (see Related-Change).
    
    Previously, any shard range treated in this way would not have its
    state moved to CLEAVED but would remain in the CREATED state. However,
    cleaving of following shard ranges does continue, leading to anomalous
    sets of shard range states, including all other shard ranges moving to
    ACTIVE but the skipped range remaining in CREATED (until another
    sharder visitation finds object rows and actually replicates the
    cleaved shard DB).
    
    These anomalies can be avoided by moving the skipped shard range to
    the CLEAVED state. This is exactly what would happen anyway if the
    cleaved DB had only one object row copied to it, or if the cleaved DB
    had zero object rows copied to it but happened to already exist on
    disk.
    
    Related-Change: Id338f6c3187f93454bcdf025a32a073284a4a159
    Change-Id: I1ca7bf42ee03a169261d8c6feffc38b53226c97f
This commit is contained in:
Zuul 2022-07-18 23:57:56 +00:00 committed by Gerrit Code Review
parent 6a80d91493
commit a5f21d7802
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
swift

@ -1 +1 @@
Subproject commit 45e13ff4c56748345c9d31bbee3bc6e7abdb5b43
Subproject commit c3aa1ce66c20c0c9148a4d3e22d3ff5bcd12bfdb