In Dave's feedback to me he raised three major points that I'll reproduce here because I'm sure other people will notice them too.
1. Spelling mistakes Easy for others to find and fix but you know how it is: one is less apt to see their own spelling mistakes. Plus, I've read the docu countless times, so I'm really not apt to see my own mistakes. That's why we have peer reviewers/editors. :-) 2. slave plugin is not an applier First let me say: I think it's crucial to foster in the user via the docs a particular way of thinking. I note in the Details section of the Slave Applier docu that the slave plugin is not in fact a TransactionApplier subclass. One of the first and most fundamental confusions of Drizzle replication that I encountered and was only clarified by first talking to Monty was that slave is a "special case" (it's a Daemon and queue produces/consumer), and that "real Drizzle replication" is the replicator-applier paradigm. This is fine from a technical point of view, but (and this refers to point #3): it's imperative, imho, to think from the user's point of view. One "true" replication system and one "oddball" (slave), especially given that slave is not the oddball for the user but probably the first thing they want to use, is both confusing for the user and bad for Drizzle because it looks like we have this awesome system of replication streams but Drizzle's native replication between two servers doesn't use it. In my opinion, the way of thinking we must communicate singularly and clearly via the docs is "replication streams". Under the hood, slave does magical things, but from the user's point of view I think we can call it an applier because in the end it does apply replication events/transactions to a slave. Once the user's mind is habituated to the replication streams paradigm, they can ask "how does such-and-such actually implement the paradigm?" Then they'll discover that slave is a special case, but they'll discover it within the singular replication streams paradigm rather than some other quasi-replication system. In the long run, the best solution for this, imho, is a lot of docs in the Details section of Slave Applier. Savvy DBAa will quickly realize that slave is a special case in the replication stream paradigm, but if its raison d'être is well documented (particularly why Drizzle doesn't have native replication that's "pure" applier-replicator) then they'll accept the paradigm and its special case plugin, slave. Other opinions? 3. Division of Replication and slave Plugin Docs In short: the user docs are for users. :-) When I first wanted to setup native Drizzle replication, I naturally went to the Replication section and found nothing helpful. Since I was aware of the slave plugin, I went to it's docu and that was helpful enough, but it left me wondering: is this replication? I felt I was missing a crucial chunk of info because the slave plugin didn't really talk about or care about replication streams. Hence my frustration which lead to these new docs. -Daniel Le 18 mars 2012 à 00:49, David Shrewsbury a écrit : > Agreed, this was much needed. > > FYI, I've replied to Daniel off-list. > > > On Sun, Mar 18, 2012 at 12:52 AM, Henrik Ingo <[email protected]> > wrote: > Thanks Daniel! With this work completed, we've really come a long way > in making Drizzle 7.1 end user friendly! > > Guys, please help Daniel by reviewing. He has the main Drizzle talk at > MySQL user conf, so your help here really means something. > > Wrt the messages documentation: Shouldn't that be moved to some kind > of internals section? (Which doesn't exist yet, I know.) > > henrik > > On Sat, Mar 17, 2012 at 10:03 PM, Daniel Nichter <[email protected]> wrote: > > I'm proud to announce the result of a lot of writing, testing, hacking, > > poking around the source code, finding and reporting bugs, and acting like > > a naïve end user: > > https://code.launchpad.net/~drizzle-developers/drizzle/replication-docs-7.1 > > > > Completely rewritten, up-to-date, correct, and "complete" information (and > > a few examples) about Drizzle 7.1 replication. My goal was docu that could > > take a reader from zero knowledge of the subject to up, running, and > > administering slave-based Drizzle replication. > > > > The docu is only "complete" in quotes à propos this goal because _a lot_ > > remains to be written. For example, a whole topic on troubleshooting is > > needed. Another topic or section about multi-master setups is needed. And > > let's not discuss the thorny question of backup/restore+replication since > > there are no "binary logs". > > > > Before I propose for merging, would some people (i.e. Dave) please check > > the branch, make html, and proof-read all docu in the Replication section? > > I suggest to start at the firs topic and go topic by topic because the docu > > builds on itself. I know it's a lot to ask but: quick feedback is > > imperative because at PLMCE in April I'll be talking about this stuff, so > > the docu needs to be done and done well before then (and ideally before I > > begin writing my talk/presentation). > > > > Info related to replication in the Plugins sections has been moved into the > > Replication section. That is: everything related to replication is in the > > Replication section, pure and simple. > > > > I have not updated the Messages topic because that's less important for end > > users. > > > > -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 > > > > -- > [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 >
_______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
