|
Hi Guys, By reading through ceph client codes, there is timeout mechanism in tick when doing mount. Recently we met some client requests to mds spending long time to reply when doing massive test to cephfs. And if we want cephfs user to know the timeout instead of waiting for the reply, can we make following change to leverage such timeout mechanism? Is there any other concern that we didn't enable client request's timeout in tick after mount succeeds? If this works, we can either use client_mount_timeout, or introduce another parameter for normal client request's timeout value. diff --git a/src/client/Client.cc b/src/client/Client.cc index 63a9faa..91a8cc9 100644 --- a/src/client/Client.cc +++ b/src/client/Client.cc @@ -4850,7 +4850,7 @@ void Client::tick() utime_t now = ceph_clock_now(cct); - if (!mounted && !mds_requests.empty()) { + if (!mds_requests.empty()) { MetaRequest *req = mds_requests.begin()->second; if (req->op_stamp + cct->_conf->client_mount_timeout < now) { req->aborted = true; Thanks. David Zhang |
_______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
