diff --git src/main/docbkx/ops_mgt.xml src/main/docbkx/ops_mgt.xml index 4d89b1f..d249766 100644 --- src/main/docbkx/ops_mgt.xml +++ src/main/docbkx/ops_mgt.xml @@ -1769,6 +1769,21 @@ false $ ./bin/hbase shell hbase> snapshot 'myTable', 'myTableSnapshot-122112' + + Take a Snapshot Without Flushing + The default behavior is to require all regions of a table to coordinate in order to + prevent writing to the table, and to perform a flush at the same time. This causes the + table to be unavailable for writes while the snapshot is being taken. In most cases, this + is the desired behavior. However, if your set-up can tolerate the possibility of some data + not being captured by the snapshot, you can use the option of + the snapshot command to disable locking and flushing while taking the + snapshot. + + hbase> snapshot 'mytable', 'snapshot123', 'SKIP_FLUSH' + + Using this option can result in data lost if you try to restore a snapshot which is + missing data that was written while the snapshot was taken. +