Dedicated Instance Upgrade Guide
Overview
CloudBase document database defaults to the shared instance mode, where multiple users or environments share computing resources (CPU, memory, etc.) while maintaining strictly isolated data. Upgrading to a dedicated instance provides dedicated resource guarantees and higher performance for your business.
Why choose dedicated instance?
| Feature | Shared Instance | Dedicated Instance |
|---|---|---|
| Resource Allocation | Multi-user shared computing resources | Dedicated computing resources, exclusive CPU and memory |
| Performance Stability | May be affected by other users' workloads | Stable and predictable performance, free from external interference |
| Resource Limit | Restricted, subject to resource quotas | Higher resource limits, can be expanded as needed |
| Use Cases | Development and testing, small-scale applications | Production environments, core business, high-load applications |
Upgrade Prerequisites
Upgrading to a dedicated instance must meet the following conditions:
- Environment Requirements: Your CloudBase environment must be on the Enterprise Edition plan or higher
Note: If your current environment is not the Enterprise Edition, please upgrade your plan first, then apply for the dedicated instance upgrade.
Upgrade Process
1. Submit an application
- Log in to the Cloud Development Console
- Go to [Document Database] - [Database Settings]
- Click the [Upgrade to Dedicated Instance] button
- Provide the relevant information based on the guidance
2. Solution Confirmation
- Technical Support team will contact you via ticket
- Assess the data volume and migration time
3. Upgrade Planning
- Determine the specific upgrade time window (it is recommended to choose the off-peak business period).
- Specify the precautions and emergency plan during the upgrade process
- Confirm the post-upgrade verification plan
4. Perform the upgrade
Cloud Development Team will perform the following operations at the scheduled time:
- Data Synchronization: Synchronize existing database data to the new dedicated instance
- Data Verification: Ensure data integrity and consistency
- Traffic Switching: Switch business traffic from the shared instance to the dedicated instance
5. Upgrade Verification
- After the upgrade is completed, verify that the business features are functioning normally
- Verify whether the data is complete.
- Check whether the database performance meets expectations
Important Notes
Prepare before upgrade
- Data Backup: It is strongly recommended to back up by performing a full data export before upgrading
- Business Assessment: Assess business peak hours and off-peak hours, and choose an appropriate upgrade time window
- Application Compatibility: Confirm that your application code is compatible with dedicated instances (usually no modification is required)
Impact of the Upgrade Process
-
Data Synchronization Phase:
- Does not affect existing business access, and the old instances continue to serve
- Synchronization time depends on the data size and is usually completed within 1 hour.
-
Traffic Switchover Phase:
- Requires a brief service suspension (approximately 10-20 minutes)
- Downtime duration depends on the data volume and verification speed
- During the switchover, the database cannot be written to, and applications may become temporarily unavailable
Post-Upgrade Impact
- Rollback Feature: After migration is completed, the rollback data on the old cluster will be unavailable. The rollback feature will be restored the next day.
- Monitoring Metrics: Monitoring data will be reset and start counting anew, and historical monitoring data will no longer be visible.
- Performance Change: Performance improvement is usually observed, with reduced response time.
Fault Handling
If you encounter issues during or after the upgrade:
- Contact Technical Support immediately via ticket
- Provide a detailed problem description and error logs
- For critical issues, you can request a rollback to the original shared instance (only feasible for a short period after upgrade)
Frequently Asked Questions
Q: Will data be lost during the upgrade process?
A: No. The upgrade process includes strict data synchronization and verification mechanisms to ensure data integrity. However, we still recommend backing up your data before upgrading.
Q: Will the application code need to be modified after the upgrade?
A: Generally not. Dedicated instances are fully interface-compatible with shared instances, so your application code will require no modifications.
Q: How to determine if an upgrade to a dedicated instance is required?
A: If you encounter the following situations, it is recommended to consider upgrading:
- Unstable response time for database operations
- Significant performance degradation during peak business hours
- Data volume and traffic volume continuing to grow
- High requirements for database performance and availability in the business
Q: Can I downgrade back to a shared instance after the upgrade?
A: Downgrading is generally not recommended. If you have special requirements, please contact our technical support team via a ticket.