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

medusa calculates podNames incorrectly when unbalanced racks are used #1460

Open
burmanm opened this issue Nov 26, 2024 · 0 comments · May be fixed by #1461
Open

medusa calculates podNames incorrectly when unbalanced racks are used #1460

burmanm opened this issue Nov 26, 2024 · 0 comments · May be fixed by #1461
Assignees
Labels
bug Something isn't working

Comments

@burmanm
Copy link
Contributor

burmanm commented Nov 26, 2024

What happened?
medusa's hostmap.go assumes evenly balanced racks, but this is not necessarily true. Given the size of 8 and 3 racks, the StS would end up with sizes 3,3,2 and this is fully functional. Yet, Medusa would believe this is actually 3,3,3 since it only divides and rounds.

Did you expect to see something different?

How to reproduce it (as minimally and precisely as possible):

Environment

  • K8ssandra Operator version:

    Insert image tag or Git SHA here

  • Kubernetes version information:

    kubectl version

  • Kubernetes cluster kind:

    insert how you created your cluster: kops, bootkube, etc.

  • Manifests:

insert manifests relevant to the issue
  • K8ssandra Operator Logs:
insert K8ssandra Operator logs relevant to the issue here

Anything else we need to know?:

┆Issue is synchronized with this Jira Story by Unito
┆Issue Number: K8OP-298

@burmanm burmanm added the bug Something isn't working label Nov 26, 2024
@burmanm burmanm self-assigned this Nov 26, 2024
@burmanm burmanm linked a pull request Dec 11, 2024 that will close this issue
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
No open projects
Status: No status
Development

Successfully merging a pull request may close this issue.

1 participant