Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: solr-user@lucene.apache.org
Received-SPF: pass (nike.apache.org: domain of markrmiller@gmail.com
 designates 209.85.212.47 as permitted sender)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: Push/pull model between leader and replica in one shard
From: Mark Miller <markrmiller@gmail.com>
In-Reply-To: 
 <CAHsXEHUSrF0z-OX+8Ot6esTsVGK91wTYa5kwtRGFpMKyEZAPew@mail.gmail.com>
Date: Wed, 17 Apr 2013 10:48:43 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <33D35EAA-EEEF-47AB-AAA9-07312A90451D@gmail.com>
References: <4b8fb256.17d83.13e115851d0.Coremail.suonayi2006@163.com>
 <DDEE9AE2-2F80-404E-A529-F2638E464424@gmail.com>
 <CAHsXEHV0SK=+fqXdfMbO+mzeot1WPLB6G+tpkuix8EFeuZ+Zng@mail.gmail.com>
 <CAHsXEHUSrF0z-OX+8Ot6esTsVGK91wTYa5kwtRGFpMKyEZAPew@mail.gmail.com>
To: solr-user@lucene.apache.org

Thanks, the earlier presentation is done with KeyNote and the later =
(more animation) is done with Tumult Hype.

- Mark

On Apr 17, 2013, at 3:43 AM, Furkan KAMACI <furkankamaci@gmail.com> =
wrote:

> Hej Mark;
>=20
> What did you use to prepare your presentation, its really nice.
>=20
> 2013/4/17 Furkan KAMACI <furkankamaci@gmail.com>
>=20
>> Really nice presentation.
>>=20
>>=20
>> 2013/4/17 Mark Miller <markrmiller@gmail.com>
>>=20
>>>=20
>>> On Apr 16, 2013, at 1:36 AM, SuoNayi <suonayi2006@163.com> wrote:
>>>=20
>>>> Hi, can someone explain more details about what model is used to =
sync
>>> docs between the lead and
>>>> replica in the shard?
>>>> The model can be push or pull.Supposing I have only one shard that =
has
>>> 1 leader and 2 replicas,
>>>> when the leader receives a update request, does it will scatter the
>>> request to each available and active
>>>> replica at first and then processes the request locally at last?In =
this
>>> case if the replicas are able to catch
>>>> up with the leader can I think this is a push model that the leader
>>> pushes updates to it's replicas?
>>>=20
>>> Currently, the leader adds the doc locally and then sends it to all
>>> replicas concurrently.
>>>=20
>>>>=20
>>>>=20
>>>> What happens if a replica is behind the leader?Will the replica =
pull
>>> docs from the leader and keep
>>>> a track of the coming updates from the lead in a log(called =
tlog)?If so
>>> when it complete pulling docs
>>>> it will replay updates in the tlog at last?
>>>=20
>>> If an update forwarded from a leader to a replica fails it's likely
>>> because that replica died. Just in case, the leader will ask that =
replica
>>> to enter "recovery".
>>>=20
>>> When a node comes up and is not a leader, it also enters "recovery".
>>>=20
>>> Recovery tries to peersync from the leader, and if that fails (works =
if
>>> off by about 100 updates), it replicates the entire index.
>>>=20
>>> If you are interested in more details on the SolrCloud architecture, =
I've
>>> given a few talks on it - two of them here:
>>>=20
>>> http://vimeo.com/43913870
>>> http://www.youtube.com/watch?v=3DeVK0wLkLw9w
>>>=20
>>> - Mark
>>>=20
>>>=20
>>=20