diff options
| author | Sage Weil <sage@newdream.net> | 2010-03-18 14:45:05 -0700 |
|---|---|---|
| committer | Sage Weil <sage@newdream.net> | 2010-05-17 15:25:35 -0700 |
| commit | 29790f26ab3e63b2a083f0811b80e2f086e4fcb2 (patch) | |
| tree | 0d254b23871db399e036c019c121f6d5c7c7b3db /mm | |
| parent | aab53dd9e81ccefa7b8d88eec5138dd73639a783 (diff) | |
| download | op-kernel-dev-29790f26ab3e63b2a083f0811b80e2f086e4fcb2.zip op-kernel-dev-29790f26ab3e63b2a083f0811b80e2f086e4fcb2.tar.gz | |
ceph: wait for mds OPEN reply to indicate reconnect success
We used to infer reconnect success by watching the MDS state, essentially
assuming that hearing nothing meant things were ok. That wasn't
particularly reliable. Instead, the MDS replies with an explicit OPEN
message to indicate success.
Strictly speaking, this is a protocol change, but it is a backwards
compatible one that does not break new clients + old servers or old
clients + new servers. At least not yet.
Drop unused @all argument from kick_requests while we're at it.
Signed-off-by: Sage Weil <sage@newdream.net>
Diffstat (limited to 'mm')
0 files changed, 0 insertions, 0 deletions
