[
https://issues.apache.org/jira/browse/SOLR-8207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16465281#comment-16465281
]
Jan Høydahl edited comment on SOLR-8207 at 5/6/18 8:19 PM:
-----------------------------------------------------------
{quote}I'm not sure how the "last 5 min stats" was calculated here in the patch
{quote}
The patch prints "Minor: 0.17/5m", which is "per 5 min", not *last* 5 min. But
since this is since JVM start which could be months ago, this value is not very
useful at this time.
{quote}it's pretty simple to create a {{Meter}} or a {{Timer}} for each of
these GC beans and register them as new metrics...
{quote}
Great! My proposal is then to remove the GC column for now and instead create a
new Jira (SOLR-12318) which adds some new 1-, 5-, 15-min avg metrics for use in
a new GC column.
was (Author: janhoy):
{quote}I'm not sure how the "last 5 min stats" was calculated here in the patch
{quote}
The patch prints "Minor: 0.17/5m", which is "per 5 min", not *last* 5 min. But
since this is since JVM start which could be months ago, this value is not very
useful at this time.
{quote}it's pretty simple to create a {{Meter}} or a {{Timer}} for each of
these GC beans and register them as new metrics...
{quote}
Great! My proposal is then to remove the GC column for now and instead create a
new Jira which adds some new 1-, 5-, 15-min avg metrics for use in a new GC
column.
> 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]
