Instances
Last updated
Last updated
The database service deplpoyed on the Tessell portal can be Single-node or Multi-AZ and per node it is assigned an instance.
For Single-node database service it has one instance.
For Multi-AZ database service it has multiple instances. One instance is primary and others are replica which provides high availability or disaster recovery.
The Instances tab
provides the list of all the configured instances for your database service in the tabular format. Each row provides the details of each instance configured per node. Each column of the table providing the information are:
Name - This field provides the name of the instances assigned for your database service. The name of instances are generated automatically in the incremental order like <name_of_db_service>-default-node-0
for primary , <name_of_db_service>-default-node-1
for replica 1, <name_of_db_service>-default-node-2
for replica 2, and so on as per the number of nodes configured for your database service.
Status - This field provides the status of each instance. The status of the instances can be:
Status | Description | Actions allowed |
---|---|---|
Role - This field provides the role of your instance. The possible values are Primary
, HA Replica (Automatic Failover)
, HA Replica (Read replica)
, and DR (Disaster Recovery)
.
Server - This field provides the name of server app where your instance is residing.
Region/AZ - This field provides the name of the cloud and its region on which your instance is hosted. For all the possible values see supported clouds and regions.
Parameter Profile - This field provides the name of the parameter profile selected for your instance at the time of provisioning your database service.
Compute - This field provides the name of the compute shape selected for your instance at the time of provisioning your database service. To view the compute, vCPUS, and memory allocated for this compute shape click on See Details
below the compute shape name. For all the possible values see Compute shapes.
Created - This field provides the date and time on which your instance is created.
Connection Endpoint - This field provides the connection details for your instance. To view the Service URL
, Host
, Port
, and Username
click on the See Details
below the connection endpoint name of your instance.
The Switch over
button on the top right helps to switch any of the available replicas to primary. Selecting Switch over
pops up a Switch over to an instance
window with the options to switch. Also remember, switching over to an instance may cause some downtime for the service. It provides the list of available replica instances along with its name and status. Select the replica instance to promote as primary and optionally you can add the comments. Select the I understand the consequences
checkbox and then click on Switch
button. It submits the switching request and to view the progress, select Submitting Request
below the service name. After the request is submitted, the Switchover Operation
starts to promote the replica to primary. Once completed, the service is again Ready
and the updates the Tessell metadata.
For any database services, you can add new replicas using the Create Replica
button on the top right corner. The possible options for adding the replicas are Disaster Recovery
and Read Only Replica
.
Select Disaster Recovery
or Read Only Replica
to add the new node. The Add DR Instance
or Add RR Instance
window pops up. Provide the details to add the new instance:
Instance Name - Provide the name for the instance.
Region - Select any of the available regions from the drop-down list for your instance.
Availability Zone - Select any of the available availability zones from the drop-down list for your instance.
VPC - Select any of the available VPC from the drop-down list for your instance.
It provides the estimated cost for the new instance to be added at the bottom of the window.
You can view the code
from the bottom of the window and the code is available in different languages like Shell
, Python
, Go
, Java
, JavaScript
, and PowerShell
. You can copy the code using the copy button
on the top right corner and also download the code using the download
button. Use Close
button to return back to the main window.
Select Add Instance
to proceed for adding your Read Replica instance.
To add the Disaster Recovery Replica or Read Replica Instance, automatically it performs this steps:
Request to add the replica is submitted
Create the compute instance(s)
Prepares the primary database to add new replica
Configures the replica database with primary database information
Availability Machine is setup for the new instance
UP
It displays UP
status when the instance is up and running. The connections are allowed once it is in READY
status.
All the actions are allowed: * Resize the compute shapes * Resize the storage * Update the parameter profile * Delete the instance if it is a Read Replica or DR.
DOWN
It displays DOWN
status when the instance is down.
* Delete the instance if it is a Read Replica or DR.
STOPPPED
It displays STOPPED
status when the database service is not running and it is completely stopped.
* Start the service
CREATING
It displays CREATING
status when the database service provision is triggered and the process of creating is on or a new instance is added to the existing database service.
* No actions allowed
DELETING
It displays DELETING
status when the database service delete is triggered and the process of deleting is on or an instance is selected to be deleted from the database service. Only RR/DR instances can be deleted from a database service.
* No actions allowed
REBUILDING
It displays REBUILDING
status when the compute shape or storage resize is triggered for the instance.
* No actions allowed
REBUILD_FAILED
It displays REBUILD_FAILED
status when the compute resize or storage resize was triggered and didn't complete.
* All actions are allowed
PATCHING
It displays PATCHING
status when the available patch is selected to apply for the database service.
* No actions allowed
PATCH_FAILED
It displays PATCH_FAILED
status when the patch application for the database service has failed for some reason.
* All actions are allowed
UPDATING_PARAMETER_PROFILE
It displays UPDATING
status when the parameter profile update is triggered for the instance.
* No actions allowed
PARAMETER_PROFILE_UPDATE_FAILED
It displays PARAMETER_PROFILE_UPDATE_FAILED
status when the parameter profile update fails for some reason.
* All actions are allowed