I think this is a great idea, and should be implemented not only for transactions, but also for SQL queries. Users should be able to turn this tracing on and off through JMX and API. I am assuming that this information will be dumped into the log as well, right?
D. On Fri, Jul 21, 2017 at 12:04 PM, Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > Alex, > > That's a great idea. I would also add an option to dump information on > demand, for case when operation hanged and can't complete. > > -Val > > On Fri, Jul 21, 2017 at 6:15 AM, Alexey Goncharuk < > alexey.goncha...@gmail.com> wrote: > > > Igniters, > > > > I've recently stumbled across a situation when occasionally Ignite > > transactions commit may take up to several seconds while in general most > of > > the transactions completed in a period of milliseconds. > > > > After a few attempts to analyze this situation with logs, I realized that > > this is a no-go and I need a finer instrument for this. The idea is to > > introduce several trace points along the way of an Ignite operation and > > collect timings when an operation passes each of the trace points. When > > enabled, this information should be available upon the operation > > completion. > > > > I've implemented a prototype of this for TX commit operation, the > > implementation is available in ignite-5797 branch. > > > > I was wondering if something of this kind may be useful as a part of > Ignite > > product and available to users. If so, I would like to discuss the public > > API for this so the feature can be finalized. > > > > Thanks, > > AG > > >
