Return-Path: Delivered-To: apmail-lucene-java-user-archive@www.apache.org Received: (qmail 16260 invoked from network); 10 Apr 2011 17:35:23 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 10 Apr 2011 17:35:23 -0000 Received: (qmail 10574 invoked by uid 500); 10 Apr 2011 17:35:21 -0000 Delivered-To: apmail-lucene-java-user-archive@lucene.apache.org Received: (qmail 10528 invoked by uid 500); 10 Apr 2011 17:35:20 -0000 Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: java-user@lucene.apache.org Delivered-To: mailing list java-user@lucene.apache.org Received: (qmail 10520 invoked by uid 99); 10 Apr 2011 17:35:20 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 10 Apr 2011 17:35:20 +0000 X-ASF-Spam-Status: No, hits=1.3 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_NEUTRAL,URI_HEX X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [74.125.82.48] (HELO mail-ww0-f48.google.com) (74.125.82.48) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 10 Apr 2011 17:35:15 +0000 Received: by wwi18 with SMTP id 18so4092913wwi.5 for ; Sun, 10 Apr 2011 10:34:55 -0700 (PDT) MIME-Version: 1.0 Received: by 10.227.178.5 with SMTP id bk5mr4468289wbb.173.1302456894392; Sun, 10 Apr 2011 10:34:54 -0700 (PDT) Received: by 10.227.143.67 with HTTP; Sun, 10 Apr 2011 10:34:54 -0700 (PDT) In-Reply-To: <1302424498091-2801878.post@n3.nabble.com> References: <1302424498091-2801878.post@n3.nabble.com> Date: Sun, 10 Apr 2011 13:34:54 -0400 Message-ID: Subject: Re: NRT consistency From: Michael McCandless To: java-user@lucene.apache.org Cc: Em Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org That's a neat question (how to replicate index changes from opening a new NRT reader). The good news, the segments are flushed "like normal", so they can be replicated to the mirror(s). But the bad news is, the segments file is not written to disk -- it's held only in RAM (inside IW and shared to the IR that's opened), as a SegmentInfos instance, so somehow replication would have to get this in-memory segments file over to the mirrors, too. Mike http://blog.mikemccandless.com On Sun, Apr 10, 2011 at 4:34 AM, Em wrote: > Hello list, > > I am currently trying to understand Lucene's Near-Real-Time-Feature which > was covered in "Lucene in Action, Second Edition". > > Let's say I got a distributed system with a master and a slave. > > In Solr replication is solved by checking for any differences in the > index-directory and to consume those differences to keep indices consistent. > > How is this possible within a NRT-System? Is there any possibility to > consume snapshots of the internal buffer of the index writer to send them to > the slave? > > Regards, > Em > > -- > View this message in context: http://lucene.472066.n3.nabble.com/NRT-consistency-tp2801878p2801878.html > Sent from the Lucene - Java Users mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org > For additional commands, e-mail: java-user-help@lucene.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org For additional commands, e-mail: java-user-help@lucene.apache.org