I think even using the FixedPartitionResolver <https://github.com/apache/incubator-geode/blob/develop/gemfire-core/src/main/java/com/gemstone/gemfire/cache/FixedPartitionResolver.java> the buckets will move between the nodes in case of a node crash or restart (given sufficient redundancy level). I also don't think that using the current host name in the FixedPartitionResolver would tie the data to a [expected] host, since it will not be necessarily executed on the host that needs to store the data.
So I second Jens, we should first understand the reason for such requirement and possibly come with alternative solution altogether. Sergey On Fri, Sep 11, 2015 at 4:53 PM, Jens Deppe <jde...@pivotal.io> wrote: > Rajiv, > > You could do something like that with Fixed Patitioning but that doesn't > give you exact control over buckets only the knowledge that buckets won't > move from host to host. However it is much more restrictive as it makes > adding additional nodes more restrictive. > > Regardless, the first question would be why you have that requirement. It > would be much better to try and remove the requirement rather than get > GemFire/Geode to do something sub-optimal. > > --Jens > > On Thu, Sep 10, 2015 at 10:01 PM, Rajiv Kumar <raku...@pivotal.io> wrote: > > > Hi, > > > > Is there any way we can fix the buckets to a specific node, so that the > > bucket sticks to same node irrespective of restarts. > > > > -- > > Thanks and Best Regards, > > > > Rajiv Kumar, > > >
