<html><body><p><tt><font size="2">/usr/lpp/mmfs/bin/mmcommon notifyOverload will not cause tracing to be started. One can verify that using the underlying command being called as shown in the following example with /tmp/n containing node names one each line that will get the notification and the IP address being the file system manager from which the command is issued.</font></tt><br><br><b><font size="2" face="Courier-Bold">/usr/lpp/mmfs/bin/mmsdrcli notifyOverload /tmp/n 1191 192.168.117.131 3 8</font></b><br><br><font size="2">The only case that deadlock detection code will initiate tracing is that debugDataControl is set to "heavy" and tracing is not started. Then on deadlock detection tracing is turned on for 20 seconds and turned off.</font><br><br><font size="2">That can be tested using command like </font><br><b><font size="2" face="Courier-Bold">/usr/lpp/mmfs/bin/mmsdrcli notifyDeadlock /tmp/n 1191 192.168.117.131 3 8</font></b><br><br><font size="2">And then mmfs.log will tell you what's going on. That's not a silent action.</font><br><br><b><font size="2" face="Courier-Bold">2018-03-12_10:16:11.243-0400: [N] sdrServ: Received deadlock notification from 192.168.117.131</font></b><br><b><font size="2" face="Courier-Bold">2018-03-12_10:16:11.243-0400: [N] GPFS will attempt to collect debug data on this node.</font></b><br><b><font size="2" face="Courier-Bold">2018-03-12_10:16:11.953-0400: [I] Tracing in overwrite mode <== tracing started</font></b><br><b><font size="2" face="Courier-Bold">Trace started: Wait 20 seconds before cut and stop trace</font></b><br><b><font size="2" face="Courier-Bold">2018-03-12_10:16:37.147-0400: [I] Tracing disabled <== tracing stopped 20 seconds later</font></b><br><b><font size="2" face="Courier-Bold">mmtrace: move /tmp/mmfs/lxtrace.trc.c69bc2xn01.cpu0 /tmp/mmfs/trcfile.2018-03-12_10.16.11.2982.deadlock.c69bc2xn01.cpu0</font></b><br><b><font size="2" face="Courier-Bold">mmtrace: formatting /tmp/mmfs/trcfile.2018-03-12_10.16.11.2982.deadlock.c69bc2xn01 to /tmp/mmfs/trcrpt.2018-03-12_10.16.11.2982.deadlock.c69bc2xn01.gz</font></b><br><br><font size="2">> </font><tt><font size="2">What's odd is there are no log events to indicate an overload occurred.</font></tt><br><br><font size="2">Overload msg is only seen in mmfs.log when debugDataControl is "heavy". mmdiag --deadlock shows overload related info starting from 4.2.3.</font><br><br><b><font size="2" face="Courier-Bold"># mmdiag --deadlock</font></b><br><br><b><font size="2" face="Courier-Bold">=== mmdiag: deadlock ===</font></b><br><br><b><font size="2" face="Courier-Bold">Effective deadlock detection threshold on c69bc2xn01 is 1800 seconds</font></b><br><b><font size="2" face="Courier-Bold">Effective deadlock detection threshold on c69bc2xn01 is 360 seconds for short waiters</font></b><br><br><b><font size="2" face="Courier-Bold">Cluster c69bc2xn01.gpfs.net is overloaded. The overload index on c69bc2xn01 is 0.01812 <==</font></b><BR>
</body></html>