Developers split over split-lock detection
Developers split over split-lock detection
Posted Dec 13, 2019 8:47 UTC (Fri) by GoodMirek (guest, #101902)In reply to: Developers split over split-lock detection by bof
Parent article: Developers split over split-lock detection
Maybe, but the issue could be caused by a faulty software or a hacked VM. Contract termination seems as a last resort, e.g. in case the customer does not cooperate. However, in the meantime there can be a huge performance issue caused to many others.
E.g. if I run 100 faulty worker nodes, spread over 100 random hosts, each host having 48 CPU cores (96 vCPU's due to hyperthreading/SMT), that looks like a potentially significant issue.
E.g. if I run 100 faulty worker nodes, spread over 100 random hosts, each host having 48 CPU cores (96 vCPU's due to hyperthreading/SMT), that looks like a potentially significant issue.