When switching to read-only mode, we're left with lots of "idle/select waiting" connections to the DBs which may be blocking the schema upgrade process
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
High
|
Stuart Bishop |
Bug Description
During the 10.02 rollout, we dropped the read-only.txt file into the coderoot to switch to read-only and noticed that Launchpad had then switched into read-only mode per the message on every page. However, we were still seeing lots of "idle/select waiting" processes from the appservers against the launchpad_prod_N DBs even though the configs state:
ro_main_master: dbname=
ro_main_slave: dbname=
We're not sure if this blocks the schema upgrade in some way (per bug 531833 it's hard to tell whether the schema upgrade is being blocked or not), but after restarting all the app servers the schema upgrade seemed to progress a little better, so it suggests this was an issue.
affects: | launchpad → launchpad-foundations |
Changed in launchpad-foundations: | |
status: | New → Triaged |
Changed in launchpad-foundations: | |
milestone: | none → 10.03 |
Changed in launchpad-foundations: | |
milestone: | 10.03 → 10.04 |
Changed in launchpad-foundations: | |
status: | Triaged → In Progress |
assignee: | nobody → Guilherme Salgado (salgado) |
Changed in launchpad-foundations: | |
status: | In Progress → Fix Committed |
Changed in launchpad-foundations: | |
assignee: | Guilherme Salgado (salgado) → nobody |
tags: | added: canonical-losa-lp |
Changed in launchpad-foundations: | |
status: | Fix Committed → Fix Released |
These connections were seen at least 30 minutes after the read-only switch, fwiw (just in case it wasn't clear whether they were just still there because there we still queries waiting to finish)