{
  "schema_version": 2,
  "id": "operate/rs/release-notes/legacy-release-notes/redis-enterprise-5",
  "title": "Redis Enterprise Pack 5.0 Release Notes (November 2017)",
  "url": "https://redis.io/docs/latest/operate/rs/release-notes/legacy-release-notes/redis-enterprise-5/",
  "summary": "",
  "tags": [
    "docs",
    "operate",
    "rs"
  ],
  "last_updated": "2026-09-24T14:54:25+01:00",
  "page_type": "content",
  "content_hash": "970d1ae5dc842cb28908943f85d0dc88e4c55e73df73b5ef2e5481765ecad325",
  "sections": [
    {
      "id": "overview-1",
      "title": "Overview",
      "role": "overview",
      "text": "Redis Enterprise Software 5.0 is now available. Key features include\nGeo-Distributed Active-Active Conflict-free Replicated Databases (CRDB),\nLDAP integration, Redis Module integration, and support for the Redis\nCluster API."
    },
    {
      "id": "overview",
      "title": "Overview",
      "role": "overview",
      "text": "If you are upgrading from a previous version, make sure to review the\nupgrade instructions before beginning the upgrade process.\n\nYou can upgrade to RS 5.0 from RS 4.4.2 and above. If you have a version\nolder than this, you must first upgrade to at least 4.4.2."
    },
    {
      "id": "new-features",
      "title": "New features",
      "role": "content",
      "text": ""
    },
    {
      "id": "support-for-redis-cluster-api",
      "title": "Support for Redis Cluster API",
      "role": "compatibility",
      "text": "The Redis Cluster API support in Redis Enterprise Software (RS) provides\na simple mechanism for Cluster enabled Redis clients to learn and know\nthe cluster topology. This enables clients to connect directly to an RS\nproxy on the node hosting the master shard for the data being operated\non. The result is that for all but the initial call to get the cluster\ntopology or reacquire the location of the master shard, the client will\nconnect to the RS endpoint proxy where the master shard is located.\n[Learn more about the Cluster API\nimplementation](https://redis.io/docs/latest/operate/rs/clusters/optimize/oss-cluster-api)."
    },
    {
      "id": "geodistributed-activeactive-conflictfree-replicated-databases-crdb",
      "title": "Geo-distributed Active-Active conflict-free replicated databases (CRDB)",
      "role": "content",
      "text": "Developing globally distributed applications can be challenging, as\ndevelopers have to think about race conditions and complex combinations\nof events under geo-failovers and cross-region write conflicts. CRDBs\nsimplify developing such applications by directly using built-in smarts\nfor handling conflicting writes based on the data type in use. Instead\nof depending on just simplistic \"last-writer-wins\" type conflict\nresolution, geo-distributed CRDBs combines techniques defined in CRDT\n(conflict-free replicated data types) research with Redis types to\nprovide smart and automatic conflict resolution based on the data type's\nintent.\n\nFor more information, go here. For information, go to [Developing with\nCRDBs](https://redis.io/docs/latest/operate/rs/databases/active-active/develop/develop-for-aa)."
    },
    {
      "id": "redis-modules",
      "title": "Redis modules",
      "role": "content",
      "text": "Redis Modules enable you to extend the functionality of Redis Enterprise\nPack. One can add new data types, capabilities, etc. to tailor the\ncluster to a specific use case or need. Once installed, modules benefit\nfrom the high performance, scalability, and high availability that Redis\nEnterprise is known for.\n\n#### Redis modules\n\nRedis has developed and certified the following modules for use with \nRedis Enterprise Pack:\n\n- [RediSearch](https://redis.io/docs/latest/operate/oss_and_stack/stack-with-enterprise/search)\n    - This module turns RS into a supercharged distributed in-memory\n      full-text indexing and search beast.\n- [ReJSON](https://redis.io/docs/latest/operate/oss_and_stack/stack-with-enterprise/json)\n    - Now you have the convenience JSON as a built-in data type and\n      easily able to address nested data via a path.\n- [RedisBloom](https://redis.io/docs/latest/operate/oss_and_stack/stack-with-enterprise/bloom)\n    - Enables RS to have a scalable bloom filter as a data type. Bloom\n      filters are probabilistic data structures that\n      quickly determine if values are in a set.\n\n#### Custom modules\n\nIn addition, Redis Enterprise Pack provides the ability to load and use\ncustom [Redis modules](https://redislabs.com/community/redis-modules-hub/) or of\nyour own creation."
    },
    {
      "id": "support-for-docker",
      "title": "Support for Docker",
      "role": "compatibility",
      "text": "Deploying and running your Redis Enterprise Software cluster on Docker\ncontainers is supported in development systems and\navailable to pull from Docker hub. With the official image, you can\neasily and quickly test several containers to build the scalable\nand highly available cluster Redis Enterprise Software is famous for.\n\nFor more information, go to [quick start with Redis Enterprise on\nDocker](https://redis.io/docs/latest/operate/rs/installing-upgrading/quickstarts/docker-quickstart)."
    },
    {
      "id": "ldap-integration",
      "title": "LDAP Integration",
      "role": "content",
      "text": "As part of our continued emphasis on security, administrative user\naccounts in Redis Enterprise Pack can now use either built-in\nauthentication or authenticate externally via LDAP with saslauthd. The\naccounts can be used for administering resources on the cluster via\ncommand line, Rest API, or admin console.\n\nFor more information see [LDAP\nIntegration](https://redis.io/docs/latest/operate/rs/security/access-control/ldap)."
    },
    {
      "id": "additionalcapabilities",
      "title": "Additional capabilities",
      "role": "content",
      "text": "Support for additional Redis commands and features:\n\n- Support for Redis version 4.0.2\n- Support added for RHEL/CentOS 6.9 and 7.4"
    },
    {
      "id": "information",
      "title": "Information",
      "role": "content",
      "text": "- In the node bootstrap API, the structure of the JSON has changed for\n    adding an external IP during the bootstrap process.\n- End-of-Life for RHEL/CentOS 6.5 and 6.6 have been reached, so those\n    versions are no longer supported.\n- Modules are not supported in Redis Enterprise Pack 5.0 for\n    RHEL/CentOS 6.x"
    },
    {
      "id": "important-fixes",
      "title": "Important fixes",
      "role": "content",
      "text": ""
    },
    {
      "id": "5-0-031",
      "title": "5.0.0-31",
      "role": "content",
      "text": "- RP9299 - Issue with reliability of metric ingress\n- RP9680 - Redis Enterprise Pack starting before /etc/rc.local script\n    executed\n- RP12363 - In some cases, flash drives do not mount following a\n    stop/start of the node\n- RP12493 - Allow change to debug package creation location\n- RP13079 - DNS doesn't change after having removed the external IP\n    address in some cases\n- RP13933 - rladmin balance sometimes shows incorrect information\n- RP14060 - pubsub stats aren't reflected correctly by the stats\n    archiver\n- RP14939 - Add license checks to all needed entry points in the\n    cluster\n- RP15090 - Problem in log rotate script causes other logs to not\n    rotate\n- RP15104 - rlutil check fix doesn't work sometimes\n- RP15130 - Fixed permission on two logs with incorrect ownership\n- RP15160 - Allow option to change ports for API and CM in NGINX\n- RP15164 - Allow unix socket folder to be configurable at build time\n- RP15499 - rladmin command not responding on a cluster with large\n    number of shards\n- RP15853 - When trying to add a new db the 'activate' button was\n    changed to 'update' and was grayed out.\n- RP15861 - Allow unix socket folder to be configurable at install\n    time\n- RP16115 - TTL bug with Replica Of and import\n- RP16447 - DMC client connection reports incorrect number of\n    connections to monitoring applications.\n- RP16481 - In some cases, resource_mgr uses incorrect directories\n    to compute persistent and ephemeral storage"
    }
  ],
  "examples": []
}