Bug 1426042 – performance/write-behind should respect window-size & trickling-writes should be configurable

Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.

Bug 1426042 - performance/write-behind should respect window-size & trickling-writes should be configurable

Summary:	performance/write-behind should respect window-size & trickling-writes should...

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Gluster Storage
Classification:	Red Hat
Component:	write-behind (Show other bugs)
Sub Component:
Version:	3.2
Hardware:	Unspecified Unspecified

Priority	medium Severity high
Target Milestone:	---
Target Release:	RHGS 3.4.0
Assigned To:	Csaba Henk
QA Contact:	Vinayak Papnoi
Docs Contact:

URL:
Whiteboard:
Keywords:	Triaged, ZStream

Depends On:	1364740 1428060 1512080
Blocks:	1503134
	Show dependency tree / graph

Reported:	2017-02-23 00:49 EST by Csaba Henk
Modified:	2018-10-01 05:55 EDT (History)
CC List:	13 users (show)

See Also:
Fixed In Version:	glusterfs-3.12.2-2
Doc Type:	Release Note
Doc Text:	performance.write-behind-trickling-writes and performance.nfs.write-behind-trickling-writes options enables the trickling-write strategy for the write-behind translator for FUSE and NFS clients respectively.
Story Points:	---
Clone Of:	1364740
Clones:	1529432 (view as bug list)
Environment:
Last Closed:	2018-09-04 02:32:03 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHSA-2018:2607	None	None	None	2018-09-04 02:33 EDT

Groups: None (edit)

Comment 3 Atin Mukherjee 2017-11-12 00:09:33 EST

upstream patch : https://review.gluster.org/#/c/18719

Comment 17 errata-xmlrpc 2018-09-04 02:32:03 EDT

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/RHSA-2018:2607

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