Skip to content

RS 8.0.18 release docs#3040

Open
rrelledge wants to merge 14 commits intomainfrom
DOC-6364
Open

RS 8.0.18 release docs#3040
rrelledge wants to merge 14 commits intomainfrom
DOC-6364

Conversation

@rrelledge
Copy link
Copy Markdown
Collaborator

@rrelledge rrelledge commented Apr 18, 2026

Release notes staged preview: https://redis.io/docs/staging/DOC-6364/operate/rs/release-notes/rs-8-0-releases/rs-8-0-18-tba/

Still TODO:

  1. Add build number and checksums when available

Note

Low Risk
Documentation-only changes with no runtime code impact; main risk is inaccuracies in newly documented API fields/ports affecting operators if incorrect.

Overview
Documents Redis Software 8.0.18 (Redis OSS 8.6 compatibility) by adding a new rs-8-0-18-tba release-notes page and updating the 8.0 release index to reflect the new feature set, crdb_controller default enablement, and a newly reserved internal port (3357).

Extends reference docs to match new capabilities: adds allkeys-lrm/volatile-lrm eviction policies, updates the default bundled DB versions table to include 8.6, documents the new POST /v1/crdbs/{crdb_guid}/upgrade endpoint and corresponding upgrade_crdb permission, and updates REST API objects (bdb, node, and bdb/search) with new fields/options (e.g., replication_oom_threshold_percent, search_on_bigstore, oss_cluster_ip_mapping, and additional search config parameters).

Reviewed by Cursor Bugbot for commit aaf0dea. Bugbot is set up for automated code reviews on this repo. Configure here.

@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Apr 18, 2026

DOC-6364

@jit-ci
Copy link
Copy Markdown

jit-ci bot commented Apr 18, 2026

🛡️ Jit Security Scan Results

CRITICAL HIGH MEDIUM

✅ No security findings were detected in this PR


Security scan by Jit

@rrelledge rrelledge requested a review from adrianoamaral April 18, 2026 01:36
Copy link
Copy Markdown
Collaborator

@dwdougherty dwdougherty left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just one comment about RQE. Otherwise, LGTM.

| search-max-aggregate-results | integer (range: 0-9223372036854775807) (default: 2147483648) | The maximum number of results to be returned by the FT.AGGREGATE command if LIMIT is used |
| search-io-threads | integer (range: 1-256) (default: 1) | The number of threads the coordinator is using for IO threads to handle network to/from other shards |
| search-enable-unstable-features | boolean (default: false) | Enable unstable features. |
| search-index-cursor-limit | integer (range: 0-9223372036854775807) (default: 128) | The maximum number of cursors that can be opened, per shard, at any given time. Cursors can be opened by the user via FT.AGGREGATE WITHCURSOR. Cursors are also opened internally by the RQE for long-running queries. Once INDEX_CURSOR_LIMIT is reached, any further attempts to open a cursor will result in an error. |
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe change "the RQE" to "Redis Search"; RQE is obsolete.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants