From 076830c068fb39bbc3e863c89a4253cbea36357e Mon Sep 17 00:00:00 2001 From: Vijay Bellur Date: Mon, 9 Apr 2012 23:11:52 +0530 Subject: doc: Move outdated documentation to legacy Change-Id: I0ceba9a993e8b1cdef4ff6a784bfd69c08107d88 BUG: 811311 Signed-off-by: Vijay Bellur Reviewed-on: http://review.gluster.com/3116 Tested-by: Gluster Build System Reviewed-by: Amar Tumballi Reviewed-by: Anand Avati --- doc/examples/legacy/io-cache.vol | 31 +++++++++++++++++++++++++++++++ 1 file changed, 31 insertions(+) create mode 100644 doc/examples/legacy/io-cache.vol (limited to 'doc/examples/legacy/io-cache.vol') diff --git a/doc/examples/legacy/io-cache.vol b/doc/examples/legacy/io-cache.vol new file mode 100644 index 000000000..a71745017 --- /dev/null +++ b/doc/examples/legacy/io-cache.vol @@ -0,0 +1,31 @@ +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 distribute, replicate, or distribute +# over replicate) +# + +### 'IO-Cache' translator is best used on client side when a filesystem has file +# which are not modified frequently but read several times. For example, while +# compiling a kernel, *.h files are read while compiling every *.c file, in +# these case, io-cache translator comes very handy, as it keeps the whole file +# content in the cache, and serves from the cache. +# One can provide the priority of the cache too. + +volume ioc + type performance/io-cache + subvolumes client # In this example it is 'client' you may have to + # change it according to your spec file. + option cache-size 64MB # 32MB is default + option force-revalidate-timeout 5 # 1second is default + option priority *.html:2,*:1 # default is *:0 +end-volume -- cgit