[
https://issues.apache.org/jira/browse/FLINK-33988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17807507#comment-17807507
]
Rui Fan commented on FLINK-33988:
---------------------------------
Merged to master(1.19) via : eb6d6ff56747e3b34e941a4cd301cd851c0b0b25
> Invalid configuration when using initialized root logger level on yarn
> application mode
> ---------------------------------------------------------------------------------------
>
> Key: FLINK-33988
> URL: https://issues.apache.org/jira/browse/FLINK-33988
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Configuration
> Affects Versions: 1.19.0
> Reporter: RocMarshal
> Assignee: RocMarshal
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.19.0
>
>
> relevant https://issues.apache.org/jira/browse/FLINK-33166
> When I set env. log. level=DEBUG and start the flink job by yarn application
> mode, the logs of TM and JM are still INFO.
> Preliminary inference is that it is ROOT_ LOG_ LEVEL value transmission link
> is not complete enough.
> So I used the following configuration:
> containerized. taskmanager. env. ROOT_ LOG_ LEVEL=DEBUG
> containerized. master. env. ROOT_ LOG_ LEVEL=DEBUG
>
> When starting the job by yarn application mode, TM and JM can output DEBUG
> level logs.
>
> Repair ideas:
> Fill the value of *env. log. level* into the Flink configuration by
> *containerized. xxx. env. ROOT_ LOG_ LEVEL* before obtaining the environment
> variable for the container
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
