: So what/how should we document all of this?
...
: I've got more info on this.
Mark: most of what you wrote is above my head, but since you fixed a
grammar error in my updated example solrconfig.xml comment w/o making any
content changes, I'm assuming you feel what i put there is
Chris Hostetter wrote:
: At a minimu, shouldn't NativeFSLock.obtain() be checking for
: OverlappingFileLockException and treating that as a failure to acquire
the
: lock?
...
: Perhaps - that should make it work in more cases - but in my simple
: testing its not 100% reliable.
Mark Miller wrote:
Chris Hostetter wrote:
: At a minimu, shouldn't NativeFSLock.obtain() be checking for
: OverlappingFileLockException and treating that as a failure to acquire
the
: lock?
...
: Perhaps - that should make it work in more cases - but in my simple
: testing
thanks for the heads-up, this is good to know.
I've updated http://wiki.apache.org/lucene-java/AvailableLockFactories
which I recently created as a guide to help in choosing between
different LockFactories.
I believe the Native LockFactory is very useful, I wouldn't consider
this a bug nor
: again. I don't think it matters if its the same FileChannel or not - you
: just can't use Native Locks within the same JVM, as the lock is held by
: the JVM - they are per process - so Lucene does its own little static
: map stuff to lock within JVM (simple in memory lock tracking) and uses
:
Chris Hostetter wrote:
: again. I don't think it matters if its the same FileChannel or not - you
: just can't use Native Locks within the same JVM, as the lock is held by
: the JVM - they are per process - so Lucene does its own little static
: map stuff to lock within JVM (simple in memory
: At a minimu, shouldn't NativeFSLock.obtain() be checking for
: OverlappingFileLockException and treating that as a failure to acquire the
: lock?
...
: Perhaps - that should make it work in more cases - but in my simple
: testing its not 100% reliable.
...
: File locks are
On Mon, Jan 18, 2010 at 1:17 AM, Chris Hostetter
hossman_luc...@fucit.org wrote:
: 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.
Yonik Seeley wrote:
On Mon, Jan 18, 2010 at 1:17 AM, Chris Hostetter
hossman_luc...@fucit.org wrote:
: 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
Mark Miller wrote:
Yonik Seeley wrote:
On Mon, Jan 18, 2010 at 1:17 AM, Chris Hostetter
hossman_luc...@fucit.org wrote:
: 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
Ah thanks - I was going by that comment :-)
On Mon, Jan 18, 2010 at 12:07 PM, Mark Miller markrmil...@gmail.com wrote:
Mark Miller wrote:
Yonik Seeley wrote:
On Mon, Jan 18, 2010 at 1:17 AM, Chris Hostetter
hossman_luc...@fucit.org wrote:
: Right... for stock Solr usage (i.e. as long as
: 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.
Actaully, the more i think about this the less i understand it ... why
don't native locks
: 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
On Sat, Jan 16, 2010 at 3:40 PM, Chris Hostetter
hossman_luc...@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 -
14 matches
Mail list logo
