1091192 - Redirect clients to different nodes if the current node is full

Status: RESOLVED INVALID

(Cloud Services Graveyard :: Server: SimplePush, defect)

Description

[Lina Butler (ex-Mozilla)]

* 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.

Comment 1

[James Bonacci [:jbonacci]]

Is this specifically Simple Push or Loop Push
/me head is exploding...

Comment 2

[Lina Butler (ex-Mozilla)]

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.

Comment 3

[Lina Butler (ex-Mozilla)]

:oremj and I agreed this should land in both clients, too. Unlikely to make it in until at least Firefox 36.

Comment 4

[Adam Roach [:abr]]

Note that this feature is probably of limited utility, at least for Loop, for reasons I describe in Bug 1094433 comment 4.

Comment 5

[Lina Butler (ex-Mozilla)]

No longer valid with the new Push server.