Bug 1405002 - [Perf] : pcs cluster resources went into stopped state during Multithreaded perf tests on RHGS layered over RHEL 6
Summary: [Perf] : pcs cluster resources went into stopped state during Multithreaded p...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: common-ha
Version: 3.9
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Kaleb KEITHLEY
QA Contact:
URL:
Whiteboard:
Depends On: 1403587 1404410
Blocks: 1405004
TreeView+ depends on / blocked
 
Reported: 2016-12-15 11:12 UTC by Kaleb KEITHLEY
Modified: 2017-03-08 10:22 UTC (History)
14 users (show)

Fixed In Version: glusterfs-3.9.1
Clone Of: 1404410
: 1405004 (view as bug list)
Environment:
Last Closed: 2017-01-24 11:45:09 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Comment 1 Worker Ant 2016-12-15 11:20:10 UTC
REVIEW: http://review.gluster.org/16139 (common-ha: explicitly set udpu transport for corosync) posted (#1) for review on release-3.9 by Kaleb KEITHLEY (kkeithle)

Comment 2 Worker Ant 2016-12-15 15:54:27 UTC
COMMIT: http://review.gluster.org/16139 committed in release-3.9 by Kaleb KEITHLEY (kkeithle) 
------
commit fb937945ab344e7ba63fb04aaa9a0c71ce80f261
Author: Kaleb S. KEITHLEY <kkeithle>
Date:   Thu Dec 15 06:16:49 2016 -0500

    common-ha: explicitly set udpu transport for corosync
    
    On RHEL7 corosync uses udpu (udp unicast) by default. On RHEL6 the
    default is (now) udp multi-cast. In network environments that don't
    support udp multi-cast this causes the ever growing lists of
    [TOTEM ] Retransmit errors.
    
    Always specifying --transport udpu is thus a no-op on RHEL7.
    
    Using the same transport on both RHEL6 and RHEL7 may (or may not
    give similar behavior and performance--it's hard to say.
    
    It remains a mystery why things have always worked on RHEL6 prior to
    now. Further investigation is required to uncover why this is the
    case.
    
    main http://review.gluster.org/16122
    main BZ 1404410
    
    Change-Id: I4d0de97fe4425c47f249beaaf51aeca3e91731fa
    BUG: 1405002
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle>
    Reviewed-on: http://review.gluster.org/16139
    Smoke: Gluster Build System <jenkins.org>
    Reviewed-by: soumya k <skoduri>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.org>

Comment 3 Kaushal 2017-03-08 10:22:32 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.9.1, please open a new bug report.

glusterfs-3.9.1 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-January/029725.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.