Hi Swapnil:
Right, and then we execute that function on that node. Now assume during that
function execution time(first user thread) two things happens simultaneously..
1. we move that bucket to other node.
2. And other user thread execute function with same set of keys on other node,
which first thread is still executing.
Basically we need to make sure while function execution we don't move the
primary bucket.
Thanks.Hitesh
From: Swapnil Bawaskar <sbawas...@pivotal.io>
To: dev@geode.apache.org; Hitesh Khamesra <hitesh...@yahoo.com>
Sent: Friday, March 24, 2017 1:55 PM
Subject: Re: GEODE-2714 Proposal for new api on Function interface (Please
read)
Here is the link: https://issues.apache.org/jira/browse/GEODE-2714
Hi Hitesh,
Before executing a function, we build a list of buckets that the function needs
to execute on and then we build the function context using only those buckets.
So, as long as the function is using the context to get the local data set, it
should not see the data twice, even if rebalance was in progress.
When you saw this behavior, was the function using the function context?
Thanks!
On Fri, Mar 24, 2017 at 1:21 PM Jared Stewart <jstew...@pivotal.io> wrote:
Can you give a link to the proposal?
Thanks,
Jared
> On Mar 24, 2017, at 12:57 PM, Hitesh Khamesra <hitesh...@yahoo.com.INVALID>
> wrote:
>
> Please let us know your opinion on that.
> Thanks.Hitesh
