Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-user@lucene.apache.org
Received-SPF: pass (asf.osuosl.org: domain of jason.polites@gmail.com
 designates 66.249.82.232 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references;
        b=AH28kX0diDtLKMK4Kgjp6vcP4MxzI0rxxaDlMXL6ivbr3rWuM9jwxoYLqQlcaBscQFyNa8dzDIic+JTTH4Xh9vq1nsGyWbBnoaWfH45bxnFhZ6DujZcRYnzTQ4UQH8TOmebLt4M9x2Qx5u4Bf5DFMksPOLsLlbKg0rE7QBYtnB8=
Message-ID: <d8050f240608272100n2c1de4e0j56e04a1ee63d014e@mail.gmail.com>
Date: Mon, 28 Aug 2006 14:00:21 +1000
From: "Jason Polites" <jason.polites@gmail.com>
To: java-user@lucene.apache.org
Subject: Re: java.io.IOException: Access is denied on
 java.io.WinNTFileSystem.createFileExclusively
In-Reply-To: <44F2048D.6060208@mikemccandless.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_131997_6509485.1156737621788"
References: 
 <OFC393C607.2B74353A-ON882571D7.005FC6E4-882571D7.00616057@il.ibm.com>
	 <44F2048D.6060208@mikemccandless.com>

------=_Part_131997_6509485.1156737621788
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Wow.  That's awesome.

I had just assumed (foolishly) that cross-JVM access would be problematic.
Maybe I should read the manual ;)

Cross machine access could be solved with some RMI magic.. but
performance/scalability may be an issue.

On 8/28/06, Michael McCandless <lucene@mikemccandless.com> wrote:
>
> Doron Cohen wrote:
> > "Jason Polites" <jason.polites@gmail.com> wrote on 27/08/2006 09:36:07:
> >
> >> I would have thought that simultaneous cross-JVM access to an index was
> >> outside of scope of the core Lucene API (although it would be great),
> but
> >> maybe the file system basis allows for this (?).
> >
> > Lucene does protect you from mis-accessing its indexes from separate
> jvms
> > or even, to a certain extent, separate machines.
>
> I would strengthen this statement: it is within scope of Lucene to allow
> cross-JVM access to the same underlying index.  Lucene has file-based
> locks for precisely this reason.  Lucene in Action (the book) has a
> great discussion about concurrency.
>
> It is also within scope for cross-JVM access when the JVMs are running
> on different machines, however, there are known problems (related to
> locking) when the index resides on an NFS mounted filesystems (and
> possibly other remote-mounted filesystems).  We are trying to address
> these known issues (see java-dev for the gory details) but it's not
> clear when these fixes will become available.
>
> Mike
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
> For additional commands, e-mail: java-user-help@lucene.apache.org
>
>

------=_Part_131997_6509485.1156737621788--