Bug 1584581

Summary: [GSS][ RPC client ping timeouts on GlusterFS mounts ]
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: nravinas
Component: protocolAssignee: Milind Changire <mchangir>
Status: CLOSED ERRATA QA Contact: Upasana <ubansal>
Severity: high Docs Contact:
Priority: high    
Version: rhgs-3.3CC: abhishku, atumball, bkunal, mchangir, mruzicka, nchilaka, nravinas, rgowdapp, rhs-bugs, rkavunga, sanandpa, sankarshan, sheggodu, smali, storage-qa-internal
Target Milestone: ---Keywords: ZStream
Target Release: RHGS 3.4.z Batch Update 4   
Hardware: Unspecified   
OS: Linux   
Whiteboard: rpc-ping-timeout
Fixed In Version: glusterfs-3.12.2-41 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-03-27 03:43:39 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:
Bug Depends On:    
Bug Blocks: 1649191, 1657798    

Comment 40 Upasana 2019-02-14 08:06:31 UTC
Hi Milind,

As per the bug i see that RPC client ping timeouts were observed on fuse mounts, while running heavy workload. 
To verify the bug -
1.Is there a specific workload we should be running ?
2.Is workload for a long duration on a FUSE mount suffice to verify the bug ?

Comment 41 Milind Changire 2019-02-14 09:32:42 UTC
(In reply to Upasana from comment #40)
> Hi Milind,
> 
> As per the bug i see that RPC client ping timeouts were observed on fuse
> mounts, while running heavy workload. 
> To verify the bug -
> 1.Is there a specific workload we should be running ?
> 2.Is workload for a long duration on a FUSE mount suffice to verify the bug ?

You could create copies of a multi-gigabyte file from multiple clients so that the load is sustained for at least 10 minutes. That should stress the system enough. Also remember to check the vm sysctl tunables:
- dirty_background_bytes
- dirty_background_ratio
before you start the IO to get the expectation correct. If possible, reduce the dirty_background_ratio to minimal, eg 1%

Comment 44 errata-xmlrpc 2019-03-27 03:43:39 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/RHBA-2019:0658