Skip to main content

Cluster starting and stopping

Starting MooseFS Cluster

To safely start the MooseFS cluster, perform the following steps in the order listed below.

1. Start the Metalogger Process

Begin by starting the MooseFS Metalogger service:

SysV init systems

service moosefs-pro-metalogger start

systemd-based systems

systemctl start moosefs-pro-metalogger.service

2. Start the Master Server Processes

Start the MooseFS Master Servers

SysV init systems

service moosefs-pro-master start

systemd-based systems

systemctl start moosefs-pro-master.service

3. Start the Chunkserver Processes

Next, start all Chunkserver instances:

SysV init systems

service moosefs-pro-chunkserver start

systemd-based systems

systemctl start moosefs-pro-chunkserver.service

4. Mount MooseFS on All Clients

Finally, mount the MooseFS file system on all client machines:

mfsmount /mnt/mfs -H mfs-master

After mounting, verify the cluster state if needed using:

df -h | grep mfs

Stopping MooseFS Cluster

To safely stop the MooseFS cluster, follow the steps below in the correct order to avoid data inconsistency or unexpected behavior.

1. Unmount MooseFS on All Clients

Before stopping any MooseFS services, unmount the MooseFS file system from all client machines:

umount /mnt/mfs

Repeat this on every machine that has MooseFS mounted.

2. Stop the Chunkserver Processes

Stop all MooseFS Chunkserver instances:

SysV init systems

service moosefs-pro-chunkserver stop

systemd-based systems

systemctl stop moosefs-pro-chunkserver.service

3. Stop the Master Server Processes

Master Servers must be stopped in order, starting with all FOLLOWER Master Servers.

The LEADER Master Server must be stopped last.

SysV init systems

service moosefs-pro-master stop

systemd-based systems

systemctl stop moosefs-pro-master.service

4. Stop the Metalogger Process

Finally, stop the Metalogger service:

SysV init systems

service moosefs-pro-metalogger stop

systemd-based systems

systemctl stop moosefs-pro-metalogger.service