diff options
| author | vmallika <vmallika@redhat.com> | 2014-10-28 12:25:43 +0530 |
|---|---|---|
| committer | Kaushal M <kaushal@redhat.com> | 2014-11-12 04:36:11 -0800 |
| commit | 4fa4b7f2c2b57d1055adb76e8258b0db176bc356 (patch) | |
| tree | e4beb4567c57370b8622f19746721e2a0b0f96f1 /doc/admin-guide | |
| parent | 55aa4b185561edd7b3d1ab77a4f29a4facfdd7ff (diff) | |
glusterd/snapshot: Snapshot should be deactivated when it is created
By default snapshot should be deactivated and this should be a
configurable option.
This behaviour can be configured by the command below:
gluster snapshot config activate-on-create <enable|disable>
Change-Id: I1911595c32beed43bb2fca4bf99f0d264b422513
BUG: 1157991
Signed-off-by: vmallika <vmallika@redhat.com>
Reviewed-on: http://review.gluster.org/8985
Tested-by: Gluster Build System <jenkins@build.gluster.com>
Reviewed-by: Avra Sengupta <asengupt@redhat.com>
Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
Reviewed-by: Kaushal M <kaushal@redhat.com>
Diffstat (limited to 'doc/admin-guide')
| -rw-r--r-- | doc/admin-guide/en-US/markdown/admin_managing_snapshots.md | 5 |
1 files changed, 4 insertions, 1 deletions
diff --git a/doc/admin-guide/en-US/markdown/admin_managing_snapshots.md b/doc/admin-guide/en-US/markdown/admin_managing_snapshots.md index 93be39d94d5..820dcb18863 100644 --- a/doc/admin-guide/en-US/markdown/admin_managing_snapshots.md +++ b/doc/admin-guide/en-US/markdown/admin_managing_snapshots.md @@ -150,7 +150,8 @@ the snapshots present in the system are displayed. Syntax: *snapshot config \[volname\] \(\[snap-max-hard-limit <count\>\] \[snap-max-soft-limit <percent>\]\) - | \(\[auto-delete <enable|disable\>\]\)* + | \(\[auto-delete <enable|disable\>\]\) + | \(\[activate-on-create <enable|disable\>\]\)* Details: Displays and sets the snapshot config values. @@ -176,6 +177,8 @@ the user gets a warning with every successful snapshot creation. Upon reaching the hard-limit, further snapshot creations will not be allowed. +activate-on-create is disabled by default. If you enable activate-on-create, +then further snapshot will be activated during the time of snapshot creation. ------------------------------------------------------------------------- **Activating a snapshot** |