[
https://issues.apache.org/jira/browse/SOLR-8207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16574776#comment-16574776
]
Andrzej Bialecki commented on SOLR-8207:
-----------------------------------------
[~janhoy] we allow at least one collection with '.' in the name, namely
{{.system}} . For this collection the metric registry name looks like this:
{{solr.core..system.shard1.replica_n1}} (notice two dots).
In other words, collection names may contain separator chars in either core
name (where '_' is used) or registry name (where '.' is used) so the best
approach is to build a regex that chops off the front and end parts of the name
that follow stricter patterns, and then what's left in the middle is the
collection name, however weird it may be ;)
> 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_underscores.patch,
> SOLR-8207_underscores.patch, 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: [email protected]
For additional commands, e-mail: [email protected]
