[ 
https://issues.apache.org/jira/browse/SOLR-16773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jan Høydahl resolved SOLR-16773.
--------------------------------
    Fix Version/s: 9.3
       Resolution: Fixed

> UI: Cloud>NOdes screen can't display disk usage from replicas using 
> non-standard core names (ie: implicit router)
> -----------------------------------------------------------------------------------------------------------------
>
>                 Key: SOLR-16773
>                 URL: https://issues.apache.org/jira/browse/SOLR-16773
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>            Reporter: Chris M. Hostetter
>            Assignee: Jan Høydahl
>            Priority: Major
>             Fix For: 9.3
>
>         Attachments: implict_router_ui_metrics_bug.png
>
>          Time Spent: 1.5h
>  Remaining Estimate: 0h
>
> Consider the following cluster w/three collections (including the 
> {{gettingstarted}} collection created by the example)...
> {noformat}
> ./solr/packaging/build/dev/bin/solr -e cloud -noprompt
> curl -sS 
> 'http://localhost:8983/solr/admin/collections?action=CREATE&name=named_shards&router.name=compositeId&numShards=2&shards=shardX,shardY'
> curl -sS 
> 'http://localhost:8983/solr/admin/collections?action=CREATE&name=implicit_named_shards&router.name=implicit&shards=shardA,shardB'{noformat}
>  
> If you look at the Cloud>Nodes screen for this cluster, the "Disk Usage" (and 
> other metrics) for the cores from the {{implicit_named_shards}} collection 
> wound show up. (see screenshot)
>  
> The problem is that {{cloud.js}} expects core names to follow a very specific 
> format, but implicit router names it's cores directly after the shard names 
> specified.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org

Reply via email to