You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@activemq.apache.org by "Francesco Nigro (Jira)" <ji...@apache.org> on 2022/01/18 06:29:00 UTC

[jira] [Updated] (ARTEMIS-3651) Simplify batch-delay with Netty's FlushConsolidationHandler

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

Francesco Nigro updated ARTEMIS-3651:
-------------------------------------
    Summary: Simplify batch-delay with Netty's FlushConsolidationHandler  (was: Replace batch-delay current logic, replacing it with Netty's FlushConsolidationHandler)

> Simplify batch-delay with Netty's FlushConsolidationHandler
> -----------------------------------------------------------
>
>                 Key: ARTEMIS-3651
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-3651
>             Project: ActiveMQ Artemis
>          Issue Type: Wish
>            Reporter: Francesco Nigro
>            Assignee: Francesco Nigro
>            Priority: Major
>
> {{batchDelay}} is an ancient acceptors/connnectors configuration parameter that aim to force batching while sending messages through Netty and use a separate thread, looping over all active connections, to flush pending batches in background.
> https://netty.io/4.1/api/io/netty/handler/flush/FlushConsolidationHandler.html  configured with {{ consolidateWhenNoReadInProgress == true}} works in the same way, while simplifying Artemis code-base ie much less code to be maintained



--
This message was sent by Atlassian Jira
(v8.20.1#820001)