Open ssherwood opened 1 month ago
I0405 03:23:19.764725 14875 reactor.cc:459] Master_R014: DEBUG:
Closing idle connection: Connection (0x0000000022ad2eb0) server
AAA.BBB.CCC.DDD:PPPP => EEE.FFF.GGG.HHH:7100 - it has been idle for
65.0009s
W0405 04:05:27.798019 14857 connection.cc:294] Connection
(0x0000000023810eb0) server AAA.BBB.CCC.DDD:PPPPP => EEE.FFF.GGG.HHH:7100:
Command sequence failure: Network error (yb/rpc/yb_rpc.cc:148):
Invalid connection header: <Very long string, for example: 16030002D7010002D303003B19F0CE...>
In one case it was thought to be a scanner, and in another case we were told it could be ignored...
An additional message which appears often, but we're told can be ignored is: Network error SSL read failed: EVP
. " @ionthegeek thinks it may be prometheus trying to hit the RPC endpoint."
Jira Link: DB-11958
Description
Both the Master and the TServers generate a lot of excessive log messages, particularly at the WARN and ERROR level that are generally confusing to users. We should either reword or suppress many of these messages if they are not actually problems and, if they are, be more clear to what the problem is and how to address it.
Master examples:
TServer examples
There are also several coming from CDC via AsyncYBClient that I will have to sanitize before I can share them, e.g.
Some clients are left in the client cache and haven't been cleaned up
Issue Type
kind/bug
Warning: Please confirm that this issue does not contain any sensitive information