Redis Data Integration release notes 1.4.1 (November 2024)

Installation on Kubernetes with a Helm chart. Improvements for installation on VMs.

This maintenance release replaces the 1.4.0 release.

RDI’s mission is to help Redis customers sync Redis Enterprise with live data from their slow disk-based databases to:

  • Meet the required speed and scale of read queries and provide an excellent and predictable user experience.
  • Save resources and time when building pipelines and coding data transformations.
  • Reduce the total cost of ownership by saving money on expensive database read replicas.

RDI keeps the Redis cache up to date with changes in the primary database, using a Change Data Capture (CDC) mechanism. It also lets you transform the data from relational tables into convenient and fast data structures that match your app's requirements. You specify the transformations using a configuration system, so no coding is required.

Headlines

  • Installation on Kubernetes using a Helm chart. You can install on OpenShift or other flavours of K8s using Helm.

  • Improvements for installation on VMs:

    • Installer checks if the OS firewall is enabled on Ubuntu and RHEL.
    • Installer verifies DNS resolution from RDI components.
    • Installer provides log lines from components that failed during RDI deployment if a problem occurs.
    • Improved verification of RDI installation.
    • Installer verifies if the RDI database is in use by another instance of RDI.
    • Installer checks and warns if any iptables rules are set.
    • Improved message when RDI tries to connect to its Redis database with invalid TLS keys.

Issues fixed

  • RDSC-2806: Remove incorrectly created deployment.
  • RDSC-2792: Disable kubectl run checks.
  • RDSC-2782: Fix coredns issue.

Limitations

RDI can write data to a Redis Active-Active database. However, it doesn't support writing data to two or more Active-Active replicas. Writing data from RDI to several Active-Active replicas could easily harm data integrity as RDI is not synchronous with the source database commits.

RATE THIS PAGE
Back to top ↑