Bug 1585104

Summary: Sharding sends all application sent fsyncs to the main shard file
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: SATHEESARAN <sasundar>
Component: rhhiAssignee: Sahina Bose <sabose>
Status: CLOSED ERRATA QA Contact: SATHEESARAN <sasundar>
Severity: high Docs Contact:
Priority: unspecified    
Version: rhhi-1.1CC: amukherj, bugs, kdhananj, knarra, nbalacha, rcyriac, rhinduja, rhs-bugs, sabose, sankarshan, sasundar, sheggodu, storage-qa-internal
Target Milestone: ---   
Target Release: RHHI-V 1.5   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: glusterfs-3.8.4-54.12 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1583462 Environment:
Last Closed: 2018-11-08 05:39:29 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: 1583462    
Bug Blocks: 1520836    

Description SATHEESARAN 2018-06-01 09:59:06 UTC
+++ This bug was initially created as a clone of Bug #1583462 +++


******* 
This bug is especially relevant in use cases where we want to use RHV-RHGS HC configuration on single brick plain distribute gluster volumes. ********

Description of problem:

While testing the VM use case with sharding (4 MB shards) enabled, we added additional dht logs to track the fops being sent on fds. Post the test, the logs indicate that most fsyncs from the application are being on the main shard file instead of the shards to which the writes were actually sent.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 SATHEESARAN 2018-06-27 02:36:33 UTC
The dependent bug is ON_QA and moving this bug too to ON_QA.
@Sahina, could you provide devel_ack on this bug ?

Comment 5 SATHEESARAN 2018-07-05 13:19:35 UTC
Tested with glusterfs-3.8.4-54.13.el7rhgs with the following steps:

1. Created few VMs with their images on the distribute volume
2. Started all the VMs and installed OS on them.
3. Triggered lot of fsyncs inside the VM
4. Ran I/O inside them for few hours

There were no issues seen.

Comment 7 errata-xmlrpc 2018-11-08 05:39:29 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:3523