Please use the form below to provide your feedback. Because your feedback is valuable to us, the information you submit in this form is recorded in our issue tracking system (JIRA), which is publicly available. You can track the status of your feedback using the ticket number displayed in the dialog once you submit the form.

Modify a Database

      +
      Review, modify, and rename Couchbase Capella databases.

      Use the procedures on this page to modify an existing Couchbase Capella database. If you want to learn about scaling a database, see Database Scaling.

      Change Options

      You can change the following options in a deployed Couchbase Capella database:

      Option Actions Considerations

      Database Name

      Rename a database

      You can rename a database at any time.

      Plan

      Modify a Database’s Service Plan

      Modify a Database’s Support Time Zone

      You may be unable to downgrade a service plan if your database uses features specific to its current plan.

      Database Recovery Authorization

      Request Prompt Action for Database Recovery

      Use the Request prompt action for database recovery feature from the Settings tab of a deployed database. This database recovery authorization allows the Capella Support Team to take any necessary, time-sensitive remedial actions to recover a failed or failing database or App Service as soon as possible.

      Couchbase Services

      Add a Service

      Remove a Service

      A service can only be added once to a database. The Data Service can’t be removed.

      Nodes

      Add or remove nodes

      The Data Service requires at least three nodes. All other services require at least two nodes.

      Compute

      Change compute

      Compute options depend on the chosen cloud provider.

      Disk Type

      Change disk type

      AWS: The options are GP3 or IO2. GP3 is general-purpose to balance price and performance where you can provision performance independent of storage capacity. IO2 is higher performance and more durable with better reliability.

      GCP: PD-SSD is the only disk type and can’t be changed.

      Azure: Capella databases using Microsoft Azure can choose between Premium SSD or Ultra disks.

      Storage

      Storage Auto-Expansion

      Increase storage

      AWS: Storage Auto-Expansion is always on, and you cannot turn it off.

      In-place Storage Auto-Expansion can only occur once every 6 hours. Refer to the AWS limitations documentation to learn more about storage scaling limitations.

      Once you add storage to a database, it cannot decrease automatically . You can decrease storage only by replacing and rebalancing nodes. Replacing and rebalancing nodes can result in data movement and a slower process, depending on the size of your data and available computing resources.

      GCP: Storage auto-expansion is always on, and you cannot turn it off.

      Azure: All Azure databases have auto-expansion turned off by default.

      Auto-expansion for Azure requires replacing and rebalancing nodes, which results in data movement. Depending on the amount of your data and available computing, this may affect performance until the auto-scaling process is complete.

      To increase storage manually, you need to choose a new disk type.

      IOPS

      Change IOPS

      Adjusting the IOPS rate affects performance and cost. When creating or modifying a database with AWS gp3, AWS io2, or Azure Ultra Disk and choosing a storage option, Capella uses recommended defaults for the IOPS field. You can replace the default IOPS value with one higher than the default but not lower. For the recommended IOPS values for databases using AWS gp3, AWS io2, or Azure Ultra Disk, see IOPS Defaults.

      AWS: The available IOPS range depends on the disk type.

      GCP: IOPS isn’t a directly configurable value. It’s set based on the amount of storage you’ve assigned to a service group: 30 read and 30 write IOPS per GB.

      Azure: IOPS for the Premium SSD (P) disk type are based on the chosen Premium SSD disk size. The IOPS for the Ultra disk type can be set, but the possible range depends on the chosen storage size.

      Prerequisites

      Permissions Required
      To make any database change, you need the Project Owner or Project Manager role for the project with the cluster you’re modifying.

      View Database Node Configurations

      Before modifying a database, you can review a list of all individual nodes running on it. This list includes the hostname, status, and services associated with each node. It also describes each node’s CPU, RAM, and disk usage. Node statuses are Normal, Deploying, and Unhealthy.

      1. Open the Settings page for your database:

        1. With the Projects tab in your organization open, click the project with the database you’re working with.

        2. With the Databases tab open, select your database.

        3. Click the Settings tab.

      2. In the navigation pane, click Nodes:

        Database nodes page

        To modify service configurations, see Modify the Database Configuration.

      Modify the Database Configuration

      Database configuration options depend on the chosen cloud provider. For more information about the configuration options available for each cloud provider, see Amazon Web Services (AWS) and Google Cloud Platform (GCP).

      Add a Service

      You can enable Couchbase Capella’s Storage Auto-Expansion feature to automatically increase your storage capacity as your data grows.

      Service groups allow you to create node configurations for specified Couchbase services.

      1. Open the Settings page for your database:

        1. With the Projects tab in your organization open, click the project with the database you’re working with.

        2. With the Databases tab open, select your database.

        3. Click the Settings tab.

      2. In the navigation pane, click Services.

      3. Use the Services list to select the services you want to add:

        Adding services to database

        You can also add another service group by clicking Add Service Group.

        Once you add a service to a new or existing service group, you may need to adjust its hardware configuration. For more information about sizing a database, see Sizing a Cluster.

      4. If you have no other changes, review and apply the new configuration.

      Limitations
      You can’t add a service when that service already exists on the database.

      Remove a Service

      1. Open the Settings page for your database:

        1. With the Projects tab in your organization open, click the project with the database you’re working with.

        2. With the Databases tab open, select your database.

        3. Click the Settings tab.

      2. In the navigation pane, click Services.

      3. To remove a service, click the x icon for the service you’re removing in the Services list:

        Deleting a database service

      4. If you have no other changes, review and apply the new configuration.

      Limitations
      You can’t remove the Data Service.

      Add or Remove Nodes

      1. Open the Settings page for your database:

        1. With the Projects tab in your organization open, click the project with the database you’re working with.

        2. With the Databases tab open, select your database.

        3. Click the Settings tab.

      2. In the navigation pane, click Services.

      3. Using the Nodes list in the service group you’re modifying, choose a new number of nodes for this configuration.

      4. If you have no other changes, review and apply the new configuration.

      Limitations
      Services require a minimum of two nodes, except for the Data Service, which needs three. A database can have up to 27 nodes.

      Change Compute

      1. Open the Settings page for your database:

        1. With the Projects tab in your organization open, click the project with the database you’re working with.

        2. With the Databases tab open, select your database.

        3. Click the Settings tab.

      2. In the navigation pane, click Services.

      3. Use the Compute drop-down in the service group you’re modifying to choose a new compute instance type.

        The compute dictates the number of vCPUs and memory provisioned for each node in a service group.

      4. If you have no other changes, review and apply the new configuration.

      Change Disk Type

      1. Open the Settings page for your database:

        1. With the Projects tab in your organization open, click the project with the database you’re working with.

        2. With the Databases tab open, select your database.

        3. Click the Settings tab.

      2. In the navigation pane, click Services.

      3. Use the Disk Type control to change disk types for the configuration you’re modifying.

      4. If you have no other changes, review and apply the new configuration.

      Limitations

      • GCP: Only supports PD-SSD.

      Increase Storage

      1. Open the Settings page for your database:

        1. With the Projects tab in your organization open, click the project with the database you’re working with.

        2. With the Databases tab open, select your database.

        3. Click the Settings tab.

      2. In the navigation pane, click Services.

      3. Using the Storage box of the service group you’re modifying, enter the amount of storage you want per node for this configuration. If the database uses Azure, you must choose a new disk type to increase storage.

      4. If you have no other changes, review and apply the new configuration.

      Limitations

      Storage can’t be removed from a service configuration once added.

      • Azure: You can only increase storage by choosing a new disk type.

      Change IOPS

      Adjusting the IOPS rate affects performance and cost. When creating or modifying a database with AWS gp3, AWS io2, or Azure Ultra Disk and choosing a storage option, Capella uses recommended defaults for the IOPS field. You can replace the default IOPS value with one higher than the default but not lower. For the recommended IOPS values for databases using AWS gp3, AWS io2, or Azure Ultra Disk, see IOPS Defaults.

      1. Open the Settings page for your database:

        1. With the Projects tab in your organization open, click the project with the database you’re working with.

        2. With the Databases tab open, select your database.

        3. Click the Settings tab.

      2. In the navigation pane, click Services.

      3. Using the IOPS box, enter the IOPS value for the service group you’re modifying.

        This field isn’t shown when a database uses GCP as its cloud provider. If you’re using Azure’s Premium SSD disk type, you can’t change the value of this field.

      4. If you have no other changes, review and apply the new configuration.

      Limitations

      • GCP: IOPS (Input/Output Operations per Second) isn’t a directly configurable value. Instead, it’s automatically set at 30 reads and 30 writes IOPS per GB of storage provisioned.

      • Azure: IOPS for the Premium SSD (P) disk type are based on the chosen Premium SSD disk size. The IOPS for the Ultra disk type can be set, but the possible range depends on the chosen storage size.

      Review and Apply Changes

      1. Review and update configuration

        All the changes you make to a database are on the Service page. Review this new configuration to ensure it meets your requirements.

        Any warnings about your proposed changes appear on the Service page and can prevent you from updating the configuration until you resolve them. If you need to discard your changes, click Cancel.

      2. Once you have reviewed the changes, click Save.

      The database rebalances and redistributes service data over the new superset of nodes. The amount of time taken for the new nodes to rebalance into the database depends on the service of the new nodes, and how much data is redistributed. The database remains available during the rebalance, but you can’t make further changes until the rebalancing is complete.

      Rename a Database

      1. Open the Settings page for your database:

        1. With the Projects tab in your organization open, click the project with the database you’re working with.

        2. With the Databases tab open, select your database.

        3. Click the Settings tab.

      2. In the Database Name field, enter a new name for the database.

      3. Click Save.

      See Also