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

Jan Høydahl commented on SOLR-12692:
------------------------------------

All good suggestions. I don't know if you played around with the other 
warnings, but you can test e.g. by specifying only two of the zk's in {{-z}} 
when starting Solr - you will then see complaints about quorum size, mismatches 
etc. Guess you could extend those checks to also look at other values as you 
suggest.

> Add hints/warnings for the ZK Status Admin UI
> ---------------------------------------------
>
>                 Key: SOLR-12692
>                 URL: https://issues.apache.org/jira/browse/SOLR-12692
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: Admin UI
>            Reporter: Varun Thacker
>            Priority: Minor
>         Attachments: zk_ensemble.png
>
>
> Firstly I love the new UI pages ( ZK Status and Nodes ) . Thanks [~janhoy] 
> for all the great work!
> I setup a 3 node ZK ensemble to play around with the UI and attaching the 
> screenshot for reference.
>  
> Here are a few suggestions I had
>  # Let’s show Approximate Size in human readable form.  We can use 
> RamUsageEstimator#humanReadableUnits to calculate it
>  # Show warning symbol when Ensemble is standalone
>  # If maxSessionTimeout < Solr's ZK_CLIENT_TIMEOUT then ZK will only honor 
> up-to the maxSessionTimeout value for the Solr->ZK connection. We could mark 
> that as a warning.
>  # If maxClientCnxns < live_nodes show this as a red? Each solr node connects 
> to all zk nodes so if the number of nodes in the cluster is high one should 
> also be increasing maxClientCnxns
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

Reply via email to