<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Mon, May 9, 2016 at 8:45 AM, Raghavendra Gowdappa <span dir="ltr"><<a href="mailto:rgowdapp@redhat.com" target="_blank">rgowdapp@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Poornima/Raghavendra,<br>
<br>
This mail is an initiation of a thread to discuss how to make xlator options setting in gfapi synchronous (so, that caller will know the result) or providing a cbk to let the application know about the status.<br>
<br>
My very naive attempt of code-reading showed me that pub_glfs_set_xlator_option just adds the option to cmd_args.xlator_options. Can you please explain how/when these values are communicated to glusterd to change volfile? From there we can carry forward the conversation.<br>
<br></blockquote><div><br></div><div>Raghavendra,</div><div><br></div><div>glfs_set_xlator_option is equivalent to --xlator-option of mount.glusterfs of FUSE. This feature is not intended to apply the setting to the volume permanently, rather it is specific to the mount and only valid for its lifetime.</div><div>The current architecture of Gluster graph takes these options only in cmd_args and then these values are given preference over whatever comes in volfile from Glusterd. In essence, these settings can be used to override the volume settings for a particular mount.</div><div><br></div><div>If the requirement is to set a volume wide option then glusterd or one of the REST interfaces for Glusterd should be used.</div><div><br></div><div>I will also reply to the other thread with possible methods on overcoming the problem with write-behind and qemu.</div><div><br></div><div>Thanks,</div><div>Raghavendra Talur</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
regards,<br>
Raghavendra<br>
</blockquote></div><br></div></div>