[
https://issues.apache.org/jira/browse/IGNITE-4699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15897629#comment-15897629
]
Alexander Menshikov commented on IGNITE-4699:
---------------------------------------------
Vladimir, I have some questions about the task:
1) Is the task only about separating compute tasks into groups or It's also
about different types of executors (with different schedule algorithms)?
2) What does "ExecutorConfiguration.size" mean? I think would better use all
parameters of IgniteThreadPoolExecutor constructor.
3) What a problem it help to solve? I mean, is it about some kind of stable
like run different client compute tasks in different executors to avoid hang in
specific compute task? Or you want to reach some other aim?
> Introduce custom configurable executors.
> ----------------------------------------
>
> Key: IGNITE-4699
> URL: https://issues.apache.org/jira/browse/IGNITE-4699
> Project: Ignite
> Issue Type: Task
> Components: compute
> Reporter: Vladimir Ozerov
> Assignee: Alexander Menshikov
> Fix For: 2.0
>
>
> We need to provide a way to configure custom thread pools for user compute
> tasks.
> Proposed API:
> 1) Config
> {code}
> class ExecutorConfiguration {
> String name;
> int size;
> }
> {code}
> 2) Choosing executor for compute task:
> {code}
> IgniteCompute compute = Ignite.compute().withExecutor("my_exec");
> {code}
> 3) Accessing raw executor (could be required for proper execution of future
> listeners):
> {code}
> ThreadPoolExecutor exec = ignite.compute().localExecutor("my_exec");
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
