[infinispan-issues] [JBoss JIRA] Resolved: (ISPN-352) Add per-cache coordinator.
Manik Surtani (JIRA)
jira-events at lists.jboss.org
Tue Nov 23 06:05:59 EST 2010
[ https://jira.jboss.org/browse/ISPN-352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Manik Surtani resolved ISPN-352.
--------------------------------
Resolution: Duplicate Issue
This duplicated by parts of ISPN-658
> Add per-cache coordinator.
> --------------------------
>
> Key: ISPN-352
> URL: https://jira.jboss.org/browse/ISPN-352
> Project: Infinispan
> Issue Type: Feature Request
> Components: Core API
> Reporter: Alexander Gavrilov
> Assignee: Manik Surtani
>
> We trying to use Infinispan for our cluster. We have two types of nodes in cluster. "Type 1" nodes use all set of caches defined in system, but "Type 2" nodes uses only small subset of caches. For each cache on each node we have job, that fetch data from external store and put that data in the cache. We need this job to be executed only in one node from whole cluster and is natural to test if node is cache coordinator and execute job only if it is. In current implementation it's possible to determinate only cluster coordinator. But when node of "Type 2" becomes coordinator it is impossible to update some caches, because they are not defined in this node. It would be fine to declare not only oldest node in cluster as cluster coordinator but oldest node containing cache as this concrete cache coordinator.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the infinispan-issues
mailing list