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.

Sign up for GitHub

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

Jump to bottom

K8SSAND-1651 ⁃ Don't call /endpoints check for nodes that are not ready #368

Closed
burmanm opened this issue Jul 13, 2022 · 0 comments · Fixed by #365
Closed

K8SSAND-1651 ⁃ Don't call /endpoints check for nodes that are not ready #368

burmanm opened this issue Jul 13, 2022 · 0 comments · Fixed by #365
Labels
bug Something isn't working

Comments

@burmanm
Copy link
Contributor

burmanm commented Jul 13, 2022 •
edited by sync-by-unito bot
Loading

What happened?
The original 500 endpoints state logging happens also, because we keep calling /endpoints for node that have not actually started yet. This feel pointless, takes time and resources while it will never work (and we know it).

Did you expect to see something different?

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

Environment

  • Cass 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
  • Cass Operator Logs:
insert Cass Operator logs relevant to the issue here

Anything else we need to know?:

┆Issue is synchronized with this Jira Task by Unito
┆Issue Number: K8SSAND-1651
┆priority: Medium
┆Link To Issue: https://k8ssandra.atlassian.net/browse/K8SSAND-1651
@burmanm burmanm added the bug Something isn't working label Jul 13, 2022
@sync-by-unito sync-by-unito bot changed the title Don't call /endpoints check for nodes that are not ready K8SSAND-1651 ⁃ Don't call /endpoints check for nodes that are not ready Jul 13, 2022
@burmanm burmanm added the backport Feature requires backporting to older release branches label Jul 13, 2022
burmanm added a commit to burmanm/cass-operator that referenced this issue Jul 13, 2022
@burmanm
Get EndpointStatus only from started pods, fixes k8ssandra#368
515cbed
@burmanm burmanm mentioned this issue Jul 13, 2022
Merged
5 tasks
burmanm added a commit that referenced this issue Jul 15, 2022
@burmanm
Remove "Could not get endpoints data" error logging (#365)
da9d6c2 
* Remove "Could not get endpoints data" error logging as it causes no action to be taken

* Get EndpointStatus only from started pods, fixes #368
burmanm added a commit that referenced this issue Jul 18, 2022
@burmanm
Remove "Could not get endpoints data" error logging (#365)
ea143a9 
* Remove "Could not get endpoints data" error logging as it causes no action to be taken

* Get EndpointStatus only from started pods, fixes #368

(cherry picked from commit da9d6c2)
@burmanm burmanm removed the backport Feature requires backporting to older release branches label Jul 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Remove "Could not get endpoints data" error logging burmanm/cass-operator
1 participant
@burmanm