Actions
Bug #39305
closedceph-fuse: client hang because its bad session PipeConnection to mds
% Done:
0%
Source:
Community (dev)
Tags:
Backport:
nautilus,mimic,luminous
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(FS):
Labels (FS):
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
There still has a risk client will hang all the time and which happened in my enviroment
a few days ago. Well konw, the start of mds will go through four stages at least(replay,
reconnect, rejoin, active). According to current logic, we recived replay mdsmap and
marked down pipe will return directly and if we miss the next reconnect mdsmap the client
may hang all the time becuase we lost the opportunity due to old_inc equal tonew_inc.
So we shuold judge if we have lost MDSMap::reconnect by comparing newstate and oldstate.
Updated by Patrick Donnelly about 5 years ago
- Related to Bug #36079: ceph-fuse: hang because it miss reconnect phase when hot standby mds switch occurs added
Updated by Patrick Donnelly about 5 years ago
- Subject changed from ceph-fuse:client hang because its bad session PipeConnection to mds to ceph-fuse: client hang because its bad session PipeConnection to mds
- Status changed from New to Fix Under Review
- Assignee set to Ivan Guan
- Target version set to v15.0.0
- Start date deleted (
04/16/2019) - Source set to Community (dev)
- Backport set to nautilus,mimic,luminous
- Pull request ID set to 27482
Updated by Patrick Donnelly about 5 years ago
- Status changed from Fix Under Review to Pending Backport
Updated by Nathan Cutler about 5 years ago
- Copied to Backport #39685: mimic: ceph-fuse: client hang because its bad session PipeConnection to mds added
Updated by Nathan Cutler about 5 years ago
- Copied to Backport #39686: nautilus: ceph-fuse: client hang because its bad session PipeConnection to mds added
Updated by Nathan Cutler about 5 years ago
- Copied to Backport #39687: luminous: ceph-fuse: client hang because its bad session PipeConnection to mds added
Updated by Nathan Cutler about 4 years ago
- Status changed from Pending Backport to Resolved
While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".
Actions