Closed Bug 433341 Opened 15 years ago Closed 14 years ago
Move database load from master to slaves
This means adding this functionality to Tiki. It seems like it should go into the database layer. (I was sure we already had a bug for this: please dupe this if it already exists.)
This blocks a release blocker - what's our ETA?
Severity: normal → major
Nearly done - aiming to get the patch into review tomorrow.
To test this, you'll need a shadowdb, and to add the following lines to your db/local.php e.g. $shadow_host ='[host]'; $shadow_user='[username]'; $shadow_pass='[password]'; $shadow_dbs='[database_name]';
Comment on attachment 323776 [details] [diff] [review] Basic master-slave support for tikiwiki This works on khan - would like to see some tests instead of the echo/debug statements, but let's get this checked in and up in staging so we can test it.
Attachment #323776 - Flags: review?(morgamic) → review+
Comment on attachment 323776 [details] [diff] [review] Basic master-slave support for tikiwiki Also, make sure that when we deploy this we make people aware of the config change. Laura - that is up to you.
Fixed in r15181. We will load test and test on stage next.
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
14 years ago
Whiteboard: [server side] → [server side] tiki_triage sumo_triage
Whiteboard: [server side] tiki_triage sumo_triage → [server side] tiki_feature
The database layer was almost entirely rewritten as part of making PDO optional. Direct upstreaming did not make sense. As a result, a different implementation was made. However, it should behave in a very similar way and be compatible. Tiki commit r22653 and installer updates in r22654. How do I flag tiki_upstreamed?
(In reply to comment #8) > How do I flag tiki_upstreamed? Simply add the string to the Whiteboard field (I just did it for this bug). Thanks!
Whiteboard: [server side] tiki_feature → [server side] tiki_feature tiki_upstreamed
firstname.lastname@example.org didn't have "editbugs" in Bugzilla; he now does.
You need to log in before you can comment on or make changes to this bug.