You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by "Siva Kotipalli (JIRA)" <ji...@apache.org> on 2015/06/14 18:21:00 UTC

[jira] [Created] (LOG4J2-1053) batchSize for FlumeAvro non persistent manager is ignored

Siva Kotipalli created LOG4J2-1053:
--------------------------------------

             Summary: batchSize for FlumeAvro non persistent manager is ignored
                 Key: LOG4J2-1053
                 URL: https://issues.apache.org/jira/browse/LOG4J2-1053
             Project: Log4j 2
          Issue Type: Bug
          Components: Flume Appender
    Affects Versions: 2.2
            Reporter: Siva Kotipalli


The batchSize parameter that is included during creation of RpcClient is only used in case of appenBatch method and not for append method.
Kindly refer to the documentation below.
http://flume.apache.org/releases/content/1.5.0/apidocs/org/apache/flume/api/AbstractRpcClient.html#getBatchSize()

In the existing unit test testBatch(), the batch size is given as 10 and check on the channel also done after populating 10 events, instead if you populate only 5 events, the events should not be transferred to the channel as batchSize is 10 and we need to get error on Assert.assertNotNull, which doesnt happen.
I had done some tweaks on FlumeAvroManager and tested with appendBatch, where the batchSize parameter is properly identified by rpc client.  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org