Modify the log level in/usr/lib/systemd/system/glusterd.service to trace
Environment= "Log_level=trace"
can see more log
After installing the Gluster, there will be 4 files associated with the/usr/sbin.
These 4 files, in fact you will find that 3 of them are pointing to the same file glusterfsd,
There is also a gluster, which is responsible for parsing the configuration from bash, querying commands such as Glustervolume Info,start, etc.
And so on, it is a client of RPC
Figure 1-1
When you call service Glusterd start, the following script will start the following process
If you configure the volume will start the following process, also when the call Gluster volume stop this process will be kill
If you configure multiple volume, you will start multiple processes, for example, we have configured 2 volume and will start 2 processes
In addition, with the launch of the volume, 2 processes will also start, but no matter how many volume you configure, it is always the 2 in charge
One responsible for NFS (Networking File System)
Another responsible for self-healing
And when we mount a volume, we start the following process
/usr/sbin/glusterfs--volfile-server=192.168.0.2--volfile-id=export-gv1/mnt-gluster-1
Please refer to/usr/sbin/mount.glusterfs script for how to start