Replication and High Availability

📄️ Does AMPS support replication?

AMPS supports replication to multiple destinations. An instance of AMPS can configure, for each destination, the topics to be replicated and the durability guarantees (configured as the acknowledgement type) that this server should enforce before considering the message to be safely persisted.

📄️ Why does publishFlush() wait forever when I'm using replication?

When this happens, the most common reason is that a replication destination configured for sync acknowledgements is offline.

📄️ Are SOWs for replicated topics guaranteed to be in sync on all instances?

Yes, provided that all of the messages used to build the SOW are still present in the transaction logs, that both instances have processed all of the messages, and that the messages were processed on both instances in the same order.

📄️ How do I set up a failover group in my replication destination?

Simply add the address for each instance in the group to the destination, as shown below:

📄️ How does AMPS report the specific failure in replication validation?

When replication validation fails, an instance will log the reason for the validation failure with error 1E-0065. That error will contain a short description of the reason for the failure.