[jira] [Commented] (ARTEMIS-3815) Target mirror controller may commit received message after receiving ACK for it

["ASF subversion and git services (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ARTEMIS-3815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17561192#comment-17561192 ] 

ASF subversion and git services commented on ARTEMIS-3815:
----------------------------------------------------------

Commit d90179b99cc217a2611a7d439ddcc9a27d79dd12 in activemq-artemis's branch refs/heads/main from iliya
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=d90179b99c ]

ARTEMIS-3815 proper retry through IOCompletion when message not found on target queue on Mirror

co-authored Clebert Suconic


> 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: 1.5h
>  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)