Closed Bug 663953 Opened 13 years ago Closed 13 years ago

Possible server data corruption after user migration

Categories

(Firefox :: Sync, defect, P1)

defect

Tracking

()

RESOLVED DUPLICATE of bug 664865

People

(Reporter: rnewman, Assigned: rnewman)

Details

(Whiteboard: [sync-hmac])

Follow on from Bug 650208, pertaining to Bug 646269.

mconnor suggested that node failover might be to blame here, and I think he might be right. I can certainly imagine the following happening:

* User begins sync.
* 401 (IIRC) is used to indicate that the user has been reassigned to a new node.
* Sync proceeds after node reassignment.
* At this point, the server contains the uploaded data, and a new meta/global, but no keys. Inconsistent!
* A new client will (prior to Bug 650208) observe this situation, generate and upload new keys, and boom: keys on the server do not match data on the server.

If this is really the case, then fixing the third item is the neat solution: after a node reassignment, stop the current sync and start a new one.

I will look into this shortly, and try to get a test case together.
Duping to the concrete fix for the bug.
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
Component: Firefox Sync: Backend → Sync
Product: Cloud Services → Firefox
You need to log in before you can comment on or make changes to this bug.