Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add CPUTimeMetricQueryRunner to ClientQuerySegmentWalker #1765

Merged
merged 1 commit into from
Oct 5, 2015

Conversation

drcrallen
Copy link
Contributor

No description provided.

@nishantmonu51
Copy link
Member

👍

@gianm
Copy link
Contributor

gianm commented Sep 25, 2015

Looks good assuming it works- I am never really sure with the sequences

}
},
emitter,
new AtomicLong(0L),
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is there a purpose to passing this value?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I assume you mean the atomiclong(0). Yes, it goes with the reporting boolean beneath it. If the runner is set to report, then it reports whatever the value of the atomiclong accumulator. It is entirely possible to have multiple runners use the same accumulator and only report once (but that is not the case here)

@himanshug
Copy link
Contributor

LGTM

xvrl added a commit that referenced this pull request Oct 5, 2015
Add CPUTimeMetricQueryRunner to ClientQuerySegmentWalker
@xvrl xvrl merged commit d8a1dd8 into apache:master Oct 5, 2015
@xvrl xvrl deleted the brokerCpuMetrics branch October 5, 2015 17:51
seoeun25 pushed a commit to seoeun25/incubator-druid that referenced this pull request Jan 10, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants