lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From renz052496 <>
Subject Re: Lock timed out 2 worker running
Date Fri, 14 Aug 2009 02:02:12 GMT
Yes, I missunderstood you question (re: the crashed). Solr did not crash but
we shutdown the JVM (tomcat) gracefully after we kill all our workers. But
upon restarting, solr just throwing the error.

2009/8/11 Chris Hostetter <>

> : > 5) are these errors appearing after Solr crashes and you restart it?
> :
> :
> : Yep, I can't find the logs but it's something like can't obtain lock for
> : <somefile>.lck Need to delete that fiile in order to start the solr
> properly
> wait ... either you missunderstood my question, or you just explained
> what's happening.
> If you are using SimpleFSLock, and solr crashes (OOM, kill -9, yank the
> power cord) then it's possible the lock file will get left arround, in
> which case this is the expected behavior.  there's a config option you
> can set to tell solr that on start up you want it to cleanup any old lock
> files, but if you switch to the "single" lock manager mode your life gets
> a lot easier anyway.
> But you never mentioned anything about the server crashing in your
> original message, so i'm wondering if you really ment to answer "yep" when
> i asked "are these errors appearing *after* Solr crashes"
> -Hoss

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message