Hi,
debug/io-stats and debug/trace are immensely useful for isolating translators that are performance bottlenecks and those that are causing iatt inconsistencies, respectively.The trick is to load these above and below one or more suspect translators, run the test and analyse the output they dump and debug your problem.
The corresponding debug/trace translators will be named testvol-replicate-0-trace-parent, testvol-client-0-trace-parent, testvol-client-1-trace-parent and so on.
To revert the change, the user simply uses volume-reset CLI:
# gluster volume reset <VOL> testvol-replicate-0-trace-parent
# gluster volume reset <VOL> testvol-client-0-trace-parent
# gluster volume reset <VOL> testvol-client-1-trace-parent
What should happen when the translator with a trace/io-stat/error-gen parent gets disabled?
Well glusterd should be made to take care to remove the trace xl too from the graph.
Comments and suggestions welcome.
-Krutika
_______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://lists.gluster.org/mailman/listinfo/gluster-devel