You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It appears that go routines 1473 and 2294 are attempting to grab the same lock - with 1473 holding the lock for more than 10 minutes whilst 2294 is waiting to access it (and presumably after 10 minutes is giving up and exiting).
Seems strange that this seems to happen at the same time each day - at around 4:30am UTC.
@lazynina - not sure if this is only affecting me or if it is a local issue (please advise if you can)
The text was updated successfully, but these errors were encountered:
Thanks @lazynina, I'll investigate further. This is a new docker container arrangement. Previously archival w/ pg was consuming >38gb ram continually (just syncing), but this time it's down in the 20s and was thinking it was running ok.
Seems to run fine other than these deadlocks, but maybe I've inadvertently limited resources somewhere.. I'll take another look.
Receiving an backend exit most days at the same time (~04:30 UTC) with the following error:
(I should note this example is taken from this afternoon after a restart and subsequent exit)
It appears that go routines 1473 and 2294 are attempting to grab the same lock - with 1473 holding the lock for more than 10 minutes whilst 2294 is waiting to access it (and presumably after 10 minutes is giving up and exiting).
Seems strange that this seems to happen at the same time each day - at around 4:30am UTC.
@lazynina - not sure if this is only affecting me or if it is a local issue (please advise if you can)
The text was updated successfully, but these errors were encountered: