On Fri, May 26, 2017 at 3:14 PM, Krutika Dhananjay <kdhananj@xxxxxxxxxx> wrote:
These features are very very useful. I recommend you to sync-up with Kaushal/Prashant Pai and Aravinda, who are working on glusterd2 to discuss the possibility of these. They already have some plan for such templates where changing these things is part of template, instead of code change.
# gluster volume set <VOL> debug.trace testvol-client-1# gluster volume set <VOL> debug.trace testvol-client-0# gluster volume set <VOL> debug.trace testvol-replicate-0For example, if i have a 2x2 dis-rep volume named testvol and I want to load trace above and below first child of DHT, I execute the following commands:where <xl-name> represents the name of the translator above which you want this translator loaded (as parent).# gluster volume set <VOL> {debug.trace, debug.io-stats, debug.error-gen} <xl-name>I propose the following CLI for achieving the same:There are other translators too under xlators/debug such as error-gen, which are useful for debugging/testing our code.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.Unfortunately, there is no way to load these at specific points in the graph using the volume-set CLI as of today. Our only option is to manually edit the volfile and restart the process and be super-careful not to perform *any* volume-{reset,set,profile} operation and graph switch operations in general that could rewrite the volfile, wiping out all previous edits to it.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-parentWhat 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.
These features are very very useful. I recommend you to sync-up with Kaushal/Prashant Pai and Aravinda, who are working on glusterd2 to discuss the possibility of these. They already have some plan for such templates where changing these things is part of template, instead of code change.
I am not sure how much of the effort it is with current glusterd-volgen.c file, it looked very confusing to me last time I checked. Samikshan you want to comment on how we can achieve this in glusterd right now?
Over all, these features are 'very' important for sure. So, please go ahead and open a github issue for this RFE, so it doesn't end up as just a mail thread.
-Amar
Comments and suggestions welcome.-Krutika
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://lists.gluster.org/mailman/listinfo/gluster-devel
--
Amar Tumballi (amarts)
_______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://lists.gluster.org/mailman/listinfo/gluster-devel
