Does Uploading a New Redis License Require Downtime or a Restart?

Redis Software licenses control cluster entitlements such as shard capacity and enabled features. When a license is renewed, replaced, or updated, administrators often need to know whether applying the new license will interrupt client traffic, require a maintenance window, or trigger a restart.

Updating a Redis license is a configuration change rather than a maintenance activity. The documented workflow does not require taking the cluster offline or restarting nodes.

This article includes separate procedures for Redis Software and Redis Enterprise for Kubernetes. Navigate directly to the section that matches your deployment.

For Redis Software, the documented license update process is performed through the Cluster Manager UI or REST API. The published workflow does not include restarting cluster nodes, restarting databases, or taking the cluster offline. Redis also documents that if a new license fails validation, the existing license remains in effect.

This article explains what to expect when updating a license, how to perform the update safely, and how to verify the new license after it is applied.

Key sections: Expected Service Impact | Update a Redis Software License | Update a Redis Enterprise for Kubernetes License | Troubleshooting

Quick Fix

Prerequisites

Before updating a license, confirm the following:

• You have administrator access to Redis Software Cluster Manager or the Redis Software REST API.

• You have the complete license text, including the ----- LICENSE START ----- and ----- LICENSE END ----- markers.

• You know the cluster name or FQDN associated with the license.

• The replacement license is valid for the current date. If the activation date is in the future, the license will not activate until that date.

• The replacement license provides sufficient capacity for the cluster's current and planned shard usage.

Expected service impact

For Redis Software, applying a new license is a configuration update rather than a cluster maintenance operation.

The documented license replacement process does not include:

• Restarting Redis Software nodes

• Restarting databases

• Taking the cluster offline

Because the documented workflow is a configuration update, license updates are typically performed during normal operational windows.

If the new license cannot be applied because of a validation issue, Redis returns an error and leaves the existing license in effect. The replacement license is not applied, and the documented workflow does not include restarting nodes, databases, or taking the cluster offline.

Update a Redis Software license

1. Sign in to Cluster Manager.

2. Navigate to Cluster > Configuration > General > License.

3. Select Change.

4. Upload or paste the new license.

5. Select Save.

Redis validates the license against:

• Cluster name

• Activation date

• Expiration date

• Licensed features

• Licensed capacity

If validation succeeds, the new license becomes active.

If validation fails, the operation returns an error and the existing license remains in effect.

You can also update the license through the REST API:

PUT /v1/license

{
  "license": "----- LICENSE START -----\n...\n----- LICENSE END -----\n"
}

Verify the update

After updating the license:

1. Return to Cluster > Configuration > General > License.

2. Confirm the expected expiration date, capacity limits, and license status.

Alternatively, run:

GET /v1/license

Verify:

• Cluster name

• License status

• Activation date

• Expiration date

• Licensed capacity

Update a Redis Enterprise for Kubernetes license

For Redis Enterprise for Kubernetes, licenses are managed through the Redis Enterprise Cluster (REC) resource.

1. Edit the REC:

kubectl edit rec <REC_NAME>

2. Update the license under spec.license:

spec:
  license: |
    ----- LICENSE START -----
    <license>
    ----- LICENSE END -----

3. Save the resource.

4. Allow the operator to reconcile the change.

5. Verify the license state:

kubectl get rec
kubectl describe rec <REC_NAME>

The documented workflow updates the REC specification and relies on operator reconciliation. A manual pod restart is not part of the standard license update procedure.

What happens if the license has already expired?

An expired Redis Software license does not stop existing databases from serving traffic.

However, Redis Software restricts database-level administrative operations until a valid license is installed.

Examples include:

• Creating databases

• Modifying database configuration

• Changing database security settings

If the cluster appears healthy but administrative changes fail, verify the license status before troubleshooting other components.

Troubleshooting

The new license was rejected

Common causes include:

• Cluster name or FQDN mismatch

• License activation date has not started

• License expiration date has already passed

• Licensed capacity is lower than current requirements

• Required features are not included

Use Troubleshooting Redis License Activation and Update Failures for detailed diagnostics.

The cluster is still serving traffic but configuration changes fail

This is expected behavior when the current license has expired.

Install a valid replacement license and verify the updated license status.

You need to validate a license before a Redis Software upgrade

Before performing a Redis Software upgrade, confirm that:

• The license is active

• The license is not close to expiration

• The cluster name matches the license

• Licensed capacity is sufficient for the environment

Resolving licensing issues before the maintenance window helps avoid operational delays during the upgrade.

When to contact Redis

Contact your Redis account team or Redis Support if:

• A replacement license is rejected and the cause is unclear.

• You need a temporary license for a migration, renewal process, or staging environment.

• The replacement license does not provide the expected capacity or features.

• A Redis Enterprise for Kubernetes license update does not reconcile successfully.

• You are unsure whether an upcoming operational change will be blocked by licensing restrictions.