[
https://issues.apache.org/jira/browse/IGNITE-17102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr updated IGNITE-17102:
-------------------------------
Description:
h2. Motivation
`cluster show` is a good candidate to be a command that gives to the user
enough information to understand:
1. if there are no problems with the cluster (all nodes in topology alive, etc.)
2. if there is something wrong (some node died, physical topology and logical
are different. etc.) the user should see *what is going wrong and what they
should do next in order to fix the issue*.
h2. Requirements
- collect all possible insights that might be important to display
- design how the result of the `cluster show` could be displayed
- create several tickets for implementation
was:Now `cluster show` is an alias for `status` but according to the IEP it
should display wider information.
> Design cluster show command
> ---------------------------
>
> Key: IGNITE-17102
> URL: https://issues.apache.org/jira/browse/IGNITE-17102
> Project: Ignite
> Issue Type: Task
> Components: cli
> Reporter: Aleksandr
> Priority: Major
> Labels: ignite-3, ignite-3-cli-tool
>
> h2. Motivation
> `cluster show` is a good candidate to be a command that gives to the user
> enough information to understand:
> 1. if there are no problems with the cluster (all nodes in topology alive,
> etc.)
> 2. if there is something wrong (some node died, physical topology and logical
> are different. etc.) the user should see *what is going wrong and what they
> should do next in order to fix the issue*.
> h2. Requirements
> - collect all possible insights that might be important to display
> - design how the result of the `cluster show` could be displayed
> - create several tickets for implementation
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
