[Bugs] [Bug 1284453] Dist-geo-rep: Support geo-replication to work with sharding

bugzilla at redhat.com bugzilla at redhat.com
Fri Nov 27 11:54:55 UTC 2015


https://bugzilla.redhat.com/show_bug.cgi?id=1284453



--- Comment #8 from Vijay Bellur <vbellur at redhat.com> ---
COMMIT: http://review.gluster.org/12729 committed in release-3.7 by Venky
Shankar (vshankar at redhat.com) 
------
commit 8b3061887319d38eb3644e5c4ec5a2b226de6723
Author: Kotresh HR <khiremat at redhat.com>
Date:   Mon Sep 21 14:51:13 2015 +0530

    geo-rep: Fix syncing chown in xsync crawl

    GEO-REP INTEROP WITH SHARD FEATURE

    Problem:
        The sequence of entry creation and chown in master
     is recorded as creation of entry with resulted
     user:group in xsync changelog. During sync, entry
     creation is always split into two ops, MKNOD and
     SETATTR. Hence the issue is not being hit otherwise
     it would have failed with EPERM if parent is owned
     by different user. But with shard translator being
     enabled on slave, doing entry creation with MKNOD and
     SETATTR is not allowed, SETATTR fails as it accesses
     inode structure which is not linked.

    Solution:
        The sequence of entry creation and chown in master
     should be recorded as MKNOD and SETATTR separately always
     and do entry creation with single op in gfid-access
     xlator. The gfid-access patch will be sent separately.

    BUG: 1284453
    Change-Id: Ia577aa5270cb96b86830885d6c4c01fb0133eeed
    Signed-off-by: Kotresh HR <khiremat at redhat.com>
    Reviewed-on: http://review.gluster.org/12205
    Tested-by: NetBSD Build System <jenkins at build.gluster.org>
    Reviewed-by: Aravinda VK <avishwan at redhat.com>
    Reviewed-on: http://review.gluster.org/12729
    Tested-by: Gluster Build System <jenkins at build.gluster.com>
    Reviewed-by: Milind Changire <mchangir at redhat.com>
    Reviewed-by: Venky Shankar <vshankar at redhat.com>

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=ybYVJdvPpS&a=cc_unsubscribe


More information about the Bugs mailing list