[
https://issues.apache.org/jira/browse/SOLR-8207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16575469#comment-16575469
]
Jan Høydahl commented on SOLR-8207:
-----------------------------------
Uploaded another patch in [^SOLR-8207_shardstate.patch] which
* Further improves the regex to support ...{{_shard_x_y_z_replica_1}} style
cores, i.e. with complex shard numbers and with missing replicaType character.
It also plays well with Solr6 style node names {{_shard1_replica1}}.
* Do not display replicas for inactive shards (that you get after a split)
* If a replica has a state other than "active" (such as recovering), display
the state in parenthesis after shard name. We could have used the same graphics
and circles with colours as in the graph view, but I just make it dead simple
for now
[~ab]: Dots or other chars in collection names works with this regex, tested
with collections ".system" as well as ".coll_with_underscores", and it all
works fine both for looking up metrics and for creating a display label.
Will commit this tomorrow if I don't hear any objections. Thanks [~tomasflobbe]
for pointing out the split shard naming which also caused me to discover the
need for hiding inactive shards.
> 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_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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
