Saturday, 2023-03-11

fungiinterestingly, nl01 hasn't logged stopping the rax-ord state machine provider for 877113 yet, not sure if that means it's not fully in use00:02
fungiwe had quite a few spikes well above 10 building, leading me to suspect it is not00:03
funginope, my bad. i grepped wrong. it stopped at 18:48:11 (moments after deployment)00:04
fungiso the past ~6 hours have been with the new configuration, but we have a spike on the graph since then with 44 building nodes00:05
fungialso some others more sustained which are still well in excess of 2500:06
clarkbfungi: note the old provider can continue running for many hours still. But the new provider should do most of the work. Previously there was no new provider until the old provider went away00:11
clarkbI'm going to remove gitea01-04 from haproxy by hand again in order to see how gitea09-14 cope00:12
clarkband thats done00:14
clarkbthere is a definite load average jump since taking the old servers out of the load balancer, but so far it seems reasonable00:27
clarkbif that changes you can easily erenable the old 01-04 bcakends by restarting haproxy (easy disruptive method) or running haproxy socket commands to reenable them (documented but 8 comments instead of 1)00:30
*** dmsimard9 is now known as dmsimard17:58

Generated by 2.17.3 by Marius Gedminas - find it at!