Uploaded image for project: 'Kudu'
  1. Kudu
  2. KUDU-1867

Improve the "Could not lock .../block_manager_instance" error message

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 1.2.0
    • Fix Version/s: 1.8.0
    • Component/s: fs
    • Labels:

      Description

      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:

      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)
      

      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.

        Attachments

          Activity

            People

            • Assignee:
              fwang29 Fengling Wang
              Reporter:
              jdcryans Jean-Daniel Cryans
            • Votes:
              1 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: