Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support Redis clusters as Tomcat session backend #31271

Open
yolabingo opened this issue Jan 30, 2025 · 0 comments
Open

Support Redis clusters as Tomcat session backend #31271

yolabingo opened this issue Jan 30, 2025 · 0 comments

Comments

@yolabingo
Copy link
Contributor

yolabingo commented Jan 30, 2025

User Story

As a dotCMS administrator,
I want to be able to use a Redis cluster for dotCMS session storage,
so I can maximize availability

Acceptance Criteria

Current Tomcat session storage supports connecting to a Redis single-node instance only. FR is to support connecting to either a single-node Redis server or to multiple Redis servers in a cluster.

Presumably we would configure using comma-separated Redis hosts
TOMCAT_REDIS_SESSION_HOST=10.1.1.10,10.1.1.20,10.2.2.30

Question - what should be the behavior if one of the Redis nodes becomes unavailable?

Proposed Objective

Core Features

Proposed Priority

Priority 3 - Average

External Links... Slack Conversations, Support Tickets, Figma Designs, etc.

An on-prem customer found this issue which lead to this feature request https://dotcms.freshdesk.com/a/tickets/28886

Assumptions & Initiation Needs

No response

Quality Assurance Notes & Workarounds

No response

Sub-Tasks & Estimates

No response

@yolabingo yolabingo changed the title Support Redis clusters as a session backend Support Redis clusters as Tomcat session backend Jan 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: New
Development

No branches or pull requests

1 participant