journal: avoid logging an error when a watch is blacklisted #12473
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
Fixes: http://tracker.ceph.com/issues/18243 Signed-off-by: Jason Dillaman <dillaman@redhat.com>
|
@dillaman I have reproduced it again and just realized that the repeating errors come from handle_watch_reset, not handle_watch_error. I think, may be it makes sense to report "client blacklisted" with error level in handle_watch_error (as it would show only once and might be useful for user) and with debug level in handle_watch_reset? |
|
@trociny thanks -- sounds like a good plan |
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.
Fixes: http://tracker.ceph.com/issues/18243
Signed-off-by: Jason Dillaman dillaman@redhat.com