You have a data-aware function (invoked by onRegion) from which you call getAll in region X. That's correct.
Is region X the region on which the function is executed? Or is it another region? X is a Different region. If multiple regions are involved, are they co-located? Not colocated. How do you determine the keys to getAll? Let's just say that key passed to both region is same we basically merge data and return the result. Are they passed into the function? If so, as a filter or as an argument? As an argument. With filter could have been a better approach. What does optimizeForWrite return? How many members are running? Have to check and confirm. We have 12 nodes running. Tue, Aug 20, 2019, 2:32 AM Barry Oglesby <[email protected]> wrote: > Ashish, > > Sorry for all the questions, but I want to make sure I understand the > scenario. You have a data-aware function (invoked by onRegion) from which > you call getAll in region X. Is region X the region on which the function > is executed? Or is it another region? If multiple regions are involved, are > they co-located? How do you determine the keys to getAll? Are they passed > into the function? If so, as a filter or as an argument? What does > optimizeForWrite return? How many members are running? > > Thanks, > Barry Oglesby > > > > On Mon, Aug 19, 2019 at 1:19 PM aashish choudhary < > [email protected]> wrote: > >> We use data aware function and We make a call to region X from a data >> aware function using getLocalData API and then we do getall. Recently we >> introduced redundancy for our partitioned region and now we are getting >> duplicate enteries for that region X from function response. My hunch is >> that it is becuase of getLocalData + get all call so if we will change it >> to getLocalPrimaryData(hope name is correct) for region X it should only do >> get for primary copies. Is that correct way of handling it.? >> >> With best regards, >> Ashish >> >
