> On Jul 4, 2016, at 11:45 PM, arihant rk <[email protected]> wrote: > > We have been trying out the sg-replicate which replicates clients requests > between syncgateway's for active-active scenarios. but we could see that > replication happens as like clients posting same request to another sync > gateway.
Yes. sg_replicate and Couchbase Lite use the same replication protocol. > we are seeing webhook is triggering twice, one for actual and other for > replicated syncgateway which should not be the case for active -active > scenarios. applications will receive webhook trigger multiplesfor the same > document. If you have web-hooks defined on both servers, and one server is replicating documents to the other, then yes, you would see the web-hooks fire on both servers. That’s expected behavior. The web-hook fires when a revision is added to that server. > any solution to stop webhook triggering in replicated sync gateway? Don’t configure web-hooks on that server? You’ll probably need to describe in more detail what you’re using the web-hooks for, why you need them on both servers, and why it’s wrong for them to fire on both. —Jens -- You received this message because you are subscribed to the Google Groups "Couchbase Mobile" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/mobile-couchbase/C1337866-F223-4D2E-87B5-D7686CC4620B%40couchbase.com. For more options, visit https://groups.google.com/d/optout.
