315106 - Provide mechanisms to control multiple shadowdbs and failovers

Status: NEW

(Bugzilla :: Bugzilla-General, enhancement)

Description

[Joel Peshkin]

Since it is possible for a shadow database to fail or just get overloaded, we should provide a mechanism that allows us to....

1) Automatically use the master for buglist if the shadow fails (param controlled)

2) Specify distinct shadow databases for colectstats and/or whining and/or buglist.

3) Independently control which will failover to use the master.

Comment 1

[Frédéric Buclin]

b.m.o is half dead actually. justdave is on vacation and aravind and polvi are both away. And the problem is that the DB replication has stopped for 15 hours now... We cannot use showdependencytree.cgi anymore because it says that the new bugs we are looking for do not exist (yet). So this bug definitely makes sense, yes.

Comment 2

[Frédéric Buclin]

This bug is retargetted to Bugzilla 3.2 for one of the following reasons:

- it has no assignee (except the default one)
- we don't expect someone to fix it in the next two weeks (i.e. before we freeze the trunk to prepare Bugzilla 3.0 RC1)
- it's not a blocker

If you are working on this bug and you think you will be able to submit a patch in the next two weeks, retarget this bug to 3.0.

If this bug is something you would like to see implemented in 3.0 but you are not a developer or you don't think you will be able to fix this bug yourself in the next two weeks, please *do not* retarget this bug.

If you think this bug should absolutely be fixed before we release 3.0, either ask on IRC or use the "blocking3.0 flag".

Comment 3

[Max Kanat-Alexander]

Bugzilla 3.2 is now frozen. Only enhancements blocking 3.2 or specifically approved for 3.2 may be checked in to the 3.2 branch. If you would like to nominate your enhancement for Bugzilla 3.2, set the "blocking3.2" flag to "?". Then, either the target milestone will be changed back, or the blocking3.2 flag will be granted, if we will accept this enhancement for Bugzilla 3.2.

This particular bug has not been touched in over eight months, and thus is being retargeted to "---" instead of "Bugzilla 4.0". If you believe this is a mistake, feel free to retarget it to Bugzilla 4.0.