This issue does not appear to have an issue weight set.
As a general guidelines use a weight of 1 for an access request issue or a simple
configuration update. Use this as a multiplier for setting the weight.
If you are unsure about what weight to set it is better to add a generous estimate and change it later.
If the weight on this issue is 8 or larger then it might be a good idea
to consider splitting this issue up into smaller pieces.
@craigf My only concern with closing this issue is that Development has been unable to find any reasoning in the LB code that points to why we didn't properly load balance afterwards. Infrastructure is the best group to determine that as they have access to the production environment (or determine we can't figure out why).
Yeah now that I've actually followed that thread through, I see I might have been too trigger happy closing this. I'm in a "cleaning house" end of the week mood. reopening.
@craigf , is this still an issue - given how much the DB ecosystem has changed over the last year? Rating it as an S2 for now (pending on your answer).
@albertoramos I think this is definitely stale, and as far as I know we've not observed this sort of behaviour in a long time. IIRC, the culprit ended up being pgbouncer saturation anyway, but I might be remembering this wrong as it was a long time ago.