[
https://issues.apache.org/jira/browse/IGNITE-22688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Puchkovskiy updated IGNITE-22688:
---------------------------------------
Description:
The executor used by the server-side code is currently hard-coded in IgniteImpl
to be ForkJoinPool.common. The user might want to use their own pool, so we
should make it configurable.
It is possible to configure it on the client (see
IgniteClientConfiguration#asyncContinuationExecutor()). We could pass some
properties/parameters to Ignition when creating an embedded Ignite instance to
make it possible to pass the desired pool.
> Make async continuation executor configurable in IgniteImpl
> -----------------------------------------------------------
>
> Key: IGNITE-22688
> URL: https://issues.apache.org/jira/browse/IGNITE-22688
> Project: Ignite
> Issue Type: Improvement
> Reporter: Roman Puchkovskiy
> Priority: Major
> Labels: ignite-3
>
> The executor used by the server-side code is currently hard-coded in
> IgniteImpl to be ForkJoinPool.common. The user might want to use their own
> pool, so we should make it configurable.
> It is possible to configure it on the client (see
> IgniteClientConfiguration#asyncContinuationExecutor()). We could pass some
> properties/parameters to Ignition when creating an embedded Ignite instance
> to make it possible to pass the desired pool.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
