[
https://issues.apache.org/jira/browse/SOLR-8207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16406358#comment-16406358
]
Jan Høydahl commented on SOLR-8207:
-----------------------------------
{quote}+1 - I'm not against a rename, but there must be a better one for Solr
that is not impl related.
{quote}
Perhaps "State"? Configs are part of the cluster->state...
{quote}I think it would be nice if it could show the names and states of the
shards that are on each node. Maybe that should be a secondary view for that
screen? Something like, click the # of shards and a list pops up?
{quote}
Agree, expanding on click to show all shard/replica names, and then being able
to initiate some action on each of the replicas, or "jump" to the Collections
view expanded on that replica - we must think about the overlap between the
screens...
{quote}The graph view, which you've renamed Collections (+1 IMO), would show
where replicas are from the POV of each collection
{quote}
The "Graph" view currently lets you see the graph for each collection -> shards
-> replicas and their state and a link to that replica. I don't plan to get rid
of that view after the rename, but I want to include a tabular view of
collections in addition. Perhaps though tabs along the top of the view, or
using two different left-hand menu tabs "Collections" and "Collections (graph)"?
> 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: Upayavira
> Priority: Major
> Attachments: nodes-tab.png
>
>
> 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
