<div dir="ltr"><div><div><div><div>I guess the grouper could use a KeyAffinityService (or something similar) to generate a key local to each node and return that instead of "0" or "1".<br></div>However, you won't have any guarantee that the keys will stay on the same node if the cache topology changes (e.g. another node joins).<br>
<br></div>It used to be that the actual address of the node would (almost) always be mapped to that node, but that was just an implementation detail, and it never worked 100%. <br><br>Ben, do you think being able to pin a key "permanently" to a node would be useful?<br>
<br></div>Cheers<br></div>Dan<br><br><br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, May 21, 2013 at 6:31 PM, Galder Zamarreño <span dir="ltr"><<a href="mailto:galder@redhat.com" target="_blank">galder@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hmmm, one hacky way might be to hold on to the grouper instance passed in via configuration, and once the cache manager has been started, set it in the grouper and use to query either the address, or the physical address (via EmbeddedCacheManager.getTransport…)?<br>
<div><div class="h5"><br>
On May 14, 2013, at 6:34 PM, cotton-ben <<a href="mailto:ben.cotton@ALUMNI.RUTGERS.EDU">ben.cotton@ALUMNI.RUTGERS.EDU</a>> wrote:<br>
<br>
> I am playing with the Infinispan 5.3 quick-start package to exercise my usage<br>
> of the Grouping API. As we know the quick start package is made up of<br>
> AbstractNode.java, Node0.java, Node1.java and Node2.java (plus a<br>
> util/listener).<br>
><br>
> My ambition is to demonstrate<br>
><br>
> 1. that any Cache<K,V>.put("DIMENSION.xxx",v) will flow through my Grouper<br>
> and "pin" that key in the Cache at @Node=0.<br>
> 2. that any Cache<K,V>.put("POSITION.xxx",v) will flow through my Grouper<br>
> and "pin" that key in the Cache at either @Node=1 or @Node=2 .<br>
><br>
> Here is my AbstractNode#createCacheManagerProgramatically() config:<br>
><br>
> private static EmbeddedCacheManager createCacheManagerProgramatically() {<br>
> return new DefaultCacheManager(<br>
> GlobalConfigurationBuilder.defaultClusteredBuilder()<br>
> .transport().addProperty("configurationFile", "jgroups.xml")<br>
> .build(),<br>
> new org.infinispan.configuration.cache.ConfigurationBuilder()<br>
> .clustering()<br>
> .cacheMode(CacheMode.DIST_SYNC)<br>
> .hash().numOwners(1).groups().enabled(Boolean.TRUE)<br>
> .addGrouper(new<br>
> com.jpmorgan.ct.lri.cs.ae.test.DimensionGrouper<String>())<br>
> .build()<br>
> );<br>
> }<br>
><br>
> And here is my Grouper<T> implementation<br>
><br>
> public class DimensionGrouper<T> implements Grouper<String> {<br>
> public String computeGroup(String key, String group) {<br>
> if (key.indexOf("DIMENSION.")==0) {<br>
> String groupPinned = "0";<br>
> System.out.println("Pinning Key=["+key+"] @Node=["+groupPinned+"]");<br>
> //node= exactly 0<br>
> return groupPinned;<br>
> } else if (key.indexOf("POSITION.")==0) {<br>
> String groupPinned = ""+(1+ (int)(Math.random()*2));<br>
> System.out.println("Pinning Key=["+key+"] @Node=["+groupPinned+"]");<br>
> //node= {1,2}<br>
> return groupPinned;<br>
> } else {<br>
> return null;<br>
> }<br>
> }<br>
><br>
> public Class<String> getKeyType() {<br>
> return String.class;<br>
> }<br>
><br>
> }<br>
><br>
> The "logic" is working correctly ... i.e. when from Node2.java I call<br>
><br>
> for (int i = 0; i < 10; i++) {<br>
> cacheDP.put("DIMENSION." + i, "DimensionValue." + i);<br>
> cacheDP.put("POSITION." + i, "PositionValue." + i);<br>
><br>
> }<br>
><br>
> My DimensionGrouper is returning "0" from computeGroup(). My question is<br>
> how in Infinispan can I map the computeGroup() return value to a physical<br>
> Node? I.e. How can I make it so that when computeGroup() returns "0", I<br>
> will *only* add that <K,V> entry to the Cache @Node 0?<br>
><br>
><br>
><br>
><br>
><br>
> --<br>
> View this message in context: <a href="http://infinispan-developer-list.980875.n3.nabble.com/Re-How-to-get-Grouper-T-computeGroup-key-return-value-to-map-to-physical-Node-tp4027134.html" target="_blank">http://infinispan-developer-list.980875.n3.nabble.com/Re-How-to-get-Grouper-T-computeGroup-key-return-value-to-map-to-physical-Node-tp4027134.html</a><br>
> Sent from the Infinispan Developer List mailing list archive at Nabble.com.<br>
> _______________________________________________<br>
> infinispan-dev mailing list<br>
> <a href="mailto:infinispan-dev@lists.jboss.org">infinispan-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/infinispan-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/infinispan-dev</a><br>
<br>
<br>
</div></div>--<br>
Galder Zamarreño<br>
<a href="mailto:galder@redhat.com">galder@redhat.com</a><br>
<a href="http://twitter.com/galderz" target="_blank">twitter.com/galderz</a><br>
<br>
Project Lead, Escalante<br>
<a href="http://escalante.io" target="_blank">http://escalante.io</a><br>
<br>
Engineer, Infinispan<br>
<a href="http://infinispan.org" target="_blank">http://infinispan.org</a><br>
<div class="HOEnZb"><div class="h5"><br>
<br>
_______________________________________________<br>
infinispan-dev mailing list<br>
<a href="mailto:infinispan-dev@lists.jboss.org">infinispan-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/infinispan-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/infinispan-dev</a><br>
</div></div></blockquote></div><br></div>