[IGNITE-21934] Sql. Jdbc. Design transparent handling of server node restart

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: sql
• Labels: ignite-3
• Ignite Flags: Docs Required, Release Notes Required
• Assignee: Unassigned
• Reporter: Pavel Pereslegin
• Created: 03/Apr/24 12:43
• Updated: 03/Apr/24 12:46

Description

We need to develop a possible solution to properly handle a server node restart.
For example:

    // 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'

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).

Issue Links

• relates to: IGNITE-21894 Sql. Undescriptive error when restart cluster node during open JDBC transaction