Looks like we replied at the same time to Dave, and my last reply conflicts with yours here...
Le 18 févr. 2012 à 07:25, Henrik Ingo a écrit : > On Sat, Feb 18, 2012 at 2:13 PM, David Shrewsbury > <[email protected]> wrote: >> 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... > > You are both right. > > Currently many plugins are built so that they will not be loaded by > default, only if you add --add-plugin. This is probably what most here > think when someone says "by default". This is not intended to change. > > Otoh our deb and rpm packages package each plugin separately. They > take the approach that if you installed the plugin, you want to use > it. Therefore the packages will install a file in conf.d/ that does > --add-plugin. Currently many plugins make the server abort on startup > (due to missing configuration / bad default configuration). Daniel's > work is to fix this problem. > >> 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. > > What Daniel said: We have to make it work. In fact, it is recommended > (in MySQL world) not to configure replication from the config file but > always do it dynamically after server restart. (The rationale is > basically you don't want the server to start replicating from some > random master just because a restart happened.) Config via/inside Drizzle instead of via/from a config file might be ideal, but the code is certainly far from that at the moment. Since Drizzle replication is multi-master, we'd probably need a table like sys_replication.slaves in which to specify one slave DSN per row. Perhaps this is something we can plan for in the future, but I don't see it happening in 7.1. It does create a problem for what you, Henrik, mentioned above: deb and rpm packages want to install a file conf.d/, but it's difficult to have such a default slave config file. Perhaps we can find a middle ground: if no slave config file, or it's not valid, etc., then slave will load but log errors and disable itself. Then user can see, "Oh, I need to write a slave config file and restart Drizzle." -Daniel _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
