You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@slider.apache.org by "Billie Rinaldi (JIRA)" <ji...@apache.org> on 2016/06/01 17:40:59 UTC

[jira] [Updated] (SLIDER-1115) stdout/stderr files have errors

     [ https://issues.apache.org/jira/browse/SLIDER-1115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Billie Rinaldi updated SLIDER-1115:
-----------------------------------
    Summary: stdout/stderr files have errors  (was: stdout/stderr files are in agent working directory rather than agent log directory)

> stdout/stderr files have errors
> -------------------------------
>
>                 Key: SLIDER-1115
>                 URL: https://issues.apache.org/jira/browse/SLIDER-1115
>             Project: Slider
>          Issue Type: Bug
>            Reporter: Billie Rinaldi
>            Assignee: thomas liu
>         Attachments: slider-1115-001.patch
>
>
> In the DockerManager.py, YarnDockerManager.py, windows/system.py and shell.py, the stdout and stderr files are created in the current working directory, rather than in the log directory.  The files should be in the log directory.
> In shell.py and windows/system.py, the files are created based on the pid file name, but this doesn't work because when the pid file is specified it has an absolute path.  The file names could just be changed to application.log and application.err.
> Also in shell.py and windows/system.py, the stdout and stderr files are opened with 'w' mode, but each container may run multiple Execute commands, so the files will be overwritten with the latest output.  The mode should be changed to 'w+' so all the output is captured.



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