Versions Compared

Version Old Version 3 New Version 4
Changes made by

Kyle Miller (Deactivated)

Kyle Miller (Deactivated)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Warning
title

Deprecated

With Storage 10.0, Swarm is single-process only. This information applies only to Storage 9.x and earlier.

Table of Contents

Use the following configuration settings in the node or cluster configuration file to implement the Swarm multi-server feature:

...

Code Block
languagebash
chassis.processes = 2
title
Info

Note

A memory overhead exists with running multiple Swarm processes in a single chassis. A single Swarm process indexes more objects than multiple processes sharing the same amount of RAM.

Make sure that the number of IP addresses specified by the network.ipAddress setting matches the number of processors specified by the chassis.processes setting. For example, if you set chassis.processes = 3, make sure you specify three IP addresses.

title
Info

Important

If chassis.processes is set, the disk.volumes setting must be left blank or set to all.

Network Setup Settings

When you implement a multi-server Swarm storage cluster, you must assign each node a static IP address because DHCP cannot be implemented in multi-server mode. When you enable the multi-server mode, the network.ipAddress setting syntax is extended by appending the IP address for each process in a list, separated by a space.

...

Code Block
languagebash
chassis.processes = 2 
network.ipAddress = 192.10.11.200 192.10.11.201 
network.netmask = 255.255.0.0 
network.gateway = 192.10.1.1
title
Info

Tip

Assign your chassis IP addresses in a continuous sequence (such as 192.10.110.200, 192,10.11.201, …). This will help you monitor and maintain related volumes in an orderly way.

Using the disk.volumes Setting

...

The disk.volumes = all setting causes all volumes in a chassis to be distributed evenly among the number of Swarm processes as defined by the chassis.processes setting. This distribution occurs automatically at boot time and adapts to any changes in the number of drives or processes from the previous boot. This allows Swarm to redistribute volumes among Swarm processes as needed each reboot.

title
Info

Important

Hot plugging is only supported for disk.volumes = all.

title
Info

Note

The volsN settings (for example, vols0, vols1) are deprecated and should be replaced with disk.volumes = all . If the chassis.processes setting is set, the disk.volumes setting must be left blank or set to all.

Using the node.subcluster Setting

...

When you assign the subcluster, you can include more than one multi-server chassis in the same subcluster provided more than one subcluster is used for the whole cluster.

title
Info

Note

If your multi-server configuration includes more than one chassis, use the drive identification feature to determine which physical chassis a given virtual node belongs to in the subcluster. Nodes are sorted by IP address, so it is possible that the Swarm Admin Console will not group nodes from the same chassis together.

title
Info

Tip

To simplify this process, assign contiguous IP addresses in a chassis. For more information about volume identification, see the Drive Identification Plugin.

You can use subclusters for other purposes, such as data protection. For example, if you have data centers in separate wings of your building, you can create subclusters to copy content to data centers in both wings to provide high availability in case of a partial building loss. A loss could be events like a fire, flooding, or air conditioning problems.

See Local Area Replication Using Subclusters.