<font size=2 face="sans-serif">thanks for the feedback. </font><br><br><font size=2 face="sans-serif">Let me clarify what mmsysmon is doing.</font><br><font size=2 face="sans-serif">Since IBM Spectrum Scale 4.2.1 the mmsysmon
process is used for the overall health monitoring and CES failover handling.</font><br><font size=2 face="sans-serif">Even without CES it is an essential
part of the system because it monitors the individual components and provides
health state information and error events. </font><br><font size=2 face="sans-serif">This information is needed by other
Spectrum Scale components (mmhealth command, the IBM Spectrum Scale GUI,
Support tools, Install Toolkit,..) and therefore disabling mmsysmon will
impact them. </font><br><br><tt><font size=2>> It’s a huge problem. I don’t understand why
it hasn’t been given <br>> much credit by dev or support.</font></tt><br><br><font size=2 face="sans-serif">Over the last couple of month, the development
team has put a strong focus on this topic. </font><br><font size=2 face="sans-serif">In order to monitor the health of the
individual components, mmsysmon listens for notifications/callback but
also has to do some polling.</font><br><font size=2 face="sans-serif">We are trying to reduce the polling
overhead constantly and replace polling with notifications when possible.
</font><br><br><font size=2 face="sans-serif">Several improvements have been added
to 4.2.3, including the ability to configure the polling frequency to reduce
the overhead. (<i>mmhealth config interval) </i></font><br><font size=2 face="sans-serif">See </font><a href=https://www.ibm.com/support/knowledgecenter/en/STXKQY_4.2.3/com.ibm.spectrum.scale.v4r23.doc/bl1adm_mmhealth.htm><font size=2 color=blue face="sans-serif">https://www.ibm.com/support/knowledgecenter/en/STXKQY_4.2.3/com.ibm.spectrum.scale.v4r23.doc/bl1adm_mmhealth.htm</font></a><br><font size=2 face="sans-serif">In addition a new option has been introduced
to clock align the monitoring threads in order to reduce CPU jitter. </font><br><br><font size=2 face="sans-serif">Nevertheless, we don't see significant
CPU consumption by mmsysmon on our test systems. </font><br><font size=2 face="sans-serif">It might be a problem specific to your
system environment or a wrong configuration therefore please get in contact
with IBM support to analyze the root cause of the high usage.</font><br><br><font size=2 face="sans-serif">Kind regards<br><br>Mathias Dietz<br></font><br><font size=2 face="sans-serif">IBM Spectrum Scale - Release Lead Architect
and RAS Architect <br></font><br><br><tt><font size=2>gpfsug-discuss-bounces@spectrumscale.org wrote on
07/18/2017 07:51:21 PM:<br><br>> From: Jonathon A Anderson <jonathon.anderson@colorado.edu></font></tt><br><tt><font size=2>> To: gpfsug main discussion list <gpfsug-discuss@spectrumscale.org></font></tt><br><tt><font size=2>> Date: 07/18/2017 07:51 PM</font></tt><br><tt><font size=2>> Subject: Re: [gpfsug-discuss] mmsysmon.py revisited</font></tt><br><tt><font size=2>> Sent by: gpfsug-discuss-bounces@spectrumscale.org</font></tt><br><tt><font size=2>> <br>> There’s no official way to cleanly disable it so far as I know yet;
<br>> but you can defacto disable it by deleting /var/mmfs/mmsysmon/<br>> mmsysmonitor.conf.<br>> <br>> It’s a huge problem. I don’t understand why it hasn’t been given
<br>> much credit by dev or support.<br>> <br>> ~jonathon<br>> <br>> <br>> On 7/18/17, 11:21 AM, "gpfsug-discuss-bounces@spectrumscale.org
on <br>> behalf of David Johnson" <gpfsug-discuss-bounces@spectrumscale.org
<br>> on behalf of david_johnson@brown.edu> wrote:<br>> <br>> <br>> <br>> <br>> We also noticed a fair amount of CPU time accumulated
by mmsysmon.py on<br>> our diskless compute nodes. I read the earlier query,
where it <br>> was answered:<br>> <br>> <br>> <br>> <br>> ces == Cluster Export Services, mmsysmon.py comes
from <br>> mmcesmon. It is used for managing export services of GPFS. If it is
<br>> killed, your nfs/smb etc will be out of work.<br>> Their overhead is small and they are very important.
Don't <br>> attempt to kill them.<br>> <br>> <br>> <br>> <br>> <br>> <br>> Our question is this — we don’t run the latest “protocols",
our <br>> NFS is CNFS, and our CIFS is clustered CIFS.<br>> I can understand it might be needed with Ganesha, but
on every node? <br>> <br>> <br>> Why in the world would I be getting this daemon running
on all <br>> client nodes, when I didn’t install the “protocols" version
<br>> of the distribution? We have release 4.2.2 at
the moment. How<br>> can we disable this?<br>> <br>> <br>> Thanks,<br>> — ddj<br>> <br>> <br>> _______________________________________________<br>> gpfsug-discuss mailing list<br>> gpfsug-discuss at spectrumscale.org<br>> </font></tt><a href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss"><tt><font size=2>http://gpfsug.org/mailman/listinfo/gpfsug-discuss</font></tt></a><tt><font size=2><br></font></tt><BR>