GitHub user neykov opened a pull request:
https://github.com/apache/incubator-brooklyn/pull/965
MySqlCluster dump based replication
When the binary log of the mysql master is truncated the only way to spin
up new slaves is to do a dump of the master and initialize the slave from it -
implemented here.
WARN: Not rebind compatible with previous version (TODO)
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/neykov/incubator-brooklyn mysqlcluster-dump
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-brooklyn/pull/965.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #965
----
commit 0de0a2a944b08437c4f0eda407265bd89a26147a
Author: Svetoslav Neykov <[email protected]>
Date: 2015-10-15T14:36:31Z
Dump based replication init
When the replication logs on master no longer start from the beginning a
database dump will be performed to initialize the slave
commit ad6ac1e00587071f227995808a1c76b1402e9bbf
Author: Svetoslav Neykov <[email protected]>
Date: 2015-10-15T14:40:26Z
Replace deprecated methods with preferred alternative
commit 15038ce2a85c83d7f7500b799f92484f80c37f0a
Author: Svetoslav Neykov <[email protected]>
Date: 2015-10-16T11:00:35Z
Don't block infinitely if any of the customize steps fail.
When changePassword fails the stop task won't ever get executed, but the
execution blocks on it, so it waits forever. The change will execute stop even
if there was a failure (as long as launch was successful), propagating the
initial error.
commit ccbee8e0587620bda5d82f5ef6409267e3a9706c
Author: Svetoslav Neykov <[email protected]>
Date: 2015-10-19T12:30:25Z
MySqlCluster dump based replication - filter databases
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
