Bug 762565 (GLUSTER-833) - WB: rename enable-trickling-writes to aggregate
Summary: WB: rename enable-trickling-writes to aggregate
Keywords:
Status: CLOSED WONTFIX
Alias: GLUSTER-833
Product: GlusterFS
Classification: Community
Component: read-ahead
Version: mainline
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Raghavendra G
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-04-20 03:11 UTC by Krishna Srinivas
Modified: 2011-11-25 09:36 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Regression: RTNR
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:

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

Description Raghavendra G 2010-04-20 01:31:03 UTC 
"enable-trickling-writes on" is not exactly equal to "aggregate off", since there can be aggregation of writes from application from the time last sync was done till a reply for this sync is received. 

The main intention of having enable-trickling-writes was to write the data to network whenever write-behind perceives the network to be free. Aggregation is the side-effect of this intention. Hence a different name was chosen for that option.
Comment 1 Krishna Srinivas 2010-04-20 03:11:54 UTC 
in write-behind rename option enable-trickling-writes to aggregate.
"enable-trickling-writes on" should be "aggregate off"
"enable-trickling-writes off" should be "aggregate on"

enable-tricking-writes is related to aggregation of write chunks right?

AB's suggestion, which is valid.
Comment 2 Amar Tumballi 2010-04-20 08:38:51 UTC 
can we think of better name than 'aggregate' ?
Note You need to log in before you can comment on or make changes to this bug.