[
https://issues.apache.org/jira/browse/MESOS-3465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14944516#comment-14944516
]
Neil Conway commented on MESOS-3465:
------------------------------------
We've been producing output without a timestamp for some time, so presumably
most downstream consumers are able to cope with it. But I think the second
alternative is a bit nicer, since a single LOG_EXIT() call results in a single
log entry, which seems logical.
> 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)
