Re: [Mysqlfs-general] mysqlfs patch

[Michal L. <mi...@lo...>]

Andrew Rose wrote:
> On 21/08/07, Michal Ludvig <mi...@lo...> wrote:
> 
>> Not in the immediate future, sorry. I don't do any active development on
>> mysqlfs anymore.
> 
> So if your not actively developing mysqfs anymore, has anyone else
> picked or is going to pick it up that you know of?

As far as I know it just sits there on SourceForge and that's it.

It was an interesting experience to take over the codebase and put it 
into shape but as I don't use it myself I don't have much interest in 
spending time on it.

>> I suggest you reconfigure the DB instead of crossing fingers ;-)
> 
> Sorry about my reaction in the last post BTW, I know you where trying
> to be helpful. Your right though, I really shouldn't cross my fingers.

I still wonder what scenario leads to the duplicate keys and subsequent 
replication failure. Do you write to the same mysqlfs on both hosts? 
Even if you create a file on "db1" and another file on "db2" they should 
have assigned different inode numbers. Perhaps if you write to a single 
file on both DBs it the INSERT on line 558 of query.c may fail. Hmm... 
Try changing it to REPLACE, ie "REPLACE INTO data_blocks ...". But I'm 
afraid you may end up with a data corruption if blindly replacing blocks 
like this. But your original solution that simply didn't do the write on 
detected conflict wasn't much more corruption proof either. In both 
cases you'd lose a write that you expected to go through.

I personally wouldn't run it in master-master setup, it's a bit 
complicated to synchronize them, not a simple "one-liner" solution.

Michal