You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-user@lucene.apache.org by Julian Davchev <jm...@drun.net> on 2009/01/20 16:07:48 UTC
I get SEVERE: Lock obtain timed out
Hi,
Any documents or something I can read on how locks work and how I can
controll it. When do they occur etc.
Cause only way I got out of this mess was restarting tomcat
SEVERE: org.apache.lucene.store.LockObtainFailedException: Lock obtain
timed out: SingleInstanceLock: write.lock
Cheers,
Re: I get SEVERE: Lock obtain timed out
Posted by Jon Drukman <jd...@gmail.com>.
Yonik Seeley wrote:
> On Thu, Jan 29, 2009 at 1:16 PM, Jon Drukman <jd...@gmail.com> wrote:
>> Julian, have you had any luck figuring this out? My production instance
>> just started having this problem. It seems to crop up after solr's been
>> running for several hours. Our usage is very light (maybe one query every
>> few seconds). I saw someone else mention an out of memory error - this
>> machine has 8GB of RAM and is running 64bit Linux so it's all available to
>> solr. Our index is very small - under 40MB. the solr process is using
>> around 615MB of RAM according to top.
>
> I've only seen failure to remove the lock file either when an OOM
> exception occured, or the JVM died or was killed.
i guess it's possible that we hit an out of memory error and the
followup lock errors just bumped it out of the log file rotation. i was
running with multilog's default settings so my log files were getting
thrown out very quickly. i just bumped up the JVM's max heap size and
told multilog to keep way more log files so if this happens again
hopefully i will be able to get more info on what happened.
-jsd-
Re: I get SEVERE: Lock obtain timed out
Posted by Yonik Seeley <ys...@gmail.com>.
On Thu, Jan 29, 2009 at 1:16 PM, Jon Drukman <jd...@gmail.com> wrote:
> Julian, have you had any luck figuring this out? My production instance
> just started having this problem. It seems to crop up after solr's been
> running for several hours. Our usage is very light (maybe one query every
> few seconds). I saw someone else mention an out of memory error - this
> machine has 8GB of RAM and is running 64bit Linux so it's all available to
> solr. Our index is very small - under 40MB. the solr process is using
> around 615MB of RAM according to top.
I've only seen failure to remove the lock file either when an OOM
exception occured, or the JVM died or was killed.
-Yonik
Re: I get SEVERE: Lock obtain timed out
Posted by Jon Drukman <jd...@gmail.com>.
Julian Davchev wrote:
> Hi,
> Any documents or something I can read on how locks work and how I can
> controll it. When do they occur etc.
> Cause only way I got out of this mess was restarting tomcat
>
> SEVERE: org.apache.lucene.store.LockObtainFailedException: Lock obtain
> timed out: SingleInstanceLock: write.lock
>
>
> Cheers,
>
Julian, have you had any luck figuring this out? My production instance
just started having this problem. It seems to crop up after solr's been
running for several hours. Our usage is very light (maybe one query
every few seconds). I saw someone else mention an out of memory error -
this machine has 8GB of RAM and is running 64bit Linux so it's all
available to solr. Our index is very small - under 40MB. the solr
process is using around 615MB of RAM according to top.
Re: I get SEVERE: Lock obtain timed out
Posted by Jerome L Quinn <jl...@us.ibm.com>.
Julian Davchev <jm...@drun.net> wrote on 01/20/2009 10:07:48 AM:
> Julian Davchev <jm...@drun.net>
> 01/20/2009 10:07 AM
>
> I get SEVERE: Lock obtain timed out
>
> Hi,
> Any documents or something I can read on how locks work and how I can
> controll it. When do they occur etc.
> Cause only way I got out of this mess was restarting tomcat
>
> SEVERE: org.apache.lucene.store.LockObtainFailedException: Lock obtain
> timed out: SingleInstanceLock: write.lock
I've seen this with my customized setup. Before I saw the write.lock
messages, I had an OutOfMemoryError, but the container didn't shut down.
After that Solr spewed write lock messages and I had to restart.
So, you might want to search backwards in your logs and see if you can find
when the write lock problems and if there is some identifiable problem
preceding that.
Jerry Quinn