You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Benjamin Mahler (JIRA)" <ji...@apache.org> on 2015/10/05 20:16:27 UTC

[jira] [Commented] (MESOS-3465) EXIT() should include timestamp

    [ https://issues.apache.org/jira/browse/MESOS-3465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14943783#comment-14943783 ] 

Benjamin Mahler commented on MESOS-3465:
----------------------------------------

EXIT was intended to be a simple wrapper around {{exit()}} that behaves like an output stream for stderr. For the most part, we used this for situations where we needed to exit due to bad configuration, or if the program completes, etc. In some cases it may be an ERROR (bad flags), in some cases it may be just INFO (expected termination). Before we decide to keep using EXIT or to change it, let's figure out how we want to do logging/termination in all of these situations :)

> EXIT() should include timestamp
> -------------------------------
>
>                 Key: MESOS-3465
>                 URL: https://issues.apache.org/jira/browse/MESOS-3465
>             Project: Mesos
>          Issue Type: Improvement
>            Reporter: Neil Conway
>            Priority: Minor
>              Labels: mesosphere, newbie
>
> EXIT() prints a log message but doesn't include a timestamp, and is otherwise inconsistent with the format of other log messages. EXIT() might be called during normal operational circumstances (e.g., during a network partition), so a timestamp would be useful to aid analysis.
> We could use LOG(FATAL), but apparently this dumps a backtrace, which is probably not warranted.
> How about EXIT() does LOG(ERROR), then calls exit() as it does now?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)