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

[bitnami/redis] Can't have master-slave with 1 master and 1 slave with Sentinel #30981

Closed
snird opened this issue Dec 11, 2024 · 3 comments
Closed
Assignees
Labels
redis solved stale 15 days without activity tech-issues The user has a technical issue about an application triage Triage is needed

Comments

@snird
Copy link

snird commented Dec 11, 2024

Name and Version

bitnami/redis 20.5.0

What architecture are you using?

amd64

What steps will reproduce the bug?

A replica set up with 2 replicas may work but is unsafe due to sentinels being attached to each instance (and thus, having only 2 sentinels).

So having 2 replicas means 2 sentinels - which is not enough.
3 sentinels is a required minimum for quorum.

There is no way currently to detach the sentinels from the replicas, but they theoretically should be completely separated.
As, for example, if you want to have 4 replicas - that won't work either because quorums require 3/5/7... voters to work properly.

What do you see instead?

Sentinels amount set separately, and live in their own pods.
If a pod of a Redis instance has gone bad - we still need the sentinel to vote on the master. Detaching it is safe anyway.

@snird snird added the tech-issues The user has a technical issue about an application label Dec 11, 2024
@github-actions github-actions bot added the triage Triage is needed label Dec 11, 2024
@snird snird changed the title Can't have master-slave with 1 master and 1 slave with Sentinel [bitnami/redis] Can't have master-slave with 1 master and 1 slave with Sentinel Dec 11, 2024
@carrodher
Copy link
Member

Thank you for bringing this issue to our attention. We appreciate your involvement! If you're interested in contributing a solution, we welcome you to create a pull request. The Bitnami team is excited to review your submission and offer feedback. You can find the contributing guidelines here.

Your contribution will greatly benefit the community. Feel free to reach out if you have any questions or need assistance.

Copy link

This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.

@github-actions github-actions bot added the stale 15 days without activity label Dec 27, 2024
Copy link

github-actions bot commented Jan 1, 2025

Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.

@github-actions github-actions bot added the solved label Jan 1, 2025
@bitnami-bot bitnami-bot closed this as not planned Won't fix, can't repro, duplicate, stale Jan 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
redis solved stale 15 days without activity tech-issues The user has a technical issue about an application triage Triage is needed
Projects
None yet
Development

No branches or pull requests

4 participants