Re: gluster source code help

jayakrishnan mm <jayakrishnan.mm@xxxxxxxxx> · Fri, 3 Feb 2017 11:44:43 +0800

On Thu, Feb 2, 2017 at 8:17 PM, Ravishankar N <ravishankar@xxxxxxxxxx> wrote:

    On 02/02/2017 10:46 AM, jayakrishnan mm
      wrote:

        Hi

        How  do I determine, which part of the  code is run on the
          client, and which part of the code is run on the server
          nodes by merely looking at the the glusterfs  source code ?
        I knew  there are client side  and server side translators
          which will run on respective platforms. I am looking at part
          of self heal daemon source  (ec/afr) which will run on the
          server nodes  and  the part which run on the clients.

    The self-heal daemon that runs on the server is also a client
    process in the sense that it has client side xlators like ec or afr
    and  protocol/client (see the shd volfile 'glustershd-server.vol')
    loaded and talks to the bricks like a normal client does.

    The difference is that only self-heal related 'logic' get executed
    on the shd while both self-heal and I/O related logic get executed
    from the mount. The self-heal logic resides mostly in
    afr-self-heal*.[ch] while I/O related logic is there in the other
    files.

    HTH,

    Ravi

Dear  Ravi,Thanks for your kind explanation.
So, each server node will have a separate self-heal daemon(shd) up and running , every time a child_up event occurs, and this will  be an index healer. 
And each daemon  will spawn  "priv->child_count " number of threads on each server node . correct ?
1. When exactly a full healer spawns  threads? 
2. When can GF_EVENT_TRANSLATOR_OP & GF_SHD_OP_HEAL_INDEX happen together (so that index healer spawns thread) ?
    similarly when can GF_EVENT_TRANSLATOR_OP & GF_SHD_OP_HEAL_FULL  happen ? During replace-brick ?
Is it possible that index healer and full healer spawns threads together (so that total number of  threads  is 2*priv->child_count)?

3. In /var/lib/glusterd/glustershd/glustershd-server.vol , why  debug/io-stats  is chosen as the top xlator ?

Thanks
Best regards 

        Best regards
        JK

      _______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://lists.gluster.org/mailman/listinfo/gluster-devel

_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://lists.gluster.org/mailman/listinfo/gluster-devel