Closed Bug 1638108 Opened 5 years ago Closed 5 years ago

Please deploy syncstorage-rs 0.3.4 to prod

Categories

(Cloud Services Graveyard :: Operations: Sync, task, P1)

Product:
Cloud Services Graveyard
Component:
Operations: Sync
Type:
task

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: pjenvey, Assigned: eolson)

Details

Bug Fixes

  • don't consider expiry during batch commit (#632) (90ff7485)

FYI:

The above mentioned issue (expired data that has not been purged conflicting with data uploaded in batches, triggering an AlreadyExists error) has caught some clients who have been repeatedly failing to sync, w/ the AlreadyExists giving them 500 errors. This usually hits their history collection.

They should now successfully sync. We may see more batch commits succeeding temporarily as they "catch up". It doesn't seem to have affected very many users (per the 500 rates it's produced). I don't foresee us noticing the "catching up" other than the lowering of 500 rates.

Priority: -- → P1

Production deploy is now complete

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Product: Cloud Services → Cloud Services Graveyard
You need to log in before you can comment on or make changes to this bug.