Bug 1364740

Summary: performance/write-behind should respect window-size & trickling-writes should be configurable
Product: [Community] GlusterFS Reporter: Shreyas Siravara <sshreyas>
Component: write-behindAssignee: Raghavendra Talur <rtalur>
Status: CLOSED EOL QA Contact: storage-qa-internal <storage-qa-internal>
Severity: high Docs Contact:
Priority: medium    
Version: 3.8CC: amukherj, bugs, rhs-bugs, smohan
Target Milestone: ---Keywords: Triaged, ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1426042 1512080 (view as bug list) Environment:
Last Closed: 2017-11-07 10:37:11 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: 1426042, 1512080    
Attachments:
Description Flags
Suggested patch none

Description Shreyas Siravara 2016-08-06 20:47:22 UTC
Created attachment 1188255 [details]
Suggested patch

Description of problem:
- window-size option does not work when it is > 128KB
- trickling-writes is not configurable


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


How reproducible: Always


Steps to Reproduce:
1. Write a 1MB file to a gluster mount and observe write sizes on the bricks.

Actual results: Write sizes are always buffered into 'page-size' (128KB) chunks rather than 'window-size' chunks.

Expected results: We expect the window-size to be respected and the writes buffered accordingly.


Additional info:

Comment 2 Niels de Vos 2016-09-12 05:40:00 UTC
All 3.8.x bugs are now reported against version 3.8 (without .x). For more information, see http://www.gluster.org/pipermail/gluster-devel/2016-September/050859.html

Comment 3 Niels de Vos 2017-11-07 10:37:11 UTC
This bug is getting closed because the 3.8 version is marked End-Of-Life. There will be no further updates to this version. Please open a new bug against a version that still receives bugfixes if you are still facing this issue in a more current release.