[
https://issues.apache.org/jira/browse/ARTEMIS-3282?focusedWorklogId=595454&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-595454
]
ASF GitHub Bot logged work on ARTEMIS-3282:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 12/May/21 16:39
Start Date: 12/May/21 16:39
Worklog Time Spent: 10m
Work Description: gtully commented on a change in pull request #3566:
URL: https://github.com/apache/activemq-artemis/pull/3566#discussion_r631215271
##########
File path:
artemis-server/src/main/java/org/apache/activemq/artemis/core/replication/ReplicationEndpoint.java
##########
@@ -221,6 +221,8 @@ public void handlePacket(final Packet packet) {
handleCommitRollback((ReplicationCommitMessage) packet);
break;
case PacketImpl.REPLICATION_PAGE_WRITE:
+ // potential blocking I/O operation! flush existing packets to
save long tail latency
+ endOfBatch();
Review comment:
For sure batching is good, what I am struggling with is the use case for
setting a limit on accumulating, b/c the other end is waiting, there also needs
to be some timeout in case the limit is not reached. Batching on low
utilisation seems unfair on the sender in this case, and the sender is
blocking. I need to peek more to see what -1 does :-) thanks for the detail.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 595454)
Time Spent: 3h (was: 2h 50m)
> Expose Replication response batching tuning
> -------------------------------------------
>
> Key: ARTEMIS-3282
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3282
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Reporter: Francesco Nigro
> Assignee: Francesco Nigro
> Priority: Major
> Time Spent: 3h
> Remaining Estimate: 0h
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
