Cleanup #18243
closedJournalMetadata flooding with errors when being blacklisted
0%
Description
When a client is blacklisted the log is flooded with error messages like below:
2016-12-12 08:17:17.550844 7f2165ff3700 -1 JournalMetadata: 0x7f217003edf0 handle_watch_reset: failed to watch journal: (108) Cannot send after transport endpoint shutdown
2016-12-12 08:17:18.552505 7f2165ff3700 -1 JournalMetadata: 0x7f217003edf0 handle_watch_reset: failed to watch journal: (108) Cannot send after transport endpoint shutdown
2016-12-12 08:17:19.558172 7f2165ff3700 -1 JournalMetadata: 0x7f217003edf0 handle_watch_reset: failed to watch journal: (108) Cannot send after transport endpoint shutdown
Since JournalMetadata can't bubble this error up to librbd, it just keeps trying to reconnect until it's told to shut down. Probably the correct thing to do is change the log level from error (-1) to debug (0).
Updated by Jason Dillaman over 7 years ago
- Status changed from New to In Progress
- Assignee set to Jason Dillaman
- Backport set to jewel, kraken
Updated by Jason Dillaman over 7 years ago
- Status changed from In Progress to Fix Under Review
Updated by Jason Dillaman over 7 years ago
Additional PR: https://github.com/ceph/ceph/pull/12497
Updated by Mykola Golub over 7 years ago
- Status changed from Fix Under Review to Pending Backport
Updated by Nathan Cutler over 7 years ago
- Copied to Backport #18323: jewel: JournalMetadata flooding with errors when being blacklisted added
Updated by Nathan Cutler over 7 years ago
- Copied to Backport #18324: kraken: JournalMetadata flooding with errors when being blacklisted added
Updated by Jason Dillaman over 7 years ago
- Backport changed from jewel, kraken to jewel
Updated by Nathan Cutler over 7 years ago
- Backport changed from jewel to jewel,kraken
Updated by Nathan Cutler about 7 years ago
- Status changed from Pending Backport to Resolved