I encountered the same issue in my setup (with an AWS SDK client) and on further investigation found that 'rgw print continue' was set to false for a civetweb driven rgw.
Updated http://tracker.ceph.com/issues/12640 Giridhar -- Giridhar Yasa | Flipkart Engineering | http://www.flipkart.com/ On Thu, Aug 6, 2015 at 5:31 AM, Srikanth Madugundi <srikanth.madugu...@gmail.com> wrote: > Hi, > > After upgrading to Hammer and moving from apache to civetweb. We > started seeing high PUT latency in the order of 2 sec for every PUT > request. The GET request lo > > Attaching the radosgw logs for a single request. The ceph.conf has the > following configuration for civetweb. > > [client.radosgw.gateway] > rgw frontends = civetweb port=5632 > > > Further investion reveled the call to get_data() at > https://github.com/ceph/ceph/blob/hammer/src/rgw/rgw_op.cc#L1786 is > taking 2 sec to respond. The cluster is running Hammer 94.2 release > > Did any one face this issue before? Is there some configuration I am missing? > > Regards > Srikanth > > _______________________________________________ > ceph-users mailing list > ceph-us...@lists.ceph.com > http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com > -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
