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

Robert Muir commented on LUCENE-7959:
-------------------------------------

{quote}
The errors currently returned are misleading in this case; there is no lock 
held at all by a VM or external process. So any safe thing we can do that has a 
chance of helping pinpoint the problem is an improvement.
{quote}

Erick, I'm trying to reiterate here, its super-important to understand, that if 
you see "Lock held by this virtual machine" or "Lock held by another program", 
it is absolutely a bug in your code. Those errors have nothing to do with this 
issue, you simply have to fix your code.

This issue is only about improving the "NoSuchFileException" case, that is it.


> Throw more helpful error messages from failures in obtainFSLock, at least in 
> NativeFSLockFactory
> ------------------------------------------------------------------------------------------------
>
>                 Key: LUCENE-7959
>                 URL: https://issues.apache.org/jira/browse/LUCENE-7959
>             Project: Lucene - Core
>          Issue Type: Improvement
>            Reporter: Erick Erickson
>            Assignee: Erick Erickson
>            Priority: Minor
>         Attachments: LUCENE-7959_untested.patch
>
>
> This is one of those small changes that would save a lot of pain for end 
> users. Currently, any failure to obtain the lock reports:
> "Lock held by this virtual machine: " + realPath
> or 
> "Lock held by another program: " + realPath
> Let's say that there's a permissions issue with the index dir. This is an 
> unhelpful/misleading error message (recent user's list discussion about this).
> The problem is that when we try to create the lock file we swallow _all_ 
> exceptions, not just the one we don't care about (Thanks [~elyograg] for 
> pointing this out).
>  {{   
>    try {
>       Files.createFile(lockFile);
>     } catch (IOException ignore) {
>       // we must create the file to have a truly canonical path.
>       // if it's already created, we don't care. if it cant be created, it 
> will fail below.
>     }
> }}
> It fails later with one of the above error messages.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to