diff --git src/main/docbkx/ops_mgt.xml src/main/docbkx/ops_mgt.xml
index 29f244f..2d67b9d 100644
--- src/main/docbkx/ops_mgt.xml
+++ src/main/docbkx/ops_mgt.xml
@@ -1917,6 +1917,22 @@ $ for i in `cat conf/regionservers|sort`; do ./bin/graceful_stop.sh --restart --
$ ./bin/hbase shell
hbase> snapshot 'myTable', 'myTableSnapshot-122112'
+
+ Take a Snapshot Without Flushing
+ The default behavior is to perform a flush of data in memory before the snapshot is
+ taken. This means that data in memory is included in the snapshot. In most cases, this is
+ the desired behavior. However, if your set-up can tolerate data in memory being excluded
+ from the snapshot, you can use the option of the
+ snapshot command to disable and flushing while taking the
+ snapshot.
+
+ hbase> snapshot 'mytable', 'snapshot123', {SKIP_FLUSH => true}
+
+ There is no way to determine or predict whether a very recent insert or update will be
+ included in a given snapshot, whether flushing is enabled or disabled. A snapshot is only
+ a representation of a table at a given point in time. There is no way to know whether a
+ given insert or update is in memory or has been flushed.
+