Shulou(Shulou.com)06/01 Report--

This article introduces the relevant knowledge of "GlusterFS server-side process instance analysis". In the operation of actual cases, many people will encounter such a dilemma, so let the editor lead you to learn how to deal with these situations. I hope you can read it carefully and be able to achieve something!

GlusterFS server-side process analysis

Server 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/log/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/glustershd.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/lab22-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

The server restarts the glusterd service, and the following process PID does not change.

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/lab21-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 three processes PID will change to produce new processes.

When the server performs the gluster volume stop operation, the above process disappears, and a new thread is created after the gluster volume start.

This is the end of "GlusterFS server-side process instance analysis". Thank you for reading. If you want to know more about the industry, you can follow the website, the editor will output more high-quality practical articles for you!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.