You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Alexey Kuznetsov (JIRA)" <ji...@apache.org> on 2018/10/27 13:12:00 UTC
[jira] [Updated] (IGNITE-10031) REST: Introduce "caches" param for
"top" command.
[ https://issues.apache.org/jira/browse/IGNITE-10031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexey Kuznetsov updated IGNITE-10031:
--------------------------------------
Description:
We have top command on REST API:
https://apacheignite.readme.io/docs/rest-api#topology
And result of this command also contains short caches info (name, mode & SQL Schema).
But in situation when node contains thousand caches and hundred nodes and caches have long names - that will result in a HUGE JSON.
For example, I get 88Mb JSON for cluster of 128 nodes and 6000 caches.
And my application do not need that info about caches, I just need a list of node IDs.
Lets add one more flag "excludeCaches" as we already have "attr" & "mtr".
was:
We have top command on REST API:
https://apacheignite.readme.io/docs/rest-api#topology
And result of this command also contains short caches info (name, mode & SQL Schema).
But in situation when node contains thousand caches and hundred nodes and caches have long names - that will result in a HUGE JSON.
For example, I get 88Mb JSON for cluster of 128 nodes and 6000 caches.
And my application do not need that info about caches, I just need a list of node IDs.
Lets add one more flag "caches" as we already have "attr" & "mtr".
For compatibility reasons I will preserve current behaviour if "caches" flag will not be specified.
> REST: Introduce "caches" param for "top" command.
> -------------------------------------------------
>
> Key: IGNITE-10031
> URL: https://issues.apache.org/jira/browse/IGNITE-10031
> Project: Ignite
> Issue Type: Improvement
> Components: rest
> Reporter: Alexey Kuznetsov
> Assignee: Alexey Kuznetsov
> Priority: Major
> Fix For: 2.8
>
>
> We have top command on REST API:
> https://apacheignite.readme.io/docs/rest-api#topology
> And result of this command also contains short caches info (name, mode & SQL Schema).
> But in situation when node contains thousand caches and hundred nodes and caches have long names - that will result in a HUGE JSON.
> For example, I get 88Mb JSON for cluster of 128 nodes and 6000 caches.
> And my application do not need that info about caches, I just need a list of node IDs.
> Lets add one more flag "excludeCaches" as we already have "attr" & "mtr".
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)