Jean-Daniel Cryans created KUDU-1867:
----------------------------------------
Summary: 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
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:
{noformat}
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)
{noformat}
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.3.15#6346)
