[infinispan-issues] [JBoss JIRA] (ISPN-1513) Enhance distributed executor framework to be more topology aware

[David B (Commented) (JIRA)]

    [ https://issues.jboss.org/browse/ISPN-1513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12642134#comment-12642134 ] 

David B commented on ISPN-1513:
-------------------------------

We'll be very interested in fail-over policies. Currently we having long running processes distributed across the cluster that when a node fails the remaining nodes need to pick up. We are implementing this via a work stealing algorithm that we execute when the cluster view changes. The typical map-reduce type use-cases don't really fit well when addressing long running processes (i,e. balancing work load across a cluster).
                
> 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: Vladimir Blagojevic
>            Priority: Minor
>             Fix For: 5.2.0.FINAL
>
>
> 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