[
https://issues.apache.org/jira/browse/IGNITE-18378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr updated IGNITE-18378:
-------------------------------
Description:
This epic is a result of IGNITE-17102.
h2. What should be displayed
h3. Cluster-only information
* Cluster name
* Cluster Id
* Cluster status
* Ignite version
* Status of CMG (available/ not available)
* Status of Meta storage (available/ not available)
* Number of total nodes in cluster (online/offline/joinig)
* Number of CMG nodes (online/offline)
* Number of Meta storage nodes (online/offline)
h3. Data-related information
* Used RAM
* Used Disc
* Total RAM
* Total Disc
* Available RAM
* Available Disc
* Number of caches
* Number of partitions
* Number of tables
* Number of databases
* Number of schemas
* Number of distribution zones
* Available storages (page memory, rocks db, ..)
* Sizes info per storage
h3. Clients info
* Number of current clients connections
* List of available connections (rest, jdbc)
h2. How to display
Take a look at the attachment.
The proposed “interface” is shown like a “live dashboard”. It means that the
user should not run the cluster show each time to see updates.
If {{--plain}} option is provided that the command should display the
“snapshot of the live dashboard”.
h2. Notes
Now we do not have API to build such a dashboard. That is why it is an epic,
not a task.
was:
This epic is a result of IGNITE-17102.
h2. What should be displayed
h3. Cluster-only information
* Cluster name
* Cluster Id
* Cluster status
* Ignite version
* Status of CMG (available/ not available)
* Status of Meta storage (available/ not available)
* Number of total nodes in cluster (online/offline/joinig)
* Number of CMG nodes (online/offline)
* Number of Meta storage nodes (online/offline)
h3. Data-related information
* Used RAM
* Used Disc
* Total RAM
* Total Disc
* Available RAM
* Available Disc
* Number of caches
* Number of partitions
* Number of tables
* Number of databases
* Number of schemas
* Number of distribution zones
* Available storages (page memory, rocks db, ..)
* Sizes info per storage
h3. Clients info
* Number of current clients connections
* List of available connections (rest, jdbc)
h2. How to display
Take a look at the attachment.
The proposed “interface” is shown like a “live dashboard”. It means that the
user should not run the cluster show each time to see updates.
If {{--plain}} option is provided that the command should display the
“snapshot of the live dashboard”.
> Cluster show command
> --------------------
>
> Key: IGNITE-18378
> URL: https://issues.apache.org/jira/browse/IGNITE-18378
> Project: Ignite
> Issue Type: Epic
> Reporter: Aleksandr
> Priority: Major
> Labels: cli, ignite-3, rest
> Attachments: cluster_show.jpg
>
>
> This epic is a result of IGNITE-17102.
> h2. What should be displayed
> h3. Cluster-only information
> * Cluster name
> * Cluster Id
> * Cluster status
> * Ignite version
> * Status of CMG (available/ not available)
> * Status of Meta storage (available/ not available)
> * Number of total nodes in cluster (online/offline/joinig)
> * Number of CMG nodes (online/offline)
> * Number of Meta storage nodes (online/offline)
> h3. Data-related information
> * Used RAM
> * Used Disc
> * Total RAM
> * Total Disc
> * Available RAM
> * Available Disc
> * Number of caches
> * Number of partitions
> * Number of tables
> * Number of databases
> * Number of schemas
> * Number of distribution zones
> * Available storages (page memory, rocks db, ..)
> * Sizes info per storage
> h3. Clients info
> * Number of current clients connections
> * List of available connections (rest, jdbc)
> h2. How to display
> Take a look at the attachment.
> The proposed “interface” is shown like a “live dashboard”. It means that the
> user should not run the cluster show each time to see updates.
> If {{--plain}} option is provided that the command should display the
> “snapshot of the live dashboard”.
> h2. Notes
> Now we do not have API to build such a dashboard. That is why it is an epic,
> not a task.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
