Gluster - How to check geo-replication related processes / daemons

Issue

The purpose of this document is to identify the expected daemons/process associated to a geo-replicated session.

When geo-replication session is stopped, all related process should be stopped.
Once geo-replication session is stoppped, it is a good practice to check whether the related process are still present or not on the gluster nodes of the master side. If still present , we would need to kill them : kill -9 <pid>

Note: Always kill monitor process first , otherwise it will respawn a new agent/worker process.