You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Pavel Pereslegin (Jira)" <ji...@apache.org> on 2024/04/03 12:44:00 UTC
[jira] [Created] (IGNITE-21934) Sql. Jdbc. Design transparent client-server "reconnect"
Pavel Pereslegin created IGNITE-21934:
-----------------------------------------
Summary: Sql. Jdbc. Design transparent client-server "reconnect"
Key: IGNITE-21934
URL: https://issues.apache.org/jira/browse/IGNITE-21934
Project: Ignite
Issue Type: Improvement
Components: sql
Reporter: Pavel Pereslegin
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)