Andrew Wong has submitted this change and it was merged. ( 
http://gerrit.cloudera.org:8080/10419 )

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 the
double file paths 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 block_manager_instance file. Make sure
that Kudu is not already running and you are not trying to run
Kudu with a different user than before: lock /private/tmp/kudu/
data/master/0/1/data/block_manager_instance: Resource temporarily
unavailable (error 35)

Change-Id: I1c6f078f95b3295e31047b9fe9a5dd643a402ba0
Reviewed-on: http://gerrit.cloudera.org:8080/10419
Reviewed-by: Andrew Wong <[email protected]>
Tested-by: Andrew Wong <[email protected]>
---
M src/kudu/fs/block_manager_util.cc
M src/kudu/fs/data_dirs.cc
2 files changed, 5 insertions(+), 5 deletions(-)

Approvals:
  Andrew Wong: Looks good to me, approved; Verified

--
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: merged
Gerrit-Change-Id: I1c6f078f95b3295e31047b9fe9a5dd643a402ba0
Gerrit-Change-Number: 10419
Gerrit-PatchSet: 8
Gerrit-Owner: Fengling Wang <[email protected]>
Gerrit-Reviewer: Andrew Wong <[email protected]>
Gerrit-Reviewer: Fengling Wang <[email protected]>
Gerrit-Reviewer: Kudu Jenkins
Gerrit-Reviewer: Will Berkeley <[email protected]>

Reply via email to