[
https://issues.apache.org/jira/browse/ARTEMIS-3507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17425417#comment-17425417
]
Lasse Lindgård commented on ARTEMIS-3507:
-----------------------------------------
The reason for not tuning the ackBatchSize for my client is that I have a lot
of queues, in a lot of environments, with very different loads.
Configuring each and everyone separately is a huge endeavor. I would just like
the defaults to be really good.
And by really good I mean - ack often when traffic is low, batch acks otherwise.
Would it be possible to be a little smarter about it?
> Smarter batching of acks
> ------------------------
>
> Key: ARTEMIS-3507
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3507
> Project: ActiveMQ Artemis
> Issue Type: Wish
> Components: Broker
> Affects Versions: 2.17.0
> Reporter: Lasse Lindgård
> Priority: Major
>
> Using the default settings and the CORE api, I create a long running
> ClientSession, with a MessageHandler.
> Now when I consume messages I can see that the message acks are batched and
> delivered to the broker as configured in ackBatchSize. And the Message Count
> in the management console are only decreased when the acks are actually sent.
> In a low traffic scenario, with long running consumers, that might cause the
> acks "never" be sent or only to be sent on restarting the services.
> I wish that that could be improved somehow. And not by setting
> ackBatchSize=0. But in some clever way make sure that the acks are sent, even
> when the traffic is lower.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
