This requires the knowledge of events (ops), applied before the gateway sender? The wan gii could be better solution as it eliminates the need for knowing the events/ops...
-Anil. On Fri, Jan 19, 2018 at 3:14 PM, Barry Oglesby <[email protected]> wrote: > Mike, > > I've implemented that pattern before using functions. First a > PrimaryGatewayDeliveryFunction to get a specific entry from the region > without deserializing it, create an event on it and deliver the event to > the primary GatewaySender. Then another function ( > SecondaryGatewayDeliveryFunction) thats invoked from the > PrimaryGatewayDeliveryFunction on the secondary to put the same event in > the secondary GatewaySender. This same idea could be internalized in a > touch operation, although we'd have to think about things like > CacheListeners and clients. Would we want those to be updated as well? > Also, if we're thinking about this kind of idea, maybe its time to revisit > WAN GII? > > Thanks, > Barry Oglesby > > > On Thu, Jan 18, 2018 at 12:37 PM, Xu, Nan <[email protected]> wrote: > >> that certainly helps. For us, the sender not started because some >> configuration issues. But in prod, if somehow the data get out of sync, it >> would be very useful. >> >> >> >> *From:* Michael Stolz [mailto:[email protected]] >> *Sent:* Thursday, January 18, 2018 2:34 PM >> *To:* [email protected] >> *Subject:* Re: sync up 2 data centers >> >> >> >> This get/put trick is a frequent enough pattern that maybe we should add >> a "touch" API that causes the touched entry to be pushed to the WAN gateway >> sender. That would be able to bypass the de/serialization that get/put >> incurs. >> >> >> -- >> >> Mike Stolz >> >> Principal Engineer, GemFire Product Lead >> >> Mobile: +1-631-835-4771 <(631)%20835-4771> >> >> Download the new GemFire book here. >> <https://urldefense.proofpoint.com/v2/url?u=https-3A__content.pivotal.io_ebooks_scaling-2Ddata-2Dservices-2Dwith-2Dpivotal-2Dgemfire&d=DwMFaQ&c=SFszdw3oxIkTvaP4xmzq_apLU3uL-3SxdAPNkldf__Q&r=HB5LZowSGF4DiMmOUsCX6Q&m=kInf2QLMnQexWXx63FzptV9PDMSBMnIV0dWVhz7svHA&s=T3-hY3K3urBveTfDfPbgMScV3uGJeMTrqdM5btYLVLA&e=> >> >> >> >> On Thu, Jan 18, 2018 at 12:25 PM, Anilkumar Gingade <[email protected]> >> wrote: >> >> The get() does not replicate the data; put() does...If you don't know the >> entries that are not replicated then you may have to do put() with all the >> entries; that could be expensive... >> >> >> >> Any reason why sender is not started... >> >> >> >> -Anil. >> >> >> >> >> >> On Wed, Jan 17, 2018 at 4:05 PM, Michael Stolz <[email protected]> wrote: >> >> You can write a function to "touch" (read get/put) the entries that >> didn't get replicated and run it on the DC1 side after the sender has been >> started, and they will be replicated automatically. >> >> >> -- >> >> Mike Stolz >> >> Principal Engineer, GemFire Product Lead >> >> Mobile: +1-631-835-4771 <(631)%20835-4771> >> >> Download the new GemFire book here. >> <https://urldefense.proofpoint.com/v2/url?u=https-3A__content.pivotal.io_ebooks_scaling-2Ddata-2Dservices-2Dwith-2Dpivotal-2Dgemfire&d=DwMFaQ&c=SFszdw3oxIkTvaP4xmzq_apLU3uL-3SxdAPNkldf__Q&r=HB5LZowSGF4DiMmOUsCX6Q&m=kInf2QLMnQexWXx63FzptV9PDMSBMnIV0dWVhz7svHA&s=T3-hY3K3urBveTfDfPbgMScV3uGJeMTrqdM5btYLVLA&e=> >> >> >> >> On Wed, Jan 17, 2018 at 12:56 PM, Xu, Nan <[email protected]> wrote: >> >> If the gateway sender was not running and new value get inserted to DC1, >> is there an easy way to make DC2 sync up? Any suggestion? I can think of >> a query based on timestamp and Export then import. Something better than >> this? >> >> >> >> Thanks, >> >> Nan >> ------------------------------ >> >> This message, and any attachments, is for the intended recipient(s) only, >> may contain information that is privileged, confidential and/or proprietary >> and subject to important terms and conditions available at >> http://www.bankofamerica.com/emaildisclaimer. If you are not the >> intended recipient, please delete this message. >> >> >> >> >> >> >> ------------------------------ >> This message, and any attachments, is for the intended recipient(s) only, >> may contain information that is privileged, confidential and/or proprietary >> and subject to important terms and conditions available at >> http://www.bankofamerica.com/emaildisclaimer. If you are not the >> intended recipient, please delete this message. >> > >
