Yes, task will be routed to public pool with a warning to the log. On Tue, Apr 18, 2017 at 9:21 PM, Dmitriy Setrakyan <dsetrak...@apache.org> wrote:
> Christos, > > I think you are right in general, however, is the executor service is not > found, there should not be an exception, we should default to the public > pool. > > D. > > On Tue, Apr 18, 2017 at 8:53 AM, Christos Erotocritou < > chris...@gridgain.com > > wrote: > > > Taras, > > > > If I’m understanding right: > > > > Executor is configured local to a node, if same configuration is used to > > start multiple nodes then they will all have the same executor hence a > > broadcast task would execute on both all nodes. If one of those nodes > > didn’t have this executor configured then task on that node will throw an > > exception. Now in a scenario where 2 nodes do not have same executor and > we > > just use compute apply api call to execute task on next available node > > chances are it can end up on a node without that executor, correct? So we > > don’t have a way of routing tasks automatically to nodes with specific > > executors, we would have to use cluster groups to ensure that, correct? > > > > I think its important that we document all these points. > > > > C. > > > > > On 18 Apr 2017, at 16:12, Taras Ledkov <tled...@gridgain.com> wrote: > > > > > > Hi, Christos. > > > > > > 1. The custom executor executor is configured for specified node. There > > is not restriction that guaranties the similar set of executors on the > > whole cluster. > > > > > > 2. I guess You can use ClusterGroup.forPredicate() and custom node > > attribute when you want to submit the job only to nodes where the > specific > > executor is configured. > > > > > > > > > On 18.04.2017 18:00, Christos Erotocritou wrote: > > >> I assume its not currently possible to constrain an executor pool to > be > > started only on a specific node? > > > > > > -- > > > Taras Ledkov > > > Mail-To: tled...@gridgain.com > > > > > > > >
