[
https://issues.apache.org/jira/browse/MESOS-3465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15932335#comment-15932335
]
Yan Xu commented on MESOS-3465:
-------------------------------
FYI https://reviews.apache.org/r/56681/ is posted for the related (duplicate)
MESOS-7115, you may want to take a look.
Also since work has started on MESOS-7115 we can perhaps close this one in
favor of that. (I know normally we should duplicate backwards)
> EXIT() should include timestamp
> -------------------------------
>
> Key: MESOS-3465
> URL: https://issues.apache.org/jira/browse/MESOS-3465
> Project: Mesos
> Issue Type: Improvement
> Reporter: Neil Conway
> Assignee: 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.15#6346)
