[jira] [Commented] (IGNITE-18300) Node cannot properly start after failure in index creation

["Andrey Khitrin (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/IGNITE-18300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17641734#comment-17641734 ] 

Andrey Khitrin commented on IGNITE-18300:
-----------------------------------------

Succesfully reproduced.
 # On a fresh DB, create a table and two indices, put some data:

{code:sql}
sql-cli> CREATE TABLE test_indices (field1 INTEGER PRIMARY KEY, field2 INTEGER, field3 INTEGER);
Updated 0 rows.
sql-cli> CREATE INDEX ti1 ON test_indices (field2);
Updated 0 rows.
sql-cli> INSERT INTO test_indices VALUES(1, 1, 1);
Updated 1 rows.
sql-cli> CREATE INDEX ti2 ON test_indices (field3, field1);
Updated 0 rows.
sql-cli> INSERT INTO test_indices VALUES(2, 1, 0);
Updated 1 rows.
sql-cli> SELECT * FROM test_indices;
╔════════╤════════╤════════╗
║ FIELD1 │ FIELD2 │ FIELD3 ║
╠════════╪════════╪════════╣
║ 2      │ 1      │ 0      ║
╟────────┼────────┼────────╢
║ 1      │ 1      │ 1      ║
╚════════╧════════╧════════╝ {code}
2. Exit from SQL console and restart DB (e.g., via `systemctl restart ignite3db.service`).

3. After restart, we got a block

 

> Node cannot properly start after failure in index creation
> ----------------------------------------------------------
>
>                 Key: IGNITE-18300
>                 URL: https://issues.apache.org/jira/browse/IGNITE-18300
>             Project: Ignite
>          Issue Type: Bug
>          Components: ignite-3
>    Affects Versions: 3.0.0-beta1
>            Reporter: Andrey Khitrin
>            Priority: Major
>              Labels: sql
>         Attachments: ignite3-cli.dump, ignite3-db.dump, logs.tgz
>
>
> I play with AI3 beta on a virtual machine (a single node). I tried to create a SQL index on a table (unsuccessfully), and now I couldn't even work with a node.
> Symptoms:
>  # ignite3 CLI connects to DB node but cannot execute any command properly. Because of auto completion, it asks DB for a list of existing tables and waits for it forever. For end user, it looks like CLI freezes. Probably, that's a separate issue.
>  # Ignite3 DB cannot respond to CLI because it's struck in endless waiting.
> I don't remember well what caused this issue. Most probably, it happened because of different `CREATE INDEX` commands I played with before. I've made thread dumps both for CLI and DB processes, and also attached all exisitng DB logs (within .tgz file). Hope this helps.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)