[jira] [Updated] (HDFS-14822) [SBN read] Revisit GlobalStateIdContext locking when getting server state id

2019-09-18 Thread Chen Liang (Jira) 


 [ 
https://issues.apache.org/jira/browse/HDFS-14822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chen Liang updated HDFS-14822:
--
Fix Version/s: 3.2.2
   3.1.4
   3.3.0
   2.10.0
   Resolution: Fixed
   Status: Resolved  (was: Patch Available)

> [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
> Fix For: 2.10.0, 3.3.0, 3.1.4, 3.2.2
>
> 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

[jira] [Updated] (HDFS-14822) [SBN read] Revisit GlobalStateIdContext locking when getting server state id

2019-09-05 Thread Chen Liang (Jira) 


 [ 
https://issues.apache.org/jira/browse/HDFS-14822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chen Liang updated HDFS-14822:
--
Status: Patch Available  (was: Open)

> [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.2#803003)

-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org

[jira] [Updated] (HDFS-14822) [SBN read] Revisit GlobalStateIdContext locking when getting server state id

2019-09-05 Thread Chen Liang (Jira) 


 [ 
https://issues.apache.org/jira/browse/HDFS-14822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chen Liang updated HDFS-14822:
--
Attachment: HDFS-14822.001.patch

> [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.2#803003)

-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org

[jira] [Updated] (HDFS-14822) [SBN read] Revisit GlobalStateIdContext locking when getting server state id

2019-09-04 Thread Konstantin Shvachko (Jira) 


 [ 
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

[jira] [Updated] (HDFS-14822) [SBN read] Revisit GlobalStateIdContext locking when getting server state id

2019-09-04 Thread Chen Liang (Jira) 


 [ 
https://issues.apache.org/jira/browse/HDFS-14822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chen Liang updated HDFS-14822:
--
Summary: [SBN read] Revisit GlobalStateIdContext locking when getting 
server state id  (was: Revisit GlobalStateIdContext locking when getting server 
state id)

> [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
>
> 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