SSO Database access and failover: Master vs Slaves
Bug #824350 reported by
Steve McInerney
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical SSO provider |
Fix Released
|
High
|
Unassigned | ||
Bug Description
Currently there isn't an automatic (degraded) failover between the SSO Master DB, and the R/O Slaves in the event the master fails hard.
Understanding is that this degraded failover was always intended but is not yet working in all cases.
Possibly related - that all Read Only requests to a Database would prefer to use one of the Slaves, vs the Master.
| tags: | added: canonical-losa-isd |
| Changed in canonical-identity-provider: | |
| status: | New → Confirmed |
| importance: | Undecided → Critical |
| assignee: | nobody → Corey Goldberg (coreygoldberg) |
Revision history for this message
| Stuart Metcalfe (stuartmetcalfe) wrote | #1 |
| Changed in canonical-identity-provider: | |
| status: | Confirmed → In Progress |
| Changed in canonical-identity-provider: | |
| status: | In Progress → Triaged |
| assignee: | Corey Goldberg (coreygoldberg) → nobody |
| Changed in canonical-identity-provider: | |
| status: | Triaged → Confirmed |
Revision history for this message
| Stuart Metcalfe (stuartmetcalfe) wrote | #2 |
| Changed in canonical-identity-provider: | |
| importance: | Critical → High |
| Changed in canonical-identity-provider: | |
| status: | Confirmed → Fix Released |
To post a comment you must log in.
I believe the read-only -> slaves feature is something we get with Django 1.3, which we recently switched to. However, I think that should be a separate bug.