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 Download the new GemFire book here. <https://content.pivotal.io/ebooks/scaling-data-services-with-pivotal-gemfire> 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://content.pivotal.io/ebooks/scaling-data-services-with-pivotal-gemfire> >> >> 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. >>> >> >> >
