This topic describes the release notes of PolarDB and provides reference links.
|In-Memory Column Index (IMCI)||IMCI is suitable for online analytical processing (OLAP) scenarios where a large amount
of data is processed and complex queries are required. PolarDB for MySQL provides IMCI to implement integrated real-time transaction processing and data analysis
features and provides a one-stop hybrid transaction/analytical processing (HTAP) solution.
PolarDB for MySQL allows you to use only one system to meet the requirements of online
transaction processing (OLTP) and OLAP scenarios.
Note If you have questions about the feature, we recommend that you submit a ticket to contact technical support.
|Different specifications for primary node and read-only nodes||For a PolarDB cluster, you can separately upgrade or downgrade the primary node and read-only nodes. This means that you can select different specifications for the primary node and read-only nodes.||2022-04-22|
|Failover with hot standby||You can enable hot standby for the read-only nodes in your cluster to improve failover speed and avoid service interruptions.||2022-04-13||Overview|
|Automatically scale local resources||PolarDB for MySQL allows you to scale local resources within several seconds. When the average CPU utilization of a PolarDB cluster within a sampling duration reaches the specified threshold, PolarDB for MySQL increases the number of CPU cores of the cluster to the specified value.||2022-03-23||Automatically scale local resources|
|PolarProxy specification upgrade||PolarProxy specification upgrade solutions:
||2022-03-10||Upgrade the specifications of PolarProxy|
|Custom parameters of cluster nodes||PolarDB allows you to configure the parameters of each cluster node based on your business requirements.||2022-03-03||Specify cluster and node parameters|
|New specification for clusters of the General-purpose type of PolarDB for MySQL Cluster Edition: 32 cores and 128 GB memory||Clusters of the General-purpose type of PolarDB for MySQL Cluster Edition support a new specification: 32 cores and 128 GB memory.||2022-02-18||Specifications of compute nodes|
|New edition: Multi-master Cluster||Multi-master Cluster Edition clusters are developed based on a multi-primary architecture that contains
multiple primary nodes and read-only nodes. This architecture is suitable for high
concurrent read and write scenarios such as multitenancy, gaming, and e-commerce.
To improve the overall concurrent read and write capabilities of clusters, this architecture
supports concurrent data writes to databases from different primary nodes and allows
you to dynamically switch the primary nodes of databases within seconds.
Note The edition is still in the phased release stage. You can submit a ticket to apply for the feature.
|2022-02-11||Multi-master Cluster Edition|
|PolarProxy Upgraded to PolarProxy Enterprise Edition||
The following PolarProxy Enterprise Editions are available: Standard Enterprise Edition and Dedicated Enterprise Edition.
Compared with the previous free edition of PolarProxy, PolarProxy Enterprise Edition provides additional advanced features such as the multi-primary architecture, compute nodes with elastic scaling within seconds, and proxy throttling protection.
Note You are charged for PolarProxy Enterprise Edition from April 1, 2022.
|Added edition: Archive Database Cluster Edition||
A Archive Database Cluster Edition cluster of the Archive Database (High Compression Ratio) Edition consists of one primary node and at least one read-only node based on shared storage. The primary node can handle read and write requests. A read-only node can handle only read requests. The multi-node architecture of Archive Database Cluster Edition inherits the advantages of Archive Database (High Compression Ratio) as well as ensures the high availability of PolarDB clusters. When the primary node in a cluster fails, the cluster can automatically fail over to a read-only node. Then, the read-only node serves as the new primary node. This ensures that the service availability is at least 99.99%.
Existing Archive Database (High Compression Ratio) clusters can be upgraded to Archive Database Cluster Edition clusters.
|Support for automatic upgrade and downgrade in subscription PolarDB clusters||Subscription PolarDB for MySQL clusters support automatic upgrade and downgrade.||2021-11-05||Automatic configuration changes (auto scaling)|
|New parameter for the thread pool feature||Multiple parameters such as bypass_thread_pool_ips and bypass_thread_pool_check_ignore_proxy are added to the thread pool feature of PolarDB for MySQL 8.0 clusters whose revision version is 22.214.171.124.9 or later.||2021-10-25||Thread Pool|
|New parameter for PolarDB: polar_replica_work_on_nonblock_mdl_mode||PolarDB supports the polar_replica_work_on_nonblock_mdl_mode parameter. After this parameter is enabled, you can prevent long-running transactions on PolarDB read-only nodes from blocking DDL operations.||2021-08-26||Prevent long-running transactions on read-only nodes from blocking DDL operations|
|Support for the scheduled event feature||For scheduled PolarDB O&M events, you can be notified by text message, phone call, email, or internal message. You can also be notified in the console. Scheduled PolarDB O&M events include database software upgrade events and hardware maintenance and upgrade events. You can view the details of each scheduled event. These details include the event type, task ID, cluster name, and switchover time. You can also change the switchover time.||2021-08-06||View and manage scheduled events|
|Specification change of clusters in a global database network (GDN)||2-core node specifications are not supported by clusters in a GDN.||2021-07-02||Specifications of compute nodes|
|Support for database and table restoration for PolarDB for MySQL 5.7 clusters||Databases and tables can be restored from a backup set or to a previous point in time in PolarDB for MySQL 5.7 clusters whose revision version is 126.96.36.199.8 or later.||2021-07-02||Method 1 for database and table restoration: Restore data from a backup set and Method 2 for database and table restoration: Restore data to a point in time|
|Support for automatic encryption of new tables in TDE encryption||PolarDB for MySQL 8.0 clusters whose revision version is 188.8.131.52.15 or later support automatic encryption for all newly created tables.||2021-06-15||Advanced settings|
|Support for automatic rotation of Secure Sockets Layer (SSL) certificates in SSL configurations||After automatic certificate rotation is enabled, PolarDB automatically updates an SSL certificate during the maintenance window of the cluster within 10 days before the expiry date of the certificate.||2021-05-28||Enable automatic certificate rotation|
|Support for the parameter template feature to centrally manage database clusters||You can configure a number of parameters at a time by using a parameter template and apply the template to a PolarDB cluster.||2021-03-09||Apply a parameter template|
|Support for enhanced backup to improve the data recovery speed.||PolarDB allows you to create backups every 2, 3, or 4 hours for the data that is generated over the past 24 hours.||2021-03-09||Enhanced backup|
|New type of specification for compute nodes: General-purpose||PolarDB for MySQL Cluster clusters support General-purpose. Idle computing resources such as idle CPUs are shared among clusters that run on the same server. Resource sharing allows you to deploy a large number of clusters at low costs.||2021-03-02||Specifications of compute nodes|
|Support for the instant ADD COLUMN and statement queue features in PolarDB for MySQL 5.7 clusters||The two features are supported in PolarDB for MySQL 5.7 clusters whose revision version is 184.108.40.206.6 or later. You can use the instant ADD COLUMN feature to quickly add columns to large tables and use the statement queue feature to reduce conflict overheads and improve database performance.||2021-02-09||Instant ADD COLUMN|
|Faster data recovery||The backup and restoration features of PolarDB clusters use multi-threading parallel processing and other innovative technologies. This allows you to restore data from a backup set (snapshot) to a new cluster within 10 minutes.||2021-02-09||Data backup and restoration|
|Archive Database available for commercial use||PolarDB of the Archive Database Edition uses X-Engine to provide a high data compression ratio and reduce storage costs by up to 70%. The Archive Database Edition is applicable to services that do not require a large number of computing resources but need to store archived data, such as DingTalk messages. PolarDB of the Archive Database Edition is highly compatible with MySQL and supports a maximum storage capacity of 200 TB.||2021-01-13||Archive Database|
|Support for two new features: upgrade configurations and add nodes on a scheduled basis||When you upgrade cluster configurations or add nodes, you can create a schedule to perform the operation during off-peak hours within 24 hours. The operation may cause short service interruptions. The two features help you reduce the impact of service interruptions.||2021-01-12||Manually upgrade or downgrade a PolarDB cluster|
|Support for the upgrade of storage plans to increase storage capacity||Storage plans can be upgraded to increase storage capacity. If your storage plan is about to expire or the storage capacity is insufficient, you can renew or upgrade the storage plan.||2021-01-04||Renew or upgrade a storage plan|
|Increase in the maximum storage capacity of the nodes of some specifications||In PolarDB for MySQL, the maximum storage capacity of 8-core 32 GB nodes is increased to 20 TB. The maximum storage capacity of 16-core 128 GB, 32-core 256 GB, and 64-core 512 GB nodes is increased to 100 TB.||2020-12-24||Specifications of compute nodes|
|Task progress bar available in the PolarDB console||In the upper-right corner of the PolarDB console, you can click the icon to view the progress of tasks, such as backup and restoration tasks.||2020-12-03||N/A|
|Support for the restoration of databases and tables in PolarDB for MySQL 5.6 clusters||PolarDB for MySQL 5.6 clusters support the database and table restoration feature.||2020-12-01|
|Support for transparent data encryption (TDE) in PolarDB for MySQL 5.6 clusters||PolarDB for MySQL 5.6 clusters support the TDE feature.||2020-12-01||Configure TDE|
|Storage plans can be used to offset level-1 backup storage fees||You can use storage plans to offset the used storage of PolarDB clusters and the used storage that exceeds the free quota for level-1 backups.||2020-11-27||Storage plans|
|Support for the configuration of time zones and the case sensitivity of table names during cluster creation||When you create a PolarDB for MySQL cluster, you can specify whether the table names are case-sensitive.||2020-09-21|
|Release of PolarDB for MySQL in the Australia (Sydney) and China (Qingdao) regions||PolarDB for MySQL is available in the Australia (Sydney) and China (Qingdao) regions.||2020-08-21|
|PolarDB for MySQL 5.7 available for commercial use||PolarDB for MySQL 5.7 is available for commercial use. Users who use PolarDB for MySQL 5.7 during public preview can purchase PolarDB for MySQL 5.7 clusters for their production environments.||2020-08-21|
|Release of PolarDB for MySQL in the UK (London) region||PolarDB for MySQL is available in the UK (London) region.||2020-08-15|
|Support for concurrent addition of multiple read-only nodes on the configuration change page||Multiple read-only nodes can be added to a PolarDB for MySQL cluster concurrently when you change the cluster configurations. It takes only about 5 minutes to add multiple read-only nodes concurrently.||2020-07-28||Add or remove read-only nodes|
|PolarDB for MySQL 5.7 available in public preview||PolarDB for MySQL 5.7 is available in public preview.||2020-07-28|
|Global read/write splitting available for GDNs||The read/write mode can be set to Read and Write (Automatic Read-write Splitting) for all the cluster endpoints in the GDNs of PolarDB for MySQL. Read requests are sent to the on-premises secondary cluster, and write requests are automatically forwarded to the primary cluster in the central region.||2020-07-01||Create and release a GDN|
|Switchover with endpoints (connection changes not required)||The Switch with Endpoints (Connection Changes not Required) option is available for you to upgrade an existing ApsaraDB RDS for MySQL instance to a PolarDB for MySQL cluster. The original endpoint of the ApsaraDB RDS for MySQL instance can be retained. You do not need to modify the configurations or the code of your applications.||2020-06-10||Create a PolarDB for MySQL cluster by migrating an ApsaraDB RDS for MySQL instance|
|Upgrade of the backup feature||PolarDB provides more advanced configurations and capabilities for the backup feature to meet enterprise-level data backup requirements. This ensures data security.||2020-05-12||Data backup and restoration|
|Backup feature available for commercial use||You are charged for the storage space occupied by backup files and log files. PolarDB provides a limited quota of free storage space.||2020-05-12||Pricing|
|Release of database services in the Japan (Tokyo) region||PolarDB for MySQL, , and are available in the Japan (Tokyo) region.||2020-04-30|
|Release of PolarDB for MySQL in the China (Chengdu) region||PolarDB for MySQL is available in the China (Chengdu) region.||2020-04-13|
|Release of PolarDB for MySQL in the US (Virginia) region||PolarDB for MySQL 5.6 and 8.0 are available in the US (Virginia) region.||2020-03-09|
|Global consistency||PolarDB for MySQL cluster endpoints support global consistency. This ensures that the latest data can be retrieved if a replication delay occurs when data is replicated from a primary node to read-only nodes.||2020-03-03|
|SSL for encrypted transmission||The primary endpoints of PolarDB for MySQL support SSL. SSL encrypts network connections at the transport layer. This improves data security and integrity, but increases network response time. You can enable SSL encryption based on your business requirements.||2020-02-11||Configure SSL encryption|
|Read requests offloaded from the primary node||PolarDB for MySQL allows read requests to offload from the primary node. SQL query requests are sent to read-only nodes while data consistency is ensured. This reduces the workloads of the primary node and ensures the stable performance of the primary node.||2020-02-07||Configure PolarProxy|
|New alert rules||The new alert rule feature (PolarDB for MySQL cluster) is available in CloudMonitor. The feature supports more performance metrics
and helps improve user experience in notifications.
To obtain better user experience in notifications, we recommend that you use the new alert rules.
|2020-01-09||Create an alert rule|
|Support for diagnosis and optimization features in more regions||The diagnosis and optimization features of PolarDB for MySQL are available in the US (Silicon Valley) and Germany (Frankfurt) regions.
The diagnosis and optimization features include the following items:
|Release of PolarDB for MySQL in the Malaysia (Kuala Lumpur) region||PolarDB for MySQL 5.6 and 8.0 are available in the Malaysia (Kuala Lumpur) region.||2019-11-14|
|Support for data migration across zones.||PolarDB for MySQL allows you to change the primary zone. You can use this feature to migrate the compute nodes of a cluster to another zone. This is applicable to diverse scenarios. For example, you can use this feature when you perform disaster recovery or enable nearby access for Elastic Compute Service (ECS) instances.||2019-11-13||Multi-zone deployment|
|API operations for performance monitoring||
|Support for the configuration of node failover priorities||PolarDB allows you to configure node failover priorities. By default, the priority of each node is 1. You can specify an integer from 1 to 15 as the priority. The configuration change takes effect in real time and does not affect the proper running of database services.||2019-10-14||N/A|
|Failover||PolarDB provides the failover feature that is included in the previous planning. You can switch the services of the primary node to a specified read-only node based on your business requirements.||2019-10-14||Automatic failover and manual failover|
|PolarDB for MySQL 8.0 available for commercial use||PolarDB for MySQL 8.0 supports parallel queries. In specific scenarios, the performance of your cluster improves by 10 times. You can add fields without locking tables. This significantly reduces the negative impact on service stability. PolarDB for MySQL 8.0 optimizes some features of NoSQL databases, provides an easy way to use JSON data, and adds some advanced SQL features, such as window functions.||2019-09-12||Parallel query|
|PolarDB available for commercial use||PolarDB is available for commercial use in the following regions:
||2019-09-05||What is PolarDB?|
|Release of PolarDB in the Indonesia (Jakarta) region||PolarDB is available in the Indonesia (Jakarta) region.||2019-08-20||What is PolarDB?|