[
https://issues.apache.org/jira/browse/IGNITE-20716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17778968#comment-17778968
]
Ivan Artiukhov commented on IGNITE-20716:
-----------------------------------------
The failure is the same as in
https://issues.apache.org/jira/browse/IGNITE-20577, but after
https://issues.apache.org/jira/browse/IGNITE-20116 it happens far less often.
> Partial data loss after node restart
> ------------------------------------
>
> Key: IGNITE-20716
> URL: https://issues.apache.org/jira/browse/IGNITE-20716
> Project: Ignite
> Issue Type: Bug
> Components: persistence
> Affects Versions: 3.0.0-beta2
> Reporter: Igor
> Priority: Major
> Labels: ignite-3
>
> How to reproduce:
> 1. Start a 1-node cluster
> 2. Create several simple tables (usually 5 is enough to reproduce):
> {code:sql}
> 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));
> ...
> {code}
> 3. Fill every table with 1000 rows.
> 4. Ensure that every table contains 1000 rows:
> {code:sql}
> SELECT COUNT(*) FROM failoverTest00;
> ...
> {code}
> 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.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
