diff options
| author | Vikas Gorur <vikas@zresearch.com> | 2009-02-18 17:36:07 +0530 | 
|---|---|---|
| committer | Vikas Gorur <vikas@zresearch.com> | 2009-02-18 17:36:07 +0530 | 
| commit | 77adf4cd648dce41f89469dd185deec6b6b53a0b (patch) | |
| tree | 02e155a5753b398ee572b45793f889b538efab6b /doc/examples/write-behind.vol | |
| parent | f3b2e6580e5663292ee113c741343c8a43ee133f (diff) | |
Added all files
Diffstat (limited to 'doc/examples/write-behind.vol')
| -rw-r--r-- | doc/examples/write-behind.vol | 26 | 
1 files changed, 26 insertions, 0 deletions
diff --git a/doc/examples/write-behind.vol b/doc/examples/write-behind.vol new file mode 100644 index 000000000..9c6bae11c --- /dev/null +++ b/doc/examples/write-behind.vol @@ -0,0 +1,26 @@ +volume client +  type protocol/client +  option transport-type tcp     # for TCP/IP transport +  option remote-host 192.168.1.10      # IP address of the remote brick +  option remote-subvolume brick        # name of the remote volume +end-volume + +## In normal clustered storage type, any of the cluster translators can come here. +# +# Definition of other clients +#  +# Definition of cluster translator (may be unify, replicate, or unify over replicate) +#  + + +### 'Write-behind' translator is a performance booster for write operation. Best used on client side, as its main intension is to reduce the network latency caused for each write operation. + +volume wb +  type performance/write-behind +  subvolumes client         # In this example it is 'client' you may have to change it according to your spec file. +  option flush-behind on    # default value is 'off' +  option window-size 2MB +  option aggregate-size 1MB # default value is 0 +  option enable_O_SYNC no  # default is no +  option disable-for-first-nbytes 128KB #default is 1  +end-volume  | 
