- Release Notes and Announcements
- User Guide
- Product Introduction
- Purchase Guide
- Getting Started
- Operation Guide
- Access Management
- Instance Management
- Node Management
- Node Overview
- Viewing Node Information
- Adjusting Mongod Node Specification
- Adding Secondary Node
- Deleting Secondary Node
- Adding Read-Only Node
- Adjusting Shard Quantity
- Adjusting Mongos Node Specification
- Adding Mongos Node
- Enabling Mongos Access Address
- Promoting Secondary Node to Primary Node
- Restarting a Node
- Version Upgrade
- Network Configuration
- Monitoring
- Backup and Rollback
- Data Security
- SSL Authentication
- Database Management
- Multi-AZ Deployment
- Disaster Recovery/Read-Only Instances
- Recycle Bin
- Task Management
- Performance Optimization
- Data Migration Guide
- Creating a DTS Migration Task
- Migration Overview
- Supported Capabilities
- User Guide
- Migration Operation Guide
- Fix for Verification Failure
- MongoDB Connection Check
- Database/Table Content Conflict Check
- Source Database Node Role Check
- Oplog Check
- Source/Target Database Account Permission Check
- Database Version Check
- Database Capacity Check
- Target Database Load Check
- ShardKey Check
- Source Database Balancer Check
- Time Series Collection Verification
- Compression Algorithm Verification
- Consistency Check After Migration
- Creating MongoDB Data Subscription
- Creating a DTS Migration Task
- Practical Tutorial
- Optimizing Indexes to Break Through Read/Write Performance Bottlenecks
- Troubleshooting Mongos Load Imbalance in Sharded Cluster
- Considerations for Using Shard Clusters
- Sample of Reading and Writing Data in MongoDB Instance
- Methods for Importing and Exporting Data Based on CVM Connected with MongoDB
- What to Do for Errors of Repeated Instance Creation and Deletion of Databases with the Same Names?
- Troubleshooting MongoDB Connection Failures
- Performance Fine-Tuning
- Ops and Development Guide
- Troubleshooting
- API Documentation
- History
- Introduction
- API Category
- Making API Requests
- Instance APIs
- RenameInstance
- OfflineIsolatedDBInstance
- ModifyDBInstanceSpec
- IsolateDBInstance
- DescribeSpecInfo
- DescribeDBInstances
- DescribeClientConnections
- CreateDBInstanceHour
- AssignProject
- RenewDBInstances
- DescribeSlowLogs
- DescribeSlowLogPatterns
- InquirePriceRenewDBInstances
- InquirePriceModifyDBInstanceSpec
- InquirePriceCreateDBInstances
- DescribeDBInstanceDeal
- DescribeSecurityGroup
- DescribeInstanceParams
- ModifyDBInstanceSecurityGroup
- ModifyDBInstanceNetworkAddress
- Backup APIs
- Account APIs
- Task APIs
- Other APIs
- Data Types
- Error Codes
- Instance Connection
- Product Performance
- FAQs
- Service Agreement
- Glossary
- Contact Us
- Release Notes and Announcements
- User Guide
- Product Introduction
- Purchase Guide
- Getting Started
- Operation Guide
- Access Management
- Instance Management
- Node Management
- Node Overview
- Viewing Node Information
- Adjusting Mongod Node Specification
- Adding Secondary Node
- Deleting Secondary Node
- Adding Read-Only Node
- Adjusting Shard Quantity
- Adjusting Mongos Node Specification
- Adding Mongos Node
- Enabling Mongos Access Address
- Promoting Secondary Node to Primary Node
- Restarting a Node
- Version Upgrade
- Network Configuration
- Monitoring
- Backup and Rollback
- Data Security
- SSL Authentication
- Database Management
- Multi-AZ Deployment
- Disaster Recovery/Read-Only Instances
- Recycle Bin
- Task Management
- Performance Optimization
- Data Migration Guide
- Creating a DTS Migration Task
- Migration Overview
- Supported Capabilities
- User Guide
- Migration Operation Guide
- Fix for Verification Failure
- MongoDB Connection Check
- Database/Table Content Conflict Check
- Source Database Node Role Check
- Oplog Check
- Source/Target Database Account Permission Check
- Database Version Check
- Database Capacity Check
- Target Database Load Check
- ShardKey Check
- Source Database Balancer Check
- Time Series Collection Verification
- Compression Algorithm Verification
- Consistency Check After Migration
- Creating MongoDB Data Subscription
- Creating a DTS Migration Task
- Practical Tutorial
- Optimizing Indexes to Break Through Read/Write Performance Bottlenecks
- Troubleshooting Mongos Load Imbalance in Sharded Cluster
- Considerations for Using Shard Clusters
- Sample of Reading and Writing Data in MongoDB Instance
- Methods for Importing and Exporting Data Based on CVM Connected with MongoDB
- What to Do for Errors of Repeated Instance Creation and Deletion of Databases with the Same Names?
- Troubleshooting MongoDB Connection Failures
- Performance Fine-Tuning
- Ops and Development Guide
- Troubleshooting
- API Documentation
- History
- Introduction
- API Category
- Making API Requests
- Instance APIs
- RenameInstance
- OfflineIsolatedDBInstance
- ModifyDBInstanceSpec
- IsolateDBInstance
- DescribeSpecInfo
- DescribeDBInstances
- DescribeClientConnections
- CreateDBInstanceHour
- AssignProject
- RenewDBInstances
- DescribeSlowLogs
- DescribeSlowLogPatterns
- InquirePriceRenewDBInstances
- InquirePriceModifyDBInstanceSpec
- InquirePriceCreateDBInstances
- DescribeDBInstanceDeal
- DescribeSecurityGroup
- DescribeInstanceParams
- ModifyDBInstanceSecurityGroup
- ModifyDBInstanceNetworkAddress
- Backup APIs
- Account APIs
- Task APIs
- Other APIs
- Data Types
- Error Codes
- Instance Connection
- Product Performance
- FAQs
- Service Agreement
- Glossary
- Contact Us
If you no longer need a TencentDB for MongoDB instance, you can directly terminate and return it in the console.
Overview
You can terminate an instance if you no longer need it. The terminated instance will be put into the recycle bin. For instances in the recycle bin, you can restore or release them as needed based on different scenarios.
Version Description
Currently, TencentDB for MongoDB 3.2, 3.6, 4.0, 4.2, 4.4, 5.0, and 6.0 support instance termination.
Billing Overview
When an instance is returned and its status has changed to Isolated, it will no longer generate fees.
For instances that met the 5-day no-questions-asked refund policy, the payment will be returned to your Tencent Cloud account.
For normal instances, the payment will be returned to your Tencent Cloud account by the proportion of the cash and gift cards paid for the purchase.
After a pay-as-you-go instance is returned, it will be moved to the recycle bin and retained there for three days. During the retention period, the instance cannot be accessed, but it can be restored after top-up.
Note
After an instance is completely terminated, its data will be cleared and cannot be recovered. You need to back up the data in advance.
Note
When an instance is terminated, its read-only instances will not be terminated simultaneously.
After an instance is terminated, it will be moved to the recycle bin. During the retention period, the instance cannot be accessed. To use the instance again, you can restore it from the recycle bin. For detailed directions, see Recycle Bin.
When the instance is terminated, its IP resources will be released simultaneously. The DR instance will be disconnected from the synchronous connection and automatically upgraded to the master instance.
Prerequisites
You have created a TencentDB for MongoDB instance. For more information, see Creating TencentDB for MongoDB Instance.
The TencentDB for MongoDB instance is in Running status.
Directions
Pay-as-you-go instance
1. Log in to the TencentDB for MongoDB console.
2. In the MongoDB drop-down list on the left sidebar, select Replica Set Instance or Sharded Cluster Instance. The directions for replica set instances and sharded cluster instances are similar.
3. Above the Instance List on the right, select the region.
4. In the instance list, find the target instance.
5. In the Operation column of the target instance, select More > Terminate.
6. In the pop-up window, read the prompt message carefully, confirm the instance to be terminated, and click OK.
Recycle Bin
Terminated instances will be put into the recycle bin and can be restored during the retention period. For more information, see Recycle Bin.
Yes
No
Was this page helpful?