You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-dev@hadoop.apache.org by "Chen Liang (Jira)" <ji...@apache.org> on 2019/09/04 18:10:00 UTC
[jira] [Created] (HDFS-14822) Revisit GlobalStateIdContext locking
when getting server state id
Chen Liang created HDFS-14822:
---------------------------------
Summary: 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
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-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org