Otis Gospodnetic wrote:
Hi,
Is anyone running Lucene trunk/HEAD version in a serious production system?
Anyone noticed any memory leaks?
I'm asking because I recently bravely went from 1.9.1 to 2.1-dev (trunk from
about a week ago) and all of a sudden my application that was previosly
consuming about 1.5GB (-Xmx1500m) now consumes 2.2GB, and blows up after it
exhausts the whole heap and the GC can't make any more room there after running
for about 3-6 hours and handling several tens of thousands of queries.
Whoa, I'm sorry to hear this Otis :(
I'd love to go back to 2.0.0, or even back to 1.9.1 and run that for a while
and just double-check that it really is the the Lucene upgrade that is the
source of the leak, but unfortunately because of LUCENE-701 (lockless commits),
I can't go back that easily without reindexing...
Moreover, I just looked at CHANGES.txt from 1.9.1 to present, and I think the
biggest change since then was LUCENE-701.
The file-format changes for lockless commits are small enough that
making a tool to back-convert a lockless format index into a
pre-lockless format index (so that Lucene 2.0 can read/write to it) is
fairly simple.
OK I coded up a first version. I will open a JIRA issue and attach a
patch.
We clearly need to also get to the bottom of where the memory leak is,
but I think first priority is to stabilize your production
environment. Hopefully this tool can at least get you back up in
production and then also enable us to narrow down where the memory
leak is.
Please tread carefully though: it makes me very nervous that this tool
I just created would be used in your production environment!
Obviously first test it in a sandbox, running against your production
index(es).
Mike
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
