When creating a new data bucket, or editing an existing one, you will be presented with the bucket configuration screen. From here you can set the memory size, access control and other settings, depending on whether you are editing or creating a new bucket, and the bucket type.
When creating a new bucket, you are presented with the Create Bucket dialog, as shown in the figure below.
Bucket Name
The bucket name. The bucket name can only contain characters in range A-Z, a-z, 0-9 as well as underscore, period, dash and percent symbols.
Bucket Type
Specifies the type of the bucket to be created, either
MemcachedorCouchbase. See Section 1.2.3, “Data Storage” for more information.Access Control
The access control configures the port your clients will use to communicate with the data bucket, and whether the bucket requires a password.
To use the TCP standard port (11211), the first bucket you create can use this port without requiring SASL authentication. For each subsequent bucket, you must specify the password to be used for SASL authentication, and client communication must be made using the binary protocol.
To use a dedicated port, select the dedicate port radio button and enter the port number you want to use. Using a dedicated port supports both the text and binary client protocols, and does not require authentication.
Memory Size
This option specifies the amount of available RAM configured on this server which should be allocated to the bucket being configured. Note that the allocation is the amount of memory that will be allocated for this bucket on each node, not the total size of the bucket across all nodes.
Warning
Changing the size of a memcached bucket will erase all the data in the bucket and recreate it, resulting in loss of all stored data.
Replicas
For Couchbase buckets you can enable replication to support multiple replicas of the default bucket across the servers within the cluster. You can configure up to three replicas. Each replica receives copies of all the key/value pairs that are managed by the bucket. If the host machine for a bucket fails, a replica can be promoted to take its place, providing continuous (high-availability) cluster operations in spite of machine failure.
You can disable replication by setting the number of replica copies to zero (0).
To configure replica indexes (a new copy of the index information is recreated from the replica data on each node), select the Index replicas.
Auto-Compaction
Both data and index information stored on disk can become fragmented. Compaction rebuilds the stored data on index to reduce the fragmentation of the data. For more information on database and view compaction, see Section 5.4, “Database and View Compaction”.
You can opt to override the default auto compaction settings for this individual bucket. Default settings are configured through the Settings menu. For more information on setting the default autocompaction parameters, see Section 6.8.4, “Enabling Auto-Compaction”. If you override the default autocompaction settings, you can configure the same parameters, but the limits will affect only this bucket.
Flush
Enable or disable support for the Flush command, which deletes all the data in an a bucket. The default is for the flush operation to be disabled. To enable the operation for a bucket, click the Enable checkbox.
The buttons at the bottom of the bucket configuration window support the following operations:
Deletes the configured bucket, deleting all the associated stored content.
If Flush is enabled, the button will empty all the data from the configured bucket, leaving the bucket and configuration in place. You will be prompted to confirm the operation before the flush operation takes place.
Note
The button will appear only if Flush support is enabled when the Configure Bucket is opened. If you change the Flush setting, you must click and re-open the Configured Bucket dialog to perform a flush operation.
Cancels any changes to the bucket configuration, and closes the window.
Saves the changes to the bucket configuration.
You can edit a number of settings for an existing Couchbase bucket in Couchbase Web Console:
Access Control, including the standard port/password or custom port settings.
Memory Size can be modified providing you have unallocated space within your Cluster configuration. You can reduce the amount of memory allocated to a bucket if that space is not already in use.
Auto-Compaction settings, including enabling the override of the default auto-compaction settings, and bucket-specific auto-compaction.
Flush support. You can enable or disable support for the Flush command.
The bucket name cannot be modified. To delete the configured bucket entirely, click the button.
For Memcached buckets, you can modify the following settings when editing an existing bucket:
Access Control, including the standard port/password or custom port settings.
Memory Size can be modified providing you have unallocated RAM quota within your Cluster configuration. You can reduce the amount of memory allocated to a bucket if that space is not already in use.
You can delete the bucket entirely by clicking the button.
You can empty a Memcached bucket of all the cached information that it stores by using the button.
Warning
Using the button removes all the objects stored in the Memcached bucket. Using this button on active Memcached buckets may delete important information.