[
https://issues.apache.org/jira/browse/LUCY-296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15222353#comment-15222353
]
Marvin Humphrey commented on LUCY-296:
--------------------------------------
For using Lucy on NFS see
[Lucy::Docs::FileLocking|https://lucy.apache.org/docs/perl/Lucy/Docs/FileLocking.html].
Only one process can hold the write lock, so if you're trying to write from
multiple machines you have to be prepared for write lock timeouts.
Lucy allows any number of readers, but you may want to use read locks in order
to avoid "stale NFS filehandle" errors.
I would be curious to hear if following the instructions in the FileLocking
docs solves all your issues. You might have to remove some problematic files
and directories first. (The easiest thing would be to delete the index and
start from scratch.)
I suspect that the "Couldn't completely remove 'seg_b9'" issue arises because
two Indexers were live at the same time and the new one tried to initialize a
segment that the old one was in the process of writing.
> unable to delete segment dir, lock files
> ----------------------------------------
>
> Key: LUCY-296
> URL: https://issues.apache.org/jira/browse/LUCY-296
> Project: Lucy
> Issue Type: Bug
> Reporter: Miroslav Madzarevic
>
> opening an index on NFS fails
> Couldn't completely remove 'seg_b9'
> closing index fails with
> Can't delete '.nfs0000000004a86c7e000f1fe5'
> do you think this issue is related to NFS or is it a bug in Lucy?
> also, opening index sometimes produces errors like these
> Can't obtain lock: 'locks/write.lock' exists
> Couldn't get deletion lock
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
