tencent cloud

PrevNext

Feedback

search by keyword

Recent Pages

Documentation
TencentDB for Redis®
    Documentation
    Download PDF

    Upgrading Proxy

    Last updated: 2024-11-25 15:52:47
    Download PDF

      Overview

      Minor versions of the TencentDB for Redis® proxy are released from time to time to add more database features or fix known bugs.
      Proxy Version
      Proxy Minor Version
      New Feature, Optimization, or Fix
      Proxy 5.0
      5.8.8
      Support for redirection of certain commands in primary-secondary edition without requiring a key (eval, evalsha, fcall, and fcall_ro).
      Added commands that support Redis 6.0. (Including copy, blmove, lmove, geosearchstore, zrangestore, zdiff, zunion, and zdiffstore.)
      5.8.1
      Added support for the shared connection feature to mitigate cluster overload caused by connection storms.
      5.6.3
      Supported getex, auth name pwd, and xautoclaim commands.
      5.6.0
      Supported wait command in Cluster Architecture instances.
      Supported SSL encryption to implement encrypted data transfer.
      5.5.0
      Supported wait commands in Cluster Architecture instances.
      Supported the “Read Local Nodes Only” feature.
      Supported the dbsize command in Cluster Edition instances to return the number of keys in all shards.
      Supported displaying the client port information in slow logs.
      Supported flushall and flushdb commands, which can be distributed to the master node of all shards in a Cluster Architecture instance while retaining data in nodes with the specified nodeid.
      Supported monitoring the number of big value requests.
      Supported the Scan command in Cluster Edition instances to traverse all shards.
      Fixed the issue where "ERR unknown command 'select' command" might be returned when the select command was executed after a transaction.
      Fixed the issue where the command was sent to an incorrect node and the Move error was reported when the locked connection wasn't released in time as the watch+ transaction was used in the pipeline scenario.
      5.4.0
      Optimized the statistics collection policies of P99 monitoring metrics, including metrics for all Redis commands.
      5.2.0
      Supported the five-second granularity for monitoring data.
      5.1.0
      Supported keys command in Cluster Architecture instances.
      Supported displaying the client address in slow logs.Client address
      Fixed the " ERR MULTI calls cannot be nested" error.
      5.0.0
      Supported unlink and exists commands in Cluster Architecture instances.
      Proxy 4.0
      3.5.0
      Supported the command analysis feature. You can view information such as QPS, P99 execution latency, average execution latency, and max execution latency of individual commands.
      3.3.0
      Supported the five-second granularity for system monitoring data collection.
      3.2.0
      Supported displaying the client address in slow logs.
      Fixed the "ERR MULTI calls can‘t be nested" error.

      Note on Upgrade

      The system automatically detects the minor version of the proxy. If the Upgrade Proxy button is grayed out, the instance proxy is already on the latest minor version.
      As the version release time varies by region, the minor version release status is as displayed in the console.

      Upgrade Impact

      The version upgrade process mainly consists of data sync and instance switch:
      During data sync, the service will not be affected.
      During switch, the instances will become read-only for less than 1 minute (to wait for the completion of data sync), and a momentary disconnection (within seconds) will occur; therefore, your business should have an automatic reconnection mechanism.

      Preparations for Upgrade

      The instance to be upgraded is in Running status and is not executing any tasks.
      We recommend that you perform upgrade in the maintenance time during off-peak hours.

      Upgrade Directions

      1. Log in to the TencentDB for Redis® console.
      2. Above the instance list on the right, select the region.
      3. In the instance list, find the target instance.
      4. Click the instance ID to enter the Instance Details page.
      5. In the Specs Info section on the Instance Details page, click Upgrade Proxy next to Proxy Version.
      
      6. In the pop-up window, confirm the information of the target instance based on the following table, configure the target version, and click OK.
      
      Parameter
      Description
      Instance ID
      ID of the instance to be upgraded
      Current Version
      Current minor version of the proxy
      Target Version
      Target version after proxy upgrade. The target version cannot be selected.
      Switch Time
      Switch Now: The switch will be performed when the data sync is almost completed (the data left to be synced is less than 10 MB).
      Switch in Maintenance Time: The switch will be performed during the instance maintenance time. If the switch conditions cannot be met in the current maintenance time, the switch will be attempted in the next maintenance time. You can modify the Maintenance Window on the instance details page.
      7. Return to the instance list. After the Instance Status changes to Running, you can see that the instance version has been upgraded in the instance list or instance details.

      Related APIs

      API Name
      Description
      Upgrades proxy version
      Contact Us

      Contact our sales team or business advisors to help your business.

      Contact Us
      Technical Support

      Open a ticket if you're looking for further assistance. Our Ticket is 7x24 avaliable.

      Submit a Ticket
      7x24 Phone Support
      Copyright © 2013-2024 Tencent Cloud. All Rights Reserved.
      Privacy PolicyLegalCookie Policy