Closed
Bug 1091192
Opened 10 years ago
Closed 9 years ago
Redirect clients to different nodes if the current node is full
Categories
(Cloud Services Graveyard :: Server: SimplePush, defect)
Cloud Services Graveyard
Server: SimplePush
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: lina, Assigned: lina)
References
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.
Comment 1•10 years ago
|
||
Is this specifically Simple Push or Loop Push /me head is exploding...
Assignee | ||
Comment 2•10 years ago
|
||
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
Assignee | ||
Comment 3•10 years ago
|
||
:oremj and I agreed this should land in both clients, too. Unlikely to make it in until at least Firefox 36.
Comment 4•10 years ago
|
||
Note that this feature is probably of limited utility, at least for Loop, for reasons I describe in Bug 1094433 comment 4.
Assignee | ||
Comment 5•9 years ago
|
||
No longer valid with the new Push server.
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → INVALID
Updated•1 year ago
|
Product: Cloud Services → Cloud Services Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•