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

Houston Putman commented on SOLR-16891:
---------------------------------------

So my way of fixing this is to remove the difference between writing to a map 
and writing to JSON, for all of DocCollection, Slice and Replica. That way we 
can easily create a Map of the state, like we need to do in 
ZookeeperInfoHandler, and we don't need to write to JSON and then deserialize 
it, like was done for PRS.

We can simply use the MapWriter interface, and write to a new map.

> Solr Cloud Graph screen blank
> -----------------------------
>
>                 Key: SOLR-16891
>                 URL: https://issues.apache.org/jira/browse/SOLR-16891
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: Admin UI
>    Affects Versions: 9.3
>            Reporter: Houston Putman
>            Priority: Blocker
>             Fix For: 9.3
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> The Solr Admin UI - Cloud - Graph screen is blank. This was not an issue in 
> Solr 9.2.1, so an API must have changed to make this no longer work.
> After some investigation, the screen uses the Zookeeper API to look at 
> {{{}clusterstate.json{}}}, so there must have been some back-compat logic in 
> the Zookeeper API to make that work given that {{clusterstate.json}} no 
> longer exists. This may no longer work.
> As an easy fix, we can just move to using the Collections ClusterStatus API 
> which returns the same data that used to exist in the 
> {{{}clusterstate.json{}}}, so we don't even need to map fields or anything.



--
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