docs(agent): corrects the Redis sizing requirement to one logical database - #12898
Merged
Conversation
Contributor
Merge Protections🟢 All 5 merge protections satisfied — ready to merge. Show 5 satisfied protections🟢 👀 Review Requirements
🟢 Enforce conventional commitMake sure that we follow https://www.conventionalcommits.org/en/v1.0.0/
🟢 🔎 Reviews
🟢 📕 PR description
🟢 🚦 Auto-queueWhen all merge protections are satisfied, this pull request will be queued automatically. |
JulianMaurin
approved these changes
Sep 21, 2026
Contributor
Merge Queue Status
This pull request spent 2 minutes 57 seconds in the queue, including 2 minutes 34 seconds running CI. Required conditions to merge
|
49 tasks
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The Redis requirements asked operators to provide "at least 16 logical
databases". That was true when the engine sharded its state across a range of
numbered databases, and it stopped being true once the queue and the event
stores moved to PostgreSQL. The engine now opens exactly one Redis connection,
for its cache, and on an on-premise deployment that connection is whatever
MERGIFYENGINE_REDIS_URLpoints at — database and all.The number mattered in practice. Sixteen is the default
databasessetting ofa stock Redis, but several managed Redis offerings expose one database per
instance, and a reader sizing against this page would rule out a provider that
serves the engine perfectly well, or provision a second instance nobody needs.
Evidence: the engine's Redis settings expose a single client URL, and the
database-sharding map behind it has one entry left.