New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MAPREDUCE-7453. Container logs are missing when yarn.app.container.lo… #6042
Conversation
…g.filesize is set to default value 0.
LGTM. |
💔 -1 overall
This message was automatically generated. |
@jojochuang @virajjasani Can you please review this PR? I think this PR should be merged into next release. In default, for trunk, only show the latest line log. It will confuse the user. |
@zhengchenyu Thank you for your contribution! We need to fix the checkstyle issue. |
@zhengchenyu Thanks for your contribution! Merged into trunk. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this broke tests:
https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java8-linux-x86_64/1351/testReport/junit/org.apache.hadoop.mapreduce.v2.app.job.impl/TestMapReduceChildJVM/testCommandLine/
@slfan1989 / @zhengchenyu can you guys check & even link the ticket which broke this on Jira
Mostly we shouldn't change the default values but fix the cause
<name>mapreduce.task.userlog.limit.kb</name> | ||
<value>0</value> | ||
<description>The maximum size of user-logs of each task in KB. 0 disables the cap. | ||
<value>10240</value> | ||
<description>The maximum size of user-logs of each task in KB. | ||
</description> | ||
</property> | ||
|
||
<property> | ||
<name>yarn.app.mapreduce.am.container.log.limit.kb</name> | ||
<value>0</value> | ||
<value>10240</value> | ||
<description>The maximum size of the MRAppMaster attempt container logs in KB. | ||
0 disables the cap. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changing the defaults is an incompatible change. You are changing the behaviour of the application here?
@ayushtkn
I think we should change the default value. I setup a new cluster with the latest package. When I submit a MR application, I can only see only one line, just the latest log. Then I found that before HADOOP-18649, both log4j.appender.CLA.MaxFileSize and log4j.appender.CLA.maximumFileSize are not set, so we will use the default value 10M. After HADOOP-18649, log4j.appender.CLA.MaxFileSize is set to ${yarn.app.container.log.filesize}, in default for mr is 0, so only see the latest log. |
@ayushtkn Thank you very much for pointing out the issue! I will revert this PR and I will continue to follow up on this PR. |
…g.filesize is set to default value 0. (apache#6042) Contributed by Chenyu Zheng. Reviewed-by: Shilun Fan <slfan1989@apache.org> Signed-off-by: Shilun Fan <slfan1989@apache.org>
…g.filesize is set to default value 0. (apache#6042) Contributed by Chenyu Zheng. Reviewed-by: Shilun Fan <slfan1989@apache.org> Signed-off-by: Shilun Fan <slfan1989@apache.org>
…ainer.log.filesize is set to default value 0. (apache#6042) Contributed by Chenyu Zheng." (apache#6103) This reverts commit ab2bc90.
Description of PR
JIRA: MAPREDUCE-7453. Container logs are missing when yarn.app.container.log.filesize is set to default value 0.
Since HADOOP-18649, in container-log4j.properties, log4j.appender.{APPENDER}.MaxFileSize is set to ${yarn.app.container.log.filesize}, but yarn.app.container.log.filesize is 0 in default. So log is missing. This log is always rolling and only show the latest log.
This is the running log like below:
When we read the log from web, syslog is alway nothing, syslog.1 only show the latest log.
How was this patch tested?
test in cluster.
For code changes:
just fix default value to avoid missing logs.