[
https://issues.apache.org/jira/browse/KUDU-1867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16319971#comment-16319971
]
Ed Vin edited comment on KUDU-1867 at 1/10/18 10:06 AM:
--------------------------------------------------------
Excuse me but, is there any plan for getting solved this issue? It was proposed
to be fixed by version 1.5, but it wasn't. Current version 1.6 is not solving
the issue.
Please, could anyone update the issue to add the expected target version when
issue will be solved?
Thanks in advance.
was (Author: evinhas):
Excuse me but, is there any plan for getting solved this issue?
> Improve the "Could not lock .../block_manager_instance" error message
> ---------------------------------------------------------------------
>
> Key: KUDU-1867
> URL: https://issues.apache.org/jira/browse/KUDU-1867
> Project: Kudu
> Issue Type: Bug
> Components: fs
> Affects Versions: 1.2.0
> Reporter: Jean-Daniel Cryans
> Labels: newbie
>
> It's possible for users to encounter a rather cryptic error when trying to
> run Kudu while it's already running or with a different user than what was
> previously used:
> {code}
> Check failed: _s.ok() Bad status: IO error: Failed to load FS layout: Could
> not lock /path/to/data/block_manager_instance: Could not lock
> /path/to/data/block_manager_instance: lock
> /path/to/data/block_manager_instance: Resource temporarily unavailable (error
> 11)
> {code}
> This is the log line that we FATAL with, so unless you already know what it
> means you're left to your own guessing and log digging. Instead, the error
> message could be more prescriptive.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
