Thanks.
--
Gian Maria Ricci
Cell: +39 320 0136949
-Original Message-
From: Alessandro Benedetti [mailto:abenede...@apache.org]
Sent: martedì 12 gennaio 2016 10:52
To: solr-user@lucene.apache.org
Subject: Re: Change leader in SolrCloud
I would like to do a special mention
ard Solr can guarantee
> consistency of data.
>
> Now everything is more clear. Thanks for the explanation.
>
> --
> Gian Maria Ricci
> Cell: +39 320 0136949
>
>
> -Original Message-
> From: Erick Erickson [mailto:erickerick...@gmail.com]
> Sent: mart
for the explanation.
--
Gian Maria Ricci
Cell: +39 320 0136949
-Original Message-
From: Erick Erickson [mailto:erickerick...@gmail.com]
Sent: martedì 12 gennaio 2016 02:27
To: solr-user <solr-user@lucene.apache.org>
Subject: Re: Change leader in SolrCloud
bq: It seems to me a huge
w
bq: It seems to me a huge wasting of resources.
How else would you guarantee consistency? Especially taking
in to account Lucene's write-once segments? Master/Slave
sidesteps the problem by moving entire, closed segments to the
slave, but as Shawn says if the master goes down the slaves
don't
On 1/11/2016 1:23 PM, Gian Maria Ricci - aka Alkampfer wrote:
> Ok, this imply that if I have X replica of a shard, the document is indexed
> X+1 times? one for each replica plus the leader shard? It seems to me a huge
> wasting of resources.
>
> In a Master/slave scenario indexing takes
Maria Ricci
Cell: +39 320 0136949
-Original Message-
From: Erick Erickson [mailto:erickerick...@gmail.com]
Sent: lunedì 11 gennaio 2016 19:03
To: solr-user <solr-user@lucene.apache.org>
Subject: Re: Change leader in SolrCloud
You have to assign the preferredLeader role firs
This is an interesting point.
Unfortunately I am not sure it is possible to configure anywhere to avoid
the leaders co-location.
I think zookeeper ideally assumes each solr node is on a separate machine.
Curious to know if we can optimize the colocation though config.
Cheers
On 11 January 2016
On 1/11/2016 8:45 AM, Gian Maria Ricci - aka Alkampfer wrote:
> Due to the different reboot times probably, I’ve noticed that upon
> reboot all three leader shards are on a single machine. I’m expecting
> shard leaders to be distributed evenly between machines, because if
> all shard leader are on
Shawn is spot-on, here's a little bit of "color commentary"
bq: all new documents to index will be routed to the same machine,
thus indexing load is not subdivided
This is something of a misconception. Indexing is always done on all
nodes, leaders and replicas alike
in SolrCloud. The leader is
but nothing changes (probably because there
are few shards).
--
Gian Maria Ricci
Cell: +39 320 0136949
-Original Message-
From: Shawn Heisey [mailto:apa...@elyograg.org]
Sent: lunedì 11 gennaio 2016 17:49
To: solr-user@lucene.apache.org
Subject: Re: Change leader in SolrCloud
On 1
I've a test solrCloud installation consisting of Three CentOS machines, each
one running one zookeeper node and one solr instance. I've created a
collection with 3 shards and 2 replica per each shard, then, after some
tests, rebooted all three machines.
Due to the different reboot times
> Cell: +39 320 0136949
>
>
>
> -Original Message-
> From: Shawn Heisey [mailto:apa...@elyograg.org]
> Sent: lunedì 11 gennaio 2016 17:49
> To: solr-user@lucene.apache.org
> Subject: Re: Change leader in SolrCloud
>
> On 1/11/2016 8:45 AM, Gian Maria R
12 matches
Mail list logo
