lucene-solr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Yonik Seeley <yo...@lucidimagination.com>
Subject Re: svn commit: r899979 - /lucene/solr/trunk/example/solr/conf/solrconfig.xml
Date Sat, 16 Jan 2010 20:53:12 GMT
On Sat, Jan 16, 2010 at 3:40 PM, Chris Hostetter
<hossman_lucene@fucit.org> wrote:
>
> : doc: note about native locks not working for multiple webapps in same JVM
>
> Is this in resposne to the OverlappingFileLockException thread started by
> Joe Kessel? ...
>
> : +      native = NativeFSLockFactory  - uses OS native file locking.
> : +               Do not use with multiple solr webapps in the same JVM.
>
> I think there's a missunderstanding about the root cause of hte problem.
> There shouldn't be any inherent problem with using Native locks
> and multiple webapps

Right... for stock Solr usage (i.e. as long as they don't try to lock
the same thing.)
It is funny that native locks always work across different processes,
but not always in the same JVM though.

> -- i believe the underlying source of the exception
> was that he was using multiple webapps w/o realizing it -- so presumably
> both webapps were trying to use the same solr home dir.

Right... it's really two issues:
#1) two separate solr instances trying to use the same solr index
#2) native lock factory fails if it's two different Solr webapps in
the same JVM trying to lock the same thing.

I do recall expert level stuff like people having mutiple solr
instances pointing to the same data directory in the past though, but
not sure if it was from the same JVM or not.

Should we clarify "Do not use with multiple solr webapps in the same
JVM" or just remove it?

-Yonik
http://www.lucidimagination.com

Mime
View raw message