diff options
author | Sage Weil <sage@newdream.net> | 2010-03-22 14:51:18 -0700 |
---|---|---|
committer | Sage Weil <sage@newdream.net> | 2010-03-23 07:47:01 -0700 |
commit | 87b315a5b5cec5d7086494b203577602f5befc8c (patch) | |
tree | 18e1638619a51cdf4605bad5b4270841450cf211 /fs/pipe.c | |
parent | 3dd72fc0e6dc49c79fa9e7cd7c654deac7ccaa29 (diff) | |
download | op-kernel-dev-87b315a5b5cec5d7086494b203577602f5befc8c.zip op-kernel-dev-87b315a5b5cec5d7086494b203577602f5befc8c.tar.gz |
ceph: avoid reopening osd connections when address hasn't changed
We get a fault callback on _every_ tcp connection fault. Normally, we
want to reopen the connection when that happens. If the address we have
is bad, however, and connection attempts always result in a connection
refused or similar error, explicitly closing and reopening the msgr
connection just prevents the messenger's backoff logic from kicking in.
The result can be a console full of
[ 3974.417106] ceph: osd11 10.3.14.138:6800 connection failed
[ 3974.423295] ceph: osd11 10.3.14.138:6800 connection failed
[ 3974.429709] ceph: osd11 10.3.14.138:6800 connection failed
Instead, if we get a fault, and have outstanding requests, but the osd
address hasn't changed and the connection never successfully connected in
the first place, do nothing to the osd connection. The messenger layer
will back off and retry periodically, because we never connected and thus
the lossy bit is not set.
Instead, touch each request's r_stamp so that handle_timeout can tell the
request is still alive and kicking.
Signed-off-by: Sage Weil <sage@newdream.net>
Diffstat (limited to 'fs/pipe.c')
0 files changed, 0 insertions, 0 deletions