[jira] [Updated] (GEODE-10346) Correct batch-time-interval description in documentation

["Alberto Gomez (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/GEODE-10346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alberto Gomez updated GEODE-10346:
----------------------------------
    Fix Version/s: 1.15.1

> Correct batch-time-interval description in documentation
> --------------------------------------------------------
>
>                 Key: GEODE-10346
>                 URL: https://issues.apache.org/jira/browse/GEODE-10346
>             Project: Geode
>          Issue Type: Bug
>          Components: docs, wan
>            Reporter: Alberto Gomez
>            Assignee: Alberto Gomez
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.15.1, 1.16.0
>
>
> The description of the batch-time-interval parameter for the Gateway Sender in the Geode documentation states the following:
> "Maximum amount of time, in ms, that can elapse before a batch is delivered."
> Nevertheless, that is not completely true.
> The number of ms that can elapse before a batch is delivered could be longer than what is configured in batch-time-interval in the case that the batch being created has not yet reached the value of max-batch-size and there are still events in the gateway sender's queue to be added to the batch. If that is the case, new events will keep being added to the batch without taking into account the value for batch-time-interval.
> The batch-time-interval parameter is only used when the batch being filled has not reached the max-batch-size but there are no events in the queue. In that case, in order not to delay the delivery of the batch until there are events in the queue, this value is used to determine if the batch must be sent.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)