Hello Will Berkeley, Kudu Jenkins, Andrew Wong,

I'd like you to reexamine a change. Please visit

    http://gerrit.cloudera.org:8080/10419

to look at the new patch set (#4).

Change subject: KUDU-1867 Improve the "Could not lock 
.../block_manager_instance" error log
......................................................................

KUDU-1867 Improve the "Could not lock .../block_manager_instance" error log

This improvement removes the double "Could not lock.." and adds
a descriptive message for the cause of the error.

Before:
Check failed: _s.ok() Bad status: IO error: Failed to load FS
layout: Could not lock /private/tmp/kudu/data/master/0/1/data/
block_manager_instance: Could not lock /private/tmp/kudu/data/
master/0/1/data/block_manager_instance: lock /private/tmp/kudu/
data/master/0/1/data/block_manager_instance: Resource temporarily
unavailable (error 35)

After:
Check failed: _s.ok() Bad status: IO error: Failed to load FS
layout: Could not lock /private/tmp/kudu/data/master/0/2/data/
block_manager_instance. Is Kudu already running or are you trying
to run Kudu with a different user than before?: lock /private/tmp/
kudu/data/master/0/2/data/block_manager_instance: Resource
temporarily unavailable (error 35)

Change-Id: I1c6f078f95b3295e31047b9fe9a5dd643a402ba0
---
M src/kudu/fs/block_manager_util.cc
M src/kudu/fs/data_dirs.cc
2 files changed, 6 insertions(+), 5 deletions(-)


  git pull ssh://gerrit.cloudera.org:29418/kudu refs/changes/19/10419/4
--
To view, visit http://gerrit.cloudera.org:8080/10419
To unsubscribe, visit http://gerrit.cloudera.org:8080/settings

Gerrit-Project: kudu
Gerrit-Branch: master
Gerrit-MessageType: newpatchset
Gerrit-Change-Id: I1c6f078f95b3295e31047b9fe9a5dd643a402ba0
Gerrit-Change-Number: 10419
Gerrit-PatchSet: 4
Gerrit-Owner: Fengling Wang <fw...@cloudera.com>
Gerrit-Reviewer: Andrew Wong <aw...@cloudera.com>
Gerrit-Reviewer: Fengling Wang <fw...@cloudera.com>
Gerrit-Reviewer: Kudu Jenkins
Gerrit-Reviewer: Will Berkeley <wdberke...@gmail.com>

Reply via email to