Administration guide > Configure the deployment environment > Configuring deployment policies > Controlling shard placement with zones

Define zones for containers


Zones are collections of container servers. A container server can belong to at most one zone. A container server is assigned to a zone when it starts.

Without WAS

Within WAS

You can use node groups to place servers in specific zones using...


Servers running on a node that is part of such a node group are included in the zone specified by the element...


WAS does not prohibit nodes from being in multiple node groups. Because eXtreme Scale limits container servers to a single zone, ensure that any of the nodes is in only one ReplicationZone node group.

For example, divide four nodes into two zones, A and B.

  1. Configure four nodes: node1, node2, node3, and node4, each node having two servers.

  2. Create a node group named ReplicationZoneA and a node group named ReplicationZoneB.

  3. Add node1 and node2 to ReplicationZoneA and add node3 and node4 to ReplicationZoneB.

  4. When the servers on node1 and node2 are started, they join ReplicationZoneA, zone A in eXtreme Scale. Also, the servers on node3 and node4 join ReplicationZoneB, as zone B to eXtreme Scale.

Remember: A container server checks for zone membership at startup only. Adding a new node group or changing the membership only has an impact on newly started or restarted container servers.

Parent topic:

Controlling shard placement with zones