[ 
https://issues.apache.org/jira/browse/SOLR-5810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14292216#comment-14292216
 ] 

Timothy Potter commented on SOLR-5810:
--------------------------------------

I don't think this is UI code related ... the /clusterstate.json after running 
the {{solr -e cloud}} command doesn't look correct to me:

{code}
{"gettingstarted":{
    "replicationFactor":"2",
    "router":{"name":"compositeId"},
    "maxShardsPerNode":"2",
    "autoAddReplicas":"false",
    "shards":{
      "shard1":{
        "range":"80000000-ffffffff",
        "state":"active",
        "replicas":{}},
      "shard2":{
        "range":"0-7fffffff",
        "state":"active",
        "replicas":{}}}}}
{code}

here's the crazy thing ... if you run {{bin/solr create -c foo}} after starting 
up the example, then /clusterstate.json gets emptied {{ {} }} and the UI 
renders both collections correctly. So seems like some weird initial state 
related to stateFormat=2

> State of external collections not displayed in cloud graph panel
> ----------------------------------------------------------------
>
>                 Key: SOLR-5810
>                 URL: https://issues.apache.org/jira/browse/SOLR-5810
>             Project: Solr
>          Issue Type: Improvement
>          Components: SolrCloud, web gui
>            Reporter: Timothy Potter
>            Assignee: Timothy Potter
>            Priority: Blocker
>             Fix For: 5.0, Trunk
>
>         Attachments: SOLR-5810-prelim.patch, SOLR-5810.patch, 
> SOLR-5810.patch, SOLR-5810.patch, SOLR-5810.prelim2.patch
>
>
> External collections (SOLR-5473) are not displayed in the Cloud -> graph 
> panel, which makes it very hard to see which external collections have 
> problems, such as after a downed node comes back online.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to