[gpfsug-discuss] mmsysmon.py revisited

Jonathon A Anderson jonathon.anderson at colorado.edu
Tue Jul 18 18:51:21 BST 2017


There’s no official way to cleanly disable it so far as I know yet; but you can defacto disable it by deleting /var/mmfs/mmsysmon/mmsysmonitor.conf.

It’s a huge problem. I don’t understand why it hasn’t been given much credit by dev or support.

~jonathon


On 7/18/17, 11:21 AM, "gpfsug-discuss-bounces at spectrumscale.org on behalf of David Johnson" <gpfsug-discuss-bounces at spectrumscale.org on behalf of david_johnson at brown.edu> wrote:

    
    
    
    We also noticed a fair amount of CPU time accumulated by mmsysmon.py on
    our diskless compute nodes. I read the earlier query, where it was answered:
    
    
    
    
    ces == Cluster Export Services,  mmsysmon.py comes from mmcesmon. It is used for managing export services of GPFS. If it is killed,  your nfs/smb etc will be out of work.
    Their overhead is small and they are very important. Don't attempt to kill them.
    
    
    
    
    
    
    Our question is this — we don’t run the latest “protocols", our NFS is CNFS, and our CIFS is clustered CIFS.
    I can understand it might be needed with Ganesha, but on every node? 
    
    
    Why in the world would I be getting this daemon running on all client nodes, when I didn’t install the “protocols" version 
    of the distribution?   We have release 4.2.2 at the moment.  How can we disable this?
    
    
    Thanks,
     — ddj
    



More information about the gpfsug-discuss mailing list