Actions
Bug #1107
closedmsgr: old outgoing connection + mark_down leaves stale state on remote peer
Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
% Done:
0%
Source:
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
Peers A and B:
- A reached epoch 10, in which A and B should exchange heartbeats
- A advances to epoch 20, and closes pipe to B
- B reaches epoch 10, opens connection to A
- A accepts connection
- B reaches epoch 20, closes it's end of connection to A
-> A still has connection state with B, but won't mark it down (again)
I think the solution is for incoming connections to start in 'server' mode, where a failure closes out the connection, unless the receiving end explicitly does a mark_lossless(). This should map cleanly onto the heartbeat exchange code. Need to look more closely at how the connection policy is applied..
Updated by Greg Farnum about 5 years ago
- Project changed from Ceph to Messengers
- Category deleted (
msgr) - Target version deleted (
v0.29)
Actions