[
https://issues.apache.org/jira/browse/SOLR-8207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16464969#comment-16464969
]
Shawn Heisey commented on SOLR-8207:
------------------------------------
Thanks for looking into making improvements! There's some really good info
being shown here.
Some thoughts after looking at screenshots:
* I think that perhaps "refresh" would be a better label than "reload". There
is potential for confusion with the reload action on core/collection APIs.
Having different buttons to reload the collections might be a nice addition.
* What is the percentage on the disk column -- free or used? Unless the nodes
being reported on the screenshots are extremely small VMs or containers, I
think that the 91 or 92 percent shown there must be percent free. It is my
opinion that without text indicating which one is displayed, it should be
percent used, not percent free, as is the case for other columns like Heap. If
consensus is that percent free is more useful for disk space, then it should
say "free" somewhere.
* I wasn't sure what the GC numbers meant until I read the comments more
closely. If I'm reading the info correctly, it's number of collections for a
five minute period, averaged over the whole JVM uptime. Unless request traffic
is fairly uniform 24 hours per day, this does not seem like a very useful
number to me. I do not know if the JVM can access GC data for a smaller
timeframe. If not, it might not be possible to provide better information here.
* If the table only includes one request rate, I think I would prefer to see
the 15 minute rate rather than the 1 minute rate. Maybe that's just me. :)
> 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: [email protected]
For additional commands, e-mail: [email protected]
