You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Aleksandr (Jira)" <ji...@apache.org> on 2023/03/02 14:57:00 UTC

[jira] [Commented] (IGNITE-18674) Introduce UI thread to CLI

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

Aleksandr commented on IGNITE-18674:
------------------------------------

merged into main: d8885b22d05231af53996ace5bbf9fb0564bedc9

> Introduce UI thread to CLI
> --------------------------
>
>                 Key: IGNITE-18674
>                 URL: https://issues.apache.org/jira/browse/IGNITE-18674
>             Project: Ignite
>          Issue Type: Task
>          Components: cli
>            Reporter: Aleksandr
>            Assignee: Aleksandr
>            Priority: Major
>              Labels: ignite-3
>          Time Spent: 1h
>  Remaining Estimate: 0h
>
> The current SQL query completion process may obstruct the UI thread and result in CLI hang-ups when Ignite 3 node fails to respond. 
> To prevent this issue, we need to implement a separate UI thread for all user-facing operations with a maximum block time of 5-10 seconds. The CLI must be protected from indefinite hang-ups at all times, regardless of Ignite 3 node behavior. To accomplish this, we should adopt a single UI thread and worker pool design with asynchronous communication, allowing the UI thread to receive notifications without being blocked.



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