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

Kubernetes statefulset yaml doesn't set locality on node start #63509

Open
lin-crl opened this issue Apr 12, 2021 · 10 comments
Open

Kubernetes statefulset yaml doesn't set locality on node start #63509

lin-crl opened this issue Apr 12, 2021 · 10 comments
Labels
C-bug Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.

Comments

@lin-crl
Copy link
Contributor

lin-crl commented Apr 12, 2021

Describe the problem

Please describe the issue you observed, and any steps we can take to reproduce it:

To Reproduce

What did you do? Describe in your own words.

If possible, provide steps to reproduce the behavior:

  1. Create a kubernetes cluster on EKS
  2. Apply statefulset yaml
  3. Look at DBConsole. The node localities are not set

Expected behavior
The statefulset can correctly set localities, since it's the supported method to deploy production clusters

Environment:

  • CockroachDB version 20.x and may impact lower versions as well
  • Kubernetes: Tested on EKS 1.17. Theoretically this can impact any Kubernetes clusters using the out-of-box yaml file.

Additional context
Customer can see reduced resiliency when locality is not properly set. And can experience data loss in production when losing multiple nodes at the same time.

Add any other context about the problem here.

Jira issue: CRDB-6613

@lin-crl lin-crl added the C-bug Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior. label Apr 12, 2021
@johnrk-zz
Copy link

@jhatcher9999 , about a month ago, I recall that you mentioned having success using the Kubernetes Statefulset Yaml with multi-region deployments. Have you encountered this issue of node localities not setting?

@jhatcher9999
Copy link
Collaborator

I haven't had this issue. I have had an issue with the EKS-specific sts files where it includes the dna name as the last part of the locality string which screws up the way things display in the DB Console (i.e., all the nodes show up in their own group in the node list).

Jessie, which sts yamls were you using when you had this issue? Can you include the link to the github file?

@lin-crl
Copy link
Contributor Author

lin-crl commented Apr 13, 2021 via email

@jhatcher9999
Copy link
Collaborator

jhatcher9999 commented Apr 13, 2021 via email

@lin-crl
Copy link
Contributor Author

lin-crl commented Apr 14, 2021

The mutliregion statefulset doesn't have any values in it either

         - exec
            /cockroach/cockroach
            start
            --logtostderr
            --certs-dir /cockroach/cockroach-certs
            --advertise-host $(hostname -f)
            --http-addr 0.0.0.0
            --join JOINLIST
            --locality LOCALITYLIST
            --cache $(expr $MEMORY_LIMIT_MIB / 4)MiB
            --max-sql-memory $(expr $MEMORY_LIMIT_MIB / 4)MiB

@jhatcher9999
Copy link
Collaborator

jhatcher9999 commented Apr 14, 2021 via email

@lin-crl
Copy link
Contributor Author

lin-crl commented Apr 19, 2021

Thanks for the update @jhatcher9999
@johnrk hope the this discuss gives a better description of the issue. could you please follow up w/ Eng/Doc team to address the issue? Thank you!

@knz
Copy link
Contributor

knz commented Oct 18, 2022

cc @mwang1026 for product triage.

@mwang1026
Copy link

cc @towfiqa

Copy link

We have marked this issue as stale because it has been inactive for
18 months. If this issue is still relevant, removing the stale label
or adding a comment will keep it active. Otherwise, we'll close it in
10 days to keep the issue queue tidy. Thank you for your contribution
to CockroachDB!

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Apr 22, 2024
@yuzefovich yuzefovich reopened this May 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-bug Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.
Projects
None yet
Development

No branches or pull requests

7 participants