You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Andrey Khitrin (Jira)" <ji...@apache.org> on 2022/12/01 06:36:00 UTC

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

Andrey Khitrin created IGNITE-18300:
---------------------------------------

             Summary: Node cannot properly start node 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
         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)