[jira] [Commented] (SOLR-10573) Hide ZooKeeper

["Shawn Heisey (JIRA)" <ji...@apache.org>]

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

Shawn Heisey commented on SOLR-10573:
-------------------------------------

For reasons that I covered in my reply to your solr-user message, I think ZK should remain in a separate process.

I am all for creating a system where the user never has to know anything about zookeeper configuration to get a fault-tolerant cloud up and running.  I agree with Yonik's message on the list where he talks about the difference between internal complexity and difficulty for the user.

My most recent comment on SOLR-9635 discusses an idea related to this that will require substantial work to realize, but would create a very easy user experience.


> Hide ZooKeeper
> --------------
>
>                 Key: SOLR-10573
>                 URL: https://issues.apache.org/jira/browse/SOLR-10573
>             Project: Solr
>          Issue Type: New Feature
>      Security Level: Public(Default Security Level. Issues are Public) 
>            Reporter: Otis Gospodnetic
>
> It may make sense to either embed ZK in Solr and allow running Solr instances with just ZK and no data or something else that hides ZK from Solr users...
> Based on what the Solr poll that revealed lowish SolrCloud adoption and comments in 
> http://search-lucene.com/m/Solr/eHNlm8wPIKJ3v51?subj=Poll+Master+Slave+or+SolrCloud that showed that people still find SolrCloud complex, at least partly because of the external ZK recommendation.
> See also: http://search-lucene.com/m/Lucene/l6pAi11rBma0gNoI1?subj=SolrCloud+master+mode+planned+



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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