Updating a kdb cluster database
You can update the databases mounted on a kdb cluster using the console. This feature is only available for HDB clusters types. With this feature, you can update the data in a cluster by selecting a changeset. You can also update the cache by providing database paths. You can't change a database name or add a new database if you created a cluster without one.
You can also choose how you want to update the databases on the cluster by selecting a deployment mode.
To update a kdb cluster database
-
Sign in to the AWS Management Console and open the Amazon FinSpace console at https://console.aws.amazon.com/finspace
. -
Choose Kdb environments.
-
From the list of environments, choose a kdb environment.
-
On the environment details page, choose the Clusters tab.
-
From the list of clusters, choose the one where you want to update the database. The cluster details page opens.
-
On the cluster details page, choose the Details tab.
-
Under Data management and storage section, choose Edit.
Note
This button is not available for RDB and Gateway type clusters.
-
On the edit page, modify the changeset that you want to cache as needed.
-
Choose a deployment mode from one of the following options.
-
Rolling – (Default) To update the database, this option stops the existing q process and starts a new q process with the updated database configuration. The initialization script re-runs when the new q process starts.
-
No restart – This option updates the database but doesn't stop the existing q process. No restart is often quicker than the other deployment modes because it reduces the turnaround time to update the changeset configuration for a kdb database on your cluster. This option doesn't re-run the initialization script.
Note
After the update completes, you must re-load the updated database. However, if you use a historical database (HDB) cluster with a single database in a rolling deployment, FinSpace autoloads the database after an update.
-
-
Choose Save changes. The cluster details page opens and the updated information is displayed once the cluster updates successfully.