[
https://issues.apache.org/jira/browse/HDFS-14822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Shvachko updated HDFS-14822:
---------------------------------------
Target Version/s: 2.10.0
Labels: release-blocker (was: )
> [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
>
> 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.2#803003)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
