Skip to main content

Committed Database Plans

Overview​

Committed plans are available for all Master Nodes, Slave Nodes and Read Replicas of a Database, allowing flexibility and cost efficiency tailored to your Database needs.

How Committed Plans Work​

  • The committed period for Database depends on the selected plan.
  • Infra credits for the committed plan are deducted in full at the time of launching the plan. (For postpaid customers, the full cost of a committed plan is added to the next bill.)
  • All Master Nodes, Slave Nodes and Read Replicas can be launched under hourly or committed plans.

Once you have launched your Database, you can manage your Database's master nodes, slave nodes and read replica via the My Account Portal dashboard.

Converting Hourly Database Nodes to Committed Plans​

If you've launched Database on an hourly plan, you can convert them into committed plans to save more. Follow these steps:

  1. In the Manage DBaaS Section in actions tab of the DBaaS, click on Convert to Committed Option

    DBaaS Dashboard

  2. In the Convert to Committed window, select the desired committed plan from the dropdown list.

    Committed Plan Dashboard

Once converted, you’ll receive an email notification confirming the successful update.

Note

For the Cassandra and Kafka you can convert their respective individual Coordinators and Brokers Node.

Managing Committed DBaaS Settings​

After launching a DBaaS with a committed plan, you can manage its settings as needed. Follow these steps to access and update committed DBaaS settings:

  1. In the Manage DBaaS Section in actions tab of the DBaaS, click on Committed Settings tab.

    Committed Settings Action

  2. In the settings window, update the renewal or billing preferences.

    Update Preferences

Renewal Options​

Committed DBaaS plans provide the following renewal options:

Auto-Renewal​

The default option for committed DBaaS plans. Once the committed period ends, the plan will auto-renew with the same settings. You can choose a different plan, but the changes will take effect only after the current committed period ends.

Hourly Billing​

If selected, the nodes will switch to hourly billing after the committed period ends, providing flexibility to terminate or modify the cluster without restrictions.

Note

Unlike committed Load Balancer plans, committed DBaaS plans do not support auto-termination after the committed period.

Note

For the Cassandra and Kafka you can choose their respective individual Coordinators and Brokers Node's Committed Settings.