You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Adam B (JIRA)" <ji...@apache.org> on 2017/01/13 20:46:26 UTC

[jira] [Commented] (MESOS-6843) Fetcher should not assume stdout/stderr in the sandbox.

    [ https://issues.apache.org/jira/browse/MESOS-6843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15822326#comment-15822326 ] 

Adam B commented on MESOS-6843:
-------------------------------

This is rather annoying with a custom container logger, because even if my task doesn't fetch anything, there's still an empty stdout/stderr file in the sandbox, but all my task output is actually in journald. It's confusing as a user.
Would this be complicated to do, or just a couple of new if checks?

> Fetcher should not assume stdout/stderr in the sandbox.
> -------------------------------------------------------
>
>                 Key: MESOS-6843
>                 URL: https://issues.apache.org/jira/browse/MESOS-6843
>             Project: Mesos
>          Issue Type: Bug
>          Components: fetcher
>    Affects Versions: 1.0.2, 1.1.0
>            Reporter: Jie Yu
>            Priority: Critical
>              Labels: mesosphere
>
> If container logger is used, this assumption might not be true. For instance, a journald logger might redirect all task logs to journald. So in theory, the fetcher log should go to journald as well, rather than writing to sandbox/stdout and sandbox/stderr.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)