[JBoss JIRA] (ISPN-1513) Enhance distributed executor framework to be more topology aware
by David B (Created) (JIRA)
Enhance distributed executor framework to be more topology aware
----------------------------------------------------------------
Key: ISPN-1513
URL: https://issues.jboss.org/browse/ISPN-1513
Project: Infinispan
Issue Type: Enhancement
Components: Distributed Cache
Affects Versions: 5.0.1.FINAL
Reporter: David B
Assignee: Manik Surtani
Priority: Minor
Our environment has 2 local infinispan/jgroups clusters with a jgroups relay cluster to handle geographic failover. Our sites are geographically distant over a WAN. Currently DistributedExecutorService's submitEverywhere() sends Callables to every node in both local clusters. We would rather have additional methods provided to DistributedExecutorService to constrain submission on Callables to the same/local site.
Currently I have extended DefaultExecutorService with my own TopologyAwareExecutorService and added a submitSameSite() method using the TopologyAwareAddress.isSameSite(). I did need to patch DistributedRunnableFuture in DefaultExecutorService to mark it protected vs. private.
This could be extended to also provide submitSameRack() & submitSameMachine() though currently we don't have a use case for that.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (ISPN-1827) De-couple cache view installation and state transfer (consistent hash installation)s
by Dan Berindei (JIRA)
Dan Berindei created ISPN-1827:
----------------------------------
Summary: De-couple cache view installation and state transfer (consistent hash installation)s
Key: ISPN-1827
URL: https://issues.jboss.org/browse/ISPN-1827
Project: Infinispan
Issue Type: Task
Components: State transfer
Affects Versions: 5.1.0.FINAL
Reporter: Dan Berindei
Assignee: Dan Berindei
Fix For: 5.2.0.FINAL
We need to know the primary owner of a key in order to do pretty much anything, and every member of a cache view should compute the same primary owner at all times. So we need a 2PC cache view installation immediately after any leave to ensure that every node determines the primary owner in the same way - we can't coalesce leaves.
However, it's highly desirable to coalesce state transfers caused by a node leaving - perhaps because we are shutting down half of the cluster to do an upgrade. So we should separate the state transfer from the cache view installation, and each one should have its own 2PC process.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] Created: (ISPN-1409) Introduce a binary-stream upgrading CacheLoader
by Sanne Grinovero (JIRA)
Introduce a binary-stream upgrading CacheLoader
-----------------------------------------------
Key: ISPN-1409
URL: https://issues.jboss.org/browse/ISPN-1409
Project: Infinispan
Issue Type: Feature Request
Reporter: Sanne Grinovero
Assignee: Manik Surtani
Fix For: 5.1.0.BETA1
We need a CacheLoader decorator able to chain sets of two different Externalizers which are targeting the same Java type to transform from one binary format to the next binary format.
Example: a Person object stored in the cache and an Externalizer is coupled to it. In a new release the Externalizer is changed to provide a different binary representation. Using the old one the stream is transformed from a byte[] to a Person, then this Java instance is feed to the new Externalizer implementation to get the new corresponding byte[]; the updated stream is stored in the decorated CacheLoader so that the nodes going to be attached to the cache store and using the new Externalizer will be fine.
A little complexity is introduced if the cache has to know about different sets of Externalizers if several different types need to be upgraded. A possible solution is to use a single decorator instance for each type, creating a chain of decorators if they are able to pass "as is" each externalizer id they are not directly coupled to.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] Created: (ISPN-1337) Infinispan query module: searchManagerImpl.extractType() throws exception on some OS.
by JaeHee Roh (JIRA)
Infinispan query module: searchManagerImpl.extractType() throws exception on some OS.
-------------------------------------------------------------------------------------
Key: ISPN-1337
URL: https://issues.jboss.org/browse/ISPN-1337
Project: Infinispan
Issue Type: Bug
Components: Querying
Affects Versions: 5.0.0.FINAL
Environment: JAVA
java version "1.6.0_24"
Java(TM) SE Runtime Environment (build 1.6.0_24-b07)
Java HotSpot(TM) 64-Bit Server VM (build 19.1-b02, mixed mode)
OS
# uname -ovr
2.6.38-8-generic #42-Ubuntu SMP Mon Apr 11 03:31:24 UTC 2011 GNU/Linux
Tested with Infinispan 5.0.0.FINAL and 5.0.0.CR8. Both versions failed on this Ubuntu platform.
However, it is ok on Suse platform.
# uname -ovr
2.6.16.60-0.85.1-smp #1 SMP Thu Mar 17 11:45:06 UTC 2011 GNU/Linux
Reporter: JaeHee Roh
Assignee: Manik Surtani
Priority: Critical
This is a same problem as https://issues.jboss.org/browse/ISPN-1232 which fixed in 5.0.0.CR8 and 5.0.0.FINAL but it seems that fix is working on some OS but not all of OS.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months