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 "Akira Ajisaka (JIRA)" <ji...@apache.org> on 2017/02/24 19:18:44 UTC
[jira] [Updated] (HDFS-10620) StringBuilder created and appended
even if logging is disabled
[ https://issues.apache.org/jira/browse/HDFS-10620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Akira Ajisaka updated HDFS-10620:
---------------------------------
Resolution: Fixed
Fix Version/s: 2.9.0
Status: Resolved (was: Patch Available)
Committed this to branch-2. Thanks [~jzhuge]!
> StringBuilder created and appended even if logging is disabled
> --------------------------------------------------------------
>
> Key: HDFS-10620
> URL: https://issues.apache.org/jira/browse/HDFS-10620
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: namenode
> Affects Versions: 2.6.4
> Reporter: Staffan Friberg
> Assignee: Staffan Friberg
> Fix For: 2.9.0, 3.0.0-alpha3
>
> Attachments: HDFS-10620.001.patch, HDFS-10620.002.patch, HDFS-10620-branch-2.01.patch
>
>
> In BlockManager.addToInvalidates the StringBuilder is appended to during the delete even if logging isn't active.
> Could avoid allocating the StringBuilder as well, but not sure if it is really worth it to add null handling in the code.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org