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

Erick Erickson commented on SOLR-13502:
---------------------------------------

Two reasons:

1> AFAIK, this is the _only_ use of the "4-letter words" in Solr, seems a bit 
awkward.
2> existing users who upgrade will not be able to use existing zoo.cfg files 
and we'll have to deal with that set of questions.

That said, I don't have strong feelings on this. If it's easy, I think it would 
be a good change. If not, not worth the hassle.

> Investigate using something other than ZooKeeper's "4 letter words" for the 
> admin UI status
> -------------------------------------------------------------------------------------------
>
>                 Key: SOLR-13502
>                 URL: https://issues.apache.org/jira/browse/SOLR-13502
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>            Reporter: Erick Erickson
>            Assignee: Erick Erickson
>            Priority: Major
>
> ZooKeeper 3.5.5 requires a whitelist of allowed "4 letter words". The only 
> place I see on a quick look at the Solr code where 4lws are used is in the 
> admin UI "ZK Status" link.
> In order to use the admin UI "ZK Status" link, users will have to modify 
> their zoo.cfg file with
> {code}
> 4lw.commands.whitelist=mntr,conf,ruok
> {code}
> This JIRA is to see if there are alternatives to using 4lw for the admin UI.
> This depends on SOLR-8346. If we find an alternative, we need to remove the 
> additions to the ref guide that mention changing zoo.cfg (just scan for 4lw 
> in all the .adoc files) and remove SolrZkServer.ZK_WHITELIST_PROPERTY and all 
> references to it (SolrZkServer and SolrTestCaseJ4).



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

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

Reply via email to