Structure Of A Dx Content Router Node - Dell DX6000 Setup And Configuration Manual

3.1.1. Structure of a DX Content Router Node

DX Content Router consists of a server machine running Linux and executes one or both of two
services:
1. Publisher - processes all streams stored in a cluster, filters them based on stream metadata, and
publishes UUIDs to remote Subscribers.
2. Subscriber - retrieves UUID publications from remote Publishers. A Replicator, the most
common subscriber, retrieves remote UUIDs and sends replication requests to local nodes
and must be installed on a server in the same subnet as its target storage cluster. A 3rd party
application, which may or may not be installed on a node with other DX Content Router services,
can also function as a subscriber by integrating with the Enumerator API defined in the Appendix.
DX Content Router service configuration parameters are used to enable one or both services,
depending on the intended network topology. For the simple example in the previous section, where
a primary cluster replicates in one direction to a single DR cluster and all nodes in both clusters are
mutually visible, the DX Content Router in the primary cluster would likely be configured to run only
the Publisher service and the DX Content Router in the DR cluster would run just the Subscriber. A
slightly more complex example would be a pair of mirrored clusters where all nodes in both clusters
still have mutual visibility. DX Content Router servers for this topology would look like the diagram
below. For clarity, the assumed direct connections between storage nodes in the two clusters as
shown and discussed in the previous example have been omitted.
Copyright © 2010 Caringo, Inc.
All rights reserved 5
Version 2.2
December 2010