[
https://issues.apache.org/jira/browse/MESOS-9687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16814438#comment-16814438
]
Andrei Sekretenko commented on MESOS-9687:
------------------------------------------
I guess that to make any use of this patch most people will need
dcos-mesos-modules>=1.13:
[https://github.com/dcos/dcos-mesos-modules/commits/1.13] (I do not know about
any other implementations of a custom LogSink for Mesos).
Does it make sense to backport this patch to Mesos=1.7.* then?
> Add the glog patch to pass microseconds via the LogSink interface.
> ------------------------------------------------------------------
>
> Key: MESOS-9687
> URL: https://issues.apache.org/jira/browse/MESOS-9687
> Project: Mesos
> Issue Type: Task
> Reporter: Andrei Sekretenko
> Assignee: Andrei Sekretenko
> Priority: Major
> Fix For: 1.8.0
>
>
> Currently, custom LogSink implementations in the modules (for example, this
> one:
> [https://github.com/dcos/dcos-mesos-modules/blob/master/logsink/logsink.hpp]
> )
> are logging `000000` instead of microseconds in the timestamp - simply
> because the LogSink interface in glog has no place for microseconds.
> The proposed glog fix is here: [https://github.com/google/glog/pull/441]
> Getting this into glog release might take a long time (they released 0.4.0
> recently, but the previous release 0.3.5 was two years ago), therefore it
> makes sense to add this patch into Mesos build.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
