[
https://issues.apache.org/jira/browse/IGNITE-21934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Pereslegin updated IGNITE-21934:
--------------------------------------
Summary: Sql. Jdbc. Design transparent handling of server node restart
(was: Sql. Jdbc. Design transparent client-server "reconnect")
> Sql. Jdbc. Design transparent handling of server node restart
> -------------------------------------------------------------
>
> Key: IGNITE-21934
> URL: https://issues.apache.org/jira/browse/IGNITE-21934
> Project: Ignite
> Issue Type: Improvement
> Components: sql
> Reporter: Pavel Pereslegin
> Priority: Major
> Labels: ignite-3
>
> We need to develop a possible solution to properly handle a server node
> restart.
> For example:
> {code:java}
> // Init connection to node 'A'.
> Connection connection = DriverManager.getConnection(URL);
> // Restart node 'A'
> restartNode();
> // Execute some query
> Statement stmt = connection.createStatement();
> stmt.executeQuery("SELECT 1"); // fails with 'Failed to find resource
> with id: 1'
> {code}
> Currently query execution fails with the root exception "Failed to find
> resource with id: 1".
> It seems that we can handle server restart situations transparently to the
> user without throwing any errors if the server does not hold open resources
> (cursors, transactions).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
