[
https://issues.apache.org/jira/browse/IGNITE-23061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Puchkovskiy updated IGNITE-23061:
---------------------------------------
Description:
Transaction object obtained in embedded mode via
IgniteServer.api().transactions().begin() should remain functional even after
the node gets restarted (using in-process restart). This should work
analogously to how it's done for Table (see RestartProofTable).
This will require transaction data to be migrated to another node, which needs
to be designed.
was:
IgniteTransaction obtained in embedded mode via
IgniteServer.api().transactions().begin() should remain functional even after
the node gets restarted (using in-process restart). This should work
analogously to how it's done for Table (see RestartProofTable).
This will require transaction data to be migrated to another node, which needs
to be designed.
> Transaction transparency wrt node restart
> -----------------------------------------
>
> Key: IGNITE-23061
> URL: https://issues.apache.org/jira/browse/IGNITE-23061
> Project: Ignite
> Issue Type: Improvement
> Reporter: Roman Puchkovskiy
> Priority: Major
> Labels: ignite-3, inprocess-restart
>
> Transaction object obtained in embedded mode via
> IgniteServer.api().transactions().begin() should remain functional even after
> the node gets restarted (using in-process restart). This should work
> analogously to how it's done for Table (see RestartProofTable).
> This will require transaction data to be migrated to another node, which
> needs to be designed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
