[
https://issues.apache.org/jira/browse/BOOKKEEPER-642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13718403#comment-13718403
]
Ivan Kelly commented on BOOKKEEPER-642:
---------------------------------------
Ah, as the bookie hasn't started at this point, it won't actually call
shutdown() to get the error code. I think this applies to 4.2.2 also.
> Bookie returns incorrect exitcode, ExitCode.ZK_REG_FAIL is getting overridden
> -----------------------------------------------------------------------------
>
> Key: BOOKKEEPER-642
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-642
> Project: Bookkeeper
> Issue Type: Bug
> Components: bookkeeper-server
> Reporter: Rakesh R
> Assignee: Rakesh R
> Priority: Minor
> Fix For: 4.3.0
>
> Attachments: 0001-BOOKKEEPER-642.patch
>
>
> When bookie registration fails due to zookeeper exception, its not exiting
> with ExitCode.ZK_REG_FAIL.
> Bookie.java
> {code}
> try {
> registerBookie(conf);
> } catch (IOException e) {
> LOG.error("Couldn't register bookie with zookeeper, shutting
> down", e);
> shutdown(ExitCode.ZK_REG_FAIL);
> }
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
