You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "Jean-Daniel Cryans (JIRA)" <ji...@apache.org> on 2018/01/10 17:40:00 UTC
[jira] [Updated] (KUDU-1867) Improve the "Could not lock
.../block_manager_instance" error message
[ https://issues.apache.org/jira/browse/KUDU-1867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Daniel Cryans updated KUDU-1867:
-------------------------------------
Target Version/s: Backlog (was: 1.5.0)
> 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)