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
Expose AWS HTTP Client stats via JMX #6503
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can this be tested, perhaps in TestHiveFileSystemS3
?
I tried and I failed. It could be testable easily if we had PT referencing S3. Then we could verify the metrics using query over |
7b4ee55
to
a21fedb
Compare
In |
I spent more time on that. I can run the test. I see that stats callback are being called. But I cannot read JMX values as mbeans are not registered at all in tests. All the JMX mbean registration is happening via Guice automation which is not done by the test at all. I would say it is not worth it.... |
Thanks for investigating this. |
That is typical issue when doing unit tests for JMX. Rule of thumb: it does not work. I have seen few examples of case where it worked but then such test has to be executed in separation as any other test can override mbeans or take precedence (not sure what actually happens). The only advised way for JMX tests are product tests. |
No description provided.