[
https://issues.apache.org/jira/browse/HDFS-11410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15871075#comment-15871075
]
Hudson commented on HDFS-11410:
-------------------------------
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #11272 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/11272/])
HDFS-11410. Use the cached instance when edit logging SetAclOp, (xiao: rev
02c549484a4fe6215c7f1a18d89389dbba6ea723)
* (edit)
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/FSEditLog.java
* (edit)
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/FSEditLogOp.java
> Use the cached instance when edit logging SetAclOp, SetXAttrOp and
> RemoveXAttrOp
> --------------------------------------------------------------------------------
>
> Key: HDFS-11410
> URL: https://issues.apache.org/jira/browse/HDFS-11410
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: namenode
> Affects Versions: 2.5.0
> Reporter: Xiao Chen
> Assignee: Xiao Chen
> Fix For: 2.9.0, 3.0.0-alpha3
>
> Attachments: HDFS-11410.01.patch
>
>
> [~andrew.wang] recently had a comment on HDFS-10899:
> {quote}
> Looks like we aren't using the op cache in FSEditLog SetXAttrOp /
> RemoveXAttrOp. I think this is accidental, could you do some research?
> Particularly since we'll be doing a lot of SetXAttrOps, avoiding all that
> object allocation would be nice. This could be a separate JIRA.
> {quote}
> i.e.
> {code}
> static SetXAttrOp getInstance() {
> return new SetXAttrOp();
> }
> {code}
> v.s.
> {code}
> static AddOp getInstance(OpInstanceCache cache) {
> return (AddOp) cache.get(OP_ADD);
> }
> {code}
> Seems we should fix these non-caching usages.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
