lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kelly, Frank" <frank.ke...@here.com>
Subject Re: solcloud on production
Date Fri, 08 Apr 2016 12:34:00 GMT
I have found that ZooKeeper is the weak link for SolrCloud especially if
deployed on a Cloud environment (AWS).

https://issues.apache.org/jira/browse/SOLR-3274

https://issues.apache.org/jira/browse/SOLR-8868


And others see 
https://issues.apache.org/jira/browse/ZOOKEEPER-2112?jql=project%20%3D%20ZO
OKEEPER%20AND%20issuetype%20%3D%20Bug%20AND%20status%20in%20(Open%2C%20%22I
n%20Progress%22%2C%20Reopened)%20AND%20text%20~%20%22quorum%22


The kicker is that is ZK loses and quorum but gets it back we not only
have to restart Solr servers but also those services who are clients :-(

-Frank

Frank Kelly
Principal Software Engineer
Predictive Analytics Team (SCBE/HAC/CDA)

HERE 
5 Wayside Rd, Burlington, MA 01803, USA
42° 29' 7" N 71° 11' 32² W

 <http://360.here.com/>   <https://twitter.com/here>
<https://www.facebook.com/here>    <https://linkedin.com/company/heremaps>
   <https://www.instagram.com/here>







On 4/8/16, 2:39 AM, "Midas A" <test.midas@gmail.com> wrote:

>Hi All ,
>
>we are moving from master slave architecture to solr cloud architecture .
>so i would like to know following
>
>-  what kind of challenges we can face on production  .
>
>-  Is there any drawback of solrcloud
>
>-  How solr cloud distributes requests between nodes and how node will
>behave on heavy traffic .
>
>- Is there any way to shard node with custom logic
>
>
>
>
>Regards,
>MA


Mime
View raw message