Fengling Wang has posted comments on this change. ( http://gerrit.cloudera.org:8080/10419 )
Change subject: KUDU-1867 Improve the "Could not lock .../block_manager_instance" error log ...................................................................... Patch Set 4: (1 comment) http://gerrit.cloudera.org:8080/#/c/10419/4//COMMIT_MSG Commit Message: http://gerrit.cloudera.org:8080/#/c/10419/4//COMMIT_MSG@22 PS4, Line 22: Could not lock /private/tmp/kudu/data/master/0/2/data/ : block_manager_instance > I don't see the changes in PS5. Also from PS5's commit message, it seems li Oops sorry, I misunderstood your previous comment. So do you mean we don't need to expose the filename in upper log layer cuz there's lower level log that also prints out this filename? So will the log be like: Check failed: _s.ok() Bad status: IO error: Failed to load FS layout: Could not lock the 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: Resourcetemporarily unavailable (error 35) -- 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: comment 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> Gerrit-Comment-Date: Fri, 18 May 2018 16:18:41 +0000 Gerrit-HasComments: Yes
