gt; H.-H.-Meier-Allee 63, D-28213 Bremen
> http://www.thetaphi.de
> eMail: u...@thetaphi.de
>
>
> > -Original Message-
> > From: Saurabh Agarwal [mailto:srbh.g...@gmail.com]
> > Sent: Tuesday, May 18, 2010 10:13 AM
> > To: java-user@lucene.apache.org
&g
gt; Subject: Re: Lock obtain timed out
>
> Thanks :)
>
> i am using only one server to create the index Saurabh Agarwal
>
>
> On Tue, May 18, 2010 at 1:41 PM, Ian Lea wrote:
>
> > Use SimpleFSLockFactory. The default, NativeFSLockFactory, doesn't
> > play w
Thanks :)
i am using only one server to create the index
Saurabh Agarwal
On Tue, May 18, 2010 at 1:41 PM, Ian Lea wrote:
> Use SimpleFSLockFactory. The default, NativeFSLockFactory, doesn't
> play well with NFS.
>
> And a warning: lucene does work on NFS but you may run into problems
> if you
Use SimpleFSLockFactory. The default, NativeFSLockFactory, doesn't
play well with NFS.
And a warning: lucene does work on NFS but you may run into problems
if your index has a lot of modifications and/or is accessed from
different servers.
--
Ian.
On Tue, May 18, 2010 at 6:56 AM, Saurabh Aga
Hi
>From the 2.4 javadocs for IndexWriter:
setDefaultWriteLockTimeout(long writeLockTimeout)
Sets the default (for any instance of IndexWriter) maximum time to
wait for a write lock (in milliseconds).
Lucene waits for the max specified time, retrying every 1000 millisecs
by default, then g
Laxmilal - this could be a left-over lock. Try removing it "manually" and
re-running your search app.
Otis
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Simpy -- http://www.simpy.com/ - Tag - Search - Share
- Original Message
From: Laxmilal Menaria <[EMAIL PROTECTE
But, locking should be fine even for this "hammering" use case (and if
it's not, that's a bug, and I'd really like to know about it!).
I have hammered over 2.5 million 5-10k docs into an index this way (a
realtime system that I had not yet added a special load call to) and had 0
problems. On
Hi Erick and Mike
Really thanks a lot for the advice... =)
I will fix my code..I'll let you guys know if any problem arises.
Many thanks and best regards ^ ^
MauReen
Michael McCandless <[EMAIL PROTECTED]> wrote: Erick Erickson wrote:
> Don't do it that way. You're ope
Erick Erickson wrote:
Don't do it that way. You're opening and closing your indexwrwiter for each
document, which is extremely wasteful. And given locking has been a source
of much discussion on this list, it's not clear that locking will withstand
this kind of hammering. You want to do something
Don't do it that way. You're opening and closing your indexwrwiter for each
document, which is extremely wasteful. And given locking has been a source
of much discussion on this list, it's not clear that locking will withstand
this kind of hammering. You want to do something like
IndexWriter writ
Hi Mike,thanks for the reply...
1.Here is the class that I use for indexing..
package edu.ntu.ce.maureen.index;
import org.apache.lucene.index.IndexWriter;
import org.apache.lucene.analysis.Analyzer;
import org.apache.lucene.analysis.standard.StandardAnalyzer;
import org.
One way to mitigate the cost of this kind of thing is to create a series of
indexes on portions of your corpus and then merge them. Say you have 10,000
documents. Create 10 separate indexes of 1,000 documents each then use
IndexWriter.addIndexes to make them all into a single index.
This pre-supp
maureen tanuwidjaja wrote:
I am indexing thousands of XML document,then it stops after indexing for
about 7 hrs
...
Indexing C:\sweetpea\wikipedia_xmlfiles\part-0\37027.xml
java.io.IOException: Lock obtain timed out: [EMAIL
PROTECTED]:\sweetpea\dual_index\DI\write.lock
java.lang
On Thu, 2006-07-27 at 08:59 +0200, Björn Ekengren wrote:
> > > When I close my application containing index writers the
> > > lock files are left in the temp directory causing an "Lock obtain
> > > timed out" error upon the next restart.
> >
> > My guess is that you keep a writer open even though
?
OS: win xp
JVM: 1.5
/B
_
-Original Message-
From: Michael McCandless [mailto:[EMAIL PROTECTED]
Sent: den 26 juli 2006 20:16
To: java-user@lucene.apache.org
Subject: Re: Lock obtain timed out
Importance: Low
>> When I close my application containing index writers the
&g
When I close my application containing index writers the
lock files are left in the temp directory causing an "Lock obtain
timed out" error upon the next restart.
My guess is that you keep a writer open even though there is no activity
involving adding new documents. Unless I have a massive neve
On Wed, 2006-07-26 at 16:24 +0200, Björn Ekengren wrote:
> When I close my application containing index writers the
> lock files are left in the temp directory causing an "Lock obtain
> timed out" error upon the next restart.
My guess is that you keep a writer open even though there is no activity
Lock files aren't contained in the index directory, but in the
standard temp directory.
remove the file referenced in the exception:
C:\DOCUME~1\harini\LOCALS~1\Temp\lucene-1b92bc48efc5c13ac4ef4ad9fd17c158-commit.lock
-Yonik
On 1/9/06, Harini Raghavan <[EMAIL PROTECTED]> wrote:
> Hi All,
>
> All
Probably a stale lock - remove it.
Otis
- Original Message
From: Harini Raghavan <[EMAIL PROTECTED]>
To: java-user@lucene.apache.org
Sent: Mon 09 Jan 2006 01:36:53 PM EST
Subject: Lock obtain timed out + IndexSearcher
Hi All,
All of a sudden I have started getting LockTimeOut exception
19 matches
Mail list logo
