If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Redirect clients to different nodes if the current node is full

RESOLVED INVALID

Status

Cloud Services
SimplePush
RESOLVED INVALID
3 years ago
2 years ago

People

(Reporter: kitcambridge, Assigned: kitcambridge)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

* If the client connects to an overloaded Simple Push node, the node should return a `"redirect"` response containing the URL of a peer node in the cluster.
* If the entire cluster is full, the node should redirect the client to a node in a different cluster.
* Simple Push nodes should publish their connection count (or threshold) to a shared etcd cluster every minute.
* etcd fetches should be staggered (perhaps every 5 minutes) and cached in memory to avoid excessive queries.
Assignee: nobody → kcambridge
Blocks: 1055139
Is this specifically Simple Push or Loop Push
/me head is exploding...
Loop Push (I wrote "Simple Push" out of habit, since they use the same codebase, but only Loop Push needs redirects enabled). Apologies for the confusion.
Status: NEW → ASSIGNED
:oremj and I agreed this should land in both clients, too. Unlikely to make it in until at least Firefox 36.

Comment 4

3 years ago
Note that this feature is probably of limited utility, at least for Loop, for reasons I describe in Bug 1094433 comment 4.
No longer valid with the new Push server.
Status: ASSIGNED → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.