[MAPREDUCE-6778] Provide way to limit MRJob's stdout/stderr size

• Type: Improvement
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: 2.7.0
• Component/s: nodemanager
• Assignee: Unassigned
• Reporter: Aleksandr Balitsky
• Created: 14/Sep/16 07:59
• Updated: 15/Sep/16 14:03

Description

We can run job with huge amount of stdout/stderr and causing undesired consequence.

The possible solution is to redirect Stdout's and Stderr's output to log4j in YarnChild.java main method.
In this case System.out and System.err streams will be redirected to log4j logger with appender that will direct output in to stderr or stdout files with needed size limitation. Thereby we are able to limit log's size on the fly, having one backup rolling file (thanks to ContainerRollingLogAppender).

One of the syslog's size limitation approaches works the same way.

So, we can set limitation via new properties in mapred-site.xml:
mapreduce.task.userlog.stderr.limit.kb
mapreduce.task.userlog.stdout.limit.kb

Advantages of such solution:

• it allows us to restrict file sizes during job execution.
• we can see logs during job execution.

Disadvantages:

• It will work only for MRs jobs.

Is it appropriate solution for solving this problem, or is there something better?

Issue Links

• duplicates: YARN-2231 Provide feature to limit MRJob's stdout/stderr size