Details
-
Improvement
-
Resolution: Duplicate
-
Major
-
5.5.1
Description
Related to customer issue CBSE-5708; during investigation it wasn't totally clear from the KV-Engine log file that KV-Engine had disconnected the consumer because a DCP noop hadn't been received in the timeout interval:
|
hmm, the dcp connection had been closed by KV engine because it thought the connection was dead:
|
018-09-19T15:31:34.511759Z NOTICE (id) DCP (Producer) eq_dcpq:xdcr:dcp_ce9eb17426e623e573c1ec25b3dc874f/id/id_ip-<REDACTED>:11210_1:RMzi-3B1t1E4eXuM54ufaw== - Disconnected because the connection appears to be dead
|
"Appears to be dead" actually means "DCP noop message not received within the timeout window" - To the casual observer this could be misleading.
We should improve the message, making it more explicit exactly what has occurred to avoid any confusion in future.
Attachments
Issue Links
- duplicates
-
MB-29872 KV-engine closing DCP connections to eventing due to noop timeout
- Closed