Thanks for writing this up dude. It's nice and clear, pretty much what I had in
mind.
A few points.
First, the section on Distributed Tasks Input. I am guessing what you are trying to model
here is access to the actual cache? Doesn't the Callable in question just need a
reference to the Cache? Not sure I get what you mean by node-local data. Are you
assuming a view of global state that is locally resident on a node in question? If so,
double-counting may still happen if the task ends up on 2 nodes, both of which happen to
own an entry.
Second, failover, perhaps initially we could just ship with a simple policy of throw an
exception if a node fails. And later add more failover and task migration policies.
I'd prefer to start simple and build out more complex features. :)
Cheers
Manik
On 21 Jul 2010, at 18:42, Vladimir Blagojevic wrote:
Hi,
I wanted to gather feedback from community regarding proposed scope and objectives of
Distributed execution framework targeted for Infinispan 5.0. The document is a gentle
introduction to the subject of distributed execution and as such is accessible to wider
audience. Eager to hear your thoughts.
Regards,
Vladimir
https://community.jboss.org/wiki/InfinispanDistributedExecutionFramework
--
Vladimir Blagojevic
JBoss Clustering Team
JBoss, by Red Hat
_______________________________________________
infinispan-dev mailing list
infinispan-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev
--
Manik Surtani
manik(a)jboss.org
Lead, Infinispan
Lead, JBoss Cache
http://www.infinispan.org
http://www.jbosscache.org