[3.0] a03088c the basics on persistent storage. Explained the semantics quickly so people understand why not all objects survive a crash
Tollef Fog Heen
tfheen at varnish-cache.org
Wed Aug 17 11:28:57 CEST 2011
commit a03088c86bec3416287652622bfd0659433a5385
Author: Per Buer <perbu at varnish-software.com>
Date: Mon Aug 15 14:52:43 2011 +0200
the basics on persistent storage.
Explained the semantics quickly so people understand why not all objects survive a crash
diff --git a/doc/sphinx/reference/varnishd.rst b/doc/sphinx/reference/varnishd.rst
index 1e00d0c..df6b87f 100644
--- a/doc/sphinx/reference/varnishd.rst
+++ b/doc/sphinx/reference/varnishd.rst
@@ -207,8 +207,32 @@ file[,path[,size[,granularity]]]
The default size is the VM page size. The size should be reduced if you have many small objects.
-persistence[XXX]
- New, shiny, better.
+persistent,path,size {experimental}
+
+ Persistent storage. Varnish will store objects in a file in a
+ manner that will secure the survival of *most* of the objects in
+ the event of a planned or unplanned shutdown of Varnish.
+
+ The path parameter specifies the path to the backing file. If
+ the file doesn't exist Varnish will create it.
+
+ The size parameter specifies the size of the backing file. The
+ size is assumed to be in bytes, unless followed by one of the
+ following suffixes:
+
+ K, k The size is expressed in kibibytes.
+
+ M, m The size is expressed in mebibytes.
+
+ G, g The size is expressed in gibibytes.
+
+ T, t The size is expressed in tebibytes.
+
+ Varnish will split the file into logical *silos* and write to
+ the silos in the manner of a circular buffer. Only one silo will
+ be kept open at any given point in time. Full silos are
+ *sealed*. When Varnish starts after a shutdown it will discard
+ the content of any silo that isn't sealed.
Transient Storage
-----------------
More information about the varnish-commit
mailing list