| commit | edeee1d6e9fd857c8fb9b8622633fee43efb00e2 | [log] [tgz] |
|---|---|---|
| author | Lee, Tian (tl5884) <TianL@amdocs.com> | Tue Jul 10 15:03:19 2018 +0100 |
| committer | sunil unnava <su622b@att.com> | Mon Jul 23 18:01:40 2018 +0000 |
| tree | 2f51c177883cd164b4aeaeb382990324989cda20 | |
| parent | 1f70b26884ba61f466eac21635eae125acd29a1f [diff] |
Fix bug with host failover functionality DMaaP client does not failover to next configured host when the current host returns an error status during event consumption. Change-Id: I117ab993c3badea819876943e446d9ab45fd2db8 Issue-ID: DMAAP-541 Signed-off-by: Lee, Tian (tl5884) <TianL@amdocs.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