[ 
https://issues.apache.org/jira/browse/ARTEMIS-5001?focusedWorklogId=931004&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-931004
 ]

ASF GitHub Bot logged work on ARTEMIS-5001:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 20/Aug/24 16:54
            Start Date: 20/Aug/24 16:54
    Worklog Time Spent: 10m 
      Work Description: clebertsuconic commented on code in PR #5158:
URL: https://github.com/apache/activemq-artemis/pull/5158#discussion_r1723651647


##########
artemis-protocols/artemis-amqp-protocol/src/main/java/org/apache/activemq/artemis/protocol/amqp/connect/mirror/AMQPMirrorControllerTarget.java:
##########
@@ -201,12 +219,31 @@ public void flow() {
       creditRunnable.run();
    }
 
+
    @Override
    protected void actualDelivery(Message message, Delivery delivery, 
DeliveryAnnotations deliveryAnnotations, Receiver receiver, Transaction tx) {
       recoverContext();
+
+
+      
OperationContextImpl.getContext().setSyncReplication(configuration.isMirrorReplicaSync());

Review Comment:
   so I don't think it needs.. although I will set the syncReplication in the 
recoverContext as it would be more obvious





Issue Time Tracking
-------------------

    Worklog Id:     (was: 931004)
    Time Spent: 50m  (was: 40m)

> Add configuration option to relax syncs journal replication for Mirror Target
> -----------------------------------------------------------------------------
>
>                 Key: ARTEMIS-5001
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-5001
>             Project: ActiveMQ Artemis
>          Issue Type: Improvement
>    Affects Versions: 2.37.0
>            Reporter: Clebert Suconic
>            Assignee: Clebert Suconic
>            Priority: Major
>             Fix For: 2.38.0
>
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> When I worked on AMQP Mirror I did not actually envision being used with 
> journal replication. I actually thought more about adding multiple mirrored 
> options instead.
> However an user reported me that when using mirror and journal replication 
> combined, the sends could take a lot longer to happen (some normal latency) 
> and the acks would eventually be missed.
> I should add an option to ignore the replication for the Mirror Target.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information, visit: https://activemq.apache.org/contact


Reply via email to