Versions Compared

Old Version 9

changes.mady.by.user Kyle Miller

Saved on

compared with

New Version 10

changes.mady.by.user Kyle Miller

Saved on

Key

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

Info

Note

To support hot plugging, Swarm requires control of all volumes (disk.volumes = all) to support hot plugging.

  • I/O errors are recorded in the log if the Health Processor is actively scanning a drive disk when it is removed. These errors are expected and do not indicate a problem.

  • When a drive disk is removed, volume recovery (FVR) and erasure coding recovery (ECR) are both triggered, which includes creating new replicas or erasure set segments for objects stored on that drivedisk.

  • Both recovery processes stop if a drive disk is inserted in the same node or in a different node in the cluster. There is a temporary state of over-replication because the returned volume has replicas or segments already recreated elsewhere. In time, the excess replicas or segments are deleted.

  • Swarm recognizes, formats, and mounts a drive disk as a new volume if a non-Swarm drive disk is inserted in a node.

  • A Swarm-formatted drive disk continues to function as a volume without loss of data if inserted, either into the same node or into a different node.

  • A volume remains retired if a previously retired Swarm-formatted drive disk is inserted. No manual configuration or intervention is required.

  • Messages display in logs and in the Swarm Admin Console to indicate a drive disk was inserted or removed.

  • Wait 2 minutes between drive disk insertions to guarantee new drives disks are evenly distributed across multiple nodes running on the chassis if inserting multiple drives disks into the same server chassis.

Info

Caution

When adding or relocating volumes to a node, verify the node has enough RAM to handle them, else the node may be unable to mount some of the volumes.

Info

Warning

Do not move Swarm drives disks between disk array controller types after they have been are formatted by Swarm. Each controller reports available drive disk space to Swarm matched with the controller. For example, many controllers claim the last section of the drivedisk, reducing the total available space. The new controller may claim additional drive disk space not reported to Swarm, so Swarm may attempt to write data to non-existing space, generating I/O errors if drives disks are switch with another controller.

...