i have not stopped writing so i am getting this error all the time.
the commit actually seems to go through with no errors but it does not seem
to write anything to the index files (i can see this because they are old
and i cannot see new stuff in search results).

my index folder is on an amazon ebs volume which is a block device and looks
like a local disk.

thanks!

udi


On Tue, Jan 18, 2011 at 10:49 AM, Otis Gospodnetic <
otis_gospodne...@yahoo.com> wrote:

> Udi,
>
> Hm, don't know off the top of my head, but sounds like "an interesting
> problem".
> Are you getting this error while still writing to the index or did you stop
> all
> writing?
> Do you get this error when you issue a commit or?
> Is the index on the local disk or?
>
> Otis
> ----
> Sematext :: http://sematext.com/ :: Solr - Lucene - Nutch
> Lucene ecosystem search :: http://search-lucene.com/
>
>
>
> ----- Original Message ----
> > From: Udi Nir <u...@threadsy.com>
> > To: solr-user@lucene.apache.org
> > Sent: Tue, January 18, 2011 12:29:47 PM
> > Subject: salvaging uncommitted data
> >
> > Hi,
> > I have a solr server that is failing to acquire a lock with the
>  exception
> > below. I think that the server has a lot of uncommitted data (I am  not
> sure
> > how to verify this) and if so I would like to salvage it.
> > Any  suggestions how to proceed?
> >
> > (btw i tried removing the lock file but it  did not help)
> >
> > Thanks,
> > Udi
> >
> >
> > Jan 18, 2011 5:17:06 PM  org.apache.solr.common.SolrException log
> > SEVERE:  org.apache.lucene.store.LockObtainFailedException: Lock obtain
> timed
> > out
> > :  NativeFSLock@
> > /vol-unifi-solr/data/index/lucene-043c34f1f06a280de60b3d4e8e05601
> > 6-write.lock
> >          at  org.apache.lucene.store.Lock.obtain(Lock.java:85)
> >          at
> org.apache.lucene.index.IndexWriter.init(IndexWriter.java:1545)
> >          at
>  org.apache.lucene.index.IndexWriter.<init>(IndexWriter.java:1402)
> >           at
> > org.apache.solr.update.SolrIndexWriter.<init>(SolrIndexWriter.java:19
> > 0)
> >
>

Reply via email to