[
https://issues.apache.org/jira/browse/ACCUMULO-1709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13764666#comment-13764666
]
Billie Rinaldi commented on ACCUMULO-1709:
------------------------------------------
Looks like this is an issue for TabletServer as well. monitor, gc, and tracer
propagate their exceptions.
{code:java}
server.run();
} catch (Exception ex) {
log.error("Uncaught exception in TabletServer.main, exiting", ex);
}
{code}
> failing Master doesn't set exit code of process
> -----------------------------------------------
>
> Key: ACCUMULO-1709
> URL: https://issues.apache.org/jira/browse/ACCUMULO-1709
> Project: Accumulo
> Issue Type: Bug
> Affects Versions: 1.4.4, 1.5.0
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Fix For: 1.5.1, 1.6.0
>
> Attachments: ACCUMULO-1709-001.patch
>
>
> If the master can't start up due to an exception, it logs it, but doesn't
> exit the process with any error code -so the failure isn't picked up by any
> scripts looking at the exit code of bin/accumulo
--
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
