Actions
Bug #2377
closedwatch is lost if tcp timeout reached on the connection
Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
% Done:
0%
Source:
Development
Tags:
Backport:
Regression:
Severity:
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
Once tcp timeout is reached on a connection that has a watch on, we don't try to reconnect immediately (should we even have a timeout on that connection?). Second issue is that once we reconnect we don't try to reregister the watch. This can be reproduced like this:
scratchtoolpp --ms-tcp-read-timeout=10
Actions