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).