674280 - If clusterURL is broken for a long time, check with node server to be certain it's correct

Status: RESOLVED INVALID

(Firefox :: Sync, defect)

Description

[:Atoll]

Problem: Once client gets a clusterURL, it engraves it in stone until either a 401 or a deactivate this device.  This prevents recovering from issues where a clusterURL that does not resolve is handed to a client by the node server.

Steps to reproduce:

1. Configure node assignment to give out a broken, does-not-resolve, hostname.
2. Set up sync in Firefox.
3. Sync Now, triggering yellow error bar about bad hostname.
4. Fix node assignment on the server and schedule your user for node reassignment.

BUG: Client never detects that node assignment has changed, because it's impossible to serve a 401 from a bogus hostname.

FIX: Once in a while, either coin-flip random or after several clusterURL errors, try pinging the node assignment server to see if it's got a new clusterURL.

Comment 1

[:Atoll]

34 new users were affected by a node assignment bug today, leading to their clients being assigned a broken server URL.  We emailed repair instructions to the affected users.

Comment 2

[Richard Newman [:rnewman]]

Correcting title.

See also Bug 716816 for Android Sync.

Comment 3

[:Atoll]

Closing this ancient Sync bug that hasn't been triaged in 5-7 years since I filed them - either it's not an issue or it's been silently refused by the teams involved.