| commit | 958e512dc08a2a2427b613e8f9c24c72905bb701 | [log] [tgz] |
|---|---|---|
| author | rama-huawei <rama.subba.reddy.s@huawei.com> | Thu Sep 14 14:31:46 2017 +0530 |
| committer | Rama SubbaReddy <rama.subba.reddy.s@huawei.com> | Thu Sep 14 09:06:10 2017 +0000 |
| tree | a09f0587564cd0b8395f5fa6108c78a76c079e3a | |
| parent | 8ce1fcc98dd09c76a8d696e7dfa479c9cea2f9d4 [diff] |
Fix for Sonar critical issues DCAEGEN2-93 Change-Id: I65ba03cca99c1aa5a845f6b5c026087a85eba2ba 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