[gpfsug-discuss] Potential problems - leaving trace enabled in over-write mode?
Oesterlin, Robert
Robert.Oesterlin at nuance.com
Tue Mar 7 20:32:32 GMT 2017
I’m considering enabling trace on all nodes all the time, doing something like this:
mmtracectl --set --trace=def --trace-recycle=global --tracedev-write-mode=overwrite --tracedev-overwrite-buffer-size=256M
mmtracectl --start
My questions are:
- What is the performance penalty of leaving this on 100% of the time on a node?
- Does anyone have any suggestions on automation on stopping trace when a particular event occurs?
- What other issues, if any?
Bob Oesterlin
Sr Principal Storage Engineer, Nuance
507-269-0413
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20170307/356db002/attachment-0001.htm>
More information about the gpfsug-discuss
mailing list