Remove "Could not get endpoints data" error logging #365
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ction to be taken
|
Do you think it could be useful for debug logging? |
|
Not this line, no. It could tell that cass-operator can't connect anywhere, but we would never catch that in the debug mode. |
jsanda
approved these changes
Jul 15, 2022
burmanm
added a commit
that referenced
this pull request
Jul 18, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…ction to be taken
What this PR does:
Remove the entire "Could not get endpoint data" logging as it is a logging statement which requires no action to be taken by the operator or by the user. It simply spams the logs for no real reason.
Which issue(s) this PR fixes:
Fixes #364
Fixes #368
Checklist