[
https://issues.apache.org/jira/browse/IGNITE-22570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr Polovtsev updated IGNITE-22570:
-----------------------------------------
Description: New embedded API introduces new methods, namely
{{IgniteServer#startAsync}} and {{IgniteServer#stopAsync}}. However, their
implementations are not fully-async by design: they have a synchronous part
(which can be quite significant) and an asynchronous part. While this is ok for
internal use, it may confuse embedded API users, because these methods can
block a user's thread, despite being called "async". We must fix that and make
the API methods fully async, i.e. they must not block the caller's thread.
(was: New embedded API introduces new methods, namely )
> IgniteServer#startAsync and IgniteServer#stopAsync are not completely async
> ---------------------------------------------------------------------------
>
> Key: IGNITE-22570
> URL: https://issues.apache.org/jira/browse/IGNITE-22570
> Project: Ignite
> Issue Type: Improvement
> Reporter: Aleksandr Polovtsev
> Priority: Minor
> Labels: ignite-3
>
> New embedded API introduces new methods, namely {{IgniteServer#startAsync}}
> and {{IgniteServer#stopAsync}}. However, their implementations are not
> fully-async by design: they have a synchronous part (which can be quite
> significant) and an asynchronous part. While this is ok for internal use, it
> may confuse embedded API users, because these methods can block a user's
> thread, despite being called "async". We must fix that and make the API
> methods fully async, i.e. they must not block the caller's thread.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
