Bug 1487647 - with AFR now making both nodes to return UUID for a file will result in georep consuming more resources
Summary: with AFR now making both nodes to return UUID for a file will result in geore...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: disperse
Version: 3.10
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
Assignee: Sunil Kumar Acharya
QA Contact:
URL:
Whiteboard:
Depends On: 1462790
Blocks: 1315781 1462693 1463250 1464078
TreeView+ depends on / blocked
 
Reported: 2017-09-01 13:31 UTC by Sunil Kumar Acharya
Modified: 2017-10-06 17:10 UTC (History)
10 users (show)

Fixed In Version: glusterfs-3.10.6
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1462790
Environment:
Last Closed: 2017-10-06 17:10:52 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)

Comment 1 Worker Ant 2017-09-01 13:37:26 UTC 
REVIEW: https://review.gluster.org/17667 (cluster/ec: Node uuid xattr support update for EC) posted (#4) for review on release-3.10 by Sunil Kumar Acharya (sheggodu)
Comment 2 Worker Ant 2017-09-13 06:41:56 UTC 
COMMIT: https://review.gluster.org/17667 committed in release-3.10 by Raghavendra Talur (rtalur) 
------
commit 439fce6551638328550a7b3eea7d75c627a9b6c8
Author: Sunil Kumar Acharya <sheggodu>
Date:   Wed Jun 21 16:37:09 2017 +0530

    cluster/ec: Node uuid xattr support update for EC
    
    Problem:
    The change in EC to return list of node uuids for
    GF_XATTR_NODE_UUID_KEY was causing problems with
    geo-rep.
    
    Fix:
    This patch will allow to get the single node uuid
    as it was doing before with the key
    "GF_XATTR_NODE_UUID_KEY", and will also allow to get
    the list of node uuids by using a new key
    "GF_XATTR_LIST_NODE_UUIDS_KEY". This will solve
    the problem with geo-rep and any other features which
    were depending on this.
    
    >BUG: 1462790
    >Change-Id: I2d9214a9658d4a41a3d6de08600884d2bda5f3eb
    >Signed-off-by: Sunil Kumar Acharya <sheggodu>
    >Reviewed-on: https://review.gluster.org/17594
    >Smoke: Gluster Build System <jenkins.org>
    >Reviewed-by: Xavier Hernandez <xhernandez>
    >Reviewed-by: Pranith Kumar Karampuri <pkarampu>
    >CentOS-regression: Gluster Build System <jenkins.org>
    >Signed-off-by: Sunil Kumar Acharya <sheggodu>
    
    BUG: 1487647
    Change-Id: I2d9214a9658d4a41a3d6de08600884d2bda5f3eb
    Signed-off-by: Sunil Kumar Acharya <sheggodu>
    Reviewed-on: https://review.gluster.org/17667
    Smoke: Gluster Build System <jenkins.org>
    Reviewed-by: Xavier Hernandez <xhernandez>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.org>
Comment 3 Shyamsundar 2017-10-06 17:10:52 UTC 
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.10.6, please open a new bug report.

glusterfs-3.10.6 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://lists.gluster.org/pipermail/announce/2017-October/000084.html
[2] https://www.gluster.org/pipermail/gluster-users/
Note You need to log in before you can comment on or make changes to this bug.