[
https://issues.apache.org/jira/browse/HDFS-14822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16932928#comment-16932928
]
Hudson commented on HDFS-14822:
-------------------------------
FAILURE: Integrated in Jenkins build Hadoop-trunk-Commit #17328 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/17328/])
HDFS-14822. [SBN read] Revisit GlobalStateIdContext locking when getting
(cliang: rev 4ed0aefe9fd3c79546d39e10ec81a142fa7b80ac)
* (edit)
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/GlobalStateIdContext.java
> [SBN read] Revisit GlobalStateIdContext locking when getting server state id
> ----------------------------------------------------------------------------
>
> Key: HDFS-14822
> URL: https://issues.apache.org/jira/browse/HDFS-14822
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: hdfs
> Reporter: Chen Liang
> Assignee: Chen Liang
> Priority: Major
> Labels: release-blocker
> Attachments: HDFS-14822.001.patch
>
>
> As mentioned under HDFS-14277. One potential performance issue of Observer
> read is that {{GlobalStateIdContext#getLastSeenStateId}} calls
> getCorrectLastAppliedOrWrittenTxId which ends up acquiring lock on txnid. We
> internally had some discussion and analysis, we believe this lock can be
> avoided, by calling the non-locking version method
> {{getLastAppliedOrWrittenTxId.}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
