Replication Validation
The following table describes the available checks for replication validation.
txlog
The topic is contained in the transaction log of the remote instance.
An error on this validation check indicates that this instance is replicating a topic that is not in the transaction log on the downstream instance. This means that the downstream instance is not persisting the messages in a way that can be used for replication, replay, or used as the basis for a queue.
replicate
The topic is replicated from the remote instance back to this instance.
An error on this validation check indicates that this instance is replicating a topic to the downstream instance that is not being replicated back to this instance. This means that any publishes or updates to the topic on the downstream instance are not replicated back to this instance.
sow
If the topic is a SOW topic in this instance, it must also be a SOW topic in the remote instance.
An error on this validation check indicates that this instance is replicating a topic to the downstream instance that is a SOW/Topic
on this instance but is not a SOW/Topic
on the downstream instance. This means that the topic has different behavior on the downstream instance, and does not maintain the current value of records in the topic in the SOW.
cascade
The remote instance must enforce the same set of validation checks for this topic as this instance does.
When relaxing validation rules for a topic that the downstream instance itself replicates, adding an exclusion for cascade
is often necessary as well.
An error on this validation check indicates that this instance enforces a validation check for a topic that the downstream instance does not enforce when that instance replicates the topic.
To understand the impact of this validation check, consider the validation checks that the downstream instance enforces. If the downstream instance enforces the appropriate validation checks, this instance can exclude the cascade
check.
It is sometimes necessary to exclude this check as part of a rolling upgrade, and then to leave this exclusion in place until all instances can be taken offline at the same time. If the cascade
check is the only check being excluded on any instance, the topology can be considered to meet validation rules (and the cascade
exclusion can be safely removed during a maintenance window when all of the instances can be updated simultaneously).
queue
If the topic is a queue in this instance, it must also be a queue in the remote instance.
A distributed queue will not function correctly if one of the instances it is replicated to does not define the topic as a queue.
This option cannot be excluded.
keys
If the topic is a SOW topic in this instance, it must also be a SOW topic in the remote instance and the SOW in the remote instance must use the same Key
definitions.
An error on this validation check indicates that this instance is replicating a topic to the downstream instance that is a SOW/Topic
on both instances, but that the definition of message identity (the Key
configuration for the topic) does not match on the two instances. This means that the contents of this topic may be different on these two instances for the same set of messages published.
replicate_filter
If this topic uses a replication filter, the remote instance must use the same replication filter for replication back to this instance.
An error on this validation check indicates that this instance uses a replication filter for a topic that the downstream instance does not use when it replicates the topic. This means that, given the same set of publishes, the downstream instance may replicate a different set of messages than are replicated to that instance. This would produce inconsistent data across the set of replicated instances.
queue_passthrough
If the topic is a queue in this instance, the remote instance must support passthrough from this group.
An error on this validation check indicates that this instance does not pass through messages for one or more groups that the queue is replicated from. This could lead to a situation where a queue message is undeliverable if a network connection is unavailable or if additional instances are added to the set of instances that contain the queue.
queue_underlying
If the topic is a queue in this instance, it must use the same underlying topic definition and filters in the remote instance.
This option cannot be excluded.
Last updated