[Update] Revised Schedule for Alibaba Cloud Network Infrastructure Upgrade In Singapore, Germany (Frankfurt) and UK (London) Regions
Jun 04, 2024
IT Hardware
The planned upgrade of our network infrastructure architecture across certain data centers has been deferred. The upgrade will affect some of your cloud database resources, and we urge you to review the following particulars closely:
● Affected Products: ApsaraDB RDS, PolarDB, PolarDB-X, ApsaraDB for Redis, Tair, ApsaraDB for MongoDB, ApsaraDB for HBase, Lindorm, AnalyticDB, ApsaraDB for ClickHouse, etc.
● Affected Regions: Germany (Frankfurt) Zone A, Singapore Zone A, Singapore Zone B, Singapore Zone C, UK (London) Zone A
● Scheduled Times:
● Singapore Time
● June 12, 2024: 00:00 AM to 06:00 AM (GMT+8)
● June 14, 2024: 00:00 AM to 06:00 AM (GMT+8)
● London Time
● June 11, 2024: 01:00 AM to 05:00 AM (BST)
● June 13, 2024: 01:00 AM to 05:00 AM (BST)
● Frankfurt Time
● June 11, 2024: 02:00 AM to 06:00 AM (CET)
● June 13, 2024: 02:00 AM to 06:00 AM (CET)
● Impact Summary:
● For Existing Long Connections: These connections will remain stable and unaffected.
● For New Connections: Expect possible disruptions, with connection failures lasting up to 30 seconds during each specific time (listing in the scheduled times) due to network fluctuations. To mitigate potential impacts, ensuring your application features a connection retry mechanism is essential, thus allowing automatic resumption of connections and safeguarding your business operations. To equip with a reconnection mechanism, please check out reference documents.
● Important Consideration:
● For instances of High Availability type with a multi-AZ deployment, attempting an HA switchover to an unaffected AZ will not bypass the anticipated impacts. While migrating the primary AZ to an unaffected AZ might seem a solution, the process time—dependent on your instance's data volume—can be extensive, potentially imposing a more significant business disruption. Consequently, we advise against this method. The most effective mitigation strategy is to integrate a connection retry mechanism within your business applications, aiming to minimize operational effects.
● Reference Documents:
● ApsaraDB RDS Reconnection Mechanism > (https://www.alibabacloud.com/help/rds/apsaradb-rds-for-mysql/use-an-application-to-connect-to-an-apsaradb-rds-for-mysql-instance)
● ApsaraDB for Redis Reconnection Mechanism > (https://www.alibabacloud.com/help/redis/use-cases/retry-mechanisms-for-redis-clients)
● ApsaraDB for MongoDB Reconnection Mechanism > (https://www.alibabacloud.com/help/mongodb/getting-started/connect-to-an-apsaradb-for-mongodb-standalone-instance-by-using-program-code)
Should you have any further inquiries or require assistance, please do not hesitate to reach out by submitting support tickets. (https://workorder-intl.console.aliyun.com/#/ticket/createIndex)
We sincerely apologize for any inconvenience or concern this postponement may cause. Your understanding and continued support are greatly appreciated.
● Affected Products: ApsaraDB RDS, PolarDB, PolarDB-X, ApsaraDB for Redis, Tair, ApsaraDB for MongoDB, ApsaraDB for HBase, Lindorm, AnalyticDB, ApsaraDB for ClickHouse, etc.
● Affected Regions: Germany (Frankfurt) Zone A, Singapore Zone A, Singapore Zone B, Singapore Zone C, UK (London) Zone A
● Scheduled Times:
● Singapore Time
● June 12, 2024: 00:00 AM to 06:00 AM (GMT+8)
● June 14, 2024: 00:00 AM to 06:00 AM (GMT+8)
● London Time
● June 11, 2024: 01:00 AM to 05:00 AM (BST)
● June 13, 2024: 01:00 AM to 05:00 AM (BST)
● Frankfurt Time
● June 11, 2024: 02:00 AM to 06:00 AM (CET)
● June 13, 2024: 02:00 AM to 06:00 AM (CET)
● Impact Summary:
● For Existing Long Connections: These connections will remain stable and unaffected.
● For New Connections: Expect possible disruptions, with connection failures lasting up to 30 seconds during each specific time (listing in the scheduled times) due to network fluctuations. To mitigate potential impacts, ensuring your application features a connection retry mechanism is essential, thus allowing automatic resumption of connections and safeguarding your business operations. To equip with a reconnection mechanism, please check out reference documents.
● Important Consideration:
● For instances of High Availability type with a multi-AZ deployment, attempting an HA switchover to an unaffected AZ will not bypass the anticipated impacts. While migrating the primary AZ to an unaffected AZ might seem a solution, the process time—dependent on your instance's data volume—can be extensive, potentially imposing a more significant business disruption. Consequently, we advise against this method. The most effective mitigation strategy is to integrate a connection retry mechanism within your business applications, aiming to minimize operational effects.
● Reference Documents:
● ApsaraDB RDS Reconnection Mechanism > (https://www.alibabacloud.com/help/rds/apsaradb-rds-for-mysql/use-an-application-to-connect-to-an-apsaradb-rds-for-mysql-instance)
● ApsaraDB for Redis Reconnection Mechanism > (https://www.alibabacloud.com/help/redis/use-cases/retry-mechanisms-for-redis-clients)
● ApsaraDB for MongoDB Reconnection Mechanism > (https://www.alibabacloud.com/help/mongodb/getting-started/connect-to-an-apsaradb-for-mongodb-standalone-instance-by-using-program-code)
Should you have any further inquiries or require assistance, please do not hesitate to reach out by submitting support tickets. (https://workorder-intl.console.aliyun.com/#/ticket/createIndex)
We sincerely apologize for any inconvenience or concern this postponement may cause. Your understanding and continued support are greatly appreciated.
