From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jason Dillaman Subject: Re: Get IO request execution profile Date: Mon, 23 Jan 2017 08:59:33 -0500 Message-ID: References: Reply-To: dillaman@redhat.com Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Return-path: Received: from mail-lf0-f46.google.com ([209.85.215.46]:36390 "EHLO mail-lf0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751004AbdAWN7g (ORCPT ); Mon, 23 Jan 2017 08:59:36 -0500 Received: by mail-lf0-f46.google.com with SMTP id z134so93827765lff.3 for ; Mon, 23 Jan 2017 05:59:35 -0800 (PST) In-Reply-To: Sender: ceph-devel-owner@vger.kernel.org List-ID: To: John Spray Cc: Konstantin Danilov , Ceph Development Have you looked at the Zipkin tracking PR [1]? [1] https://github.com/ceph/ceph/pull/11053 On Mon, Jan 23, 2017 at 7:54 AM, John Spray wrote: > On Mon, Jan 23, 2017 at 12:36 PM, Konstantin Danilov > wrote: >> Hi all, >> >> is there a way to get something like 'dump historic ops' for particular request? >> Probably from client side. Ideally I'd like to send a normal IO >> request with special >> flag and get execution profile in response metadata. >> If it's not possible right now - is this an interesting feature to >> implement, or I miss >> something and it's useless? > > Potentially interesting idea, although it's not obvious to me why it's > useful to have this dumped on the client rather than the server? > Would be it equally useful to be able to tag a specific client on the > server side to have its requests dumped like this? > > John > >> >> Thanks >> >> -- >> Kostiantyn Danilov aka koder.ua >> Principal software engineer, Mirantis >> >> skype:koder.ua >> http://koder-ua.blogspot.com/ >> http://mirantis.com >> -- >> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in >> the body of a message to majordomo@vger.kernel.org >> More majordomo info at http://vger.kernel.org/majordomo-info.html > -- > To unsubscribe from this list: send the line "unsubscribe ceph-devel" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html -- Jason