Skip to main content
Skip table of contents

VDB Configuration Changes for CockroachDB


  • Delphix highly recommends disabling the VDB before making any configuration changes to an existing CockroachDB Target cluster. This precautionary measure is advised due to the following reasons:

    • To ensure a smooth transition when altering the topology of the Cockroach cluster, such as scaling up or down the number of nodes, a graceful shutdown is required.

    • A service restart is necessary after applying any configuration changes to a CockroachDB target cluster.

    • From the Delphix workflow perspective, during the disable operation, cluster services are stopped, and the file system is unmounted. If changes to the configuration are made without disabling, it may lead to unforeseen issues when attempting to bring down the services.


Steps to change the VDB configuration

  1. Login to the Delphix Management application.

  2. Click Manage.

  3. Select Datasets.

  4. Select the VDB for your CockroachDB target cluster.

  5. From the Actions menu (...) select Disable.

While updating a connector, it is not required to disable and re-enable datasets.

  1. Select the VDB and click on Configurations -> Custom section. Click on edit (pencil) button.


  2. Modify the VDB specific parameters you wish to update for your CockroachDB target cluster.

    1. To update additional CRDB Parameters to CockroachDB Target Cluster.


    2. To add additional nodes to existing CockroachDB Target Cluster.

    3. To Remove additional node from existing CockroachDB Target Cluster.


    4. To overwrite additional node CRDB parameter for a specific node.


  3. Apply the configuration changes by clicking the save button at the bottom.

  4. Once the VDB configuration changes are saved. Click the Refresh button and select the Snapshot from which to refresh.


  5. In the Refresh VDB dialog, confirm the Refresh by clicking the submit button.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.