Description
The gomemcached client currently enables dead-connection detection by default with a 2 minute interval - however this only ensures disconnection by the Producer in the event of a slow Consumer, and not vice-versa.
Currently the gomemcached client just responds to a NOOP request and goes back to listening for the next event.
Hence we need to implement the logic to disconnect as the Consumer to a slow Producer; and then that will be used to replace the CheckStuckness() logic flow.
Attachments
Issue Links
- is a backport of
-
MB-62624 XDCR - Utilise dead-connection detection for a "stuck" DCP Producer
- Resolved
Gerrit Reviews
For Gerrit Dashboard: MB-63125 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
215861,1 | MB-63125: Utilise dead-connection detection for a "stuck" DCP Producer | neo | gomemcached | Status: NEW | +2 | +1 |
215862,2 | MB-63125: Utilise dead-connection detection for a "stuck" DCP Producer | neo | goxdcr | Status: NEW | +2 | +1 |