diff options
| author | jerryshao <sshao@hortonworks.com> | 2016-06-29 08:17:27 -0500 |
|---|---|---|
| committer | Tom Graves <tgraves@yahoo-inc.com> | 2016-06-29 08:17:27 -0500 |
| commit | 272a2f78f3ff801b94a81fa8fcc6633190eaa2f4 (patch) | |
| tree | 116630944456f0dbc3599d82694239c4e2a67c54 /conf | |
| parent | 393db655c3c43155305fbba1b2f8c48a95f18d93 (diff) | |
| download | spark-272a2f78f3ff801b94a81fa8fcc6633190eaa2f4.tar.gz spark-272a2f78f3ff801b94a81fa8fcc6633190eaa2f4.tar.bz2 spark-272a2f78f3ff801b94a81fa8fcc6633190eaa2f4.zip | |
[SPARK-15990][YARN] Add rolling log aggregation support for Spark on yarn
## What changes were proposed in this pull request?
Yarn supports rolling log aggregation since 2.6, previously log will only be aggregated to HDFS after application is finished, it is quite painful for long running applications like Spark Streaming, thriftserver. Also out of disk problem will be occurred when log file is too large. So here propose to add support of rolling log aggregation for Spark on yarn.
One limitation for this is that log4j should be set to change to file appender, now in Spark itself uses console appender by default, in which file will not be created again once removed after aggregation. But I think lots of production users should have changed their log4j configuration instead of default on, so this is not a big problem.
## How was this patch tested?
Manually verified with Hadoop 2.7.1.
Author: jerryshao <sshao@hortonworks.com>
Closes #13712 from jerryshao/SPARK-15990.
Diffstat (limited to 'conf')
0 files changed, 0 insertions, 0 deletions