<html>
  <head>
    <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <p><br>
    </p>
    <br>
    <div class="moz-cite-prefix">On 03/10/2017 10:47 AM, Tahereh Fattahi
      wrote:<br>
    </div>
    <blockquote
cite="mid:CAHG6sptW+KOTYGD1E4uB2uutZNmTToW4mztGTmZMPix2+Sf0yQ@mail.gmail.com"
      type="cite">
      <div dir="ltr">Thank you very much, it is very helpful.
        <div>I see the client graph also in
          /var/log/glusterfs/mnt-glusterfs.log when mount the file
          system.</div>
      </div>
    </blockquote>
    <br>
    Yes, you are on the right place. Fuse mount process log's the graph
    if the log level is INFO.<br>
    <br>
    <blockquote
cite="mid:CAHG6sptW+KOTYGD1E4uB2uutZNmTToW4mztGTmZMPix2+Sf0yQ@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div>I think there is a tree structure between xlator (I had
          seen something in code like child and parent of each xlator),
          so just some of them are the point of connecting to server. I
          think xlator with type protocol/client is responsible for send
          request and get response from server. </div>
      </div>
    </blockquote>
    <br>
    <blockquote
cite="mid:CAHG6sptW+KOTYGD1E4uB2uutZNmTToW4mztGTmZMPix2+Sf0yQ@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div>am I correct?</div>
      </div>
    </blockquote>
    <br>
    Indeed, you are a quick learner. Translator with type
    protocol/client will be the last node in the graph which connects to
    the protocol/server loaded in server . protocol/server will be the
    starting node in server.<br>
    <br>
    <br>
    Regards<br>
    Rafi KC<br>
    <br>
    <blockquote
cite="mid:CAHG6sptW+KOTYGD1E4uB2uutZNmTToW4mztGTmZMPix2+Sf0yQ@mail.gmail.com"
      type="cite">
      <div class="gmail_extra"><br>
        <div class="gmail_quote">On Thu, Mar 9, 2017 at 8:38 PM,
          Mohammed Rafi K C <span dir="ltr">&lt;<a
              moz-do-not-send="true" href="mailto:rkavunga@redhat.com"
              target="_blank"><a class="moz-txt-link-abbreviated" href="mailto:rkavunga@redhat.com">rkavunga@redhat.com</a></a>&gt;</span> wrote:<br>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">
            <div bgcolor="#FFFFFF" text="#000000">
              <p>GlusterFS has mainly four daemons, ie glusterfs
                (generally client process), glusterfsd (generally brick
                process), glusterd (management daemon) and gluster
                (cli).</p>
              <p>Except cli (cli/src) all of them are basically the same
                binary symlinked to different name. So what makes them
                different is graphs, ie each daemons loads a graph and
                based on the graph it does it's job.</p>
              <p><br>
              </p>
              <p>Nodes of each graph are called xlators. So to figure
                out what are the xlators loaded in client side graph.
                You can see a client graph
                /var/lib/glusterd/vols/&lt;<wbr>volname&gt;/trusted-&lt;volname&gt;.&lt;<wbr>protocol&gt;-fuse.vol</p>
              <p>Once you figured out the xlators in client graph and
                their type, you can go to the source code,
                xlatos/&lt;type&gt;/&lt;name&gt;.</p>
              <p><br>
              </p>
              <p>Please note that, if an xlator loaded on client graph
                it doesn't mean that it will only run in client side.
                The same xlator can also run in server if we load a
                graph with that xlator loaded.</p>
              <p><br>
              </p>
              <p>Let me know if this is not helping you to understand<br>
              </p>
              <p><br>
              </p>
              <p>Regards</p>
              <p>Rafi KC<br>
              </p>
              <p><br>
              </p>
              <p>So glusterd and cli codes are always ran on servers. <br>
              </p>
              <div>
                <div class="h5">
                  <div class="m_-6115639838331500950moz-cite-prefix">On
                    03/09/2017 08:28 PM, Tahereh Fattahi wrote:<br>
                  </div>
                </div>
              </div>
              <blockquote type="cite">
                <div>
                  <div class="h5">
                    <div dir="ltr">Hi
                      <div>Is there any way to understand that some code
                        is running client side or server side (from
                        source code and its directories)?</div>
                      <div>Is it possible for some code to execute both
                        client and server side?</div>
                    </div>
                    <br>
                    <fieldset
                      class="m_-6115639838331500950mimeAttachmentHeader"></fieldset>
                    <br>
                  </div>
                </div>
                <pre>______________________________<wbr>_________________
Gluster-users mailing list
<a moz-do-not-send="true" class="m_-6115639838331500950moz-txt-link-abbreviated" href="mailto:Gluster-users@gluster.org" target="_blank">Gluster-users@gluster.org</a>
<a moz-do-not-send="true" class="m_-6115639838331500950moz-txt-link-freetext" href="http://lists.gluster.org/mailman/listinfo/gluster-users" target="_blank">http://lists.gluster.org/<wbr>mailman/listinfo/gluster-users</a></pre>
    </blockquote>
    

  </div>

</blockquote></div>
</div>



</blockquote>
</body></html>