Comment 4 for bug 435674
Revision history for this message
| Francis J. Lacoste (flacoste) wrote Re: [Bug 435674] Re: fti.py wants to lock all replication sets | #4 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
e2d829f
demo site
(Get the code!)
On October 7, 2009, Stuart Bishop wrote:
> I believe this behavior stops being a problem if we move the master for
> the auth replication set to a dedicated server that does not have a
> replica of the lpmain replication set.
>
> In this setup, the authdb tables will get locked on the Launchpad
> databases (launchpad_prod*). They will not be locked on the standalone
> database used for read only mode, as it is stand alone. They will not be
> locked on the authdb replication set master as there is no lpmain
> replica there.
>
The plan was to still have a replica of the lpmain replication set on the auth
master DB. Otherwise, we'll need to set-up another separate launchpad replica
for the ShipIt/OpenID servers.
--
Francis J. Lacoste
<email address hidden>