You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Terry Wang (Jira)" <ji...@apache.org> on 2019/12/05 03:01:00 UTC

[jira] [Commented] (FLINK-15055) YarnDistributedCacheITCase does not generate logs.

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

Terry Wang commented on FLINK-15055:
------------------------------------

It indeed confuses me a lot that all my PRs Travis build failed due to this issue. + 1 to fix soon.

> YarnDistributedCacheITCase does not generate logs.
> --------------------------------------------------
>
>                 Key: FLINK-15055
>                 URL: https://issues.apache.org/jira/browse/FLINK-15055
>             Project: Flink
>          Issue Type: Improvement
>          Components: Deployment / YARN, Tests
>    Affects Versions: 1.10.0
>            Reporter: Xintong Song
>            Priority: Minor
>              Labels: testability
>
> According to FLINK-14630, in order to properly generate logs, test cases that use starts cluster with YarnClusterDescriptor on MiniYARNCluster should call the util function FlinkYarnSessionCli#setLogConfigFileInConfig to set the path of log4j property file into the configuration.
> The YarnDistributedCacheITCase failed to do this.
> We probably should also revisit other Yarn IT cases see if there's any other case that also failed to do this. 
> A discussable alternative is to make it a default behavior for YarnClusterDescriptor to always set the default log4j property file, if it can find one, when the property file is not explicitly configured.



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