Glusterfs server-side process analysis
Server-side Process information:
Root 348 0.0 0.2 273104 16268? SSL 17:31 0:00/usr/sbin/glusterd--pid-file=/run/glusterd.pid
Root 401 0.0 0.6 308532 52700? SSL 17:31 0:00/usr/sbin/glusterfs-s localhost--volfile-id gluster/nfs-p/var/lib/glusterd/nfs/run/nfs.pid-l/var/l Og/glusterfs/nfs.log-s/var/run/bdec9c41dda184769df21998432b9bf2.socket
Root 417 0.0 0.2 323660 23612? SSL 17:31 0:00/usr/sbin/glusterfs-s localhost--volfile-id gluster/glustershd-p/var/lib/glusterd/glustershd/run/glu Stershd.pid-l/var/log/glusterfs/glustershd.log-s/var/run/510a9fdbe684d9518726048e1b21a40d.socket-- Xlator-option *replicate*.node-uuid=f22b60d6-ff4d-4247-bdda-0a4fe0223384
Root 32756 0.9 0.2 548512 22132? SSL 17:30 0:07/usr/sbin/glusterfsd-s lab22--volfile-id tank.lab22.letv-disk3-p/var/lib/glusterd/vols/tank/run/lab2 2-letv-disk3.pid-s/var/run/a71a75abe47e437d55b915773b3b4f5c.socket--brick-name/letv/disk3-l/var/log/glusterfs/ Bricks/letv-disk3.log--xlator-option *-posix.glusterd-uuid=f22b60d6-ff4d-4247-bdda-0a4fe0223384--brick-port 49155--xlator-option tank-server.listen-port=49155
Service End multiplicity Start Glusterd service, the following process PID change not.
Root 24082 2.0 0.3 548508 24752? SSL 17:46 0:05/usr/sbin/glusterfsd-s lab21--volfile-id tank.lab21.letv-disk3-p/var/lib/glusterd/vols/tank/run/lab2 1-letv-disk3.pid-s/var/run/5e33431834617265b46d9dc89cdb2e53.socket--brick-name/letv/disk3-l/var/log/glusterfs/ Bricks/letv-disk3.log--xlator-option *-posix.glusterd-uuid=0d5ba4a3-c6fa-4afd-ad39-a2842ca3cde0--brick-port 49176--xlator-option tank-server.listen-port=49176
The other 3 process PID will change, producing a new process.
When the server side performs a gluster volume stop operation, the above process disappears, and a new thread is created after Gluster volume start.
This article is from the "Members Doukua" blog, make sure to keep this source http://dangzhiqiang.blog.51cto.com/7961271/1653799
Glusterfs server-side process analysis