Page MenuHomePhabricator

Implement stateless TCP balancing in our LVS servers
Open, HighPublic

Description

Some of our scaling and/or DDoS problems really come down to limitations induced by our LVS servers' TCP state-tracking. We don't truly need state-tracking there, it's just an artifact of our present circumstances and the available kernel code. Quite a few distinct chunks of work need to come together to eliminate it:

  1. A proper chashing lvs scheduler kernel module - T86651
  2. Something like the ipvs "one packet scheduler" support that exists for UDP, but for TCP (I suspect all we have to do is remove the protocol checks in both ipvsadm and the kernel here.
  3. Pybal needs to be a bit more flap-resistant, somehow, because we don't want very minor artificial healthcheck failures causing a large number of RSTs, which is what would happen with stateless LVS otherwise. Related to T172124 and others.

Event Timeline

Restricted Application added a subscriber: Aklapper. · View Herald Transcript

The swap of Traffic for Traffic-Icebox in this ticket's set of tags was based on a bulk action for all such tickets that haven't been updated in 6 months or more. This does not imply any human judgement about the validity or importance of the task, and is simply the first step in a larger task cleanup effort. Further manual triage and/or requests for updates will happen this month for all such tickets. For more detail, have a look at the extended explanation on the main page of Traffic-Icebox . Thank you!