[
https://issues.apache.org/jira/browse/ARTEMIS-3815?focusedWorklogId=786787&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-786787
]
ASF GitHub Bot logged work on ARTEMIS-3815:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 30/Jun/22 19:49
Start Date: 30/Jun/22 19:49
Worklog Time Spent: 10m
Work Description: clebertsuconic commented on PR #4130:
URL:
https://github.com/apache/activemq-artemis/pull/4130#issuecomment-1171613491
@iliya-gr I was considering always calling ACL on the afterCompletion
operations... however that would incur into more objects used.
So, I'm keeping the flow the way it is, and having now two levels of retry:
1st the IOCompletion, 2nd: the flush on the queue.
let me know what you think please?
Issue Time Tracking
-------------------
Worklog Id: (was: 786787)
Time Spent: 1h 10m (was: 1h)
> Target mirror controller may commit received message after receiving ACK for
> it
> -------------------------------------------------------------------------------
>
> Key: ARTEMIS-3815
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3815
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: AMQP
> Affects Versions: 2.19.1, 2.21.0, 2.22.0
> Reporter: Iliya Grushevskiy
> Priority: Major
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> Given two brokers *A* and {*}B{*}, with configured mirror *A* towards *B* and
> a queue {*}Q{*}. If disk operations on *B* are slow, and there are active
> exchanges of messages on queue {*}Q{*}, for example:
> # Send message 1
> # ACK message 1
> # Send message 2
> # ACK message 2
> # ...
> At the end queue *Q* on *B* will contain some unacknowledged messages, while
> queue *Q* on *A* will be empty.
> The issue is that commit in sendMessage may take some time and ref to message
> will be written to the intermediate store only after receiving an ACK for
> this message.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
