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

[jira] [Commented] (FLINK-17935) Logs could not show up when deploying Flink on Yarn via "--executor"

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

Echo Lee commented on FLINK-17935:
----------------------------------

[~fly_in_gis] There is really a problem here. Our approach is to add {{setLogConfigFileInConfig}} to the custom executor.

> Logs could not show up when deploying Flink on Yarn via "--executor"
> --------------------------------------------------------------------
>
>                 Key: FLINK-17935
>                 URL: https://issues.apache.org/jira/browse/FLINK-17935
>             Project: Flink
>          Issue Type: Bug
>          Components: Deployment / YARN
>    Affects Versions: 1.11.0, 1.12.0
>            Reporter: Yang Wang
>            Priority: Critical
>             Fix For: 1.11.0
>
>
> {code:java}
> ./bin/flink run -d -p 5 -e yarn-per-job examples/streaming/WindowJoin.jar{code}
> When we use the {{-e/--executor}} to specify the deploy target to Yarn per-job, the logs could not show up. The root cause is we do not set the logging files in {{ExecutorCLI}}. We only do it in the {{FlinkYarnSessionCli}}.
> If we use {{-m yarn-cluster}}, everything works well.
>  
> Maybe we should move the {{setLogConfigFileInConfig}} to {{YarnClusterDescriptor}} to avoid this problem. cc [~kkl0u]



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