| commit | 3af66448e6107f51ff30acfd440f8331515f1792 | [log] [tgz] |
|---|---|---|
| author | rama-huawei <rama.subba.reddy.s@huawei.com> | Mon Sep 18 17:00:39 2017 +0530 |
| committer | Rama SubbaReddy <rama.subba.reddy.s@huawei.com> | Mon Sep 18 12:31:26 2017 +0000 |
| tree | 9c8c38ca8470f2d7b668e8a8878941e5a74f18df | |
| parent | d87c09894ad714e711ea2e10844262182d226fa3 [diff] |
Fix for Sonar major issues DCAEGEN2-93 Change-Id: I5f06f8086f2c64ae2b8cdeca68900839b5c73fa3 Signed-off-by: rama-huawei <rama.subba.reddy.s@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