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

Log metadata and read data latencies #744

Closed

Conversation

mayanks
Copy link
Contributor

@mayanks mayanks commented Mar 3, 2022

Log metadata and read data latencies on the JSON read path. Moreover when the latency is more than a second, log the request id fetched from the response header

@mayanks
Copy link
Contributor Author

mayanks commented Mar 3, 2022

/gcbrun

@codecov
Copy link

codecov bot commented Mar 3, 2022

Codecov Report

❗ No coverage uploaded for pull request base (branch-2.2.x@4e82790). Click here to learn what that means.
The diff coverage is n/a.

❗ Current head 2a9d97a differs from pull request most recent head d80b754. Consider uploading reports for the commit d80b754 to get more accurate results

Impacted file tree graph

@@               Coverage Diff               @@
##             branch-2.2.x     #744   +/-   ##
===============================================
  Coverage                ?   80.29%           
  Complexity              ?     2111           
===============================================
  Files                   ?      146           
  Lines                   ?     9549           
  Branches                ?     1111           
===============================================
  Hits                    ?     7667           
  Misses                  ?     1420           
  Partials                ?      462           
Flag Coverage Δ
hadoop2integrationtest 60.50% <0.00%> (?)
hadoop2unittest 68.82% <0.00%> (?)
hadoop3integrationtest 60.44% <0.00%> (?)
hadoop3unittest 68.86% <0.00%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.


Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 4e82790...d80b754. Read the comment docs.

@Deependra-Patel
Copy link
Member

We should create the PR on master branch and then cherry-pick to this branch?

@mayanks
Copy link
Contributor Author

mayanks commented Mar 8, 2022

/gcbrun

@mayanks
Copy link
Contributor Author

mayanks commented Mar 8, 2022

/gcbrun

@mayanks mayanks requested a review from medb March 8, 2022 15:26
object =
ResilientOperation.retry(
getObject::execute,
readBackOff.get(),
RetryDeterminer.SOCKET_ERRORS,
IOException.class,
sleeper);

long requestDelay = metadataStopwatch.elapsed(MILLISECONDS);
logger.atFinest().log(
Copy link
Contributor

Choose a reason for hiding this comment

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

same here with exceptions

Copy link
Contributor

Choose a reason for hiding this comment

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

Bump

Thread.currentThread().getId(),
metadataStopwatch.elapsed(MILLISECONDS),
resourceId,
getObject.getLastResponseHeaders().getFirstHeaderStringValue("x-guploader-uploadid"));
Copy link
Contributor

Choose a reason for hiding this comment

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

nit: extract string literal to const

@mprashanthsagar
Copy link
Contributor

Please create the pr against master

@mprashanthsagar
Copy link
Contributor

Closing in favor of #749

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.

None yet

3 participants