You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Neil Conway (JIRA)" <ji...@apache.org> on 2015/10/05 17:48:26 UTC
[jira] [Updated] (MESOS-3465) EXIT() should include timestamp
[ https://issues.apache.org/jira/browse/MESOS-3465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Neil Conway updated MESOS-3465:
-------------------------------
Labels: mesosphere newbie (was: )
> 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)