[JBoss JIRA] Created: (ISPN-359) Affinity accross caches - static or dynamic - infinispan-issues

[JBoss JIRA] Created: (ISPN-359) Affinity accross caches - static or dynamic

[JBoss JIRA] Created: (ISPN-1233)...

[JBoss JIRA] Created: (ISPN-312)...

Tero Heinonen (JIRA)

Tuesday, 2 March 2010 Tue, 2 Mar '10

9:03 a.m.

Affinity accross caches - static or dynamic ------------------------------------------- Key: ISPN-359 URL: https://jira.jboss.org/jira/browse/ISPN-359 Project: Infinispan Issue Type: Feature Request Components: Distributed Cache Affects Versions: 4.0.0.Final Reporter: Tero Heinonen Assignee: Manik Surtani Programmable affinity either through: 1) statically (e.g. annotating a certain field as the key for consistent hashing) - in our case this cannot be based on the hashCode() as the affinity requirement and object identity are not directly related 2) dynamically (e.g. providing a overridable/annotatable consistentHashCode() function) This would help to assign entities (in multiple Caches), which are needed together in the same nodes (to avoid remote lookups) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

Show replies by date

Manik Surtani (JIRA)

Monday, 8 March Mon, 8 Mar

5:28 a.m.

New subject: [JBoss JIRA] Updated: (ISPN-359) Affinity accross caches - static or dynamic

[ https://jira.jboss.org/jira/browse/ISPN-359?page=com.atlassian.jira.plugi... ] Manik Surtani updated ISPN-359: ------------------------------- Fix Version/s: 4.1.0.ALPHA2 4.1.0.Final Complexity: Medium (was: Low)

...

Affinity accross caches - static or dynamic ------------------------------------------- Key: ISPN-359 URL: https://jira.jboss.org/jira/browse/ISPN-359 Project: Infinispan Issue Type: Feature Request Components: Distributed Cache Affects Versions: 4.0.0.Final Reporter: Tero Heinonen Assignee: Manik Surtani Fix For: 4.1.0.ALPHA2, 4.1.0.Final Programmable affinity either through: 1) statically (e.g. annotating a certain field as the key for consistent hashing) - in our case this cannot be based on the hashCode() as the affinity requirement and object identity are not directly related 2) dynamically (e.g. providing a overridable/annotatable consistentHashCode() function) This would help to assign entities (in multiple Caches), which are needed together in the same nodes (to avoid remote lookups)

-- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

Manik Surtani (JIRA)

Monday, 22 March Mon, 22 Mar

10:31 a.m.

New subject: [JBoss JIRA] Updated: (ISPN-359) Provide mechanism for users to control data locality when using DIST

[ https://jira.jboss.org/jira/browse/ISPN-359?page=com.atlassian.jira.plugi... ] Manik Surtani updated ISPN-359: ------------------------------- Summary: Provide mechanism for users to control data locality when using DIST (was: Affinity accross caches - static or dynamic)

...

Provide mechanism for users to control data locality when using DIST -------------------------------------------------------------------- Key: ISPN-359 URL: https://jira.jboss.org/jira/browse/ISPN-359 Project: Infinispan Issue Type: Feature Request Components: Distributed Cache Affects Versions: 4.0.0.Final Reporter: Tero Heinonen Assignee: Manik Surtani Fix For: 4.1.0.ALPHA2, 4.1.0.Final Programmable affinity either through: 1) statically (e.g. annotating a certain field as the key for consistent hashing) - in our case this cannot be based on the hashCode() as the affinity requirement and object identity are not directly related 2) dynamically (e.g. providing a overridable/annotatable consistentHashCode() function) This would help to assign entities (in multiple Caches), which are needed together in the same nodes (to avoid remote lookups)

Manik Surtani (JIRA)

12:14 p.m.

New subject: [JBoss JIRA] Commented: (ISPN-359) Provide mechanism for users to control data locality when using DIST

[ https://jira.jboss.org/jira/browse/ISPN-359?page=com.atlassian.jira.plugi... ] Manik Surtani commented on ISPN-359: ------------------------------------ ISPN-312 may provide a group API that may help

...

Mircea Markus (JIRA)

Wednesday, 7 April Wed, 7 Apr

7:23 a.m.

New subject: [JBoss JIRA] Updated: (ISPN-359) Provide mechanism for users to control data locality when using DIST

[ https://jira.jboss.org/jira/browse/ISPN-359?page=com.atlassian.jira.plugi... ] Mircea Markus updated ISPN-359: ------------------------------- Fix Version/s: 4.1.0.BETA1 (was: 4.1.0.Final) (was: 4.1.0.ALPHA2)

...

Provide mechanism for users to control data locality when using DIST -------------------------------------------------------------------- Key: ISPN-359 URL: https://jira.jboss.org/jira/browse/ISPN-359 Project: Infinispan Issue Type: Feature Request Components: Distributed Cache Affects Versions: 4.0.0.Final Reporter: Tero Heinonen Assignee: Manik Surtani Fix For: 4.1.0.BETA1 Programmable affinity either through: 1) statically (e.g. annotating a certain field as the key for consistent hashing) - in our case this cannot be based on the hashCode() as the affinity requirement and object identity are not directly related 2) dynamically (e.g. providing a overridable/annotatable consistentHashCode() function) This would help to assign entities (in multiple Caches), which are needed together in the same nodes (to avoid remote lookups)

Vladimir Ralev (JIRA)

Thursday, 8 April Thu, 8 Apr

2:52 p.m.

New subject: [JBoss JIRA] Commented: (ISPN-359) Provide mechanism for users to control data locality when using DIST

[ https://jira.jboss.org/jira/browse/ISPN-359?page=com.atlassian.jira.plugi... ] Vladimir Ralev commented on ISPN-359: ------------------------------------- Would it be possible to make this feature work with buddy replication in cooperation with mod_cluster? For example you have node1,node2,node3,node4. Session A is on node1 and node2. When node1 fails it would be best mod_cluster to hit deterministically node2 instead of the other nodes. I remember I have seen hints that Infinispan is looking into rehashing or rebalancing, but I am not sure how smart is the algorithm and is it working cooperatively with mod_cluster?

...

Provide mechanism for users to control data locality when using DIST -------------------------------------------------------------------- Key: ISPN-359 URL: https://jira.jboss.org/jira/browse/ISPN-359 Project: Infinispan Issue Type: Feature Request Components: Distributed Cache Affects Versions: 4.0.0.Final Reporter: Tero Heinonen Assignee: Manik Surtani Fix For: 4.1.0.BETA1 Programmable affinity either through: 1) statically (e.g. annotating a certain field as the key for consistent hashing) - in our case this cannot be based on the hashCode() as the affinity requirement and object identity are not directly related 2) dynamically (e.g. providing a overridable/annotatable consistentHashCode() function) This would help to assign entities (in multiple Caches), which are needed together in the same nodes (to avoid remote lookups)

Manik Surtani (JIRA)

Friday, 9 April Fri, 9 Apr

5:52 a.m.

New subject: [JBoss JIRA] Commented: (ISPN-359) Provide mechanism for users to control data locality when using DIST

[ https://jira.jboss.org/jira/browse/ISPN-359?page=com.atlassian.jira.plugi... ] Manik Surtani commented on ISPN-359: ------------------------------------ @Vladimir do you mean Buddy Replication in JBoss Cache? This is specifically an Infinispan feature and Infinispan does not support Buddy Replication. (See http://infinispan.blogspot.com/2009/08/distribution-instead-of-buddy.html ) Regarding load balancers, there has been some talk on exposing the consistent hash mechanism to mod_cluster but this makes things pretty tightly coupled. A better approach would be for the app server to determine the location of a session (this can be done easily and cheaply via an API on Infinispan) and attach this to the jvmRoute of the session so that mod_cluster can direct the request accordingly. This would mean 1 "inefficient" dispatch in the event of a failover until the "correct" backup node is located and the jvmRoute updated though.

...

Provide mechanism for users to control data locality when using DIST -------------------------------------------------------------------- Key: ISPN-359 URL: https://jira.jboss.org/jira/browse/ISPN-359 Project: Infinispan Issue Type: Feature Request Components: Distributed Cache Affects Versions: 4.0.0.Final Reporter: Tero Heinonen Assignee: Manik Surtani Fix For: 4.1.0.BETA1 Programmable affinity either through: 1) statically (e.g. annotating a certain field as the key for consistent hashing) - in our case this cannot be based on the hashCode() as the affinity requirement and object identity are not directly related 2) dynamically (e.g. providing a overridable/annotatable consistentHashCode() function) This would help to assign entities (in multiple Caches), which are needed together in the same nodes (to avoid remote lookups)

Vladimir Ralev (JIRA)

10:13 a.m.

New subject: [JBoss JIRA] Commented: (ISPN-359) Provide mechanism for users to control data locality when using DIST

[ https://jira.jboss.org/jira/browse/ISPN-359?page=com.atlassian.jira.plugi... ] Vladimir Ralev commented on ISPN-359: ------------------------------------- By Buddy Replication I meant the DIST mode. I thought it is still called that way. Anyway, I will see what Brian says about mod_cluster. Other similar products use configurable affinity key independently in the cache and in the load balancers. In Mobicents we use pluggable algorithms for example and we will probably try to teach it to cooperate with this feature deterministically to cover some telco cases (some telco protocols dont have cookies or redirects to hunt down the right node). But what is still unclear on this topic is the rehashing/rebalancing. If a node fails is everything completely re-hashed to a new location (along with the huge network overhead of moving the chunks around over the network) or is there some effort to minimize the state transfer?

...

Provide mechanism for users to control data locality when using DIST -------------------------------------------------------------------- Key: ISPN-359 URL: https://jira.jboss.org/jira/browse/ISPN-359 Project: Infinispan Issue Type: Feature Request Components: Distributed Cache Affects Versions: 4.0.0.Final Reporter: Tero Heinonen Assignee: Manik Surtani Fix For: 4.1.0.BETA1 Programmable affinity either through: 1) statically (e.g. annotating a certain field as the key for consistent hashing) - in our case this cannot be based on the hashCode() as the affinity requirement and object identity are not directly related 2) dynamically (e.g. providing a overridable/annotatable consistentHashCode() function) This would help to assign entities (in multiple Caches), which are needed together in the same nodes (to avoid remote lookups)

Manik Surtani (JIRA)

10:23 a.m.

New subject: [JBoss JIRA] Commented: (ISPN-359) Provide mechanism for users to control data locality when using DIST

[ https://jira.jboss.org/jira/browse/ISPN-359?page=com.atlassian.jira.plugi... ] Manik Surtani commented on ISPN-359: ------------------------------------ Have a look at http://community.jboss.org/wiki/DIST-distributedcachemode - should help answer your q's

...

Provide mechanism for users to control data locality when using DIST -------------------------------------------------------------------- Key: ISPN-359 URL: https://jira.jboss.org/jira/browse/ISPN-359 Project: Infinispan Issue Type: Feature Request Components: Distributed Cache Affects Versions: 4.0.0.Final Reporter: Tero Heinonen Assignee: Manik Surtani Fix For: 4.1.0.BETA1 Programmable affinity either through: 1) statically (e.g. annotating a certain field as the key for consistent hashing) - in our case this cannot be based on the hashCode() as the affinity requirement and object identity are not directly related 2) dynamically (e.g. providing a overridable/annotatable consistentHashCode() function) This would help to assign entities (in multiple Caches), which are needed together in the same nodes (to avoid remote lookups)

Manik Surtani (JIRA)

Monday, 12 April Mon, 12 Apr

8:22 a.m.

New subject: [JBoss JIRA] Updated: (ISPN-359) Provide mechanism for users to control data locality when using DIST

[ https://jira.jboss.org/jira/browse/ISPN-359?page=com.atlassian.jira.plugi... ] Manik Surtani updated ISPN-359: ------------------------------- Fix Version/s: 4.1.0.Final

...

Provide mechanism for users to control data locality when using DIST -------------------------------------------------------------------- Key: ISPN-359 URL: https://jira.jboss.org/jira/browse/ISPN-359 Project: Infinispan Issue Type: Feature Request Components: Distributed Cache Affects Versions: 4.0.0.Final Reporter: Tero Heinonen Assignee: Manik Surtani Fix For: 4.1.0.BETA1, 4.1.0.Final Programmable affinity either through: 1) statically (e.g. annotating a certain field as the key for consistent hashing) - in our case this cannot be based on the hashCode() as the affinity requirement and object identity are not directly related 2) dynamically (e.g. providing a overridable/annotatable consistentHashCode() function) This would help to assign entities (in multiple Caches), which are needed together in the same nodes (to avoid remote lookups)

Manik Surtani (JIRA)

8:26 a.m.

New subject: [JBoss JIRA] Updated: (ISPN-359) Provide mechanism for users to control data locality when using DIST

[ https://jira.jboss.org/jira/browse/ISPN-359?page=com.atlassian.jira.plugi... ] Manik Surtani updated ISPN-359: ------------------------------- JBoss Forum Reference: http://community.jboss.org/message/528752#528752

...

Provide mechanism for users to control data locality when using DIST -------------------------------------------------------------------- Key: ISPN-359 URL: https://jira.jboss.org/jira/browse/ISPN-359 Project: Infinispan Issue Type: Feature Request Components: Distributed Cache Affects Versions: 4.0.0.Final Reporter: Tero Heinonen Assignee: Manik Surtani Fix For: 4.1.0.BETA1, 4.1.0.Final Programmable affinity either through: 1) statically (e.g. annotating a certain field as the key for consistent hashing) - in our case this cannot be based on the hashCode() as the affinity requirement and object identity are not directly related 2) dynamically (e.g. providing a overridable/annotatable consistentHashCode() function) This would help to assign entities (in multiple Caches), which are needed together in the same nodes (to avoid remote lookups)

Manik Surtani (JIRA)

Thursday, 6 May Thu, 6 May

7:20 a.m.

New subject: [JBoss JIRA] Updated: (ISPN-359) Provide mechanism for users to control data locality when using DIST

[ https://jira.jboss.org/jira/browse/ISPN-359?page=com.atlassian.jira.plugi... ] Manik Surtani updated ISPN-359: ------------------------------- Fix Version/s: 4.1.0.CR1 (was: 4.1.0.BETA1)

...

Provide mechanism for users to control data locality when using DIST -------------------------------------------------------------------- Key: ISPN-359 URL: https://jira.jboss.org/jira/browse/ISPN-359 Project: Infinispan Issue Type: Feature Request Components: Distributed Cache Affects Versions: 4.0.0.Final Reporter: Tero Heinonen Assignee: Manik Surtani Fix For: 4.1.0.CR1, 4.1.0.Final Programmable affinity either through: 1) statically (e.g. annotating a certain field as the key for consistent hashing) - in our case this cannot be based on the hashCode() as the affinity requirement and object identity are not directly related 2) dynamically (e.g. providing a overridable/annotatable consistentHashCode() function) This would help to assign entities (in multiple Caches), which are needed together in the same nodes (to avoid remote lookups)

Manik Surtani (JIRA)

Monday, 17 May Mon, 17 May

10:09 a.m.

New subject: [JBoss JIRA] Work started: (ISPN-359) Provide mechanism for users to control data locality when using DIST

[ https://jira.jboss.org/browse/ISPN-359?page=com.atlassian.jira.plugin.sys... ] Work on ISPN-359 started by Manik Surtani.

...

Provide mechanism for users to control data locality when using DIST -------------------------------------------------------------------- Key: ISPN-359 URL: https://jira.jboss.org/browse/ISPN-359 Project: Infinispan Issue Type: Feature Request Components: Distributed Cache Affects Versions: 4.0.0.Final Reporter: Tero Heinonen Assignee: Manik Surtani Fix For: 4.1.0.CR1, 4.1.0.Final Programmable affinity either through: 1) statically (e.g. annotating a certain field as the key for consistent hashing) - in our case this cannot be based on the hashCode() as the affinity requirement and object identity are not directly related 2) dynamically (e.g. providing a overridable/annotatable consistentHashCode() function) This would help to assign entities (in multiple Caches), which are needed together in the same nodes (to avoid remote lookups)

-- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

Manik Surtani (JIRA)

Wednesday, 19 May Wed, 19 May

10:34 a.m.

New subject: [JBoss JIRA] Commented: (ISPN-359) Provide mechanism for users to control data locality when using DIST

[ https://jira.jboss.org/browse/ISPN-359?page=com.atlassian.jira.plugin.sys... ] Manik Surtani commented on ISPN-359: ------------------------------------ Also see related mail list thread http://www.mailarchy.com/thread.php?id=532764

...

Provide mechanism for users to control data locality when using DIST -------------------------------------------------------------------- Key: ISPN-359 URL: https://jira.jboss.org/browse/ISPN-359 Project: Infinispan Issue Type: Feature Request Components: Distributed Cache Affects Versions: 4.0.0.Final Reporter: Tero Heinonen Assignee: Manik Surtani Fix For: 4.1.0.CR1, 4.1.0.Final Programmable affinity either through: 1) statically (e.g. annotating a certain field as the key for consistent hashing) - in our case this cannot be based on the hashCode() as the affinity requirement and object identity are not directly related 2) dynamically (e.g. providing a overridable/annotatable consistentHashCode() function) This would help to assign entities (in multiple Caches), which are needed together in the same nodes (to avoid remote lookups)

Manik Surtani (JIRA)

Friday, 21 May Fri, 21 May

5:25 a.m.

New subject: [JBoss JIRA] Updated: (ISPN-359) Provide mechanism for users to control data locality when using DIST

[ https://jira.jboss.org/browse/ISPN-359?page=com.atlassian.jira.plugin.sys... ] Manik Surtani updated ISPN-359: ------------------------------- Fix Version/s: 5.0.0.BETA1 5.0.0.Final (was: 4.1.0.CR1) (was: 4.1.0.Final) Needs more thought and a decision on scoping behaviour

...

Provide mechanism for users to control data locality when using DIST -------------------------------------------------------------------- Key: ISPN-359 URL: https://jira.jboss.org/browse/ISPN-359 Project: Infinispan Issue Type: Feature Request Components: Distributed Cache Affects Versions: 4.0.0.Final Reporter: Tero Heinonen Assignee: Manik Surtani Fix For: 5.0.0.BETA1, 5.0.0.Final Programmable affinity either through: 1) statically (e.g. annotating a certain field as the key for consistent hashing) - in our case this cannot be based on the hashCode() as the affinity requirement and object identity are not directly related 2) dynamically (e.g. providing a overridable/annotatable consistentHashCode() function) This would help to assign entities (in multiple Caches), which are needed together in the same nodes (to avoid remote lookups)

Manik Surtani (JIRA)

5:31 a.m.

New subject: [JBoss JIRA] Work stopped: (ISPN-359) Provide mechanism for users to control data locality when using DIST

[ https://jira.jboss.org/browse/ISPN-359?page=com.atlassian.jira.plugin.sys... ] Work on ISPN-359 stopped by Manik Surtani.

...

Provide mechanism for users to control data locality when using DIST -------------------------------------------------------------------- Key: ISPN-359 URL: https://jira.jboss.org/browse/ISPN-359 Project: Infinispan Issue Type: Feature Request Components: Distributed Cache Affects Versions: 4.0.0.Final Reporter: Tero Heinonen Assignee: Manik Surtani Fix For: 5.0.0.BETA1, 5.0.0.Final Programmable affinity either through: 1) statically (e.g. annotating a certain field as the key for consistent hashing) - in our case this cannot be based on the hashCode() as the affinity requirement and object identity are not directly related 2) dynamically (e.g. providing a overridable/annotatable consistentHashCode() function) This would help to assign entities (in multiple Caches), which are needed together in the same nodes (to avoid remote lookups)

Trustin Lee (JIRA)

Friday, 29 October Fri, 29 Oct

8:59 a.m.

New subject: [JBoss JIRA] Assigned: (ISPN-359) Provide mechanism for users to control data locality when using DIST

[ https://jira.jboss.org/browse/ISPN-359?page=com.atlassian.jira.plugin.sys... ] Trustin Lee reassigned ISPN-359: -------------------------------- Assignee: Trustin Lee (was: Manik Surtani)

...

Provide mechanism for users to control data locality when using DIST -------------------------------------------------------------------- Key: ISPN-359 URL: https://jira.jboss.org/browse/ISPN-359 Project: Infinispan Issue Type: Feature Request Components: Distributed Cache Affects Versions: 4.0.0.Final Reporter: Tero Heinonen Assignee: Trustin Lee Fix For: 5.0.0.BETA1, 5.0.0.Final Programmable affinity either through: 1) statically (e.g. annotating a certain field as the key for consistent hashing) - in our case this cannot be based on the hashCode() as the affinity requirement and object identity are not directly related 2) dynamically (e.g. providing a overridable/annotatable consistentHashCode() function) This would help to assign entities (in multiple Caches), which are needed together in the same nodes (to avoid remote lookups)

Mircea Markus (JIRA)

Friday, 7 January Fri, 7 Jan

7:27 a.m.

New subject: [JBoss JIRA] Assigned: (ISPN-359) Provide mechanism for users to control data locality when using DIST

[ https://issues.jboss.org/browse/ISPN-359?page=com.atlassian.jira.plugin.s... ] Mircea Markus reassigned ISPN-359: ---------------------------------- Assignee: Mircea Markus (was: Trustin Lee)

...

Provide mechanism for users to control data locality when using DIST -------------------------------------------------------------------- Key: ISPN-359 URL: https://issues.jboss.org/browse/ISPN-359 Project: Infinispan Issue Type: Feature Request Components: Distributed Cache Affects Versions: 4.0.0.Final Reporter: Tero Heinonen Assignee: Mircea Markus Labels: affinity, hackathon Fix For: 5.0.0.BETA1, 5.0.0.Final Programmable affinity either through: 1) statically (e.g. annotating a certain field as the key for consistent hashing) - in our case this cannot be based on the hashCode() as the affinity requirement and object identity are not directly related 2) dynamically (e.g. providing a overridable/annotatable consistentHashCode() function) This would help to assign entities (in multiple Caches), which are needed together in the same nodes (to avoid remote lookups)

-- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

Manik Surtani (JIRA)

Tuesday, 11 January Tue, 11 Jan

6:12 a.m.

New subject: [JBoss JIRA] Issue Comment Edited: (ISPN-359) Provide mechanism for users to control data locality when using DIST

[ https://issues.jboss.org/browse/ISPN-359?page=com.atlassian.jira.plugin.s... ] Manik Surtani edited comment on ISPN-359 at 1/11/11 6:10 AM: ------------------------------------------------------------- Also see related mail list thread http://lists.jboss.org/pipermail/infinispan-dev/2010-April/005382.html was (Author: manik.surtani(a)jboss.com): Also see related mail list thread http://www.mailarchy.com/thread.php?id=532764

...

Provide mechanism for users to control data locality when using DIST -------------------------------------------------------------------- Key: ISPN-359 URL: https://issues.jboss.org/browse/ISPN-359 Project: Infinispan Issue Type: Feature Request Components: Distributed Cache Affects Versions: 4.0.0.Final Reporter: Tero Heinonen Assignee: Mircea Markus Labels: affinity, hackathon Fix For: 5.0.0.BETA1, 5.0.0.Final Programmable affinity either through: 1) statically (e.g. annotating a certain field as the key for consistent hashing) - in our case this cannot be based on the hashCode() as the affinity requirement and object identity are not directly related 2) dynamically (e.g. providing a overridable/annotatable consistentHashCode() function) This would help to assign entities (in multiple Caches), which are needed together in the same nodes (to avoid remote lookups)

-- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

Manik Surtani (JIRA)

6:12 a.m.

New subject: [JBoss JIRA] Assigned: (ISPN-359) Provide mechanism for users to control data locality when using DIST

[ https://issues.jboss.org/browse/ISPN-359?page=com.atlassian.jira.plugin.s... ] Manik Surtani reassigned ISPN-359: ---------------------------------- Assignee: Pete Muir (was: Mircea Markus)

...

Provide mechanism for users to control data locality when using DIST -------------------------------------------------------------------- Key: ISPN-359 URL: https://issues.jboss.org/browse/ISPN-359 Project: Infinispan Issue Type: Feature Request Components: Distributed Cache Affects Versions: 4.0.0.Final Reporter: Tero Heinonen Assignee: Pete Muir Labels: affinity, hackathon Fix For: 5.0.0.BETA1, 5.0.0.Final Programmable affinity either through: 1) statically (e.g. annotating a certain field as the key for consistent hashing) - in our case this cannot be based on the hashCode() as the affinity requirement and object identity are not directly related 2) dynamically (e.g. providing a overridable/annotatable consistentHashCode() function) This would help to assign entities (in multiple Caches), which are needed together in the same nodes (to avoid remote lookups)

-- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

Pete Muir (JIRA)

Tuesday, 22 March Tue, 22 Mar

12:14 p.m.

New subject: [JBoss JIRA] Updated: (ISPN-359) Provide mechanism for users to control data locality when using DIST

[ https://issues.jboss.org/browse/ISPN-359?page=com.atlassian.jira.plugin.s... ] Pete Muir updated ISPN-359: --------------------------- Fix Version/s: 5.0.0.BETA2 (was: 5.0.0.BETA1)

...

Provide mechanism for users to control data locality when using DIST -------------------------------------------------------------------- Key: ISPN-359 URL: https://issues.jboss.org/browse/ISPN-359 Project: Infinispan Issue Type: Feature Request Components: Distributed Cache Affects Versions: 4.0.0.Final Reporter: Tero Heinonen Assignee: Pete Muir Labels: affinity, hackathon Fix For: 5.0.0.BETA2, 5.0.0.FINAL Programmable affinity either through: 1) statically (e.g. annotating a certain field as the key for consistent hashing) - in our case this cannot be based on the hashCode() as the affinity requirement and object identity are not directly related 2) dynamically (e.g. providing a overridable/annotatable consistentHashCode() function) This would help to assign entities (in multiple Caches), which are needed together in the same nodes (to avoid remote lookups)

-- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

Galder Zamarreño (JIRA)

Tuesday, 19 April Tue, 19 Apr

5:38 a.m.

New subject: [JBoss JIRA] Updated: (ISPN-359) Provide mechanism for users to control data locality when using DIST

[ https://issues.jboss.org/browse/ISPN-359?page=com.atlassian.jira.plugin.s... ] Galder Zamarreño updated ISPN-359: ---------------------------------- Fix Version/s: 5.0.0.CR1 (was: 5.0.0.BETA2)

...

Provide mechanism for users to control data locality when using DIST -------------------------------------------------------------------- Key: ISPN-359 URL: https://issues.jboss.org/browse/ISPN-359 Project: Infinispan Issue Type: Feature Request Components: Distributed Cache Affects Versions: 4.0.0.Final Reporter: Tero Heinonen Assignee: Pete Muir Labels: affinity, hackathon Fix For: 5.0.0.CR1, 5.0.0.FINAL Programmable affinity either through: 1) statically (e.g. annotating a certain field as the key for consistent hashing) - in our case this cannot be based on the hashCode() as the affinity requirement and object identity are not directly related 2) dynamically (e.g. providing a overridable/annotatable consistentHashCode() function) This would help to assign entities (in multiple Caches), which are needed together in the same nodes (to avoid remote lookups)

-- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

Pete Muir (JIRA)

Tuesday, 26 April Tue, 26 Apr

5:19 a.m.

New subject: [JBoss JIRA] Updated: (ISPN-359) Provide mechanism for users to control data locality when using DIST

[ https://issues.jboss.org/browse/ISPN-359?page=com.atlassian.jira.plugin.s... ] Pete Muir updated ISPN-359: --------------------------- Fix Version/s: 5.1.0.BETA1 (was: 5.0.0.FINAL) (was: 5.0.0.CR1)

...

Provide mechanism for users to control data locality when using DIST -------------------------------------------------------------------- Key: ISPN-359 URL: https://issues.jboss.org/browse/ISPN-359 Project: Infinispan Issue Type: Feature Request Components: Distributed Cache Affects Versions: 4.0.0.Final Reporter: Tero Heinonen Assignee: Pete Muir Labels: affinity, hackathon Fix For: 5.1.0.BETA1 Programmable affinity either through: 1) statically (e.g. annotating a certain field as the key for consistent hashing) - in our case this cannot be based on the hashCode() as the affinity requirement and object identity are not directly related 2) dynamically (e.g. providing a overridable/annotatable consistentHashCode() function) This would help to assign entities (in multiple Caches), which are needed together in the same nodes (to avoid remote lookups)

-- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

Pete Muir (JIRA)

Thursday, 14 July Thu, 14 Jul

2:36 p.m.

New subject: [JBoss JIRA] Resolved: (ISPN-359) Provide mechanism for users to control data locality when using DIST

[ https://issues.jboss.org/browse/ISPN-359?page=com.atlassian.jira.plugin.s... ] Pete Muir resolved ISPN-359. ---------------------------- Fix Version/s: 5.0.0.FINAL (was: 5.1.0.BETA1) Resolution: Done Resolved as part of ISPN-312

...

Provide mechanism for users to control data locality when using DIST -------------------------------------------------------------------- Key: ISPN-359 URL: https://issues.jboss.org/browse/ISPN-359 Project: Infinispan Issue Type: Feature Request Components: Distributed Cache Affects Versions: 4.0.0.Final Reporter: Tero Heinonen Assignee: Pete Muir Labels: affinity, hackathon Fix For: 5.0.0.FINAL Programmable affinity either through: 1) statically (e.g. annotating a certain field as the key for consistent hashing) - in our case this cannot be based on the hashCode() as the affinity requirement and object identity are not directly related 2) dynamically (e.g. providing a overridable/annotatable consistentHashCode() function) This would help to assign entities (in multiple Caches), which are needed together in the same nodes (to avoid remote lookups)

-- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

4668

days inactive

5167

days old

infinispan-issues@lists.jboss.org

Manage subscription

23 comments

7 participants

tags (0)

participants (7)

Galder Zamarreño (JIRA)
Manik Surtani (JIRA)
Mircea Markus (JIRA)
Pete Muir (JIRA)
Tero Heinonen (JIRA)
Trustin Lee (JIRA)
Vladimir Ralev (JIRA)

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

[JBoss JIRA] Created: (ISPN-359) Affinity accross caches - static or dynamic