Closed Bug 1465317 Opened 7 years ago Closed 2 years ago

Collect and visualize metrics on server-side node migrations

Categories

(Cloud Services Graveyard :: Server: Sync, enhancement)

Product:
Cloud Services Graveyard
Component:
Server: Sync
Type:
enhancement
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: rfkelly, Unassigned)

References

(Blocks 1 open bug)

Details

Bug 1465313 identifies some events which might cause a user to be migrated to a new sync storage node, discarding their previously-synced data. But IIUC we don't really know how likely those events are to happen in practice. Let's find out. We should be able to get pretty decent metrics on this server-side, because tokenserver is what ultimately does the new allocation, either in response to a change in encryption key: https://github.com/mozilla-services/tokenserver/blob/master/tokenserver/assignment/sqlnode/sql.py#L341 In due to some operational script that marked the user as needing to be re-assigned: https://github.com/mozilla-services/tokenserver/blob/master/tokenserver/assignment/sqlnode/sql.py#L276 So instrumenting at those two points will be a good start. I'm not sure what the best place to send those metrics is though...maybe we could even send them to amplitude in order to examine the effect of these events on user retention!

With the advent of more durable sync, this is no longer necessary.

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