!zghijEASpYQWYFzriI:nixos.org

Hydra

392 Members
111 Servers

You have reached the beginning of time (for this room).


SenderMessageTime
9 Feb 2022
@amanda:camnet.siteAmanda (she/her) Unless the 'COMMIT' psql query differs from the ->commit method, the only place that is causing all these idle connections is hydra-init? 14:59:24
@amanda:camnet.siteAmanda (she/her)oh. It's hydra-queue-runner, I just tried killing active hydra proccesses and seeing which made the entries in pg_stat_activity go away, and it was hydra-queue-runner. For some reason it's got a lot of idle connections with the query of 'COMMIT'15:08:08
@grahamc:nixos.org@grahamc:nixos.orghmmm15:15:44
@grahamc:nixos.org@grahamc:nixos.orglike the query is still running, or?15:15:51
@grahamc:nixos.org@grahamc:nixos.org das_j: I'm coming around to test that ldap PR and I am just struggling to get excited about digging in lol 15:16:19
@amanda:camnet.siteAmanda (she/her) grahamc (he/him): Yes, I think that hydra-queue-runner might be leaking the connection. There's 10-20 connections all started at the same time, then never closed 15:17:27
@grahamc:nixos.org@grahamc:nixos.org if the COMMIT is still running then it would not be a leaked connection, it is waiting for postgres to finish 15:17:50
@amanda:camnet.siteAmanda (she/her) pg_stat_actibity has it listed as idle state 15:18:07
@grahamc:nixos.org@grahamc:nixos.orggotcha15:18:12
@amanda:camnet.siteAmanda (she/her) so I'm working under the assumtion that means commit just was the last query ran 15:18:27
@grahamc:nixos.org@grahamc:nixos.orgyeah15:18:32
@grahamc:nixos.org@grahamc:nixos.orgit sounds like it started a worker thread with a connection to handle a build and now it is waiting15:18:42
@amanda:camnet.siteAmanda (she/her)"At the same time" +- some milliseconds, all within the same couple seconds at least15:19:32
@grahamc:nixos.org@grahamc:nixos.org I am hesitant to call it a leak exactly, because the # of connections is very stable for both h.n.o and ajs124 's, but does seem like it would be good to be able to tune that 15:22:24
@amanda:camnet.siteAmanda (she/her) Just checked hydra-queue-runner, lots of messages like this, stedially increasing: warning: 48 concurrent database updates; PostgreSQL may be stalled 15:24:28
@grahamc:nixos.org@grahamc:nixos.orgyeah, there's some tuning that would be good15:24:52
@grahamc:nixos.org@grahamc:nixos.orgI wonder if there are some already15:24:56
@grahamc:nixos.org@grahamc:nixos.orgyes!15:25:15
@grahamc:nixos.org@grahamc:nixos.org max_db_connections defaults to 128 15:25:29
@amanda:camnet.siteAmanda (she/her)I'm not sure what postgres defaults to, but I've not changed it15:28:17
@amanda:camnet.siteAmanda (she/her)( Nor even how to do so )15:29:44
@amanda:camnet.siteAmanda (she/her)max_db_connections seems to have been the knob I needed though, danke15:32:45
@amanda:camnet.siteAmanda (she/her)the default may need to be tweaked, not sure if the postgres connection limit is global or per-database15:33:15
@casey:hubns.netcransomit's a global setting.15:37:24
@janne.hess:helsinki-systems.dedas_j
In reply to @grahamc:nixos.org
das_j: I'm coming around to test that ldap PR and I am just struggling to get excited about digging in lol
No worries ;)
16:03:24
@grahamc:nixos.org@grahamc:nixos.orgokay but some worries because I'm supposed to :P 16:06:28
@hexa:lossy.networkhexahopefully we can soon slap kanidm in there and get rid of slapd 🙂16:08:51

Show newer messages


Back to Room ListRoom Version: 6