[
https://issues.apache.org/jira/browse/HDFS-17762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17938598#comment-17938598
]
ASF GitHub Bot commented on HDFS-17762:
---------------------------------------
hfutatzhanghb commented on PR #7539:
URL: https://github.com/apache/hadoop/pull/7539#issuecomment-2754246539
> > addClientInfoToCallerContext
>
> hi @hfutatzhanghb thanks, got it! We can fix this issue in the transfer
method of ThreadLocalContext:
>
> ```java
> public void transfer() {
> if (call != null) {
> Server.getCurCall().set(call);
> }
> CallerContext.setCurrent(null);
> if (context != null) {
> CallerContext.setCurrent(context);
> }
> if (startOpTime != -1L) {
> FederationRPCPerformanceMonitor.setStartOpTime(startOpTime);
> }
> if (proxyOpTime != -1L) {
> FederationRPCPerformanceMonitor.setProxyOpTime(proxyOpTime);
> }
> }
> ```
@KeeProMise Thanks for this nice suggestion, move
`CallerContext.setCurrent(null);` to transfer() seems better, because the goal
of this method is to manipulate ThreadLocal object. Will modify it. Thanks
again.
> [ARR] Reset CallerContext information when async handler thread done
> --------------------------------------------------------------------
>
> Key: HDFS-17762
> URL: https://issues.apache.org/jira/browse/HDFS-17762
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: rbf
> Reporter: farmmamba
> Assignee: farmmamba
> Priority: Major
> Labels: pull-request-available
>
> CallerContext information may be wrong due to the async handler executor
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
