[MESOS-6961] Executors don't use glog for logging.

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.4.0
• Component/s: executor
• Labels: log mesosphere newbie++
• Sprint: Mesosphere Sprint 57
• Story Points: 1
• Assignee: Andrei Budnik
• Reporter: Alex R
• Shepherd: Alex R
• Created: 20/Jan/17 14:00
• Updated: 13/Jul/17 09:01
• Resolved: 07/Jun/17 14:02

Description

Built-in Mesos executors use cout/cerr for logging. This is not only inconsistent with the rest of the codebase, it also complicates debugging, since, e.g., a stack trace is not printed on an abort. Having timestamps will be also a huge plus.

Consider migrating logging in all built-in executors to glog.

There have been reported issues related to glog internal state races when a process that has glog initialized {{fork-exec}}s another process that also initialize glog. We should investigate how this issue is related to this ticket, cc tillt, vinodkone, bmahler.

Issue Links

• duplicates: MESOS-7294 Cleanup Docker executor logging.
• relates to: MESOS-7586 Make use of cout/cerr and glog consistent.