You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2023/01/23 17:39:00 UTC

[jira] [Commented] (ARTEMIS-4136) Mirror sync replication

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

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

Commit 0d3cd8d88031dbf78851969a56041e839f828bf7 in activemq-artemis's branch refs/heads/main from Clebert Suconic
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=0d3cd8d880 ]

ARTEMIS-4136 Mirrored sync replica

I am adding an option sync=true or false on mirror. if sync, any client blocking operation will wait a roundtrip to the mirror
acting like a sync replica.


> Mirror sync replication
> -----------------------
>
>                 Key: ARTEMIS-4136
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-4136
>             Project: ActiveMQ Artemis
>          Issue Type: New Feature
>            Reporter: Clebert Suconic
>            Assignee: Clebert Suconic
>            Priority: Major
>             Fix For: 2.28.0
>
>          Time Spent: 5h 20m
>  Remaining Estimate: 0h
>
> I'm adding an option sync=true|false on mirror.
> It will be possible to configure a mirror as this:
>      <broker-connections>
>          <amqp-connection uri="tcp://test1:111" name="test1" retry-interval="333" reconnect-attempts="33" user="testuser" password="testpassword">
>             <mirror sync="true"/>
>        </amqp-connection
>    </broker-connection>
> if sync is set to true, any client blocking operation would wait a mirror callback.
> With that option set, any blocking operation on the broker will wait a mirror roundtrip:
> tx.commit(), session.send (non transactional). client.ack (when configured as sync).
> Notice that in AMQP client dispositions are always asynchronous, hence it's only possible to sync acks if using transactional for AMQP.



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