[
https://issues.apache.org/jira/browse/HDFS-16431?focusedWorklogId=731344&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-731344
]
ASF GitHub Bot logged work on HDFS-16431:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 23/Feb/22 04:29
Start Date: 23/Feb/22 04:29
Worklog Time Spent: 10m
Work Description: Hexiaoqiao commented on pull request #3909:
URL: https://github.com/apache/hadoop/pull/3909#issuecomment-1048440490
Thanks @smarthanwang involve me here. I am not very familiar with
CallerContext. I think @jojochuang should be the good candidate to review it.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 731344)
Time Spent: 2h 10m (was: 2h)
> Truncate CallerContext in client side
> -------------------------------------
>
> Key: HDFS-16431
> URL: https://issues.apache.org/jira/browse/HDFS-16431
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: nn
> Reporter: Chengwei Wang
> Assignee: Chengwei Wang
> Priority: Major
> Labels: pull-request-available
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
> The context of CallerContext would be truncated when it exceeds the maximum
> allowed length in server side. I think it's better to do check and truncate
> in client side to reduce the unnecessary overhead of network and memory for
> NN.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
