[
https://issues.apache.org/jira/browse/HDFS-17503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17841815#comment-17841815
]
Zilong Zhu commented on HDFS-17503:
-----------------------------------
[~Keepromise] It appears to occur when creating the BlockSender object. This is
an intermittent issue that occurs in our production environment. If I manually
throw an OOM error while creating the BlockSender object, it can cause volume
references not to be released.
> Unreleased volume references because of OOM
> -------------------------------------------
>
> Key: HDFS-17503
> URL: https://issues.apache.org/jira/browse/HDFS-17503
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: Zilong Zhu
> Assignee: Zilong Zhu
> Priority: Major
>
> When BlockSender throws an error because of OOM，the volume reference obtained
> by the thread is not released，which causes the thread trying to remove the
> volume to wait and fall into an infinite loop.
> I found HDFS-15963 catched exception and release volume reference. But it did
> not handle the case of throwing errors. I think "catch (Throwable t)" should
> be used instead of "catch (IOException ioe)".
--
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
