summaryrefslogtreecommitdiff
path: root/src/ceph_fuse.cc
diff options
context:
space:
mode:
authorSage Weil <sage@inktank.com>2012-07-17 10:56:15 -0700
committerSage Weil <sage@inktank.com>2012-07-20 18:36:32 -0700
commit7b398a5d9c340159e46c9e8cca05ac079c979340 (patch)
tree8d22465156ae22b671134fd98aab8bffb85db2aa /src/ceph_fuse.cc
parent525830cd0bf9017fe65a52e5e62b483bbb6543b1 (diff)
downloadceph-7b398a5d9c340159e46c9e8cca05ac079c979340.tar.gz
msgr: indicate whether clients are lossy
We need to know whether the client is lossy before we connect to the peer in order to know whether to deliver a RESET event or not on connection failure. Lossy clients get one, lossless do not. And in any case, we know ahead of time, so we may as well indicate as much in the Policy. Signed-off-by: Sage Weil <sage@inktank.com>
Diffstat (limited to 'src/ceph_fuse.cc')
-rw-r--r--src/ceph_fuse.cc5
1 files changed, 5 insertions, 0 deletions
diff --git a/src/ceph_fuse.cc b/src/ceph_fuse.cc
index d76963a7880..d00859404f2 100644
--- a/src/ceph_fuse.cc
+++ b/src/ceph_fuse.cc
@@ -94,6 +94,11 @@ int main(int argc, const char **argv, const char *envp[]) {
entity_name_t::CLIENT(), "client",
getpid());
Client *client = new Client(messenger, &mc);
+
+ messenger->set_default_policy(Messenger::Policy::lossy_client(0, 0));
+ messenger->set_policy(entity_name_t::TYPE_MDS,
+ Messenger::Policy::lossless_client(0, 0));
+
if (filer_flags) {
client->set_filer_flags(filer_flags);
}