commit | 6454abb6d4e469b0bb33dbc94105bae6c31dbe89 | [log] [tgz] |
---|---|---|
author | Gary Wu <gary.i.wu@huawei.com> | Fri Aug 24 15:22:40 2018 -0700 |
committer | Gary Wu <gary.i.wu@huawei.com> | Mon Aug 27 10:28:14 2018 -0700 |
tree | f433a77f66d2dde16a9af7fcd7c96418908a8381 | |
parent | 476332cc4a86aada98798c23f6f48b0df6307375 [diff] |
Use managed guava version Use centrally managed guava version specified in oparent. Includes upgrade to oparent 1.2.0. This change was submitted by script and may include additional whitespace or formatting changes. Change-Id: I2b9a2311c7c5d23406923c8d056fb8da8ae6a9be Issue-ID: INT-619 Signed-off-by: Gary Wu <gary.i.wu@huawei.com>
To configure a MR Log4J appender the following parameters are available:
(R) Topic [String] - The topic which you wish to publish your log messages to (R) Partition [String]- The partition within the Topic that you wish you publish your log messages to (R) Hosts [String]- A comma separated string containing the MR API server nodes you wish to connect to (O) MaxBatchSize [Integer] - The maximum size of the batch of log messages. When the batch grows larger than this, the messages are flushed to the topic/partition. (O) MaxAgeMs [Integer] - The maximum age in milliseconds of the batch. When the batch age is older than this, the messages are flushed to the topic/partition. (O) Compress [Boolean] - Indicates whether you would like your messages compressed or not.
An example can be found in ./src/main/resources/log4j.xml