[IGNITE-20716] Partial data loss after node restart

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 3.0.0-beta2
• Component/s: persistence
• Labels: ignite-3
• Ignite Flags: Docs Required, Release Notes Required
• Assignee: Unassigned
• Reporter: Igor
• Created: 23/Oct/23 15:14
• Updated: 24/Oct/23 07:26

Description

How to reproduce:

1. Start a 1-node cluster
2. Create several simple tables (usually 5 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: for some tables, 1 or 2 rows may be missing, if we're fast enough on steps 3-4-5. Some contains 1000 rows, some contains 999 or 998.

No errors in logs observed.

Issue Links

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