-
Notifications
You must be signed in to change notification settings - Fork 616
HDDS-3981. Add more debug level log to XceiverClientGrpc for debug purpose #1214
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
Merged
+15
−3
Merged
Changes from 7 commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
0729631
HDDS-3981. Add more debug level log to XceiverClientGrpc for debug pu…
maobaolong 39a4825
trigger new ci check
maobaolong a49773e
trigger new ci check
maobaolong e1d7e9a
trigger new ci check
maobaolong 9e13176
trigger new ci check
maobaolong 6a3d7b3
trigger new ci check
maobaolong 6a7a413
Address comments, log the ip address o dn only.
maobaolong 0f027d8
Address comment, move the debug log into sendCommandAsync
maobaolong File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
In sendCommandAsync() below we already have a LOG.debug(cmdType, Dn). Can you move this there to avoid duplicate debug log?
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.
@xiaoyuyao I hope so, but I think it would be difficult, because, i want to log the retry index and cost time.
when the
sendCommandAsyncreturn back, the client still doesn't get the result from datanode. the result return until thegetreturn.If i have something wrong, please correct me.
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.
I mean if we could move the LOG for latency around Line 464 where the container op latency metrics are updated. This way, we can piggyback LOG with the existing metrics update.
metrics.addContainerOpsLatency(request.getCmdType(),
System.nanoTime() - requestTime);
Uh oh!
There was an error while loading. Please reload this page.
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.
@xiaoyuyao Thanks you for your reply and suggestion. I tried to add the LOG into the L464, like following
But, there are some question
Indexwhich stand for the retried datanode index of thedatanodeList.onErroralso? Otherwise, when we met error, theonNextwon't be executed.As
indexcan be calculate from the log context, I drop it.