News for hackers. Stuff that matters.
Re:eBPF will help solve service mesh by getting rid of sidecars by q3k on Thursday December 09, 2021 @06:10PM (#29504365)
You don’t :).

To do it properly you want a maglev-style layer that allows for withdrawals/drains of application servers with minimal disruption thanks to a minimum disruption maglev-style hash and draining support. This will allow you to first drain the given application server (continue maintaining existing connections, but send new ones to a secondaries for that part shard) before fully taking down the instance.

Re:eBPF will help solve service mesh by getting rid of sidecars by rhizome on Thursday December 09, 2021 @09:21PM (#29505727)
Sounds like Apache's graceful-restart.
Re:eBPF will help solve service mesh by getting rid of sidecars by transitorykris on Thursday December 09, 2021 @10:46PM (#29506173)
Sort of. Processes on the same node (graceful restart) vs processes on different nodes (maglev).
Re:eBPF will help solve service mesh by getting rid of sidecars by rhizome on Sunday December 12, 2021 @07:03PM (#29535042)
Eh, a signal is a signal even if it's an RPC, but my point was to focus on the "waiting for something to end or empty before restarting" part.