[infinispan-issues] [JBoss JIRA] (ISPN-1513) Enhance distributed executor framework to be more topology aware
Vladimir Blagojevic (JIRA)
jira-events at lists.jboss.org
Fri Sep 28 10:15:04 EDT 2012
[ https://issues.jboss.org/browse/ISPN-1513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vladimir Blagojevic resolved ISPN-1513.
---------------------------------------
Fix Version/s: 5.2.0.Beta1
(was: 5.2.0.Final)
Resolution: Done
> 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 Execution and Map/Reduce
> Affects Versions: 5.0.1.FINAL
> Reporter: David B
> Assignee: Vladimir Blagojevic
> Priority: Minor
> Fix For: 5.2.0.Beta1
>
>
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the infinispan-issues
mailing list