glusterfs.git/xlators/cluster/afr/src/afr-messages.h, branch v3.7.19

afr: propagate child up event after timeout

2016-04-28T04:44:50+00:00

Backport of: http://review.gluster.org/11113

Problem: During mount, afr waits for response from all its children before
notifying the parent xlator. In a 1x2 replica volume , if one of the nodes is
down, the mount will hang for more than a minute until child down is received
from the client xlator for that node.

Fix:
When parent up is received by afr, start a 10 second timer. In the timer call
back, if we receive a successful child up from atleast one brick, propagate the
event to the parent xlator.

Change-Id: I31e57c8802c1a03a4a5d581ee4ab82f3a9c8799d
BUG: 1330855
Signed-off-by: Ravishankar N 
Signed-off-by: Pranith Kumar K 
Reviewed-on: http://review.gluster.org/14088
Smoke: Gluster Build System 
NetBSD-regression: NetBSD Build System 
CentOS-regression: Gluster Build System

afr : Enable auto heal when replica count increases

2016-03-23T11:49:36+00:00

            Backport of: http://review.gluster.org/12454

    This patch is part two change to prevent data loss
    in a replicate volume on doing a add-brick operation.

    Problem: After doing add-brick, there is a chance that
    self heal might happen from the newly added brick rather
    than the source brick, leading to data loss.

    Solution: Mark pending changelogs on afr children for
    the new afr-child so that heal is performed in the
    correct direction.

            >Change-Id: I11871e55eef3593aec874f92214a2d97da229b17
            >BUG: 1276203
            >Signed-off-by: Anuradha Talur 
            >Reviewed-on: http://review.gluster.org/12454
            >Smoke: Gluster Build System 
            >Reviewed-by: Pranith Kumar Karampuri 
            >Tested-by: Pranith Kumar Karampuri 
            >CentOS-regression: Gluster Build System 
            >NetBSD-regression: NetBSD Build System 

Change-Id: Iae6af44f97e612cb3ee8c642254ec3d15ac063f5
BUG: 1320020
Signed-off-by: Anuradha Talur 
Reviewed-on: http://review.gluster.org/13807
Smoke: Gluster Build System 
NetBSD-regression: NetBSD Build System 
CentOS-regression: Gluster Build System 
Reviewed-by: Raghavendra G

Revert "afr: warn if pending xattrs missing during init()"

2016-02-05T07:53:28+00:00

This reverts commit 101243860bca1bbda8a03ab76f6753ecc10799ed.

Change-Id: I042b251250515d703b5bc8bac55e0fc49f2dfc69
BUG: 1293536
Signed-off-by: Pranith Kumar Karampuri 
Reviewed-on: http://review.gluster.org/13338
Smoke: Gluster Build System 
CentOS-regression: Gluster Build System 
NetBSD-regression: NetBSD Build System

afr: warn if pending xattrs missing during init()

2015-12-29T07:26:57+00:00

Backport of http://review.gluster.org/#/c/13038/

Since commit 6e635284a4411b816d4d860a28262c9e6dc4bd6a
(glusterfs-3.7.7), the afr pending xattrs are stored in the volfile and used
by afr when it initializes. If a cluster is upgraded, prevent afr from loading
until the op-version has been bumped up to 3.7.7 and the volfiles have been
regenerated using a volume set command.

Without this fix, AFR will crash when initialzing.

Change-Id: I14249dedb3f2f77cd754d78d8a9a70fdc5fc8c10
BUG: 1293536
Signed-off-by: Ravishankar N 
(cherry picked from commit 4bfbabfdd698e93a1dc1aad5590ed18f10936c55)
Reviewed-on: http://review.gluster.org/13058
Tested-by: Gluster Build System 
Tested-by: NetBSD Build System 
Reviewed-by: Pranith Kumar Karampuri

afr: perform replace-brick in a synctask

2015-09-16T02:27:44+00:00

Backport of http://review.gluster.org/#/c/12169/

Problem:
replace-brick setxattr is not performed inside a synctask. This can lead
to hangs if the setxattr is executed by epoll thread, as the epoll
thread will be waiting for replies to come where as epoll thread is the
thread that needs to epoll_ctl for reading from socket and listen.

Fix:
Move replace-brick to synctask to prevent epoll thread hang.

This patch is in line with the fix performed in
http://review.gluster.org/#/c/12163/

Change-Id: I7284930ead9b0adaa0257f21ec2d893fa5a7146f
BUG: 1262547
Signed-off-by: Ravishankar N 
Reviewed-on: http://review.gluster.org/12172
Tested-by: NetBSD Build System 
Tested-by: Gluster Build System 
Reviewed-by: Pranith Kumar Karampuri

afr : get split-brain-status in a synctask

2015-09-16T02:22:58+00:00

        Backport of: http://review.gluster.org/#/c/12163/

On executing `getfattr -n replica.split-brain-status ` on mount,
there is a possibility that the mount hangs. To avoid this hang,
fetch the split-brain-status of a file in synctask.

 >Change-Id: I87b781419ffc63248f915325b845e3233143d385
 >BUG: 1262345
 >Signed-off-by: Anuradha Talur 

Change-Id: I9f4f4b54e108d3a0017264353b8272e072170c16
BUG: 1262547
Signed-off-by: Anuradha Talur 
Reviewed-on: http://review.gluster.org/12166
Tested-by: NetBSD Build System 
Tested-by: Gluster Build System 
Reviewed-by: Pranith Kumar Karampuri

afr: Porting messages to new logging framework

2015-06-29T06:15:44+00:00

     updated

        Backport of http://review.gluster.org/9897

Cherry picked from 58a736111fa1db4f10c6646e81066434260f674f
>Change-Id: I94ac7b2cb0d43a82cf0eeee21407cff9b575c458
>BUG: 1194640
>Signed-off-by: arao 
>Signed-off-by: Mohamed Ashiq 
>Reviewed-on: http://review.gluster.org/9897
>Tested-by: Gluster Build System 
>Tested-by: NetBSD Build System 
>Reviewed-by: Pranith Kumar Karampuri 

Change-Id: I5fb464da38594579f31661b42a8a3e9d858a797e
BUG: 1217722
Signed-off-by: arao 
Signed-off-by: Mohamed Ashiq 
Reviewed-on: http://review.gluster.org/11351
Tested-by: NetBSD Build System 
Tested-by: Gluster Build System 
Reviewed-by: Anuradha Talur 
Reviewed-by: Pranith Kumar Karampuri

cluster/afr : set pending xattrs for replaced brick

2015-06-27T13:08:54+00:00

       Backport of: http://review.gluster.org/10448/
                  & http://review.gluster.org/11416

This patch is part two change to prevent data loss
in a replicate volume on doing a replace-brick commit
force operation.

Problem: After doing replace-brick commit force, there is a
chance that self heal might happen from the replaced (sink) brick
rather than the source brick leading to data loss.

Solution: Mark pending changelogs on afr children for
the replaced afr-child so that heal is performed in the
correct direction.

Credits to Ravishankar N for patch 11416.

Change-Id: Icb9807e49b4c1c4f1dcab115318d9a58ccf95675
BUG: 1232173
Reviewed-on: http://review.gluster.org/10448
Reviewed-by: Pranith Kumar Karampuri 
Tested-by: NetBSD Build System 
Reviewed-by: Krutika Dhananjay 
Signed-off-by: Anuradha Talur 
Reviewed-on: http://review.gluster.org/11254
Tested-by: Gluster Build System

cluster/afr: Improve inodelk/entrylk failure log messages

2014-07-30T11:36:28+00:00

Change-Id: Ie792875546b4f8e11ebf870a6e63aaf5cb221976
BUG: 1121920
Signed-off-by: Krutika Dhananjay 
Reviewed-on: http://review.gluster.org/8344
Reviewed-by: Ravishankar N 
Tested-by: Gluster Build System 
Reviewed-by: Pranith Kumar Karampuri 
Tested-by: Pranith Kumar Karampuri

cluster/afr: change message description in afr-messages.h

2014-06-24T08:31:57+00:00

Changed the description of AFR_MSG_SUBVOL_UP to make it more meaningful.

Change-Id: I30fa13c2e9a280a22d48e777d259d04a3b71deef
BUG: 1075611
Signed-off-by: Ravishankar N 
Reviewed-on: http://review.gluster.org/8149
Reviewed-by: Krutika Dhananjay 
Tested-by: Gluster Build System 
Reviewed-by: Pranith Kumar Karampuri 
Tested-by: Pranith Kumar Karampuri