[
https://issues.apache.org/jira/browse/HADOOP-13200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15978907#comment-15978907
]
Wei-Chiu Chuang commented on HADOOP-13200:
------------------------------------------
bq. This is a good point. I don’t worry about this much and guess JVM can
manage the temp objects well, so I’d prefer to leave this simpler. If to avoid
this and use another map managing coder names, it will incur some kinds of
complexity overhead.
Thanks for the comment.
This might be true for other projects, but untrue for Hadoop, especially in
NameNodes.
For DataNodes, this patch returns a new array every time a connection is
established. Given that a DataNode can have thousands of concurrent client
connections on a busy cluster, adding this extra overhead is not a good idea.
Plus, this array will not be updated after initialization. I think we can do a
better job than that. If you think the improvement incurs extra code
complexity, I don't mind filing a new jira to improve this.
> Seeking a better approach allowing to customize and configure erasure coders
> ----------------------------------------------------------------------------
>
> Key: HADOOP-13200
> URL: https://issues.apache.org/jira/browse/HADOOP-13200
> Project: Hadoop Common
> Issue Type: Sub-task
> Reporter: Kai Zheng
> Assignee: Tim Yao
> Priority: Blocker
> Labels: hdfs-ec-3.0-must-do
> Attachments: HADOOP-13200.02.patch, HADOOP-13200.03.patch,
> HADOOP-13200.04.patch, HADOOP-13200.05.patch, HADOOP-13200.06.patch
>
>
> This is a follow-on task for HADOOP-13010 as discussed over there. There may
> be some better approach allowing to customize and configure erasure coders
> than the current having raw coder factory, as [~cmccabe] suggested. Will copy
> the relevant comments here to continue the discussion.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
