Bug #9152
closed
mds: beacon needs to not take mds_lock
Added by Sage Weil over 9 years ago.
Updated over 9 years ago.
Description
any random task that holds the mds lock for a long time prevents beacons, which will trigger a failover
Hmm, the beacon send code doesn't need to hold the lock on its own, but it's triggered by the SafeTimer, which is just using the mds lock. (At least, on master.)
Should we just create a separate BeaconTimer that doesn't use the MDS lock?
- Status changed from New to In Progress
- Assignee set to John Spray
- Status changed from In Progress to Fix Under Review
- Status changed from Fix Under Review to Resolved
commit 8657022cc8a664462b57f2d5156970a12c71729c
Merge: d0e0eb4 c8d2388
Author: John Spray <john.spray@inktank.com>
Date: Tue Sep 2 22:02:59 2014 +0100
Merge pull request #2343 from ceph/wip-9151
Wip 9151 + 9152
Reviewed-by: Sage Weil <sage@redhat.com>
Also available in: Atom
PDF