You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2022/04/08 07:35:00 UTC
[jira] [Work logged] (HDFS-16431) Truncate CallerContext in client side
[ https://issues.apache.org/jira/browse/HDFS-16431?focusedWorklogId=754444&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-754444 ]
ASF GitHub Bot logged work on HDFS-16431:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 08/Apr/22 07:34
Start Date: 08/Apr/22 07:34
Worklog Time Spent: 10m
Work Description: smarthanwang commented on PR #3909:
URL: https://github.com/apache/hadoop/pull/3909#issuecomment-1092545709
@jojochuang @ferhui cloud you take a look?
Issue Time Tracking
-------------------
Worklog Id: (was: 754444)
Time Spent: 2.5h (was: 2h 20m)
> 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: 2.5h
> 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: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org