Bug 1401801
Summary: | [RFE] Use Host UUID to find local nodes to spawn workers | ||
---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | Aravinda VK <avishwan> |
Component: | geo-replication | Assignee: | Aravinda VK <avishwan> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | mainline | CC: | bugs |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | glusterfs-3.10.0 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2017-03-06 17:37:56 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Aravinda VK
2016-12-06 06:50:36 UTC
REVIEW: http://review.gluster.org/16035 (geo-rep: Use Host UUID to find local Gluster node) posted (#1) for review on master by Aravinda VK (avishwan) COMMIT: http://review.gluster.org/16035 committed in master by Aravinda VK (avishwan) ------ commit 009454de29d6653e07ac090af1c5d233c7150dd4 Author: Aravinda VK <avishwan> Date: Tue Dec 6 12:11:35 2016 +0530 geo-rep: Use Host UUID to find local Gluster node To spawn workers for each local brick, Geo-rep was collecting all the machine IPs based on hostname and finds based on the connectivity. With this patch, Geo-rep finds local brick if host UUID matches with UUID of the brick from Volume info. BUG: 1401801 Change-Id: Ic83c65df89e43cb86346e3ede227aa84d17ffd79 Signed-off-by: Aravinda VK <avishwan> Reviewed-on: http://review.gluster.org/16035 Smoke: Gluster Build System <jenkins.org> NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.org> Reviewed-by: Kotresh HR <khiremat> 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.0, please open a new bug report. glusterfs-3.10.0 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/gluster-users/2017-February/030119.html [2] https://www.gluster.org/pipermail/gluster-users/ |