You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On graphd/storaged reboots/failures, we observed that QPS skews toward remaining living servers, and QPS are never balanced again without intervention(client reboot, network fluctuation, etc).
The more servers we have, the lower the probability that a new session is created on a recently started server, because pos is only an index.
This undermines the purpose of a distributed database.
Proposal
Implement a new priority queue based on existing connections count for graphd server to replace pos, enabling each client to balance connections across all available servers. (I believe this would serve as a suitable default configuration.)
The text was updated successfully, but these errors were encountered:
Introduction
On graphd/storaged reboots/failures, we observed that QPS skews toward remaining living servers, and QPS are never balanced again without intervention(client reboot, network fluctuation, etc).
The more servers we have, the lower the probability that a new session is created on a recently started server, because pos is only an index.
This undermines the purpose of a distributed database.
Proposal
Implement a new priority queue based on existing connections count for graphd server to replace
pos
, enabling each client to balance connections across all available servers. (I believe this would serve as a suitable default configuration.)The text was updated successfully, but these errors were encountered: