On Sat, Feb 18, 2012 at 6:14 PM, Daniel Nichter <[email protected]> wrote:
>> 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.
>

7.1 is RC so none of this will happen in 7.1 anymore. The work
continues and this should be a goal just like the other things in your
list.

> 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."
>

For the packages there can be exceptions. That's not the main point.

But configuring replication dymanically is a best practice anyway. You
need to be able to start and stop the slave to freeze a readonly slave
for backups. (Currently this is also the case for Drizzle, even if it
needn't be in the future, since Stewart re-implemented .frm files as
protobuf-files-on disk.) You want to stop the slave for online
upgrades. Etc...

henrik

-- 
[email protected]
+358-40-8211286 skype: henrik.ingo irc: hingo
www.openlife.cc

My LinkedIn profile: http://www.linkedin.com/profile/view?id=9522559

_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help   : https://help.launchpad.net/ListHelp

Reply via email to