The timer is added to the runtime profile by ADD_TIMER(), and incremented by CANCEL_SAFE_SCOPED_TIMER(), as Andrey said. What's the issue you're seeing?
On 7 March 2017 at 23:13, Jim Apple <[email protected]> wrote: > I don't see any other user of this either. Feel free to file a JIRA on > this, and, if you like, a patch: > https://cwiki.apache.org/confluence/display/IMPALA/Contributing+to+Impala > > On Fri, Feb 24, 2017 at 3:12 AM, Andrey Morskoy <[email protected]> wrote: > > > Seems that's it: > > DataStreamRecvr::SenderQueue::AddBatch: > > if (timer_lock) { > > CANCEL_SAFE_SCOPED_TIMER(recvr_->buffer_full_wall_timer_, > > &is_cancelled_); > > .... > > > > On Fri, Feb 24, 2017 at 12:35 PM, Andrey Morskoy <[email protected]> > wrote: > > > > > Could you please explain a code pattern for situation: > > > In a data-stream-recvr.cc there is section: > > > buffer_full_wall_timer_ = ADD_TIMER(profile_, "SendersBlockedTimer"); > > > > > > > > > But I could not find the code section responsible for increment this > > > timer. Thanks > > > > > > > > > -- Henry Robinson Software Engineer Cloudera 415-994-6679
