diff options
| author | Ravishankar N <ravishankar@redhat.com> | 2015-11-25 09:49:19 +0530 |
|---|---|---|
| committer | Atin Mukherjee <amukherj@redhat.com> | 2015-12-15 22:17:14 -0800 |
| commit | 6e635284a4411b816d4d860a28262c9e6dc4bd6a (patch) | |
| tree | 26cfc4129b2632ce1aa3891e31ac7031a53c54b4 /tests/bugs/glusterfs/bug-853690.t | |
| parent | 55f4e8a74e89d61c97e79474c4488ba0bf40a3c1 (diff) | |
glusterd/afr: store afr pending xattrs as a volume option
Problem:
When AFR xlator initialises, it uses the name of the client xlators
below it for storing the pending changelogs (xattrs). This can be
problem when some other xlator is loaded in between AFR and the client.
Though that is a trivial 'traverse-graph-till-the-client-and-use-the-name'
fix in AFR's init(), there are other issues like when there's no client
xlator at all when, say, AFR is moved to the server side.
Fix:
The client xlator names are currenly unique and stored as
brickinfo->brick_ids. So persist these ids as comma separated values in
AFR's volume_options and use them as xattr values during init().
Change-Id: Ie761ffeb3373a4c4d85ad05c84a768c4188aa90d
BUG: 1285152
Signed-off-by: Ravishankar N <ravishankar@redhat.com>
Reviewed-on: http://review.gluster.org/12738
Tested-by: NetBSD Build System <jenkins@build.gluster.org>
Tested-by: Gluster Build System <jenkins@build.gluster.com>
Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
Diffstat (limited to 'tests/bugs/glusterfs/bug-853690.t')
| -rwxr-xr-x | tests/bugs/glusterfs/bug-853690.t | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/tests/bugs/glusterfs/bug-853690.t b/tests/bugs/glusterfs/bug-853690.t index 59facfcddb0..7880b64488f 100755 --- a/tests/bugs/glusterfs/bug-853690.t +++ b/tests/bugs/glusterfs/bug-853690.t @@ -53,6 +53,7 @@ end-volume volume test-replicate-0 type cluster/replicate + option afr-pending-xattr test-locks-0,test-locks-1 option background-self-heal-count 0 subvolumes test-locks-0 test-locks-1 end-volume |