Bug 1327366 - glusterd crashed in RHGS-3.1.1 [NEEDINFO]
Summary: glusterd crashed in RHGS-3.1.1
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: glusterd
Version: rhgs-3.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Atin Mukherjee
QA Contact: storage-qa-internal@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-15 00:11 UTC by Raghavendra Bhat
Modified: 2019-11-14 07:47 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-04-19 17:36:42 UTC
Target Upstream Version:
amukherj: needinfo? (rabhat)


Attachments (Terms of Use)

Comment 3 SATHEESARAN 2016-04-15 09:10:19 UTC
glusterd volfile as seen in rhssp4 was :

<snip>
volume management
    type mgmt/glusterd
    option working-directory /var/lib/glusterd
    option transport-type socket,rdma
    option transport.socket.keepalive-time 10
    option transport.socket.keepalive-interval 2
    option transport.socket.read-fail-log off
    option ping-timeout 0
#   option base-port 49152
# 2014-12-19 b.goodfellow added for SMB
    option rpc-auth-allow-insecure on
end-volume
</snip>

The glusterd volfile has no option for event-threads, which means that glusterd will start with the default ( which is 2 ) number of epoll threads.

After upgrading to RHGS 3.1.1, the glusterd volfile should have got updated with this entry "option event-threads 1".

We already know of glusterd issues with multiple epoll threads and that's the reason why glusterd is started with single epoll thread.

Comment 4 Atin Mukherjee 2016-04-15 09:17:58 UTC
A big thank you Satheesaran for identifying this. 

Raghavendra,

Question for the customer here is how did this happen?

1. Did the accidentally remove the event-threads entry from glusterd.vol ?
2. Or there was an upgrade issue where the binaries were successfully upgraded but not the configuration including glusterd.vol? We have seen a similar case in BZ 1305884.

As Satheesaran pointed out, that we have some known issues if multi threaded e-poll is enabled in glusterd.

Considering it, can we close this bug?

Comment 9 Atin Mukherjee 2016-04-19 16:37:36 UTC
Oonkwee, Raghavendra,

There is no point of looking at the core since the set up was incorrectly configured and multi threaded e-poll got enabled by default in glusterd accidentally due to a manual change in glusterd.vol file. I'd request you to close this bug.

~Atin

Comment 10 Oonkwee Lim_ 2016-04-19 17:36:42 UTC
Closing


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