| commit | 952b238717fbc558d7b017c531220f246921d968 | [log] [tgz] |
|---|---|---|
| author | varun gudisena <vg411h@att.com> | Wed Jan 31 02:09:42 2018 +0000 |
| committer | Gerrit Code Review <gerrit@onap.org> | Wed Jan 31 02:09:42 2018 +0000 |
| tree | 2b3cfec5f5697fbde8379d1b07def7cd352f9a00 | |
| parent | 85c21e1d85c545717affd3f18cd8e9fe6dc14562 [diff] | |
| parent | 92ff34414e70a7fb2936246ce4760095f46c8323 [diff] |
Merge "sonar critical for InterruptedException"
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