You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Roman Puchkovskiy (Jira)" <ji...@apache.org> on 2024/09/06 17:08:00 UTC

[jira] [Updated] (IGNITE-23014) IgniteCompute transparency with respect to node restart

     [ https://issues.apache.org/jira/browse/IGNITE-23014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Roman Puchkovskiy updated IGNITE-23014:
---------------------------------------
    Summary: IgniteCompute transparency with respect to node restart  (was: IgniteCompute transparency wrt node restart)

> IgniteCompute transparency with respect to node restart
> -------------------------------------------------------
>
>                 Key: IGNITE-23014
>                 URL: https://issues.apache.org/jira/browse/IGNITE-23014
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Roman Puchkovskiy
>            Assignee: Roman Puchkovskiy
>            Priority: Major
>              Labels: ignite-3, inprocess-restart
>
> IgniteCompute obtained in embedded mode via IgniteServer.api() should remain functional even after the node gets restarted (using in-process restart). This should work analogously to how it's done for IgniteTables (see RestartProofIgniteTables).



--
This message was sent by Atlassian Jira
(v8.20.10#820010)