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

Posted to issues@ignite.apache.org by "Kirill Gusakov (Jira)" <ji...@apache.org> on 2022/07/18 20:29:00 UTC

[jira] [Commented] (IGNITE-17091) Implement status command

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

Kirill Gusakov commented on IGNITE-17091:
-----------------------------------------

LGTM, thanks

> Implement status command
> ------------------------
>
>                 Key: IGNITE-17091
>                 URL: https://issues.apache.org/jira/browse/IGNITE-17091
>             Project: Ignite
>          Issue Type: Task
>            Reporter: Aleksandr
>            Assignee: Aleksandr
>            Priority: Major
>              Labels: ignite-3, ignite-3-cli-tool
>          Time Spent: 1h
>  Remaining Estimate: 0h
>
> Now "ignite status" will display the status based on local running nodes and some hacks. There should be a special endpoint to get the cluster status. CLI should call this endpoint.
>  * create a  REST endpoint
>  * Implement status command based on new endpoint
> The status command has to display at least: a cluster name, a number of nodes, initialized/not initialized.
> Also, it would be consistent to define {{cluster status}} and {{node status}} commands. 



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