How to Upgrade Major Version of ApsaraDB for MongoDB Instances in One Click

This article introduces how to perform a one-click major version upgrade for ApsaraDB for MongoDB instances with minimal downtime and no rollback option.

By Yuanyi

Overview

ApsaraDB for MongoDB provides a streamlined one-click major version upgrade feature that enables users to upgrade database instances to newer major versions with ease. This in-place upgrade process is designed for efficiency while maintaining service availability.

Key Characteristics

1. In-Place Upgrade: Performed directly on your existing instance

2. Minimal Downtime:

Business operations continue normally during upgrade
Only a brief connection flash (<30 seconds) occurs during final switchover

3. Variable Duration:

Typically completes in minutes for databases under 100GB
Larger databases may require proportionally more time

4. Irreversible Operation: Version rollback is not supported after completion

Recommended Upgrade Procedure

Pre-Upgrade Preparation

1. Test Environment Validation:

Perform upgrade in a staging environment first
Verify application compatibility with new MongoDB version
Test all critical operations and queries

2. Production Planning:

Schedule during low-traffic periods despite minimal downtime
Prepare for potential <30s connection interruption
Ensure complete database backups
Notify stakeholders about brief possible connectivity issues

Upgrade Execution

Access ApsaraDB for MongoDB console
Select target instance
Initiate one-click upgrade
Monitor progress:

Expect continuous service availability
Prepare for brief switchover interruption

The following gives an example to show the whole process of the one-click upgrade.

Post-Upgrade Verification

Confirm database connectivity restoration
Validate all application functions
Monitor system performance metrics
Update drivers if required by new version

Technical Considerations

Zero Downtime Architecture: Reads/writes continue during bulk of upgrade process
Switchover Impact: <30 second connection flash during final phase
Size-Dependent Timing:
- Small/medium databases: 2-10 minutes
- Large databases: Time increases with data volume
No Rollback Path: Upgrade commitment is permanent