* Get IO request execution profile @ 2017-01-23 12:36 Konstantin Danilov 2017-01-23 12:54 ` John Spray 0 siblings, 1 reply; 6+ messages in thread From: Konstantin Danilov @ 2017-01-23 12:36 UTC (permalink / raw) To: ceph-devel 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? Thanks -- Kostiantyn Danilov aka koder.ua Principal software engineer, Mirantis skype:koder.ua http://koder-ua.blogspot.com/ http://mirantis.com ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Get IO request execution profile 2017-01-23 12:36 Get IO request execution profile Konstantin Danilov @ 2017-01-23 12:54 ` John Spray 2017-01-23 13:59 ` Jason Dillaman 2017-01-24 0:12 ` Gregory Farnum 0 siblings, 2 replies; 6+ messages in thread From: John Spray @ 2017-01-23 12:54 UTC (permalink / raw) To: Konstantin Danilov; +Cc: Ceph Development On Mon, Jan 23, 2017 at 12:36 PM, Konstantin Danilov <kdanilov@mirantis.com> 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 ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Get IO request execution profile 2017-01-23 12:54 ` John Spray @ 2017-01-23 13:59 ` Jason Dillaman 2017-01-23 15:59 ` Konstantin Danilov 2017-01-24 0:12 ` Gregory Farnum 1 sibling, 1 reply; 6+ messages in thread From: Jason Dillaman @ 2017-01-23 13:59 UTC (permalink / raw) 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 <jspray@redhat.com> wrote: > On Mon, Jan 23, 2017 at 12:36 PM, Konstantin Danilov > <kdanilov@mirantis.com> 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 ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Get IO request execution profile 2017-01-23 13:59 ` Jason Dillaman @ 2017-01-23 15:59 ` Konstantin Danilov 2017-01-23 16:02 ` Jason Dillaman 0 siblings, 1 reply; 6+ messages in thread From: Konstantin Danilov @ 2017-01-23 15:59 UTC (permalink / raw) To: dillaman; +Cc: John Spray, Ceph Development > 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? The idea is to monitor requests execution time per stage. dump_historic_ops covers large part of this idea, meanwhile in case of large cluster it hard follow particular request. You have to calculate primary OSD for it. Historic store only slowest requests. To get a timing profile historic ops buffer have to increased to fit all requests. So if you like to get a requests execution profile(and potentially monitor how it changes over time) you can very easily get it for slowest requests, but for all kind of requests it requires tricks and put unnecessary additional load on OSD nodes. > Have you looked at the Zipkin tracking PR [1]? Nope. Is there any plans to merge it? Thanks On Mon, Jan 23, 2017 at 3:59 PM, Jason Dillaman <jdillama@redhat.com> wrote: > 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 <jspray@redhat.com> wrote: >> On Mon, Jan 23, 2017 at 12:36 PM, Konstantin Danilov >> <kdanilov@mirantis.com> 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 -- Kostiantyn Danilov aka koder.ua Principal software engineer, Mirantis skype:koder.ua http://koder-ua.blogspot.com/ http://mirantis.com ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Get IO request execution profile 2017-01-23 15:59 ` Konstantin Danilov @ 2017-01-23 16:02 ` Jason Dillaman 0 siblings, 0 replies; 6+ messages in thread From: Jason Dillaman @ 2017-01-23 16:02 UTC (permalink / raw) To: Konstantin Danilov; +Cc: John Spray, Ceph Development On Mon, Jan 23, 2017 at 10:59 AM, Konstantin Danilov <kdanilov@mirantis.com> wrote: >> Have you looked at the Zipkin tracking PR [1]? > Nope. Is there any plans to merge it? Definitely! It was delayed due to Kraken feature freeze, so now that Kraken is out I'd expect it to pick up steam again and hopefully land in Luminous. -- Jason ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Get IO request execution profile 2017-01-23 12:54 ` John Spray 2017-01-23 13:59 ` Jason Dillaman @ 2017-01-24 0:12 ` Gregory Farnum 1 sibling, 0 replies; 6+ messages in thread From: Gregory Farnum @ 2017-01-24 0:12 UTC (permalink / raw) To: John Spray; +Cc: Konstantin Danilov, Ceph Development On Mon, Jan 23, 2017 at 4:54 AM, John Spray <jspray@redhat.com> wrote: > On Mon, Jan 23, 2017 at 12:36 PM, Konstantin Danilov > <kdanilov@mirantis.com> 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? We don't have very good client-side op tracking yet (at least, not the same way we have the OpTracker server-side), but if we did that would let us identify from a client if server issues were making it very slow. Could be quite useful! -Greg > > 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 ^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2017-01-24 0:12 UTC | newest] Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2017-01-23 12:36 Get IO request execution profile Konstantin Danilov 2017-01-23 12:54 ` John Spray 2017-01-23 13:59 ` Jason Dillaman 2017-01-23 15:59 ` Konstantin Danilov 2017-01-23 16:02 ` Jason Dillaman 2017-01-24 0:12 ` Gregory Farnum
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.