[
https://issues.apache.org/jira/browse/FLINK-19768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17222687#comment-17222687
]
YUJIANBO commented on FLINK-19768:
----------------------------------
Thanks a lot for your answer！
I changed the log4j.properties parameters "appender.main.fileName =
${sys:log.file}-aaaaa", but failed realized the log in the yarn session mode to
distinguish logs of different tasks.
I've tried the above steps，but I encountered two serious proble:
1, in per-job model, form flink web I see taskmanager side that the web shows
"taskmanager.log-aaaaa" and taskmanager.err doesn't shows
"taskmanager.err-aaaaa", but jobmanager side 's Log List has nothing. I'm
puzzled why it's like this。
2,in yarn-session model, I have done three steps：
(1) "appender.main.fileName = ${sys:log.file}-aaaaa" I do the shell
"FLINK_CONF_DIR=<> ./yarn-session.sh ..." to submit yarn-session.
(2) "appender.main.fileName = ${sys:log.file}-bbbbb" I do the shell
"FLINK_CONF_DIR=<> ./flink run -yid ..." to task one.
(3) "appender.main.fileName = ${sys:log.file}-ccccc" I do the shell
"FLINK_CONF_DIR=<> ./flink run -yid ..." to task two.
>From flink web, I aslo see the jobmanager side 's Log List has nothing。But I
>found something more important:
Whether it's task one or task two, the taskmanager side show logs
"taskmanager.log-aaaaa", not "taskmanager.log-bbbbb" or
"taskmanager.log-ccccc".
> The shell "./yarn-session.sh " not use log4j-session.properties , it use
> log4j.properties
> ------------------------------------------------------------------------------------------
>
> Key: FLINK-19768
> URL: https://issues.apache.org/jira/browse/FLINK-19768
> Project: Flink
> Issue Type: Bug
> Components: Client / Job Submission, Deployment / YARN
> Affects Versions: 1.11.2
> Reporter: YUJIANBO
> Priority: Major
>
> The shell "./yarn-session.sh " not use log4j-session.properties , it use
> log4j.properties
> My Flink Job UI shows the $internal.yarn.log-config-file is
> "/usr/local/flink-1.11.2/conf/log4j.properties", is it a bug?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
