Bug 1630688 - Low Random write IOPS in VM in RHHI 2.0
Summary: Low Random write IOPS in VM in RHHI 2.0
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: replicate
Version: rhgs-3.4
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: RHGS 3.4.z Batch Update 1
Assignee: Ravishankar N
QA Contact: Vijay Avuthu
Depends On: 1630368 1635972 1635976 1635980
Blocks: 1577822 1596040 1616270
TreeView+ depends on / blocked
Reported: 2018-09-19 06:23 UTC by Pranith Kumar K
Modified: 2018-10-31 08:47 UTC (History)
25 users (show)

Fixed In Version: glusterfs-3.12.2-20
Doc Type: Bug Fix
Doc Text:
Previously, the eager-lock mechanism blocked simultaneous file access even in cases where many reads and only one write was being attempted. This increased wait times for read operations when a write was occurring. The eager-lock mechanism now only blocks simultaneous write operations, instead of affecting write and read operations. With this fix, the algorithm to disable the eager-lock is modified and it disables only when multiple write operations are trying to modify a file at the same time. This led to performance improvement while a write operation is performed on a file irrespective of the number of times it is opened at the same time for read operation.
Clone Of: 1616270
Last Closed: 2018-10-31 08:46:17 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2018:3432 0 None None None 2018-10-31 08:47:53 UTC

Comment 15 SATHEESARAN 2018-10-18 18:35:59 UTC
Adding the RHHI QE validation results.

As part of RHHI functional testing, the changes are good and verified.
Also measured the high-level performance ( without accurate numbers ), the performance has improved a lot now.

Comment 16 Anees Patel 2018-10-22 06:51:00 UTC
As per comment #9 and comment #15, setting this bug to verified state

Comment 18 errata-xmlrpc 2018-10-31 08:46:17 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.


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