-
Enhancement
-
Resolution: Unresolved
-
Major
-
None
-
None
With the exception of our RESP server, none of our other server end points have any sort of back pressure support.
Just a few issues that need to be taken into account for back pressure:
1. If a server receives a large amount of operations that do not complete synchronously they can pile up.
2. If a server sends responses to a client and the clients socket buffer is full, we should delay requests from that
3. A very very large number of clients connect. This is the most difficult to gauge properly as there is no easy way to know how many clients a server can handle. Maybe just have something configurable? And do we then prevent new connections or kill oldest?
Please see the various sub issues to see where each end point stands in regards to these, although none do anything for #3.
1.
|
HotRod backpressure support | New | Unassigned | ||
2.
|
RESP backpressure support | Resolved | Will Burns | ||
3.
|
HTTP backpressure support | New | Unassigned | ||
4.
|
Memached backpressure support | Resolved | Jose Bolina |