[
https://issues.apache.org/jira/browse/SOLR-8207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16576137#comment-16576137
]
Jan Høydahl commented on SOLR-8207:
-----------------------------------
I have put som effort into this:
* Paging 10 hosts at a time, i.e. even if you have 1000 nodes, only 10 will be
queried for status/metrics at a time
If you have 1000's of nodes on one single host name, then there may be issues,
since we page per host and not per node
* All collections and replicas per node will be filled in the HTML page, but
only the first few will be shown by default until expanding. When expanding,
all collections/replicas on that node will be shown. If you have 1000
collections, I assume that those will be spread across more than one node :)
* If you have 1000 collections, each with multi shards and replicas, I can
imagine that the CLUSTERSTATUS command will take quite some time and result in
a huge JSON. But that is only fetched on page load, not on paging through the
nodes, filtering by name or clicking "refresh".
> Add "Nodes" view to the Admin UI "Cloud" tab
> --------------------------------------------
>
> Key: SOLR-8207
> URL: https://issues.apache.org/jira/browse/SOLR-8207
> Project: Solr
> Issue Type: New Feature
> Components: Admin UI
> Reporter: Upayavira
> Assignee: Jan Høydahl
> Priority: Major
> Fix For: master (8.0), 7.5
>
> Attachments: SOLR-8207.patch, SOLR-8207_shardstate.patch,
> SOLR-8207_shardstate.patch, SOLR-8207_underscores.patch,
> SOLR-8207_underscores.patch, image-2018-08-10-10-33-08-290.png,
> node-compact.png, node-details.png, node-hostcolumn.png,
> node-toggle-row-numdocs.png, nodes-tab-real.png, nodes-tab.png, nodes.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-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
