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

Stefan Matheis (steffkes) updated SOLR-6614:
--------------------------------------------
    Attachment: Screen Shot 2014-11-14 at 3.44.38 PM.png
                Screen Shot 2014-11-14 at 3.44.05 PM.png
                Screen Shot 2014-11-14 at 3.43.53 PM.png
                Screen Shot 2014-11-14 at 3.43.39 PM.png

sometimes a picture can say more than a bunch of words .. at least for me, 
right now ;> attached screenshots should give an explanation what is happening 
here. they are btw done in chrome, on the bottom you see the chrome developer 
tools - just in case you're wondering.

> SolrCloud graph viz truncates port designation
> ----------------------------------------------
>
>                 Key: SOLR-6614
>                 URL: https://issues.apache.org/jira/browse/SOLR-6614
>             Project: Solr
>          Issue Type: Bug
>          Components: SolrCloud, web gui
>    Affects Versions: 4.10.1
>            Reporter: Ralph Tice
>            Priority: Minor
>         Attachments: SOLR-6614.patch, Screen Shot 2014-11-14 at 3.43.39 
> PM.png, Screen Shot 2014-11-14 at 3.43.53 PM.png, Screen Shot 2014-11-14 at 
> 3.44.05 PM.png, Screen Shot 2014-11-14 at 3.44.38 PM.png
>
>
> I believe this is a regression but I didn't see anything jump out at me from 
> the history on cloud.js.  The port designation for shards is truncated.  I am 
> pretty sure the port designation only appears if you have multiple JVMs on 
> the same hostname in your SolrCloud.
> Here is a visual depiction of the problem: 
> http://monosnap.com/image/WzETqptfhcuDGKXjpJPR854lIzriyI
> I have a very minor patch which addresses this as well as an issue with the 
> legend being overlaid on top of shard designations.  It's pretty simple, but 
> I generally only have the use case of dozens or hundreds of shards so I'm not 
> sure how this looks in other situations.



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