To Bugzilla Support/Users, We are trying to do the following: 1. We have MySQL (5.5) Database setup with master and a slave database on another host. 2. We also have Bugzilla application configured (Version 3.0.4) on the MySQL instance. One issue which we have encountered with MySQL Replication is on the Slave host, the CPU continues to spin when it encounters a large INSERT/DELETE issued on a table without a Primary Key. 3. For tables installed by Bugzilla application, we noted there are many tables without a Primary Key. 4. But we would like the Bugzilla database to be part of a replication. 5. However we do not want to manually add Primary Keys to the tables created by the application as we do not know what impact it will have on its functionality. 1. Has anyone implemented above successfully? 2. Or have any suggestions/thoughts on possible workarounds? Any feedback will be very helpful.
Summary: MySQL Replication with Bugzilla, bugzilla tables present without primary key → MySQL Replication with Bugzilla, bugzilla tables present without primary key, CPU on slave host spins
This is a support question. Please see http://www.bugzilla.org/support for help.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.