lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Varun Thacker (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SOLR-8207) Modernise cloud tab on Admin UI
Date Wed, 09 May 2018 19:30:00 GMT

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

Varun Thacker commented on SOLR-8207:
-------------------------------------

Hi Jan,

Under the heap section we have 

Used: 125.6Mb
Total: 245.4Mb
Free: 119.8Mb

Instead of displaying "Free" would displaying "Max" be more useful ? 

>From the metrics API the max of this JVM is "memory.heap.max":257294336 .  This would
help indicate to the user he's running pretty close to the limit?

 

Under the Host tab, showing RAM used might bring more pain than gain? I can imagine people
going like "oh i'm running out of memory" , but then we'll have to point them to Uwe's MMap
blog? 

> Modernise cloud tab on Admin UI
> -------------------------------
>
>                 Key: SOLR-8207
>                 URL: https://issues.apache.org/jira/browse/SOLR-8207
>             Project: Solr
>          Issue Type: Improvement
>          Components: Admin UI
>    Affects Versions: 5.3
>            Reporter: Upayavira
>            Assignee: Jan Høydahl
>            Priority: Major
>         Attachments: node-compact.png, node-details.png, node-hostcolumn.png, node-toggle-row-numdocs.png,
nodes-tab-real.png, nodes-tab.png
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> The various sub-tabs of the "Cloud tab" were designed before anyone was making real use
of SolrCloud, and when we didn't really know the use-cases we would need to support. I would
argue that, whilst they are pretty (and clever) they aren't really fit for purpose (with the
exception of tree view).
> Issues:
> * Radial view doesn't scale beyond a small number of nodes/collections
> * Paging on the graph view is based on collections - so a collection with many replicas
won't be subject to pagination
> * The Dump feature is kinda redundant and should be removed
> * There is now a major overlap in functionality with the new Collections tab
> What I'd propose is that we:
>  * promote the tree tab to top level
>  * remove the graph views and the dump tab
>  * add a new Nodes tab
> This nodes tab would complement the collections tab - showing nodes, and their associated
replicas/collections. From this view, it would be possible to add/remove replicas and to see
the status of nodes. It would also be possible to filter nodes by status: "show me only up
nodes", "show me nodes that are in trouble", "show me nodes that have leaders on them", etc.
> Presumably, if we have APIs to support it, we might have a "decommission node" option,
that would ensure that no replicas on this node are leaders, and then remove all replicas
from the node, ready for it to be removed from the cluster.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message