[
https://issues.apache.org/jira/browse/MESOS-3465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14943827#comment-14943827
]
Neil Conway commented on MESOS-3465:
------------------------------------
Fair enough. How about introducing `LOG_EXIT(level)`, which does `LOG(level) <<
msg`, followed by EXIT(EXIT_FAILURE)?
> 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)
