Hi, On Feb 17, 2012, at 8:41 PM, Daniel Nichter wrote:
<snip> > The big challenge in that list is slave which currently reads a config file. > It should be possible to start Drizzle with slave enabled, but no config, and > then config and connect to the master dynamically. After all, MySQL can > dynamically re-connect to or change the master. I'm not sure if the slave > code is amenable to this requirement, but it must be made amenable else > replication will suffer a serious blow to usability. So the idea was that plugins would only be enabled based on what the user needed. I don't think we ever intended to match MySQL functionality straight out of the box. Leaner and meaner and only what you need and whatnot... That said, the slave plugin cannot be turned on by default since there are no mechanisms to dynamically add masters or alter how it works other than through the slave config file. There were plans to add more to it in the future to re-enable some of the dynamic config features. But obviously we are not quite there. filtered_replicator - Should not be enabled by default. No sense adding it unless you are replicating events AND want to filter them. transaction_log - Should not be enabled by default. This is the file-based transaction log (not used by the slave) and is rather buggy, IMO. I almost feel like we should remove it from the tree... -Dave _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
