ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Artem Budnikov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-10031) REST: Introduce "caches" param for "top" command.
Date Mon, 29 Oct 2018 09:41:00 GMT

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

Artem Budnikov commented on IGNITE-10031:
-----------------------------------------

[~kuaw26] please create a documentation ticket for this.

> 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: Artem Budnikov
>            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 "caches" (with default value "true", for compatibility) as we
already have "attr" & "mtr".



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message