Issue 2170: Cleaned up error message for NoNodeException for lostBook…

[Ghatage]

…ieRecoveryDelay when Auditor is not initialized.

Motivation

If Auditor has not been initialized, running lostBookieRecoveryDelay from bookie shell will result in a stack trace and NoNodeException.

Changes

Added a catch clause which:

• Cleans up stack trace
• Explains that the Auditor is not up yet, which means the znode for lostbookierecoverydelay has not been created yet.
• Prints exception

Master Issue: #2170

[eolivelli]

LGTM

That stackteace was very annoying. Thanks

[eolivelli]

@Ghatage is it generally better to not merge your own pull requests.
Recently I committed my own patches after waiting the approval of other committers but that was because we haven't many active committers who had time to merge.

Now that you are onboard I see that we will move at a faster pace

[Ghatage]

@Ghatage is it generally better to not merge your own pull requests

Understood!

…

On Fri, Oct 23, 2020, 1:38 AM Enrico Olivelli ***@***.***> wrote: @Ghatage <https://github.com/Ghatage> is it generally better to not merge your own pull requests. Recently I committed my own patches after waiting the approval of other committers but that was because we haven't many active committers who had time to merge. Now that you are onboard I see that we will move at a faster pace — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#2452 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAX6QQJ6MI32ACJDQ3SDA6TSME6I5ANCNFSM4S33URMA> .