Re: [Maria-developers] Thoughts on Global Transaction ID, parallel slave, and multi-source replication

2012-08-10 Thread Stewart Smith
Kristian Nielsen writes: > Stewart Smith writes: > >> Idea: if txn touches more than one database, record as metadata the >> position of other db, so slave just has to wait for at least that id to >> be applied in other database before applying this txn in this >> source. This seems like a relat

Re: [Maria-developers] Thoughts on Global Transaction ID, parallel slave, and multi-source replication

2012-08-10 Thread Stewart Smith
Kristian Nielsen writes: > Stewart Smith writes: > >> Kristian Nielsen writes: >>> https://mariadb.atlassian.net/browse/TODO-171 >> >> this seems to be private, and I can't view even having created a JIRA >> account. > > Oops :-( Very sorry about that. I *think* I fixed it now, at least I

Re: [Maria-developers] Thoughts on Global Transaction ID, parallel slave, and multi-source replication

2012-08-10 Thread Kristian Nielsen
Stewart Smith writes: > Idea: if txn touches more than one database, record as metadata the > position of other db, so slave just has to wait for at least that id to > be applied in other database before applying this txn in this > source. This seems like a relatively simple solution to the probl

Re: [Maria-developers] Thoughts on Global Transaction ID, parallel slave, and multi-source replication

2012-08-10 Thread Kristian Nielsen
Stewart Smith writes: > Kristian Nielsen writes: >> https://mariadb.atlassian.net/browse/TODO-171 > > this seems to be private, and I can't view even having created a JIRA account. Oops :-( Very sorry about that. I *think* I fixed it now, at least I could open the link after logging out, bu

Re: [Maria-developers] Thoughts on Global Transaction ID, parallel slave, and multi-source replication

2012-08-10 Thread Stewart Smith
Sergei Golubchik writes: > On Aug 10, Stewart Smith wrote: >> >> > Suppose we instead make the decision on the _master_ on how to split >> > up the replication stream for parallel apply. Instead of a single >> > server-id for the master, we can have multiple - let us call them >> > "Source ID". >