You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2019/11/07 11:56:00 UTC

[jira] [Updated] (FLINK-14630) Yarn tests no longer create jobmanager log files

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

ASF GitHub Bot updated FLINK-14630:
-----------------------------------
    Labels: pull-request-available  (was: )

> Yarn tests no longer create jobmanager log files
> ------------------------------------------------
>
>                 Key: FLINK-14630
>                 URL: https://issues.apache.org/jira/browse/FLINK-14630
>             Project: Flink
>          Issue Type: Bug
>          Components: Deployment / YARN, Tests
>    Affects Versions: 1.10.0
>            Reporter: Till Rohrmann
>            Assignee: Kostas Kloudas
>            Priority: Critical
>              Labels: pull-request-available
>             Fix For: 1.10.0
>
>
> With FLINK-14502 we changed how log property files are being discovered by the {{YarnClusterDescriptor}}. In fact we moved the responsibility to the {{FlinkYarnSessionCli}}. This is problematic because the {{YarnTestBase}} creates for Yarn tests a configuration directory which contains the Flink configuration and the log property files. These files are no longer respected because the respective code path has been removed.
> I think it is important to fix this problem so that our Yarn tests start to log again. Otherwise it becomes harder to debug Yarn problems and the tests can no longer check for the absence of exceptions in the logs.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)