title: Overview

text:
If you are upgrading from a previous version, make sure to review the
[upgrade
instructions]()
before running through the upgrade process.

title: New features

text:
- rsyslog logging support - RLEC now writes by default to syslog,
    which enables monitoring through rsyslog.
- Profile support for tuning cloud and non-cloud environments --
    enables the administrator to configure RLEC to run with different
    performance profiles that are optimized for either cloud or
    non-cloud environments. For additional details, refer to the
    [Performance
    optimization]()
    section.
- SLA for AOF rewrite - enables the administrator to configure
    database parameters, by running the rladmin tune command, related to
    when AOF rewrite is triggered based on the time it would take to
    load the database from the AOF file, and on the maximum AOF rewrite
    file size. In addition, updates to the AOF rewrite mechanism
    minimize chances of the disk getting full.
- New warning and alerts related to AOF rewrite mechanism - a warning
    is shown during the setup process in case the disk size is lower
    than twice the size of the RAM. New cluster level alerts added to
    alert when node available disk space is lower than the needed disk
    space for AOF rewrite purposes, and when node performance is
    degraded due to reaching disk I/O limits.
- Replica Of support for multiple sources - the Replica Of feature is
    enhanced to support creating a database that is a replica of
    multiple source databases. For additional details, refer to the Replica Of section.
- Cross cluster Replica Of - the Replica Of feature now supports
    defining a database that is a replica of databases that belong to a
    different RLEC cluster. For additional details, refer to the
    Replica Of section.
- Multi-IP support - on a node that has multiple IPs, enables the
    administrator to specify which IP address is used for internal
    traffic and which IP addresses are used for external traffic. For
    additional details, refer to [Multi-IP &
    IPv6]()
    support.
- IPv6 support for external traffic - on a node that has multiple
    IPs, external IP addresses can be of IPv6 type. For additional
    details, refer to [Multi-IP &
    IPv6]()
    support section.
- Support for OpenStack Object Store ("Swift") location for import /
    export / backup. For additional details, refer to [Database
    backup]()
    and [Importing data to a
    database]()
    sections.
- Import of a sharded database - support for importing data of a
    sharded database by indicating multiple files paths. For additional
    details, refer to the [Importing data to a
    database]()
    section.
- Enable running the install script in silent mode using "-y"
    parameter for default answers ("Y") or "-c" for file path parameters
    for custom answers. For additional details, refer to [Accessing and
    installing the setup
    package]()
    section.
- New rladmin command-line-interface "info" command allows for
    fetching current value of tunable parameters.

title: Changes

text:
- rladmin command-line-interface can only be run under user root or
    redislabs. For additional details, refer to the [rladmin
    command-line
    interface (CLI)](https://docs.redis.com/latest/rs/references/rladmin/)
    section.
- Import / export / backup to/from Amazon S3 requires supplying the
    credentials per usage instance; it does not use central cloud
    credentials that used to be supplied in the Settings -\> General
    page.
- Fields related to storing Amazon S3 Cloud credentials have been
    removed from Settings -\> General page.
- Performance optimization in the database resharding mechanism.
- Persistent and ephemeral storage cluster level alerts are enabled by
    default and set to 70%.
- Various enhancements to rladmin command-line-interface (CLI) to
    support new commands.
- Redis version updated to 2.8.21 that addresses
    [CVE-2015-4335/DSA-3279 - Redis Lua Sandbox
    Escape](https://groups.google.com/forum/#!msg/redis-db/4Y6OqK8gEyk/Dg-5cejl-eUJ).
- Port 3336 added to the list of ports being used by RLEC.
- Node "Network utilization" alert measured in percentages (%) has
    been updated to "Network throughput" alert measured in MBps. If the
    alert was defined then it will be disabled when upgrading to this
    version and the user needs to reconfigure it with a new value.
- Performance improvements to the database Import to make the process
    much faster.
- Enhancements to the support package to include additional details.
- Removed support for SSL 2.0/3.0 protocols due to security
    vulnerabilities.
- Disabled "dofile" functionality in Redis to solve a possible
    security vulnerability.
- rladmin CLI "tune watchdog profile" command syntax updated to "tune
    cluster watchdog_profile".

title: Fixed issues

text:
- Support for relative path for backup and import functionalities.
- Fix issue with TLS configuration of email server settings.
- Email alerts not sent for database export and import processes.
- Fix erroneous entries in the Log page.
- Sometimes a wrong value is reported in the UI for node used
    ephemeral storage space.
- Sometime the wrong Replica Of Lag value is reported in the UI.
- RLEC-6875 - email server settings not working when using port 587.
- RLEC-5498 - Improve rladmin response time when a node is down.
- Validation of Replica Of source definition did not fail in the UI
    and would only fail in runtime if it was using the Cluster Name
    (FQDN) and the FQDN was not properly configured in the DNS.
- Various improvements to error messages reported by rladmin.

title: Known issues

text:
- **Issue**: Connecting from a client to a database endpoint with
    mixed upper case and lower case letters can result in a slow
    response from the database.

    **Workaround**: The cluster name (FQDN)
    should consist of only lower-case letters. When connecting from a
    client to a database endpoint, only lower case letters should be
    used in the endpoint.

- **Issue**: When upgrading a node to a new RLEC version (refer to
    [Upgrading
    nodes]()
    while the node is in the offline state (refer to [Taking a node
    offline](),
    the upgrade process succeeds but might result in an unstable
    cluster.

    **Workaround**: Do not try to upgrade a node while it is in
    the offline state.

- **Issue**: In Red Hat Enterprise Linux, and CentOS operating
    systems, the process used for cleaning up internal log files does
    not work, thereby allowing the log files to grow and possibly result
    in disk space issues.

    **Workaround**: On each machine that functions
    as a node in the cluster, create a file named "redislabs", and save
    it in the following location: "/etc/logrotate.d/" (e.g.
    "/etc/logrotate.d/redislabs").
    The file should contain the following text:
    [code example]
    The file's permissions should be root:root, 644.
    Afterwards, from the operating system command line interface (CLI)
    run the following commands:
    [code example]

- **Issue**: In the Replica Of process, if the target database does
    not have replication enabled and it is restarted or fails for any
    reason, the data on target database might not be in sync with the
    source database, although the status of the Replica Of process
    indicates it is.

    **Workaround**: You need to manually stop and
    restart the synchronization process in order to ensure the databases
    are in sync.

- **Issue**: In the Replica Of process, if the source database is
    resharded while the replica of process is active, the
    synchronization process will fail.

    **Workaround**: You need to
    manually stop and restart the synchronization process after
    resharding of the source database is done.
- **Issue**: In the replica of process, high database traffic might restart the Replica of process as result of the "replica buffer" being exceeded. In this case you see
    the status of the replica of process as "Syncing"
    frequently.

    **Workaround**: You need to manually reconfigure the
    "replica buffer" through rladmin and set the buffer size to a new
    size. In order to find the appropriate buffer size please contact
    support at: <support@redislabs.com>.

- **Issue**: In a cluster that is configured to support rack-zone
    awareness, if the user forces migration of a master or replica shard,
    through rladmin, to a node on the same rack-zone as its
    corresponding master or replica shard, and later runs the rebalance
    process, the rebalance process will not migrate the shards to ensure
    rack-zone awareness compliance.

    **Workaround**: In the scenario
    described above, you need to manually migrate the shard, through
    rladmin, to a node on a valid rack-zone in order to ensure rack-zone
    awareness
    compliance.

code:
/var/opt/redislabs/log/\*.log {
    daily
    missingok
    copytruncate
    rotate 7
    compress
    notifempty
    }

section_id: known-issues

code:
yum install policycoreutils-python
    semanage fcontext -a -t var_log_t '/var/opt/redislabs/log(/.\*)?'
    restsorecon -R /var/opt/redislabs/log


title: RLEC 4.3.0-230 Release Notes (August 2, 2016)

page_type: content

title: Overview

role: overview

text:
If you are upgrading from a previous version, make sure to review the
[upgrade
instructions]()
before running through the upgrade process.

You can upgrade to this version from any 4.2 version. If you have a
version older than 4.2 you should first upgrade to 4.2 and only then
upgrade to this version.

title: New features

role: content

text:
- Various improvements to internal performance and stability were
    implemented.
- RLEC Flash functionality added. For additional details, refer to
    [Auto Tiering]()
    and contact <support@redislabs.com> if you are interested in this
    functionality.
- Support for Redis version 3.0 added. When you install or upgrade the
    cluster the new default version for Redis databases will be 3.0 and
    when you upgrade the databases they will be updated to this version.
    If you would like to change the default version to Redis 2.8 refer
    to the instruction in the [Upgrading
    databases]()
    section. If you would like to upgrade existing databases to the
    latest 2.8 minor version, refer to the Known Issues section below.
- Complete cluster failure recovery instructions added. For additional
    details, refer to [Cluster
    Recovery]().
- Major improvements made to database replication performance process
    by using diskless replication between master and replica shards. The
    data between the master and replica shards is streamed directly,
    instead of using the default file-on-disk mechanism. This behavior
    can be changed for the entire cluster or per database through
    rladmin.
- Major enhancements made to rladmin command line interface to add new
    administration functionalities.
- rlcheck installation verification utility added to facilitate
    checking node health. For additional details, refer to [rlcheck
    installation verification
    utility]().
- Added the ability to allow the user to configure how machine IP
    addresses are used in Node Configuration setup in the management UI.
    For additional details, refer to [Initial setup - creating a new
    cluster.]()
- Connection to database endpoint can now be encrypted with SSL. For
    additional details, refer to [Securing client connection with
    SSL]().
- Added support for running the cluster on the following operating
    systems and versions: RHEL/CentOS 6.6, 7.1, 7.2, RHEL 6.7, Oracle
    Linux 6.5.

title: Changes

text:
- Environment configuration profile with name "default" has been
    changed to "cloud" and the default value has been changed to
    "local-network". For additional details, refer to [Performance
    optimization]()
    section.
- In the REST API, when creating a database and not setting the
    database replication parameter to "true", the default value assigned
    by the cluster has changed from "true" to "false".
- rladmin syntax updates can affect commands written for prior
    versions of RLEC. In this version commands that are run directly
    from the operating system CLI prompt (not through the rladmin
    prompt) no longer require quotation marks for text with special
    characters.
- Option added to the *Replica-of* process that allows gradual
    "shard-by- shard" replication of a sharded database, reducing the
    load on internal buffers. This optimization setting can be
    configured on the target database using the gradual_sync_mode
    parameter in rladmin.
- The functionality for taking a node offline was removed from the UI.

title: Fixed issues

text:
- RLEC-7110 - node does not recover properly after restart in case
    ephemeral storage is not available yet
- RLEC-7502 - log rotate job not working properly on RHEL operating
    system
- RLEC-7599 - issues running on a server with no IPv6 kernel support
- RLEC-7561, RLEC-7597 - issues connecting to database endpoint as
    result of cluster name containing capital letters
- RLEC-7245 - on machines with multiple IPs sometimes the wrong IP
    address is chosen for internal traffic
- RLEC-6815 - wrong log entry is added when enabling cluster alert
    regarding database version compatibility
- RLEC-7652 - database is down in certain failover scenarios only
    when the database is completely empty
- RLEC-7737 - issue where in a specific scenario after node restarts,
    a database with replication both master and replica shards are
    reported as down
- RLEC-7712 - in some cases, the Replica Of process may fail when
    Redis password is set
- RLEC-7726 - node object "avg_latency" statistic is not returned in
    the REST API
- RLEC-7358 - install script issue when running on LVM disks
- RLEC-8086 - port 9443 missing from redislabs-clients.xml
- RLEC-7281 - rotation of internal log files not working properly
- RLEC-8279 - updates to a user definition might cause password reset
    to be required
- RLEC-8512 - when upgrading an existing cluster that has uppercase
    letters in the cluster name (FQDN) the cluster might not function
    properly after the upgrade and attempts to connect to a database
    might fail
- RLEC-8371 - email alerts do not work when using Amazon SES service
- In certain scenarios the node upgrade process may fail if the node
    is in the offline state

title: Known issues

text:
- **Issue**: When upgrading to this version from a previous RLEC
    version, rladmin status output will show the database status as
    having an old version. When you upgrade the Redis database (using
    rladmin upgrade db command) the Redis version will be updated to 3.0
    even if you updated the cluster's Redis default version to
    2.8.

    **Workaround**: If you would like to cancel the old version
    indication in rladmin status without upgrading the Redis version to
    3.0 you should first change the cluster default version to 2.8
    (using rladmin tune cluster command), and then trigger the Redis
    process to be restarted by migrating the database shards (using
    rladmin migrate db command).

- **Issue**: RLEC-8486 - On Ubuntu, when uninstalling RLEC using the
    apt-get purge command, some of the Redis processes on the machine
    might continue running.

    **Workaround**: If you encounter this issue
    you must manually kill the Redis processes.

- **Issue**: RLEC-8283 - The cluster recovery process does not work
    properly when the cluster that needs to be recovered does not have a
    node with ID 1.

    **Workaround**: If you encounter this issue please
    [contact Redis support](https://redislabs.com/company/support/)

- **Issue**: In the Replica Of process, if the target database does
    not have replication enabled and it is restarted or fails for any
    reason, the data on the target database might not be in sync with
    the source database, although the status of the Replica Of process
    indicates that it is.

    **Workaround**: You must manually stop and
    restart the synchronization process in order to ensure the databases
    are in sync.

- **Issue**: In the Replica Of process, if the source database is
    resharded while the Replica Of process is active, the
    synchronization process will fail.

    **Workaround**: You must manually
    stop and restart the synchronization process after the resharding of
    the source database is done.

- **Issue**: In the Replica Of process, high database traffic might restart the Replica Of process due to the "replica buffer" being exceeded. In this case
    you will often see the status of the Replica Of process display as
    "Syncing".

    **Workaround**: You must manually increase the "replica
    buffer" size through rladmin. In order to find the appropriate
    buffer size please [contact Redis support](https://redislabs.com/company/support/)

- **Issue**: In a cluster that is configured to support rack-zone
    awareness, if the user forces migration of a master or replica shard
    through rladmin to a node on the same rack-zone as its corresponding
    master or replica shard, and later runs the rebalance process, the
    rebalance process will not migrate the shards to ensure rack-zone
    awareness compliance.

    **Workaround**: In the scenario described
    above, you must use rladmin to manually migrate the shard, to a node
    on a valid rack-zone in order to ensure rack-zone awareness
    compliance.


title: RLEC 4.4 Release Notes (December 2016)

title: Overview

text:
If you are upgrading from a previous version, make sure to review the
[upgrade
instructions]()
before beginning the upgrade process.

You can upgrade to this version from any 4.3 version. If you have a
version older than 4.3 you must first upgrade to 4.3 and only then
upgrade to this version.

title: New features

text:
- Databases can now be configured to have multiple proxies for
    improved performance. Note that when you upgrade the cluster to this
    version and then upgrade existing databases, the databases will be
    updated to use the Single proxy policy and Dense shard placement
    policy. For additional details, refer to [Multiple active
    proxies]().
- Support for Redis version 3.2 added. When you install or upgrade the
    cluster the new default version for Redis databases will be 3.2 and
    when you upgrade the databases they will be updated to this version.
    If you would like to change the default version to Redis 3.0, refer
    to the instruction in the [Upgrading
    databases]()
    If you would like to upgrade existing databases to the latest 3.0
    minor version, refer to the Known Issues section below.
- The cluster can now be configured to support both private and public
    IPs to connect to database endpoints through both public and private
    networks. For additional details, refer to [Private and Public
    Endpoints]().
- **rladmin status** command output has been enhanced to include an
    indication on which node rladmin is running by adding the '\*' sign
    next to the node entry, and to show the host name of the machine the
    node is running on.
- Users can now be assigned security roles to control what level of
    the databases or cluster the users can view and/or edit.

title: Changes

text:
- As result of adding the support for multiple proxies for a database,
    the following changes have been made:
    - When you upgrade the cluster to this version and then upgrade
          existing databases, the databases will be updated to use the
          Single proxy policy and Dense shard placement policy.
    - **rladmin status** command output has been updated.
    - **failover \[db \<db:id \| name\>\] endpoint \<id1 .. idN\>**
          and **migrate \[db \<db:id \| name\> \| node \<origin
          node:id\>\] endpoint \<id\> target_node \<id\>** commands are
          no longer relevant for databases using the **single \|
          all-master-shards \| all-nodes** proxy policy. Instead proxies
          can be bound or unbounded to databases as needed.
    - New **rladmin** commands were added, such as **bind** and
          **placement**.
- RLEC has been updated to remove the need to use **sudo** in runtime.
    You still need to be root or use **sudo** when initially installing
    RLEC.
- You no longer need to be root or use **sudo** to run the rladmin
    command, now it is preferred to be a non-privileged user that is
    member of the *redislabs* group to run the command.
- All cluster services are now run using the supervisor mechanism. As
    a result starting, stopping and restarting RLEC services should be
    done using **supervisorctl** command from the OS CLI.
- Linux OS vm.swappiness is now advised to be set to zero, for more
    information see [Disabling Swap in
    Linux]().

title: Important fixed issues since 4.3.0

text:
- RLEC-7542 - Add ability to create and manage role based user
    security
- RLEC-8283 - The cluster recovery process does not work properly
    when the cluster that needs to be recovered does not have a node
    with ID 1.
- RLEC-8284 - Add functionality to rladmin to mark a node as a quorum
    only node
- RLEC-8498 - Backup fails under rare conditions
- RLEC-8579 - rladmin supports uppercase for external_addr value
- RLEC-8656 - Fixed conflict with SELinux
- RLEC-8687 - Fixed issue where strong password requirements were not
    honored correctly.
- RLEC-8694 - DMC failed while creating DB with 75 (150 replicated)
    shards
- RLEC-8700 - Fixed issue with network split scenario
- RLEC-8833 - Fixed issue where in some cases endpoint were not
    getting new IPs after node replacement.
- RLEC-9069 - Fixed issue related to RHEL 7 and IPv6.
- RLEC-9156 - Fixed issue causing a full resync of data when a source
    or destination failure occurred.
- RLEC-9173 - Issue with writing data after master and replica failed
- RLEC-9235 - Issue with SSL connection error and self signed
    certificates
- RLEC-9491 - Fixed alerting issue due to incorrect measurement
- RLEC-9534 - Fixed issue with node remove command after RLEC
    uninstalled
- RLEC-9658 - Failed to import backup file from FTP server.
- RLEC-9737 - Fixed issue with backup process to use ephemeral
    storage when needed
- RLEC-9761 - UI had incorrect value increments
- RLEC-9827 - Server with a high number of cores and running RHEL can
    have issues running systune.sh
- RLEC-9853 - Fixed issues with logrotate on RHEL 7.1 so it runs as
    non-privileged user
- RLEC-9858 - If proxy crashed, in some cases this would prevent
    completion of redis failover process
- RLEC-9893 - DB recovery process doesn't recognize original rack
    name when in uppercase
- RLEC-9905 - x.509 certificate signed by custom CA cannot be loaded
    in UI
- RLEC-9925 - master endpoint and shards goes down if co-hosted with
    master of the cluster and the node goes down (single proxy policy)
- RLEC-9926 - Master shard could remain down if on the same node as
    the master of the cluster and the entire node goes down
- RLEC-10340 - Fixed a typo that crashed rladmin status output in
    some cases

Changes in 4.4.2-42:

- RLEC-11941 - Upgrade to 4.4.2-35 on RHEL6 - leash failed when
    python2.6 is installed
- RLEC-11994 - RLEC 4.4.2-35: the UI doesn't display the DBs with
    replication

Changes in 4.4.2 - 49

- RLEC-11209 - Unable to run upgrade due to running_actions check
- RLEC-12647 - Backup to S3 with periods in bucket name are failing
    in some cases

title: Known issues

text:
- **Issue:** When upgrading to this version from a previous RLEC
    version, **rladmin status** output will show the database status as
    having an old version. When you upgrade the Redis database (using
    **rladmin upgrade db** command) the Redis version will be updated to
    3.2 even if you updated the cluster's Redis default version to 3.0.
    **Workaround:** If you would like to cancel the old version
    indication in **rladmin status** without upgrading the Redis version
    to 3.2 you should run the **rladmin upgrade db** command with the
    **keep_current_version** flag which will ensure the database is
    upgraded to the latest 3.0 version supported by RLEC.
- **Issue:** RLEC-9200 - in a database configured with multiple
    proxies, if a client sends the MONITOR, CLIENT LIST or CLIENT KILL
    commands, only commands from clients connected from the same proxy
    are returned instead of all commands from all connections.
    **Workaround:** If you would like to get a result across all
    clients, you need to send the monitor command to all proxies and
    aggregate them.
- **Issue:** RLEC-9296 - Different actions in the cluster, like node
    failure or taking a node offline, might cause the Proxy policy to
    change Manual.
    **Workaround:** You can use the **rladmin bind \[db \<db:id \|
    name\>\] endpoint \<id\> policy \<single \| all-master-shards \|
    all-nodes\>** command to set the policy back to the required policy,
    which will ensure all needed proxies are bounded. Note that existing
    client connections might disconnected as result of this process.
- **Issue:** RLEC-8787 - In some cases when using the replica-of
    feature, if the source database(s) are larget than the target
    database, the memory limit on the target database is not enforced
    and that used memory of the target database can go over the memory
    limit set.
    **Workaround:** You should make sure that the total memory limit of all
    source databases is not bigger than the memory limit of the target
    database.
- **Issue:** RLEC-8487 - Some Redis processes stay running after
    purging RLEC from the machine and causes an attempt to reinstall
    RLEC to fail.
    **Workaround:** Run the purge process for a second time and ensure
    that the Redis processes were removed.
- **Issue:** RLEC-8747 - When upgrading to this version, if the UI is
    open in the browser the UI might not work properly after the
    upgrade.
    **Workaround:** Refresh the browser and the UI will return to work
    properly.
- **Issue:** In the Replica Of process, if the target database does
    not have replication enabled and it is restarted or fails for any
    reason, the data on the target database might not be in sync with
    the source database, although the status of the Replica Of process
    indicates that it is.
    **Workaround:** You must manually stop and restart the
    synchronization process in order to ensure the databases are in
    sync.
- **Issue:** In the Replica Of process, if the source database is
    resharded while the Replica Of process is active, the
    synchronization process will fail.
    **Workaround:** You must manually stop and restart the
    synchronization process after the resharding of the source database
    is done.
- **Issue:** In the Replica Of process, if there is very high
    traffic on the database the Replica Of process might be restarted
    frequently due to the "replica buffer" being exceeded. In this case,
    you will often see the status of the Replica Of process display as
    "Syncing".
    **Workaround:** You must manually increase the "replica buffer" size
    through rladmin. To find the appropriate buffer size please contact
    support at: <support@redislabs.com>.
- **Issue:** In a cluster that is configured to support rack-zone
    awareness, if the user forces migration of a master or replica shard
    through rladmin to a node on the same rack-zone as its corresponding
    master or replica shard, and later runs the rebalance process, the
    rebalance process will not migrate the shards to ensure rack-zone
    awareness compliance.
    **Workaround:** In the scenario described above, you must use
    rladmin to manually migrate the shard to a node on a valid rack-zone
    in order to ensure rack-zone awareness compliance.
- **Issue:** DNS doesn't change after having removed the external IP
    address.
    **Workaround:** Unbind IP from affected node and then bind it back.
- **Issue**: CCS gets an error and won't start
    if /var/opt/redislabs/persist/ does not exist.
    **Workaround**: Make sure this directory is not deleted and
    continues to exist.


title: Redis Enterprise Software 5.2.2 (August 2018)

title: Overview

text:
Redis Enterprise Software (RS) 5.2.2 is now available.

RS 5.2.2 is a minor version that includes important fixes and minor enhancements to Redis Enterprise 5.2.

title: Overview

text: If you are upgrading from a previous version, make sure to review the upgrade instructions before beginning the upgrade process. You can upgrade to RS 5.2.2 from RS 4.5 and above. If you have a version older than 4.5, you should first upgrade to version 5.0 (or at least 4.5).

title: New capabilities

text:
Support for Redis version 4.0.10
RediSearch Enterprise, which is installed with Redis Enterprise Software by default, has been updated to a newer version (1.4.0)

title: Important fixes

text:
- RED-21080 – Fixed the memory limit calculation for RoF databases
- RED-20825 – Updated the ‘RAM limit’ of RoF databases to a range between 10% and 100%
- RED-20506 – Fixed high CPU and File Descriptors utilization by the node watchdog process (node_wd)
- RED-20275 – Fixed wrong metrics values while importing a dataset into an RoF database
- RED-20214 – Fixed obstacles to login to the UI when using an LDAP integration
- RED-20162 – Fixed known limitation of being able to activate "Require SSL for All Communication" to Redis Enterprise CRDBs via Rest API without providing a certificate
- RED-19758 – Upgraded NGINX from 1.10.3 to 1.13.12
- RED-19415, RED-18945 – Improved support for Lettuce client with OSS Cluster enabled
- RED-19287 – Fixed a scenario of a stuck shard migration process
- RED-18459 – Updated the data persistence (AOF / Snapshot) of RoF databases to be handled, by default, by the replica shard/s
- RED-20541– Improved handling of aof file when its tail is corrupted (using aof-load-corrupt-tail flag)
- RED-21936 – Improved handling of CRDB configuration update when URL parameter was supplied at creation time
- RED-19760 – Added the capability to control the minimum TLS version that can be used for encrypting the Discovery Service data

title: Known limitations

text:
- When updating the general settings of a cluster, the ‘username’ and ‘password’ fields in the email server settings cannot be left empty. In case one wants to update the general settings and prefer to leave the ‘username’ and ‘password’ fields empty, the REST API should be used.
- An issue prevents the user from defining ‘min_data_TLS_version’ on the source cluster when working with Replica Of or CRDB.


title: Redis Enterprise Software Release Notes 5.2 (June 2018)

title: Overview

text:
Redis Enterprise Software (RS) 5.2 is now available. Key features
include new data types and casual consistency for active-active (also
known as the Redis CRDT or CRDB Conflict-free Replicated Database), as
well as enhanced security features.

title: Overview

text:
If you are upgrading from a previous version, make sure to review the
upgrade instructions before beginning the upgrade process. You can
upgrade to RS 5.2 from RS 4.5 and above. If you have a version older
than 4.5, you should first upgrade to version 5.0 (or at least
4.5).

title: New features

title: Active-Active Redis (CRDB) supports sorted sets and lists {#activeactive-redis-crdb-supports-sorted-sets-and-lists}

text:
RS 5.2 adds active-active Redis (CRDB) support for Sorted Sets and
Lists. Now all major Redis data types are supported with CRDT, so you
can use Redis Enterprise in an active-active manner for all your Redis
use cases, with seamless conflict resolution. [Click here](develop/develop-for-aa/)
for more information about how to develop applications with
geo-replicated CRDBs.

title: Causal consistency in Active-Active Redis (CRDB) {#causal-consistency-in-activeactive-redis-crdb}

text:
casual consistency in active-active Redis (CRDB) guarantees that the
order of operations on a specific key will be maintained across all CRDB
instances. For instance, if operations A and B were applied on the same
key, and B was performed after the effect of A was observed by the CRDB
instance that initiated B, then all CRDB instances would observe the
effect of A before observing the effect of B.

This way, any causal relationship between operations on the same key is
also observed and maintained by every replica. Such capability is
important for various applications, e.g. social network status updates
or chat applications (assuring that the chronology of messages doesn't
get mixed up). For more information, [click
here]().

title: Enhanced security features

text:
- **Admin action audit trail**

Management actions performed with Redis Software are audited in order
to fulfill two major objectives: (1) make sure that system management tasks
are appropriately performed and/or monitored by the Administrator(s),
and (2) facilitate compliance with regulatory standards such as HIPAA,
SOC2, PCI, etc.

In order to fulfill both objectives, audit records contain the
following information: (1) who performed the action, (2) what exactly
was the performed action, (3) when the action was performed, and (4)
whether  the action succeeded.

To get the list of audit records/events, one can use the REST API or
the Log page in the UI; the Log page displays the system and user events
regarding alerts, notifications and
configurations.

- **Ability to disable TLS versions**

Version 5.2 introduces the option to set the minimum TLS version that
can be used for encrypting the various flows. You can do so using the
REST API or the following rladmin commands:

- For the management UI and the REST API:

[code example]

- For the data path encryption:

[code example]

Note that communications that use older TLS versions will not be
allowed.

- **HTTPS enforcement**

With this feature, you can restrict REST API  access to only those
using HTTPS. In order to do so, use the REST API or the following
rladmin command:

[code example]

title: Additional capabilities

text:
- Support for Redis version 4.0.9
- Fixes for Redis important security issues related to the Lua
    scripting engine

title: Information

text:
- The end-of-service-life (EOSL) for Redis Enterprise Software 4.4.X
    is June 30th, 2018, in accordance with our [published
    policy]().
    We recommend that customers running version 4.4 or below
    upgrade to the latest version.

title: Important fixes

text:
- RS19755 - Added the ability to enforce HTTPS communication when
    accessing REST API
- RS19571 - Fixed RHEL installation when FIPS mode is
    enabled
- RS19490 - Fixed a failure while upgrading from 4.5 to
    5.0.2
- RS19475 - Added the ability to disable TLS versions for the
    control and data paths
- RS18712 - Fixed a failure in endpoint failover

- RS17208 - Added an option to disable Redis commands via Rest
    API
- RS14973 - Updated NGINX.conf template to turn off exposing the
    server version
- RS11181 - Set file permissions of log files, redis-conf files, rdb
    files and their rotations to "640"

title: Known limitations

text:
- After creating Redis Enterprise CRDBs which "Require SSL for CRDB
    communication only," one can set definitions via Rest API to
    activate "Require SSL for All Communication" without providing a
    certificate. In such case, connections to the cluster will be
    blocked.

code: rladmin> cluster config min_control_TLS_version [version, e.g. 1.2]

section_id: enhanced-security-features

code: rladmin> cluster config min_data_TLS_version [version, e.g. 1.2]

code: rladmin> cluster config http_support [disabled | enabled]


title: Redis Enterprise Software Release Notes 5.3 BETA (July 2018)

title: Overview

text:
Redis Enterprise Software (RS) 5.3 is now available.

RS 5.3 is a preview version that includes all the capabilities of Redis Enterprise 5.2, plus support for Redis 5.0 with the new data type, which is called Streams.

title: New features

text: RS 5.3 adds support for Redis 5.0 and is based on its latest Release Candidate (RC3). Redis 5.0 exposes the new Redis Streams data type, which provides a super fast in-memory abstraction of an append-only log. For more information and usage examples, check out the Streams documentation here.

title: Preview considerations

text: As a preview version, we do not support upgrading to RS 5.3 from any previous version or upgrading from RS 5.3 to any future version. In addition, we do not commit to fixing bugs in RS 5.3.

title: Known limitations

text: The RS 5.3 preview version does not support Enterprise Modules (- RediSearch, ReJSON and ReBloom), Auto Tiering or active-active Redis (CRDB).


title: Redis Enterprise Software Release Notes 5.4.10 (December 2019)

title: Overview

text:
[Redis Enterprise Software (RS) 5.4.10](https://redislabs.com/redis-enterprise/software/downloads/#downloads) is now available.
This release includes an improved synchronization mechanism for Active-Active Redis and Replica-of, several enhancements, and bug fixes.

title: Overview

text: Follow these [instructions]() for upgrading to RS 5.4.10 from RS 5.0 and above.

title: New features

title: Synchronization mechanism in Active-Active Redis and Replica-of

text:
RS 5.4.10 incorporates the improved [Redis synchronization mechanism](#syncer-process) ([PSYNC2]()) for Active-Active Redis (CRDB) and Replica-of.

As a result, failure scenarios in any A-A replica (and the source database of Replica-of), require only partial synchronization between the cross-region replicas instead of full synchronization that can be costly in time and bandwidth.

title: RS on RHEL 7 supports OpenSSL 1.0.2 and up

text:
To keep RS secure and keep our internal libraries up-to-date, starting from RS 5.4.10 our RHEL 7 installations require a minimum of OpenSSL 1.0.2.

When you install or upgrade RS 5.4.10 on RHEL 7 with older version of OpenSLL, the installation fails with the error:

[code example]

If you see this error, upgrade to OpenSSL 1.0.2 or higher before you install RS.

title: Additional capabilities

text:
- The following new GA releases of Redis Modules are bundled in RS 5.4.10:
    - RedisBloom, version 2.0.3
    - RedisSearch, version 1.4.18
    - RedisJson, version 1.0.4
    - RedisGraph, version 1.2.2
    - RedisTimeSeries, version 1.0.3
- Version 5.0.5 of Redis OSS, along with a fix to a corruption related to the HyperLogLog (that is part of [Redis 5.0.6](https://raw.githubusercontent.com/antirez/redis/5.0/00-RELEASENOTES)) are merged into RS 5.4.10.
- Using REST API, you can retrieve various license details such as activation date, expiration date,and the number of licensed shards. To get these details, run:

    `curl -v -u <user>:<password> https://localhost:9443/v1/license`

- Updated PDNS version from 4.1.5 to 4.1.13.

title: Information

text:
- End of Life (EOL) for Redis Enterprise Software 5.4, as well as for Redis Modules and previous RS versions, can be found [here](https://docs.redis.com/latest/rs/installing-upgrading/product-lifecycle).
- Google Chrome browser on macOS Catalina requires self-signed certificate generated after June 2019 to include the extendedKeyUsage field in order to connect to the RS admin console.
    If you use a self-signed certificate that does not include this field, [update the self-signed certificate]().
- When you upgrade an Active-Active Redis with active AOF from version RS 5.4.2 or lower to version RS 5.4.4 or higher:
    - If replication is enabled, you must run the BGREWRITEAOF command on all replica shards after the upgrade.
    - If replication is not enabled, you must run the BGREWRITEAOF command on all shards after the upgrade.

title: Important fixes

text:
- The titles of the ‘rladmin status nodes’ command output were updated from ‘RAM’ to ‘FREE_RAM’ (the amount of RAM in the node that is currently not used) and from ‘AVAILABLE_RAM’ to ‘PROVISIONAL_RAM’ (the amount of RAM in the node that can be provisioned).
- RS31492 - Upgraded dependent libraries: [python-cryptography to version 2.7](https://github.com/redislabsdev/Redis-Enterprise/pull/4209/commits/3b5a408696b91a0b545f670ce35bb920d5a4beb4); [NGINX to version 1.16.0](https://github.com/redislabsdev/Redis-Enterprise/pull/4209/commits/4ab171d4467bd91c6b38cec81da3c52a6113a787); [PyYaml to version 5.1.2](https://github.com/redislabsdev/Redis-Enterprise/pull/4209/commits/11e814ae0d14c85b248bc7451edbbbcb71f3858f); [python-requests to version 2.22.0](https://github.com/redislabsdev/Redis-Enterprise/pull/4209/commits/0e2ab74b4e2b2dc9872a86fbdb5593f5354eb103); [urllib3 to version 1.25.3](https://github.com/redislabsdev/Redis-Enterprise/pull/4209/commits/038e44163d7dc1fed4e3b67cb252a84583c2f44a)
- RS31187 - Upgraded the internal Python interpreter to version 2.7.16
- RS33042 - Fixed Support Package to contain complete SLOWLOG information
- RS32699 - Avoided unnecessary restart and failover of Redis processes when Active-Active database is upgraded
- RS32061 - Improved support of the Redis WAIT command
- RS31759 - Fixed failure during database import
- RS31747 - Fixed failure in upgrade from version 5.0.0-31 to 5.4.6-11
- RS30063 - Fixed the upgrade process when WatchdogAPI fails to bind to its port
- RS31477 - Fixed wrong calculation of node’s ‘AVAILABLE_RAM’ (‘PROVISIONAL_RAM’) as displayed the output of ‘rladmin status nodes’ command
- RS30165 - Fixed failover scenario that did not take place during node restart
- RS29250 - REST API documentation was updated to include the SFTP and Mount Point backup/export options
- RS27327 - Improved the backup timing when using the database parameter of ‘backup_interval_offset’ through the REST API
- RS33883 - HCSAN command in Active-Active Redis updated to return Integer instead of a String.
- Fixed a limitation so Redis 5 and Redis 4 can be selected as the Redis version to use CRDB and RoF

title: Known limitations

title: Upgrade

text:
- [RS 5.4.2]() introduced new Active-Active Redis (CRDB) capabilities
    that improve its compatibility with open source Redis.
    Now the string data-type in Active-Active Redis (CRDB) is implicitly and dynamically typed, just like open source Redis.
    To use the new capabilities on nodes that are upgraded from version RS 5.4.2 or lower,
    you must [upgrade the CRDB protocol]().
- Before you upgrade a database with RediSearch Module to Redis 5.0,
    you must [upgrade the RediSearch Module]() to version 1.4.2 or above.
- Node upgrade fails if the SSL certificates were configured in version 5.0.2 or above
    by manually updating the certificates on the disk instead of [updating them through the API]().
    For assistance with this issue, [contact Redis support](https://redislabs.com/company/support/).
- We recommend that you test module upgrade commands in a test environment before you upgrade modules in a production environment.
    The module upgrade arguments are not validated during the upgrade process and incorrect arguments can cause unexpected downtime.
- Starting from RS 5.4.2, to preserve the current Redis major.minor version during database upgrade you must use the `keep_redis_version` option instead of `keep_current_version`.

title: Cluster API

text:
- The API for removing a node is updated in RS 5.4.2 or higher. The API call must include json data and the "Content-Type: application/json" header. For example:

    `curl -X POST -H "Content-Type: application/json" -i -k -u user@redislabs.com:password https://localhost:9443/v1/nodes/3/actions/remove --data "{}"`

title: Discovery service

text: - For [Redis Sentinel (Discovery Service)](), every database name must be unique across the cluster.

title: Redis commands

text:
- The capability of disabling specific Redis commands does not work on commands specific to Redis Modules.
- The CLIENT ID command cannot guarantee incremental IDs between clients that connect to different nodes under multi proxy policies.
- CLIENT UNBLOCK command is not supported in RS 5.4 and above
- Starting from RS 5.4.2 and after upgrading the CRDB, TYPE command for string data-type in CRDBs return "string" (OSS Redis standard).

code:
Error: Package: redislabs-5.4.10-1.rhel7.x86_64 (/redislabs-5.4.10-1.rhel7.x86_64)
        Requires: libcrypto.so.10(OPENSSL_1.0.2)(64bit)


title: Redis Enterprise Software Release Notes 5.4.14 (February 2020)

title: Overview

text:
[Redis Enterprise Software (RS) 5.4.14](https://redislabs.com/redis-enterprise/software/downloads/#downloads) is now available.
This release bundles OSS Redis 5.0.7 and includes new Redis Modules versions, several enhancements, and bug fixes.

title: Overview

text: Follow these [instructions]() for upgrading to RS 5.4.14 from RS 5.0.2 and above.

title: New features

text:
- Version [5.0.7](https://raw.githubusercontent.com/antirez/redis/5.0/00-RELEASENOTES) of OSS Redis is merged into RS 5.4.14.
- The following GA releases of Redis Modules are bundled in RS 5.4.14:
    - [RedisBloom](https://redislabs.com/redis-enterprise/redis-bloom/), version 2.2.1 (updated, [release notes](release-notes/redisbloom/redisbloom-2.2-release-notes.md#redisbloom-221-january-2020))
    - [RedisGraph](https://redislabs.com/redis-enterprise/redis-graph/), version 2.0.1 (updated, [release notes](release-notes/redisgraph/redisgraph-2.0-release-notes.md#redisgraph-20-ga-201---january-2020))
    - [RedisJSON](https://redislabs.com/redis-enterprise/redis-json/), version 1.0.4 (update, [release notes](release-notes/redisjson/redisjson-1.0-release-notes))
    - [RediSearch](https://redislabs.com/redis-enterprise/redis-search/), version 1.4.25 (updated, [release notes](release-notes/redisearch/redisearch-1.4-release-notes.md#redisearch-1425-march-2020))
    - [RedisTimeSeries](https://redislabs.com/redis-enterprise/redis-time-series/), version 1.2.3 (updated, [release notes](release-notes/redistimeseries/redistimeseries-1.2-release-notes))

title: Additional capabilities

text:
- Added the ability to retrieve license details with a REST API command.
    Now you can get your license details from the admin console (settings > general) or from the REST API command:

    `GET https://localhost:9443/v1/license`

    The REST API response includes:

    - license - The cluster’s name (FQDN) in the key string
    - expired - If the cluster key is expired (True or False)
    - activation_date - The date of the cluster key activation
    - expiration_date - The date of the cluster key expiration
    - shards_limit - The number of shards allowed by the cluster key
- Added Flush command in the UI console for Active-Active databases. The command flushes the data from all participating clusters.
- Updated `rladmin upgrade module` command so module arguments are optional. When you upgrade the module for a database, you can either:
    - Specify the module arguments to replace the existing arguments
    - Specify the `keep_module_args` flag to use the existing arguments

    Examples:

    1. To upgrade the version of RediSearch to 10017 and replace the module arguments:

        `rladmin upgrade module db_name MyAwesomeDB module_name ft version 10017 module_args "PARTITIONS AUTO"`

    1. To upgrade RedisBloom to version 10100 and remove the current module arguments:

        `rladmin upgrade module db_name MyDB module_name bf version 10100 module_args " "`

    1. To upgrade RedisJSON to 10002 and use the current module arguments:

        `rladmin upgrade module db_name MyDB module_name ReJSON version 10002 keep_module_args`

- Upgraded `js-yaml` version to 3.13.1, and `lodash` version to 4.17.15 (RS31819)
- Added an alert for actions that run for an extended period of time. For example, a notification is sent when an action like updating database property runs for more than a configurable threshold. Default value is set to 24 hours.

title: Information

title: Important fixes

text:
- RS23396 - Improved the disconnection mechanism in case of inactive UI session
- RS27924 - Added descriptive error messages in the UI console when validating the license
- RS29968 - Improved internal mechanism to better support high scale of clients connections
- RS35675 - Updated the upgrade process of Active-Active Redis databases to save causal consistency and encryption flags
- RS36922 - Fixed an issue in a specific cluster upgrade scenario from versions earlier than RS 5.4.0 to RS 5.4.0 or higher

title: Known limitations

title: Upgrade

text:
- When you upgrade a cluster from version 5.0.2-20 to version 5.4.14, you must first upgrade to version 5.2.2 and then to version 5.4.14.
- [RS 5.4.2]() introduced new Active-Active Redis (CRDB) capabilities
    that improve its compatibility with open source Redis.
    Now the string data-type in Active-Active Redis (CRDB) is implicitly and dynamically typed, just like open source Redis.
    To use the new capabilities on nodes that are upgraded from version RS 5.4.2 or lower,
    you must [upgrade the CRDB protocol]().
- Before you upgrade a database with RediSearch Module to Redis 5.0,
    you must [upgrade the RediSearch Module]() to version 1.4.2 or above.
- Node upgrade fails if the SSL certificates were configured in version 5.0.2 or above
    by manually updating the certificates on the disk instead of [updating them through the API]().
    For assistance with this issue, [contact Redis support](https://redislabs.com/company/support/).
- We recommend that you test module upgrade commands in a test environment before you upgrade modules in a production environment.
    The module upgrade arguments are not validated during the upgrade process and incorrect arguments can cause unexpected downtime.
- Starting from RS 5.4.2, to preserve the current Redis major.minor version during database upgrade you must use the `keep_redis_version` option instead of `keep_current_version`.

title: Cluster API

title: Discovery service

title: Redis commands


title: Redis Enterprise Software Release Notes 5.4.2 (April 2019)

title: Overview

text:
[Redis Enterprise Software (RS) 5.4.2](https://redislabs.com/redis-enterprise/software/downloads/#downloads) is now available.
This release improves the compatibility of Active-Active Redis (CRDB) with open source Redis, adds SFTP and Mount Points as backup destinations, email alerting and a number of other enhancements and bug fixes.

title: Overview

text:
Follow these [instructions]() for upgrading to RS 5.4.2 from RS 5.0 and above.
If you have a version older than 5.0, you must first upgrade to version 5.2 (or at least 5.0).

title: New features

title: Active-Active Redis (CRDB) {#activeactive-redis-crdb}

text:
RS 5.4.2 introduces new Active-Active Redis (CRDB) capabilities which improve its compatibility with open source Redis.
This simplifies the progress of migration from open source Redis to Active-Active Redis:

1. The string data-type in CRDB is now implicitly and dynamically typed, just like open source Redis.
1. Geospatial data is now supported in CRDB.

These changes required upgrading the internal structures of CRDB and the communication protocol between the CRDB replicas.
To take advantage of these updates with existing CRDBs you must [upgrade the CRDB protocol](#upgrading-crdbs/).

title: New backup destinations - SFTP and mount point

text:
The storage options for [periodic database backup](), [data export](https://docs.redis.com/latest/rs/databases/import-export/export-data.md), and [data import](https://docs.redis.com/latest/rs/databases/import-export/import-data/) are extended to include:

- SFTP - a secured and well accepted protocol
- A local mount path that can point to network storage

These new options are in addition to the existing backup locations of FTP, AWS S3 and OpenStack Swift.

title: Email alerts per database (per team member)

text:
Improved distribution of [email alerts]() for cluster or database alerts.
The cluster administrator can define, for each team member, the specific databases to receive alerts for, and whether to get the cluster alerts.

title: Optional client authentication (TLS)

role: parameters

text:
You can now fine tune the [TLS configuration](), and ease certificates management by excluding client authentication enforcement,
so that the database clients, such as applications or other clusters, can connect to your database without authentication.

title: Node maintenance mode

text:
When you do hardware or operating system maintenance on a server that hosts an Redis Enterprise node,
it is important that you move all of the shards on that node to another node to protect the data.
Starting with RS 5.4.2 you can use [maintenance mode]() to handle this process simply and efficiently.

title: Additional capabilities

text:
- Support for open source Redis version 5.0.4
- Viewer roles were further limited to improve security compliance. The DB Viewer and Cluster Viewer roles cannot view the Redis password of a database. The DB Viewer role also cannot view the ‘log’ screen.

These improvements are also included in the REST API and are breaking-changes.
If you use the relevant API requests with a DB Viewer or Cluster Viewer role, make sure that you update it accordingly.

- External user credentials for periodic backup destinations are now hidden.
    In REST API responses the password is hashed and in the admin console the password is displayed as asterisks.

title: Information

text: - For Redis Enterprise Software 5.4 End of Life (EOL), as well as for previous Redis Enterprise Software versions, see [product lifecycle]().

title: Important fixes

text:
- RS26985 - Fixed a failure of a DB with all-nodes policy, when a node is rebooted
- RS26433 - Fixed a scenario in which the CRDB sync stopped on one of the participating clusters
- RS25968 - Fixed a redis crash on RoF cluster
- RS25835 - Fixed a failure in periodic backup when AOF rewrite is in progress on the same shard
- RS25558 - Enabled updating absolute path in periodic backup FTP setup
- RS25381 - Fixed a race condition while updating a database parameter
- RS24188 - Fixed a failure during database upgrade
- RS23508 - Fixed a failure in ‘rladmin status’ command
- RS22485 - Fixed irregularities in service after increasing the size of a database which uses OSS cluster API

title: Known limitations

title: Upgrade

text:
- Before you upgrade a database with RediSearch Module to Redis 5.0,
    the RediSearch [Module must be upgraded]() to version 1.4.2 or above.
- Node upgrade fails if the SSL certificates were configured in version 5.0.2 and above by updating the certificates on the disk instead of using the new API.
    For assistance with this issue, see [SSL/TLS certificate updates]() in our documentation or [contact Redis support](https://redislabs.com/company/support/).
- We recommend that you test module upgrade commands in a test environment before you upgrade modules in a production environment.
    The module upgrade arguments are not validated during the upgrade process and incorrect arguments can cause unexpected downtime.
- The rladmin option to use to preserve the current Redis major.minor version during database upgrade is now `keep_redis_version`, instead of `keep_current_version`.

title: Cluster API

text:
- The API for node removal was updated. It must include json data, and "Content-Type: application/json" header. For example:

    [code example]

title: Redis commands

text:
- The capability of disabling specific Redis commands does not work on Redis Module specific commands.
- The CLIENT ID command cannot guarantee incremental IDs between clients that connect to different nodes under multi proxy policies.
- CLIENT UNBLOCK command is not supported in RS 5.4 and RS 5.4.2
- Starting from RS 5.4.2 and after upgrading the CRDB, TYPE command for string data-type in CRDBs return "string" (OSS Redis standard).

code: curl -X POST -H "Content-Type: application/json" -i -k -u user@redislabs.com:passsword https://localhost:9443/v1/nodes/3/actions/remove --data "{}"

section_id: cluster-api


title: Redis Enterprise Software Release Notes 5.4.4 (June 2019)

title: Overview

text:
Redis Enterprise Software (RS) 5.4.4 is now available.
This release enables the functionality of Active-Active Redis (CRDB) combined with RoF (Auto Tiering),
supports the creation of Redis databases with multiple modules,
and adds other enhancements and bug fixes.

title: Overview

text:
Follow these [instructions for upgrading]() to RS 5.4.4 from RS 5.0 and above.
If you have a version older than 5.0, you must first upgrade to version 5.2 (or at least 5.0).

title: New features

title: Active-Active Redis with RoF {#activeactive-redis-with-rof}

text:
RS 5.4.4 lets you create Active-Active Redis databases (CRDBs) with Auto Tiering and get the benefits of geo-distributed Redis databases along with the significant cost savings of using Auto Tiering.

You must select **Redis 5** as the Redis version to use CRDB and RoF.

title: Support for multiple modules

role: compatibility

text:
RS 5.4.4 supports the creation and management of Redis databases with a combination of any of the following GA modules:

- RediSearch (GA)
- RedisGraph (GA)
- RedisBloom (GA)
- RedisJSON (GA)

To upgrade databases with multiple modules, you can use the `rladmin upgrade` command.

The syntax for the `rladmin upgrade` command now requires that the module_args parameter be written inside quotation marks.

- To upgrade only the modules within an existing database, for example with RedisBloom (bf) and RedisJSON:

    [code example]

- To upgrade a database with its modules, for example db1 with RediSearch and RedisGraph:

    [code example]

You can also upgrade the modules with the REST API.

- To upgrade multiple modules, enter the details of each module in the `modules` parameter:

    [code example]

- To upgrade a single module, you can either:
    - Enter the details of the module in the `modules` parameter
    - Enter the details of the module without the `modules` parameter, as in previous releases

title: Additional capabilities

text:
- Support for persistence of AOF every 1 second in Active-Active Redis (CRDB), in addition to AOF every write.
    We recommend that you use AOF every 1 second for the best performance during the initial CRDB sync of a new replica.
- NGINX version updated to 1.14.2

title: Information

text: - Stay up to date with the [End of Life (EOL) Policy]() for RS 5.4 and all previous RS versions.

title: Important fixes

text:
- RS26508 - Fixed redis-cli failure for a specific CRDB data type.
- RS29191 - Fixed a failure when removing a replica from a CRDB.
- RS29097 - Fixed a misconfiguration when using SFTP backup and encounter a node failure.
- RS28286 - Updated `SETEX` and `PSETEX` commands output of CRDB to match Redis outputs.
- RS26984 - Fixed metrics_exporter reports for node and shard level metrics.
- RS19854 - Fixed uploading a Redis Module so you can upload a Redis Module when the admin console is connected to any node.
- RS29238 - Improved the compression performance in CRDB.

title: Known limitations

title: Upgrade

text:
- [RS 5.4.2]() introduced new Active-Active Redis (CRDB) capabilities that improve its compatibility with open source Redis. Now the string data-type in CRDB is implicitly and dynamically typed, just like open source Redis. To use the new capabilities on nodes that are upgraded from version RS 5.4.2 or lower, you must [upgrade the CRDB protocol]().
- Before you upgrade a database with RediSearch Module to Redis 5.0, you must [upgrade the RediSearch Module]() to version 1.4.2 or above.
- Node upgrade fails if the SSL certificates were configured in version 5.0.2 or above by manually updating the certificates on the disk instead of [updating them through the API](). For assistance with this issue, [contact Redis support](https://redislabs.com/company/support/).
- We recommend that you test module upgrade commands in a test environment before you upgrade modules in a production environment. The module upgrade arguments are not validated during the upgrade process and incorrect arguments can cause unexpected downtime.
- Starting from RS 5.4.2, to preserve the current Redis major.minor version during database upgrade you must use the `keep_redis_version` option instead of `keep_current_version`.

title: Subscriptions

text: - If a user subscribes to a channel during recovery of a CRDB from AOF, the user receives old messages that are stored in the AOF file.

title: Cluster API

text:
- The API for removing a node is updated in RS 5.4.2 or higher. The API call must include json data and the "Content-Type: application/json" header. For example:

    [code example]

title: Redis commands

text:
- The capability of disabling specific Redis commands does not work on commands specific to Redis Modules.
- The CLIENT ID command cannot guarantee incremental IDs between clients that connect to different nodes under multi proxy policies.
- CLIENT UNBLOCK command is not supported in RS 5.4.x
- Starting from RS 5.4.2 and after upgrading the CRDB, TYPE command for string data-type in CRDBs return "string" (OSS Redis standard).

code: rladmin upgrade module db_name db1 module_name bf version 10003 module_args "" module_name ReJSON version 10001 module_args ""

section_id: support-for-multiple-modules

code: rladmin upgrade db db1 and module module_name redisearch version 103 module_args "ON_TIMEOUT FAIL NOGC" and module module_name graph version 10016 module_args ""

code: curl -X POST -u "demo@redislabs.com:password" -H "Content-Type: application/json" -d '{"modules":[{"module_name": "ReJSON", "current_module": "<module_uid>", "new_module": "<module_uid>", "new_module_args": "", "current_semantic_version":"1.0.4"}, {"module_name":"ft","current_module":"<module_uid>","new_module": "<module_uid>","current_semantic_version":"1.4.3", "new_module_args":"PARTITIONS AUTO"}], "force_restart":true}' https://127.0.0.1:9443/v1/bdbs/2/modules/upgrade


title: Redis Enterprise Software Release Notes 5.4.6 (July 2019)

title: Overview

text:
[Redis Enterprise Software (RS) 5.4.6](https://redislabs.com/redis-enterprise/software/downloads/#downloads) is now available.
This release includes the latest version of Redis 5 (5.0.5), bundles the GA release of the new RedisTimeSeries module,
and adds other enhancements and bug fixes.

title: Overview

text:
Follow these [instructions]() for upgrading to RS 5.4.6 from RS 5.0 and above.
If you have a version older than 5.0, you must first upgrade to version 5.2 (or at least 5.0).

title: New features

title: Time series

text: New GA release of the [RedisTimeSeries](https://redislabs.com/blog/redistimeseries-ga-making-4th-dimension-truly-immersive/) (version v1.0.0) module is bundled in RS 5.4.6.

title: Modules versions

text:
Updated versions of GA modules:

- RedisTimeSeries  - v1.0.0 (new module)
- RedisBloom   -  v2.0.0 (version update)
- RediSearch  -  v1.4.11 (version update)
- RedisGraph  -  v1.2.2 (no change)
- RedisJSON  -  v1.0.3 (no change)

title: Additional capabilities

text:
- Latest version of Redis 5 (5.0.5) was merged into RS 5.4.6.
- If a user subscribes to a channel during recovery of a Active-Active Redis (CRDB) from an Append Only File (AOF), the user receives only the new messages.
    (Fixes known limitation from RS 5.4.4)
- CROSSSLOT behavior now matches Redis OSS behavior for accessing multiple keys in a single command.
    Now, when you use CRC16 hash function (default), you can pass a command for different keys/tags that are mapped to the same slot. (RS23189)
- Cluster upgrade process was improved so that the duration of the cluster upgrade process reduced.

title: Information

text:
- End of Life (EOL) for Redis Enterprise Software 5.4, as well as for Redis Modules and previous RS versions,
    can be found [here]().

title: Important fixes

text:
- RS28679 - Syncer and peers related statistics for Active-Active Redis (CRDB),
    which are already available with the REST API, are exposed through Prometheus.
- RS28946 - Metrics exporter related minor memory leak fix.
- RS26312 - Ports handling during installation fix.
- RS31703 - Fixed performance issue with MSET command.

title: Known limitations

title: Upgrade

text:
- [RS 5.4.2]() introduced new Active-Active Redis (CRDB) capabilities
    that improve its compatibility with open source Redis.
    Now the string data-type in Active-Active Redis (CRDB) is implicitly and dynamically typed, just like open source Redis.
    To use the new capabilities on nodes that are upgraded from version RS 5.4.2 or lower,
    you must [upgrade the CRDB protocol]().
- Before you upgrade a database with RediSearch Module to Redis 5.0,
    you must [upgrade the RediSearch Module]() to version 1.4.2 or above.
- Node upgrade fails if the SSL certificates were configured in version 5.0.2 or above
    by manually updating the certificates on the disk instead of [updating them through the API]().
    For assistance with this issue, [contact Redis support](https://redislabs.com/company/support/).
- We recommend that you test module upgrade commands in a test environment before you upgrade modules in a production environment.
    The module upgrade arguments are not validated during the upgrade process and incorrect arguments can cause unexpected downtime.
- Starting from RS 5.4.2, to preserve the current Redis major.minor version during database upgrade you must use the `keep_redis_version` option instead of `keep_current_version`.

title: Cluster API

title: Redis commands

text:
- The capability of disabling specific Redis commands does not work on commands specific to Redis Modules.
- The CLIENT ID command cannot guarantee incremental IDs between clients that connect to different nodes under multi proxy policies.
- CLIENT UNBLOCK command is not supported in RS 5.4 and above
- Starting from RS 5.4.2 and after upgrading the CRDB, TYPE command for string data-type in CRDBs return "string" (OSS Redis standard).


title: Redis Enterprise Software Release Notes 5.4 (December 2018)

title: Overview

text: Redis Enterprise Software (RS) 5.4 is now available. RS 5.4 adds support for Redis 5.0 (GA) with the new Redis Streams data type.

title: Overview

text: You can upgrade to RS 5.4 from RS 5.0 and above according to the [upgrade instructions](). If you have a version older than 5.0, you should first upgrade to version 5.2 (or at least 5.0).

title: New features

title: Redis 5.0 GA - Redis Streams

text: RS 5.4 adds support for Redis 5.0 (GA version- 5.0.2), which introduces the new [Redis Streams]() data type. Redis Streams models a log data structure in-memory and implements additional powerful operations, such as Consumer Groups.

title: Redis graph module

text:
Starting from RS 5.4, Redis Graph, a new Redis Enterprise Module that introduces the world's fastest graph database, is an integral part of Redis Enterprise package.

RedisGraph is the first queryable [Property Graph](https://github.com/opencypher/openCypher/blob/master/docs/property-graph-model.adoc) database to use [sparse matrices](https://en.wikipedia.org/wiki/Sparse_matrix) to represent the [adjacency matrix](https://en.wikipedia.org/wiki/Adjacency_matrix) in graphs and [linear algebra](http://faculty.cse.tamu.edu/davis/GraphBLAS.html) to query the graph.

title: Active-Active Redis (CRDB) - Creation in non-clustering mode {#activeactive-redis-crdb-creation-in-nonclustering-mode}

text:
In RS 5.4 you can [create Active-Active databases (CRDBs)]() in a non-clustering mode. As a result, the following creation options are allowed:

1. Clustering mode - Creates a CRDB that consists of any number of shards in a clustering mode and is subject to [multi-key commands limitations]().
1. Non-clustering mode - Creates a CRDB that consists of one shard only in a non-clustering mode so that [multi-key command limitations]() do not apply.

title: High availability for replica shards

text:
When [replica high availability]() is enabled and a master shard fails, a replica (formerly _slave_) shard is automatically promoted to a master shard to maintain data availability. This creates a single point of failure until a new replica shard is manually created.

RS 5.4 expands the high availability capabilities by adding the ability to automatically avoid this single point of failure by configuring the cluster to automatically migrate the replica shard to another available node. In practice, replica migration creates a new replica shard and replicates the data from the master shard to the new replica shard.

*_Note that just as is the case with the Redis open-source project, Redis is in the process of changing the "master-replica" terminology to "master-replica" everywhere, including within our documentation._

title: Additional capabilities

text: - Support for new operating systems- Ubuntu 18.04 and RHEL 7.6.

title: Product version lifecycle

text: - The End of Life (EOL) for Redis Enterprise Software 4.5.X was November 30th, 2018, in accordance with our [published policy](). We recommend that customers with version 4.5 or below upgrade to the latest version.

title: Important fixes

text:
- RS23616 - Fixed a failure when updating the memory limit of RoF database.
- RS22871 - Fixed a certificate verify failure after nodes upgrade.
- RS2862 - Improved admin console performance in case multiple browsers or windows are directed to the admin console.
- RS22751 - Fixed an issue in the backup process which caused temporary service outage.
- RS22636 - Fixed Redis process failure when a ReJSON Module's command is executed.
- RS22601 - Fixed a failure during shard migration procedure.
- RS22478 - Fixed a failure in replica-of process between two databases with ReBloom Module.
- RS21974 - SMTP username and password are not mandatory in the email server settings when there is no need for authentication.
- RS21801 - Fixed admin console issues when cluster is configured with FIPS compliance.
- RS21772 - Fixed a failure when trying to update a database's endpoint policy to all-master-shards.
- RS19842 - Updated permissions of some internal files.
- RS19433 - Improved RAM eviction process for RoF databases.
- RS18875 - Added the ability to upgrade database gradually, few shards at a time.
- RS15207 - Fixed a failure during re-shard operation.

title: Known limitations

title: Installation

role: setup

text: - In default Ubuntu 18.04 installations, port 53 is in use by systemd-resolved (DNS server). In such a case, the system configuration must be changed to make this port available before running RS installation.

title: Upgrade

text:
- Before you upgrade a database with the RediSearch module to Redis 5.0, you must [upgrade the RediSearch module on that DB]() to 1.4.2 or higher. We recommend that you upgrade the RediSearch module before you upgrade the cluster to RS 5.4.
- Node upgrade fails if SSL certificates were configured in version 5.0.2 and above by updating the certificates on the disk instead of using the new API. For assistance with this issue, please [contact Redis support](https://redislabs.com/company/support/).

title: Cluster API

text: - Removed the deprecated argument `backup_path` from cluster API. To create or update BDBs, please use `backup_location`.

title: Redis commands

text:
- The capability of disabling specific Redis commands does not work on Redis Module specific commands.
- The CLIENT ID command cannot guarantee incremental IDs between clients that connect to different nodes under multi proxy policies.
- The length of the socket_path variable, which is defined in a node, cannot exceed 88 characters.
- CLIENT UNBLOCK command is not supported in RS 5.4.


title: Redis Enterprise Software Release Notes 5.5 Preview (April 2019)

summary: Preview release. Databases support multiple modules.

title: Overview

text:
Redis Enterprise Software (RS) 5.5 Preview Edition is now available.

RS 5.5 is a preview version that includes all the capabilities of Redis Enterprise 5.4,
plus support for creation of Redis databases with multiple modules and support for these modules:

- RediSearch (GA)
- RedisGraph (GA)
- RedisBloom (GA)
- RedisJSON (GA)
- RedisAI (Preview Version)
- RedisTimeSeries (Preview Version)
- RedisGears (Preview Version)

title: New features

text: RS 5.5 lets you create Redis databases with multiple Redis modules.

title: Preview considerations

text:
This preview version is a standalone version and is not supported for production environments.
You cannot upgrade to it from a lower version or upgrade from it to a higher version.
Unexpected behaviors/issues found in this release will be addressed in future releases.

This preview version is not supported for networks that are isolated from the internet.

title: Installation instructions

text:
To set up a cluster with nodes that can host databases with multiple modules, you must follow this procedure on each node in the cluster:

1. [Install RS 5.5]().
1. To install the modules, run: `sudo ./install-modules.sh`
1. Either:
    - Set up the node as the [first node in the cluster]().
    - [Join the node to an existing cluster]().


title: Redis Enterprise Software Release Notes 5.6.0 (April 2020)

summary: Install improvements for RHEL 6 and 7. Active-Active support for HyperLogLog. Auto Tiering now supports RedisJSON. Active-Active default changes for high availability and OSS Cluster API support. Backup support for Google Cloud Storage and Azure Blob storage.

title: Overview

text:
[Redis Enterprise Software (RS) 5.6.0](https://redislabs.com/download-center/) is now available. This major version release includes:

- Improved installation process to be customizable
- Support for the HyperLogLog data type in Active-Active databases
- RedisJSON support in databases with Auto Tiering enabled
- Support for Redis OSS Cluster API for Active-Active and Replica Of databases
- Replica HA enabled by default for Active-Active databases
- Cloud backup locations support
- Support for Red Hat Enterprise Linux version 7.7, 7.8
- Additional enhancements, and minor bug fixes

title: Information

title: Upgrade

text:
- Follow [these instructions]() for upgrading to RS 5.6.0 from RS 5.0.2 and above.
- For Active-Active databases, you must upgrade the [feature set version](#upgrade-activeactive-databases).

title: End of life

text:
- End of Life (EOL) for Redis Enterprise Software 5.6 and previous RS versions can be found [here]().
    EOL for Redis Modules can be found [here](#modules-endoflife-schedule).
- Support of Red Hat Enterprise Linux 6 and Oracle Linux 6 [operating systems platforms]() will end on November 30, 2020.
- Support of OpenStack Object Storage ("Swift") for [backup, import and export location](https://docs.redis.com/latest/rs/databases/import-export/import-data/) will end on November 30, 2020.

title: New features

title: Redis Software installer

text:
Redis Enterprise Software installer adds the ability to specify custom installation paths and a custom installation user, group, or both on RHEL versions 6 and 7.

When you run the installer you can specify the installation, the configuration and the var as well as the user and the group:

[code example]

For more information, check out the [Redis Enterprise Software installer documentation](https://docs.redis.com/latest/rs/installing-upgrading/).

title: Hyperloglog on Active-Active

text:
RS 5.6.0 adds the support of [HyperLogLog](http://www.antirez.com/news/75) data structure for [Active-Active Redis]() databases.

Because HyperLogLog is a counting data structure by nature, conflicts can occur when deleting entries. For efficiency, performance and memory considerations, conflicts between instances are resolved with DEL (delete) operations winning over ADD operations that took place in concurrent or before the DEL operation.

For more information, check out the [HyperLogLog on Active-Active documentation](develop/hyperloglog-active-active.md).

title: RedisJSON on Auto Tiering

text:
RS 5.6.0 adds support for [Auto Tiering]() databases with [Redis Modules](https://docs.redis.com/latest/modules). [RedisJSON]() is the first module to be available to run on a database with Auto Tiering enabled.

Using RedisJSON on Auto Tiering allows you to benefit from high performance redis with high data volume at lower costs.

title: OSS Cluster API support

text:
For more information, check out the [OSS Cluster API documentation]().

**Support for Active-Active and Replica Of databases**

You can configure [Active-Active]() databases to use the [OSS Cluster API](https://docs.redis.com/latest/rs/clusters/optimize/oss-cluster-api/) using the admin console.
The OSS Cluster API improves the performance of user operations against your database.

You can also create or modify an Active-Active Redis database in OSS Cluster mode using the `crdb-cli` tool with the `--oss-cluster` option to apply the changes to all of the instances.

**Create and edit database using the admin console**

You can configure OSS Cluster API for databases using the admin console.

For Active-Active databases, you can create the database with OSS Cluster API enabled for all of its instances.
When you enable OSS Cluster after the Active-Active database is created, the change applies only to the local instance.

title: Replica HA defaults for Active-Active

text:
To enhance the availability and the consistency of [Active-Active geo-distributed Redis](),
[Replica HA]() is enabled by default for all existing and new Active-Active Redis Databases.

To disable Replica HA for for a local instance of an Active-Active database, run this command on the instance: `rladmin tune db <bdb_uid> slave_ha disabled`

title: Cloud backup locations support

text: Redis Enterprise 5.6.0 adds the ability to configure Azure Blob Storage and Google Cloud Storage as backup, import, and export locations.

title: Red Hat Enterprise Linux 7.7, 7.8

text: Redis Enterprise 5.6.0 adds RHEL 7.7, 7.8 to its [supported platforms]().

title: Redis modules

text:
The following GA releases of Redis Modules are bundled in RS 5.6.0:

- [RedisBloom](https://redislabs.com/redis-enterprise/redis-bloom/), version [2.2.1](release-notes/redisbloom/redisbloom-2.2-release-notes)
- [RedisGraph](https://redislabs.com/redis-enterprise/redis-graph/), version [2.0.10](release-notes/redisgraph/redisgraph-2.0-release-notes)
- [RedisJson](https://redislabs.com/redis-enterprise/redis-json/), version [1.0.4](release-notes/redisjson/redisjson-1.0-release-notes)
- [RediSearch](https://redislabs.com/redis-enterprise/redis-search/), version [1.6.11](release-notes/redisearch/redisearch-1.6-release-notes) (updated)
- [RedisTimeSeries](https://redislabs.com/redis-enterprise/redis-time-series/), version [1.2.3](release-notes/redistimeseries/redistimeseries-1.2-release-notes)

title: Additional capabilities

text:
- OSS Redis version [5.0.8](https://raw.githubusercontent.com/antirez/redis/5.0/00-RELEASENOTES)  is merged into RS 5.6.0.
- Starting RS 5.6.0, to upgrade modules during database upgrade you must use the module_args option instead of keep_module_args or <argument> or " " (for no arguments). The module_args option must follow with one of the following (Always in quotation marks): "keep_args" or " " or "<argument>".
For more info and examples, check out [upgrading Redis Modules documentation]() .
- rladmin adds the ability to demote the cluster master node when setting it to [maintenance mode]() by using the `demote_node` option:

[code example]

- The `SENTINEL MASTER` command output format was updated to be aligned with OSS equivalent output.

title: Important fixes

text:
- RS38315, RS33747 - Added the LUA script name (SHA) and its arguments to the warning message indicating the LUA script has been running for more than 5 seconds.
- RS38706 - Fixed a bug which caused a stuck state machine in some scenarios of restoring DB from RDB.
- RS34309 - Improved internal passwords handling.
- RS38498 - Fixed a bug in the upgrade process of a database to avoid failure when saving large RDB (Redis Database Backup) file.
- RS38706 - Fixed a bug that caused a stuck state machine after restoring a snapshot of an Active-Active database.
- RS43996 - Fixed a bug in the upgrade process when using ./install.sh -y and firewalld is not running.
- RS45777 - Fixed a bug that caused clients on a shared connection to the proxy to get disonnected. Disconnections occured in case a response for a request of an already disconnected client was received.
With build 5.6.0-39:
- RS45627, RS47382 - Fixed bugs causing clients to disconnect when using XREAD and XREADGROUP commands in blocking mode on other clients’ connections.
- RS44656 - Fixed a bug causing TLS mode for clients connections to toggle between ‘all communication’ to ‘for crdb communication only’ when performing a global configuration change.

title: Known limitations

title: Active-Active databases

text: - RS51359 - Active-Active databases, using replication and Append Only File (AOF) for [database persistence](), are suffering from memory leaks on replica shards, causing them to grow bigger than the master shards. Customers are advised to upgrade to RS 6.0.12. Meanwhile, you can use a snapshot for database persistence or restart the replica shards.

title: Upgrade notes

text:
- [RS 5.4.2]() introduced new Active-Active Redis Database capabilities that improve its compatibility with open source Redis.
    Now the string data-type in Active-Active Redis Database is implicitly and dynamically typed, just like open source Redis.
    To use the new capabilities on nodes that are upgraded from version RS 5.4.2 or lower,
    you must [upgrade the Active-Active Redis Database protocol]().
- When you upgrade an Active-Active Redis with active AOF from version [RS 5.4.2]() or lower to version [RS 5.4.4]() or higher:
    - If replication is enabled, you must run the BGREWRITEAOF command on all replica shards after the upgrade.
    - If replication is not enabled, you must run the BGREWRITEAOF command on all shards after the upgrade.
- Node upgrade fails if the SSL certificates were configured in version 5.0.2 or above by manually updating the certificates on the disk instead of [updating them through the API]().
    For assistance with this issue, contact Support.
- Starting from [RS 5.4.2](), to preserve the current Redis major.minor version during database upgrade you must use the keep_redis_version option instead of keep_current_version.
- Google Chrome browser on macOS Catalina requires a self-signed certificate generated after June 2019 to include the extendedKeyUsage field in order to connect to the RS admin console. If you use a self-signed certificate that does not include this field, [update the self-signed certificate]().

title: Modules upgrade

text:
- We recommend that you test module upgrade commands in a test environment before you upgrade modules in a production environment. The module upgrade arguments are not validated during the upgrade process and incorrect arguments can cause unexpected downtime.
- Before you upgrade a database with RediSearch Module to Redis 5.0, you must [upgrade the RediSearch Module]() to version 1.4.2 or above.

title: Cluster API

text:
- The API for removing a node is updated in [RS 5.4.2]() or higher. The API call must include json data and the "Content-Type: application/json" header. For example:

    [code example]

title: Discover service

text: - For [Redis Sentinel (Discovery Service)](), every database name must be unique across the cluster.

title: Redis commands

text:
- The capability of disabling specific Redis commands does not work on commands specific to Redis Modules.
- The CLIENT ID command cannot guarantee incremental IDs between clients that connect to different nodes under multi proxy policies.
- CLIENT UNBLOCK command is not supported in RS 5.4 and above
- Starting from RS 5.4.2 and after upgrading the CRDB, TYPE commands for string data-type in CRDBs return "string" (OSS Redis standard).

code: sudo ./install.sh --install-dir <path> --config-dir <path> --var-dir <path> --os-user <user> --os-group <group>

section_id: redis-software-installer

code: rladmin node <node_uid> maintenance_mode on demote_node

section_id: additional-capabilities

code: curl -X POST -H "Content-Type: application/json" -i -k -u user@redislabs.com:password https://localhost:9443/v1/nodes/3/actions/remove --data "{}"


title: Redis Enterprise Software Release Notes 6.0.12 (January 2021)

summary: Distribute synchronization across nodes for Active-Active and Active-Passive databases. Disable internal services to free memory. User accounts support password rotation. Module depdencies automatically installed. Syncer process recovery.

title: Overview

text:
[Redis Enterprise Software (RS) 6.0.12](https://redislabs.com/download-center/#downloads) is now available!
This version includes the following new features and improvements:

- [Synchronization](#syncer-process) can now be [distributed across the nodes]() of Active-Active or Active-Passive databases
- You can [disable several internal RS services]() to free up more memory
- User accounts can have multiple passwords to allow for [password rotation]()
- [Dependencies are automatically installed]() when you add modules to a cluster
- [Envoy replaces NGINX]() for internal cluster administration
- Automatic recovery of the [syncer process](#syncer-process)s from out-of-memory (preview mode)

And other functional and stability improvements.

title: Version information

title: Upgrade instructions

text:
- Follow [these instructions]() for upgrading to RS 6.0.12 from RS 5.4.0 and above.
- For Active-Active deployments, this release requires that you [upgrade the CRDB featureset version]().

title: Product lifecycle information

text:
- End of Life (EOL) for Redis Enterprise Software 6.0 and previous RS versions, can be found [here]().
- EOL for Redis modules can be found [here]().

title: Deprecation Notice

text:
- Support for RS 5.4.X ended on December 31, 2020.
- Support for Red Hat Enterprise Linux 6 and Oracle Linux 6 and Ubuntu 14.04 (Trusty) operating systems platforms ended on November 30, 2020.
- This is the last RS version that supports direct upgrades from versions below 5.6.0.
- This is the last RS version that supports Active-Active protocol version below 1 and featureset version below 1.

title: New Features

text:
#### Distributed Syncer

The syncer process now supports running in a [distributed mode](). This option can improve the latency for Active-Active databases with a very high throughput profile. You can configure a replicated database to use distributed synchronization so that any available proxy endpoint can manage synchronization traffic.

#### Disabling RS services to free memory

Redis Software users can now use the REST API to [disable the following services]():

- cm_server
- mdns_server
- pdns_server
- stats_archiver
- saslauthd
- crdb_coordinator
- crdb_worker

Once disabled, services are not monitored and controlled by the supervisord.

This feature can cause unintended results if the cluster relies on the disabled services.
To make sure you understand the impact of disabled services, test the system in a lab environment before you deploy in production.

#### Support for multiple passwords

For users of Redis 6 and RS 6.0 and above, you can now add more security to your password management by maintaining multiple passwords for a user to allow seamless password rotation.

As of RS 6.0, you can assign specific data access permissions (Redis ACLs) and cluster administration permissions to users.
Password rotation is especially helpful so that you can do a rolling update of the passwords in the application clients that connect to the Redis databases.

In this version, you can only configure multiple passwords [using the REST API]().

#### Redis Modules dependencies management

RedisGears GA and RedisAI GA require Redis Software to fetch and manage external dependencies.
Modules declare dependencies at release time in their ramp file.

In this version of RS, these dependencies are installed by Redis Software when the module is added to the cluster.
The master node downloads the required dependencies and prompts the other nodes to copy the dependencies from the master node.
When all dependency requirements are satisfied, the module installation is complete.
New nodes to the cluster also automatically install the dependencies.

#### Syncer automatic recovery from out-of-memory (Preview mode)

For Active-Active databases, the syncer process gracefully recovers from an out of memory (OOM) state.

Although Active-Active synchronization is bi-directional, in each direction we can define a source instance and a destination instance.
When a destination instance (that is, the instance running the syncer process) gets OOM, the syncer process attempts to automatically recover the data synchronization when memory becomes available.

This is a configurable option and currently under preview mode. This behavior will be GA and set as default in the next RS version.

To enable the syncer automatic recovery, do these steps on each participating cluster:

1. [Upgrade the featureset version]() to `3`.
1. Enable the syncer automatic recovery using the REST API:

    [code example]

The syncer process restarts to with automatic recovery on.

title: Redis modules

text:
The following GA releases of Redis modules are bundled with RS 6.0.12:

- [RediSearch](https://redislabs.com/redis-enterprise/redis-search/), version [2.0.6]()
- [RedisJSON](https://redislabs.com/redis-enterprise/redis-json/), version [1.0.4]()
- [RedisGraph](https://redislabs.com/redis-enterprise/redis-graph/), version [2.2.11]()
- [RedisTimeSeries](https://redislabs.com/redis-enterprise/redis-time-series/), version [1.4.7]()
- [RedisBloom](https://redislabs.com/redis-enterprise/redis-bloom/), version [2.2.4]()

To use the updated modules with a database, you must [upgrade the module on the database]().

title: Additional capabilities

text:
- RS 6.0.12 includes open source Redis 6.0.6. For more information about Redis 6.0.6, check out the [release notes](https://raw.githubusercontent.com/redis/redis/6.0.6/00-RELEASENOTES).
- The bundled Nginx version was updated from version 1.16.0 to 1.18.0.
- The crdb-cli syntax to remove an instance is changed from
`remove-instance [--ordered|--unordered]` to `remove-instance [--force|--no-force]`.

title: Important fixes

text:
- RS45627, RS47382 - Fixed bugs causing clients to disconnect when using XREAD and XREADGROUP commands in blocking mode on other clients’ connections.
- RS44656 - Fixed a bug causing TLS mode for clients connections to toggle between ‘all communication’ to ‘for crdb communication only’ when performing a global configuration change.
- RS42587 - Fixed a bug in the web UI console if the FQDN of the cluster is a substring of the FQDN of a participating cluster
- RS49404 - Fixed a bug in for upgrades with custom directories that prevent users from creating databases via the web UI console.
- RS43961 - bigkeys command fixed to handle non-printable key names
- RS45707 - Fixed a bug that caused RCP (Redis Cloud Pro) databases to reject connections while resharding the database.
- RS51144 - Fixed a bug in the syncer process that was stopping synchronization between all instances in some scenarios of network disconnection of one or more participating clusters.

with 6.0.12-58:
- RS50865 - Fixed a bug causing rladmin change master node to fail when performed after a prior successful master change.
- RS51359 - Fixed a memory leak on replica shards in Active-Active databases with replication and AOF for persistence.
- RS52363 - Updated PUB/SUB max message value size from 64KB to 512MB

title: Known limitations

text: -RS81463 - A shard may crash when resharding an Active-Active database with Auto Tiering . Specifically, the shard will crash when volatile keys or Active-Active tombstone keys reside in Flash memory.

title: Installation limitations

text:
Several Redis Enterprise Software installation reference files are installed to the directory `/etc/opt/redislabs/` even if you use [custom installation directories]().

As a workaround to install Redis Enterprise Software without using any root directories, do the following before installing Redis Enterprise Software:

1. Create all custom, non-root directories you want to use with Redis Enterprise Software.

1. Mount `/etc/opt/redislabs` to one of the custom, non-root directories.

#### Upgrade

- [RS 5.4.2]() introduced new Active-Active Redis Database capabilities that improve its compatibility with open source Redis. Now the string data-type in Active-Active Redis Database is implicitly and dynamically typed, just like open source Redis. To use the new capabilities on nodes that are upgraded from version RS 5.4.2 or lower, you must [upgrade the Active-Active Redis Database protocol]().
- When you upgrade an Active-Active Redis with active AOF from version [RS 5.4.2]() or earlier to version [RS 5.4.4]() or later:
    - If replication is enabled, you must run the BGREWRITEAOF command on all replica shards after the upgrade.
    - If replication is not enabled, you must run the BGREWRITEAOF command on all shards after the upgrade.
- Node upgrade fails if the SSL certificates were configured in version 5.0.2 or above by manually updating the certificates on the disk instead of [updating them through the API](). For assistance with this issue, contact Support.
- Starting from [RS 5.4.2](), to preserve the current Redis major.minor version during database upgrade you must use the keep_redis_version option instead of keep_current_version.

#### Redis commands

- The capability of disabling specific Redis commands does not work on commands specific to Redis modules.
- CLIENT UNBLOCK command is not supported in RS 5.4 and above
- Starting from RS 5.4.2 and after upgrading the CRDB, TYPE commands for string data-type in CRDBs return "string" (OSS Redis standard).

code: curl -v -k -u <username>:<password> -X PUT -H "Content-Type: application/json" -d ‘{crdt_syncer_auto_oom_unlatch":true}’ http://<cluster_address>:8080/v1/bdbs/<database_ID>

section_id: new-features