accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-1709) failing Master doesn't set exit code of process
Date Thu, 24 Oct 2013 19:51:02 GMT


Steve Loughran commented on ACCUMULO-1709:

I've done something a bit like this, with an exception that [can provide an exit code |]
, [a list of exceptions|],
which hooks up somewhat to Hadoop's [ExitException and exit logic|].
That code is intended to provide a single exit point that tests can downgrade to exceptions,
but I'd like it improved, hence HADOOP-9626.

Key point: yes, it's nice for exceptions to serve up numbers, having some interface for this
lets you retrofit it into exceptions where the base classes are not under your control. And
a single exit method is good for logging, debugging and testing. 

but: with only 255 exceptions on a linux system, you are limited in what you can signal, which
is a shame

> failing Master doesn't set exit code of process
> -----------------------------------------------
>                 Key: ACCUMULO-1709
>                 URL:
>             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 was sent by Atlassian JIRA

View raw message