I execute an application on two computers, each with a CouchDB model. Now when the model changes, the view on the other computer get's updated, too. But when the order of changes is wrong, there will be errors (e.g. edit an item before it was added).
> Why do you need replicator to follow exact the order in which > documents were added? What's the case? > -- > ,,,^..^,,, > > > On Thu, Mar 26, 2015 at 4:52 AM, Tamriel <[email protected]> wrote: > > Hello! > > > > A replicate all changes from Server A to B to C. Sometimes the order of > > changes is mixed, > for example: > > On A I add doc 'one' then doc 'two'. > > On C appear two changes: First doc 'two' then doc 'one'. > > > > I set the number of worker_processes from 4 to 1 in all involved databases, > > but there > was no improvement. > > > > I would be great if we can find a solution to enforce order. > > > > Best regards, > > Tamriel
signature.asc
Description: Message signed with OpenPGP using GPGMail
