jaehacker.blogg.se - Dmr control center monitor

If there is a topology error, or DMR is down for some other reason, subscription propagation and data forwarding throughout the network may not be working properly.

problems with Guaranteed Messaging (e.g., the message spool is down).

misconfiguration in other areas, such as replication or redundancy.

In addition, for nodes connected by an internal link, the list of Message VPNs participating in DMR on each node must be the same.ĭMR can be operationally down for other reasons, such as:

DMR is not correctly enabled-each participating VPN must opt in to DMR.

node name mismatch-each node must correctly specify the name of the remote node connected by the link.missing channels-each link must have a control channel plus one data channel per message VPN.The configuration at both ends of the link must match. mismatched link span-a link is either internal (connecting two nodes within a cluster) or external (connecting gateway nodes in two different clusters).Links must be bi-directional that is, each link must be configured correctly on both nodes. missing links-every node in a cluster must be connected by an internal link.However, if you following the procedures in this documentation, no message loss is expected, and the topology problem should be temporary and clear by itself. Topology problems are expected while adding and removing nodes in a network, because configuration changes need time to propagate through the event mesh.

Topology errors are caused by problems in the configured or operational network topology. If there are problems with your event mesh, for example if DMR is configured incorrectly or if there are operational problems in the network, one or more brokers may report topology errors or DMR being operationally down.