Thanks Alfke for quick reply, we want use sg-replicate for active-active scenarioes. two syncgateway replication, and each one will be connected respective couchbase cluster. i am using a same config file in both syncgateway. And clients will be connected to both syncgateways and serving requests.
we are using the webhooks for activating clients, we can not have different configurations in both syncgateways as request will be of similar kind in both syncgateways. if the request sent SYNC1 and webhook triggered to activate. The same request will be replicated to SYNC 2 by sg-replicate, again webhook triggers for activating client which is already activated. webhooks used for sending events, why do we need same events multiple times. please let me know is it correct usage of webhook. On Tuesday, July 5, 2016 at 12:15:33 PM UTC+5:30, arihant rk 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 > syncgateway. > we are using webhooks for triggering pending documents which changes state > as it triggers to webservices. > > 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. > any solution to stop webhook triggering in replicated syncgateway? > -- 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/fc6552c8-1e31-4dc7-8259-daa2a4822f53%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
