By default, this setting appears in Couchbase Web Console and is disabled; when it is enabled Couchbase Server is able to flush all the data in a bucket. Be also aware that this operation will be deprecated as a way to enable data bucket flushes. This is because cbepctl is designed for individual node configuration not operating on data buckets shared by multiple nodes.
The preferred way to enable data bucket flush is either 1) Couchbase Web Console or via 2) couchbase-cli. For more information about these two options, see Section 6.3.1, “Creating and Editing Data Buckets” and Section 7.4.1, “Flushing Buckets with couchbase-cli”.
Flushing a bucket is data destructive. If you use
cbepctl, it makes no attempt
to confirm or double check the request. Client applications
using this are advised to double check with the end user
before sending such a request. You can control and limit the
ability to flush individual buckets by setting the
flushEnabled parameter on a bucket in
Couchbase Web Console or via cbepctl
flush_param.
Be aware that this tool is a per-node, per-bucket operation. That means that if you want to perform this operation, you must specify the IP address of a node in the cluster and a named bucket. If you do not provided a named bucket, the server will apply the setting to any default bucket that exists at the specified node. If you want to perform this operation for an entire cluster, you will need to perform the command for every node/bucket combination that exists for that cluster.
To enable flushing a data bucket:
shell> ./cbepctl hostname:port -b bucket_name -p bucket_password set flush_param flushall_enabled trueTo disable flushing a data bucket:
shell> ./cbepctl hostname:port -b bucket_name -p bucket_password set flush_param flushall_enabled falseYou can initiate the flush via the REST-API. For information about changing this setting in the Web Console, see Section 6.3, “Viewing Data Buckets”. For information about flushing data buckets via REST, see Section 8.6.12, “Flushing a Bucket”.