lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Uwe Schindler (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LUCENE-3956) Urgent Lucene Exception Issue
Date Thu, 05 Apr 2012 08:27:32 GMT

    [ https://issues.apache.org/jira/browse/LUCENE-3956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13247087#comment-13247087
] 

Uwe Schindler commented on LUCENE-3956:
---------------------------------------

Please contact Atlassian support about JIRA issues! This may be caused by JIRAs indexer.

I can only suggest:
- Delete the whole index from disk and trigger a reindex in JIRA
- Make sure that the index is not placed on a remote disk (e.g. NFS filesystem)
                
> Urgent Lucene Exception Issue
> -----------------------------
>
>                 Key: LUCENE-3956
>                 URL: https://issues.apache.org/jira/browse/LUCENE-3956
>             Project: Lucene - Java
>          Issue Type: Bug
>            Reporter: Dylan SD
>            Priority: Critical
>
> Hello,
> Could you please advise how this issue:
> TP-Processor13 ERROR [com.atlassian.bonnie.ConcurrentLuceneConnection] Error closing
writer. java.io.FileNotFoundException: /opt/jira/indexes/comments/_4ubij.fnm (No such file
or directory)
> java.io.FileNotFoundException: /opt/jira/indexes/comments/_4ubij.fnm (No such file or
directory)
> Thread-228 ERROR [atlassian.core.user.UserUtils] [Ljava.lang.StackTraceElement;@258e5d0e
> Thread-228 ERROR [event.listeners.search.IssueIndexListener] Error re-indexing changes
for issue 'current issue'
> com.atlassian.jira.issue.index.IndexException: com.atlassian.bonnie.LuceneException:
org.apache.lucene.store.LockObtainFailedException: Lock obtain timed out: SimpleFSLock@/opt/jira/indexes/comments/write.lock
> can be resolved in JIRA.
> I've deleted the write.lock file from directory /opt/jira/indexes/comments/ and restarted
JIRA but it did not help. The problem with Lucene still exists.
> Please advise what caused the problem and how it can be avoid in the future and what
is more important how this Lucene Exception can be resolved.
> Regards,
> Dylan

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message