On Nov 11, 2004, at 1:47 AM, <[EMAIL PROTECTED]> wrote:
Yes, I tried that too and it worked. The issue is that our
Operations folks plan to install this on a pretty busy box and I
was hoping that Lucene wouldn't cause issues if it only had a
small slice of the CPU.
I don't think that Lucene is cau
Yes, I tried that too and it worked. The issue is that our
Operations folks plan to install this on a pretty busy box and I
was hoping that Lucene wouldn't cause issues if it only had a
small slice of the CPU.
Guess I'll tell them to buy a bigger box! Unless you have any
other ideas. I'm runnin
I just added a Thread.sleep(1000) in the writer thread and it has run
for quite some time, and is still running as I send this.
Erik
On Nov 10, 2004, at 8:02 PM, [EMAIL PROTECTED] wrote:
I added it to Bugzilla like you suggested:
http://issues.apache.org/bugzilla/show_bug.cgi?id=32171
Let
I just ran the code you provided. On my puny PowerBook (Mac OS X
10.3.5) it dies in much less than 5 minutes.
I do not know what the issue is, but certainly the actions the program
is taking are atypical. Opening and closing an IndexWriter repeatedly
is certainly expensive on large indexes.
I added it to Bugzilla like you suggested:
http://issues.apache.org/bugzilla/show_bug.cgi?id=32171
Let me know if you see any way to get around this issue.
--- Lucene
Users List" <[EMAIL PROTECTED] wrote:
Whoops! Looks like my
attachment didn't make it through. I'm
> re-attaching my simp
Whoops! Looks like my attachment didn't make it through. I'm
re-attaching my simple test app.
Thanks.
--- Erik Hatcher <[EMAIL PROTECTED]> wrote:
> On Nov 10, 2004, at 5:48 PM, [EMAIL PROTECTED]
> wrote:
> > Hi,
> >
> >> With the information provided, I have no
> >> idea what the issue
> > may
On Nov 10, 2004, at 5:48 PM, [EMAIL PROTECTED] wrote:
Hi,
With the information provided, I have no
idea what the issue
may be.
Is there some information that I should post that will help determine
why Lucene is giving me this error?
You mentioned posting code - though I don't recall getting an
att
no idea what the issue may be.
> There certainly is no issue reading
and writing to an index at the same
> time, but only one process can be
writing/deleting from the index at a
> time.
>
> Erik
>
> >
> >
--- Lucene Users List"
> > &l
one process can be
writing/deleting from the index at a
> time.
>
> Erik
>
> >
> >
--- Lucene Users List"
> > <[EMAIL PROTECTED] wrote:
> > The
attached Java file shows a locking
> > issue that occurs with
> >> Lucene.
>
e.
There certainly is no issue reading and writing to an index at the same
time, but only one process can be writing/deleting from the index at a
time.
Erik
--- Lucene Users List"
<[EMAIL PROTECTED] wrote:
The attached Java file shows a locking
issue that occurs with
Lucene.
On
Otis or Erik, do you know if a Reader continously opening should cause the
Writer to fail with a "Lock obtain timed out" error?
--- Lucene Users List"
<[EMAIL PROTECTED] wrote:
The attached Java file shows a locking
issue that occurs with
> Lucene.
>
> One
The attached Java file shows a locking issue that occurs with
Lucene.
One thread opens and closes an IndexReader. The other thread
opens an IndexWriter, adds a document and then closes the
IndexWriter. I would expect that this app should be able to
happily run without an issues.
It fails with
12 matches
Mail list logo