[
https://issues.apache.org/jira/browse/ARTEMIS-3815?focusedWorklogId=786650&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-786650
]
ASF GitHub Bot logged work on ARTEMIS-3815:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 30/Jun/22 15:08
Start Date: 30/Jun/22 15:08
Worklog Time Spent: 10m
Work Description: clebertsuconic commented on PR #4066:
URL:
https://github.com/apache/activemq-artemis/pull/4066#issuecomment-1171339019
not that the changes are not welcomed.. it's just that I'm having a hard
time with the rebase.. but leave it with me :)
Issue Time Tracking
-------------------
Worklog Id: (was: 786650)
Time Spent: 20m (was: 10m)
> 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: 20m
> 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)
