[
https://issues.apache.org/jira/browse/SOLR-8207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16465219#comment-16465219
]
Jan Høydahl commented on SOLR-8207:
-----------------------------------
Thanks all for looking at this and giving such constructive feedback!
[~dsmiley]:
{quote} * the large fonts for CPU/Heap/Disk seem uncalled for; it gives the
appearance that it's super important and maybe trying to tell me about a
problem{quote}
I'd love for someone to do better styling of this, but I just think it creates
a nice visual :) I planned to use colors to warn about dangerous numbers, such
as RED for >80% full disk or >80% CPU, and orange for >50%. Wdyt?
{quote} * it's not visually evident that clicking stuff will do
something.{quote}
Good point. Will update the CSS with some underlining, colour change and
perhaps pointer change. Or perhaps we have a global css style that can be
applied to all the links here.
[~elyograg]:
{quote}I think that perhaps "refresh" would be a better label than "reload"
{quote}
Definitely, will change that.
{quote} Having different buttons to reload the collections might be a nice
addition
{quote}
In the next iteration I plan to add context-sensitive menus to many of these
cells, so e.g. clicking collection name could have an option to reload,
clicking a core name could have an option to delete etc.
{quote}What is the percentage on the disk column – free or used?
{quote}
Disk is used %, just like CPU is. If you mouse-over (check the demo link)
you'll see details of total disk, free etc. It may be an idea to replace the
disk percentage (or all percentage numbers) with a horizontal bar instead,
where the bar changes colour to orange/red at critical levels?
{quote}[GC...] 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.
{quote}
That were the only numbers I found in current metrics API. I agree that if it
is possible to get, say, last-15-minutes numbers that would be much better.
[~ab]?
{quote}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.
{quote}
Yea, just picked something, could very well be that 15min rate makes more
sense. Can change that :)
[~upayavira]:
{quote}If you click on a node cell, it only opens up the first instance row,
not all for that node.
{quote}
That's by design, since the {{ng-click}} is on the {{<tr>}}. However, it could
be nice if clicking the "host" cell would expand all node rows on that same
host. Guess that means that we need to move the ng-click from tr to the
{{<td>}} level to be able to call different functions? Btw - now if you click a
collection/core name, the details view gets expanded first and then the link is
clicked/followed. Is there any way to disable the ng-click handler for the <a>
inside that cell?
{quote}If the window is too narrow, something odd happens with the text in the
right-hand column
{quote}
You mean the line wraps? The alternative I guess is to specify a min-width on
that 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]
