[
https://issues.apache.org/jira/browse/SOLR-8207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16471035#comment-16471035
]
Jan Høydahl commented on SOLR-8207:
-----------------------------------
{quote}How about making it default for Solr 8.0
{quote}
Agree
{quote}Can we change the key name from "Cores" to "Replicas" maybe?
{quote}
Yea, guess that's the official term in cloud setting, will change
{quote}[heap] Instead of displaying "Free" would displaying "Max" be more
useful ?
{quote}
Sure, we can display "Max" and "Used" and pct used.
{quote}I think that physical RAM usage should not be shown in the Solr admin UI
{quote}
In a debugging setting it is useful to know how much physical RAM is on each
server. One of the more common mistakes I see is to allocate 15G to JVM when
you have 16G physical. So I want to display amount of physical mem. Knowing
this and the max heap we normally know about how much free physical mem is left
for caching, if Solr is the only major application running on the host. Still,
for consistency I thin we should also show "used" number, and explain how to
interpret in the ref guide and perhaps mouseover.
> 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]
