[IGNITE-20834] SQL query may hang forerver after node restart

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.0.0-beta2
• Labels: ignite-3 sql
• Ignite Flags: Docs Required, Release Notes Required
• Assignee: Unassigned
• Reporter: Andrey Khitrin
• Created: 13/Nov/23 07:55
• Updated: 22/Dec/23 13:21
• Resolved: 22/Dec/23 13:21

Description

How to reproduce:

1. Start a 1-node cluster
2. Create several simple tables (usually 5-10 is enough to reproduce):

create table failoverTest00(k1 INTEGER not null, k2 INTEGER not null, v1 VARCHAR(100), v2 VARCHAR(255), v3 TIMESTAMP not null, primary key (k1, k2));
create table failoverTest01(k1 INTEGER not null, k2 INTEGER not null, v1 VARCHAR(100), v2 VARCHAR(255), v3 TIMESTAMP not null, primary key (k1, k2));
...

3. Fill every table with 1000 rows.
4. Ensure that every table contains 1000 rows:

SELECT COUNT(*) FROM failoverTest00;
...

5. Restart node (kill a Java process and start node again).
6. Check all tables again.

Expected behavior: after restart, all tables still contains the same data as before.

Actual behavior: cannot perform SQL query after restart. It hangs for a long time. Ignite log is overwhelmed with "Primary replica expired" messages.

This bug was first observed soon after fixes in https://issues.apache.org/jira/browse/IGNITE-20116.

Issue Links

• is a clone of: IGNITE-20577 Partial data loss after node restart
• is related to: IGNITE-20116 Linearize storage updates with safeTime adjustment rules