Bug 1595531 - With HA=3, in a 4 node cluster, for all block devices, a fixed set of 3 IPs/Gluster Pods are used as targets, with 1 pod staying unused
Summary: With HA=3, in a 4 node cluster, for all block devices, a fixed set of 3 IPs/G...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: heketi
Version: cns-3.10
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: CNS 3.10
Assignee: John Mulligan
QA Contact: Neha Berry
URL:
Whiteboard:
Depends On:
Blocks: 1568862
TreeView+ depends on / blocked
 
Reported: 2018-06-27 05:05 UTC by Neha Berry
Modified: 2018-12-14 09:43 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Previously, the same set of nodes were selected by Heketi as block volume targets when distributing block volumes across all available nodes. With this fix, Heketi shuffles the list of nodes such that different block volumes are distributed across different nodes.
Clone Of:
Environment:
Last Closed: 2018-09-12 09:23:45 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2018:2686 0 None None None 2018-09-12 09:24:56 UTC

Comment 8 Raghavendra Talur 2018-07-10 02:34:44 UTC
It has been found that heketi is erroneously passing 4 IPs where it should pass 3. That will be fixed in next build.

Also, to fix this bug, a simple patch that pseudo randomly selects n of Host IPs should be doable in this release. Providing acks.

Comment 17 Saravanakumar 2018-07-27 04:58:49 UTC
Build is provided now -  please check - rhgs3/rhgs-volmanager-rhel7:3.3.1-22

Comment 21 Anjana KD 2018-08-30 23:58:47 UTC
Updated doc text in the Doc Text field. Please review for technical accuracy.

Comment 22 Anjana KD 2018-09-07 08:14:47 UTC
Updated doc text in the Doc Text field. Please review for technical accuracy.

Comment 23 John Mulligan 2018-09-07 17:41:35 UTC
Doc Text looks OK

Comment 25 errata-xmlrpc 2018-09-12 09:23:45 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2018:2686


Note You need to log in before you can comment on or make changes to this bug.