[
https://issues.apache.org/jira/browse/HDFS-16869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Ma updated HDFS-16869:
-----------------------------
Summary: Fail to start namenode owing to 0 size of clientid recorded in
edit log. (was: DelegationTokenRenewer timeout feature may cause high
utilization of CPU and object leak)
> Fail to start namenode owing to 0 size of clientid recorded in edit log.
> ------------------------------------------------------------------------
>
> Key: HDFS-16869
> URL: https://issues.apache.org/jira/browse/HDFS-16869
> Project: Hadoop HDFS
> Issue Type: Improvement
> Affects Versions: 3.3.1, 3.3.2, 3.3.3, 3.3.4
> Reporter: Daniel Ma
> Assignee: Daniel Ma
> Priority: Major
>
> DelegationTokenRenewer timeout feature may cause high utilization of CPU and
> object leak。
> 1-If yarn cluster is in idle state, that is almost no token renewer event
> triggered, the DelegationTokenRenewerPoolTracker thread will do nothing but
> dead loop, it will cause high CPU utilization.
> 2-The renewer event is hold in a map named futures, will has no remove logic
> , that is the map will become increasingly great with time going by.
--
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
