You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Matthias (Jira)" <ji...@apache.org> on 2020/08/28 09:41: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=17186420#comment-17186420 ] 

Matthias commented on FLINK-15055:
----------------------------------

[~xintongsong] I was verifying this issue as part of the Engine team's backlog grooming today. It looks like the {{YarnDistributedCacheITCase}} was removed. Should we leave this ticket open as since we still want to check other ITs for the same issue? Or can you verify that this isn't an issue anymore?

> 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)