Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-user@lucene.apache.org
Received-SPF: pass (athena.apache.org: domain of stopman@gmail.com designates
 209.85.146.181 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:mime-version:content-type;
        b=kNPchMlNJ5DwVb4K4w9nLwOjLFHJ3s7UPGBmmcagmD04jonxFQM8eRFab2KldP8Nhw
         yGMdXe98XDmVIp/KyeaThy+9vNdIjqmVUpJCeVDjGLD5qFWoP02MiVwTLhThra8DOPSF
         qbnae8k/mOmg7EGL186to6Ny9m02Jt1E2MdaI=
Message-ID: <652776090812152204g3fd47793ta77a2fb09ce30296@mail.gmail.com>
Date: Mon, 15 Dec 2008 22:04:37 -0800
From: "Michael Stoppelman" <stopman@gmail.com>
To: java-user@lucene.apache.org
Subject: replication question
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_126761_31179758.1229407477462"

------=_Part_126761_31179758.1229407477462
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

I've got a question from Doug's original email about replication (
http://www.mail-archive.com/lucene-user@jakarta.apache.org/msg12709.html):

"1. On the index master, periodically checkpoint the index. Every minute or
so the IndexWriter is closed and a 'cp -lr index index.DATE' command is
executed from Java, where DATE is the current date and time. This
efficiently makes a copy of the index when its in a consistent state by
constructing a tree of hard links. If Lucene re-writes any files (e.g., the
segments file) a new inode is created and the copy is unchanged."

Is closing the IndexWriter really a requirement on taking a snapshot? Or can
one take a snapshot on an index being written, I've done this in my
development environment and it seems to work fine w/o closing the
IndexWriter. Also the solr replication shell scripts don't seem to worry
about this either.

M

------=_Part_126761_31179758.1229407477462--