[JBoss JIRA] Created: (ISPN-530) Hot Rod client should load balance between different owners for a key
by Galder Zamarreno (JIRA)
Hot Rod client should load balance between different owners for a key
---------------------------------------------------------------------
Key: ISPN-530
URL: https://jira.jboss.org/browse/ISPN-530
Project: Infinispan
Issue Type: Feature Request
Components: Cache Server
Reporter: Galder Zamarreno
Assignee: Mircea Markus
Fix For: 5.0.0.BETA1
While doing the demo for JUDCon, I realised that smart routing on the client side always choses the same node for the same key.
IOW, assume you have k1 stored in nodes A, B and the cluster is formed of nodes A, B and C. Now, when the client figures out that the owner is A, any further requests on k1 will be sent to A. This has the possibility of overloading A.
I think the client should, from the given list of owners of a key, do round robin between them for requests on the same key.
--
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
12 years, 11 months
[JBoss JIRA] Created: (ISPN-862) XAResource.isSameRM is not implemented correctly
by Mircea Markus (JIRA)
XAResource.isSameRM is not implemented correctly
------------------------------------------------
Key: ISPN-862
URL: https://issues.jboss.org/browse/ISPN-862
Project: Infinispan
Issue Type: Bug
Affects Versions: 4.2.0.Final
Reporter: Mircea Markus
Assignee: Mircea Markus
Fix For: 5.0.0.BETA1
XAResource.isSameRM is described withing "3.4.9 Identifying Resource Manager Instance" of JTA spec.
Discussing this with Jonathan Halliday a cluster itself should be seen as a ResourceManager, which means that the semantic of XAResource.isSameRM(XAResource) is as follows:
- if it is the same type as ours (TransactionXAResource)
AND
- other's cluster name is same as ours
then return true. False in all other situations.
Current implementation returns true if and only of the two TransactionXAResource implementations are associated with the same Transaction object.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months
[JBoss JIRA] Created: (ISPN-899) ConsistentHash related improvements
by Mircea Markus (JIRA)
ConsistentHash related improvements
-----------------------------------
Key: ISPN-899
URL: https://issues.jboss.org/browse/ISPN-899
Project: Infinispan
Issue Type: Feature Request
Components: Distributed Cache
Affects Versions: 4.2.0.Final
Reporter: Mircea Markus
Assignee: Manik Surtani
Fix For: 5.0.0.Final
Following methods of CH are no longer used in the code base:
int getHashId(Address a);
int getHashSpace();
They should be removed.
Also AbstractConsistentHash.getCaches can/should be added in the abstract implementation.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] Created: (ISPN-850) RemoteCache.replaceWithVersion javadoc is incorrect
by Galder Zamarreño (JIRA)
RemoteCache.replaceWithVersion javadoc is incorrect
---------------------------------------------------
Key: ISPN-850
URL: https://issues.jboss.org/browse/ISPN-850
Project: Infinispan
Issue Type: Bug
Components: Cache Server
Affects Versions: 5.0.0.ALPHA1, 4.2.0.Final
Reporter: Galder Zamarreño
Assignee: Mircea Markus
Priority: Minor
Fix For: 5.0.0.BETA1, 5.0.0.Final
replaceWithVersion javadoc is incorrect:
/**
* Removes the given value only if its version matches the supplied version. See {@link #removeWithVersion(Object,
* long)} for a sample usage.
*
* @return true if the method has been replaced
* @see #getVersioned(Object)
* @see VersionedValue
*/
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] Created: (ISPN-792) Migrate to David's JBoss Logging
by Galder Zamarreño (JIRA)
Migrate to David's JBoss Logging
--------------------------------
Key: ISPN-792
URL: https://jira.jboss.org/browse/ISPN-792
Project: Infinispan
Issue Type: Feature Request
Reporter: Galder Zamarreño
Assignee: Manik Surtani
Based on what David Lloyd said in the AS7 podcast, it performs much better than log4j and in particular, when it comes to log level checks (it apparently uses volatile int checks).
This could have a direct impact on the Infinispan performance since we do a fair few level checks.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years