NoSQL Databases
Last updated
Last updated
The NoSQL Database available with Tessell is MongoDB. The NOSQL Databases tab provides the list of all the database services owned by you by default. You can filter the list as per the clouds, owner and subscriptions.
The fields in the above image are:
Search — In the search bar, you can provide the name of the database service to search and list its details.
Total Services N — It provides the total number of the listed database services where N is the number of the database services listed. Next to Total Services, it displays:
a green triangle symbol along with the number of running services
an orange square symbol along with the number of stopped services
a grey play button symbol with the number of starting services
a red cylinder with an exclamation symbol along with the number of failed services
Cloud — You can select the cloud from the drop-down list. By default, it lists all the cloud regions. The possible values are All, AWS, and Azure.
Owner — You can select the specific username from the drop-down list to view the details of the database services owned by the user. By default, it lists all the owners in the specific subscription. The possible values are All, and any username in the subscription list.
Subscription — You can select the specific subscription from the drop-down list available to you. By default, it lists all the subscriptions added to your account if you are the owner of the account. The possible values are All, and any number of subscriptions added to your account or accessible to you depending on your role.
The fields in the table provide an overview of the services you created:
Service Name — This field lists the name of the database service given by you at the time of provisioning your database. It also displays the database engine icon you have chosen for your database service. If you select the service name, it takes you to the home page of that database service
Status — This field provides the current status of your database service. Also, it has a specific number of dots following the status. One dot indicates it is a single-node database service having only one instance. Two dots indicate it is a two-node database service with two instances, that is one primary and one replica. Three dots indicate it is a three-node database service with three instances, that is one primary and two replicas and so on. The status of your database service can be:
READY
It displays READY status when the database service is created and it is up and running. The connections are allowed once it is in ready status.
All the actions are allowed: * Stop the service * Edit the service * Restore the service * Reset the password * Modify the VM access, public accessibility, allowed IP addresses, AWS private link, and Tags * Switch over for High-Availability * Add read replicas * Add new databases * Delete the existing databases * Set or modify the Start/Stop schedules * Set or modify the Delete schedules * Share the service with users * Snapshots
STARTING
It displays STARTING status when the database service is in the process to start. The connections are not allowed while the service is starting.
* No actions allowed
STOPPING
It displays STOPPING status when the database service stop is triggered and the process of stopping is on. It stops all the connections and then the database service.
* No actions allowed
STOPPPED
It displays STOPPED status when the database service is not running.
* Start the service
DOWN
It displays DOWN status when the primary instance in the High Availability service is down.
* Start the instance
DELETING
It displays DELETING status when the database service delete is triggered and the process of deleting is on.
* No actions allowed
CREATING
It displays CREATING status when the database service provision is triggered and the process of creating is on.
* No actions allowed
FAILED
It displays FAILED status when the database service provision or the restore operation fails.
* Clean up the database service entry using the remove button
SWITCHOVER
It displays SWITCHOVER status when the replica in the High Availability service is promoted as the primary instance.
* No actions allowed
DEGRADED
It displays DEGRADED status when one of the replica instance in the High Availability service is down.
* Delete the service * Edit the service * Restore the service * Reset the password * Modify the VM access, public accessibility, allowed IP addresses, AWS private link, and Tags * Switch over for High-Availability * Add read replicas * Add new databases * Delete the existing databases * Set or modify Start/Stop schedules * Set or modify the Delete schedules * Share the service with users * Snapshots
READY (Sub status is BACKING_UP)
It displays READY status but the snapshot is running.
READY (Sub status is STOP_FAILED )
It displays READY status but the database service stop failed.
* All actions are allowed
READY (Sub status is SWITCH_OVER_FAILED)
It displays READY status but the switch over operation for a High Availabitiy database service failed.
* All actions are allowed
STOPPED (Sub status is START_FAILED)
It displays STOPPED status but the database service start failed.
* Start the service
Subscription — This field provides the subscription you choose at the time of provisioning your database. It also displays the chosen cloud region icon. You can define and add the subscription as per your requirement using the Subscriptions app under Governance.
Compute — This field provides the compute shape you choose for your database service at the time of provisioning. The different compute shapes are available with Tessell based on your cloud and workload type. For more information, see compute shapes.
Cloud and Region — This field provides the cloud and region name you choose to host your database service at the time of provisioning. For more information, see cloud and regions.
Created On — This field provides the date and time on which your database service is created.
Created By — This field provides the email ID used to log in to the Tessell portal and create the database service.
In the right corner, next to the Created By field hover over the ellipsis icon. It provides options to Stop, Edit, or Delete the services.
Select Stop, to stop the database services. On selecting the Stop button, a window pops up reminding you that Stopping the service will disconnect all the sessions. Optionally you can add comments to provide any details regarding your action to stop the database service. Also, there is a check box asking Are you sure you want to continue. Once you select the check box, the Stop button gets enabled. Select the Stop button, to stop the database service. The status of the database service changes to Stopping, the status will be Stopped after the database service is stopped completely.
Once your database service is stopped, you can see the option to Start the database service on the ellipsis icon.
Select Edit, to edit the database service. The Edit service window pops up that allows to:
edit the Name of the database service
description of the database service
toggle the Enable delete protection button. By default it is disabled. When you enable this option, it doesn't allow you to delete the database service. This helps to safeguard against mistaken deletes.
toggle the Enable stop protection button. By default it is disabled. When you enable this option, it doesn't allow you to stop the database service.
toggle the Enable auto minor version `update button. By default, it is enabled. It automatically updates your database service whenever a minor patch is released.
After the required edits, click on Update button to apply the changes.
Select Delete, to delete the database service. The Delete confirmation window pops up with the warning This action cannot be undone Please read carefully. It gives you the option Do you want to retain the Availability Machine?. If you choose Yes, the Availability Machine is retained and only the database service is deleted. If you choose No, the Availability Machine and the database service both are deleted. Also, all the existing snapshots of the database service across all the regions are deleted. Optionally you can add comments to provide any details regarding the action.
