[jira] [Created] (HDFS-15161) When evictableMmapped or evictable size is zero, do not throw NoSuchElementException in ShortCircuitCache#close()

Lisheng Sun created HDFS-15161: -- Summary: When evictableMmapped or evictable size is zero, do not throw NoSuchElementException in ShortCircuitCache#close() Key: HDFS-15161 URL: https://issues.apache.org/jira/browse/

[jira] [Updated] (HDFS-15161) When evictableMmapped or evictable size is zero, do not throw NoSuchElementException in ShortCircuitCache#close()

[ https://issues.apache.org/jira/browse/HDFS-15161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lisheng Sun updated HDFS-15161: --- Description: detail see HDFS-14541 {code:java} /** * Close the cache and free all associated resourc

[jira] [Updated] (HDFS-15161) When evictableMmapped or evictable size is zero, do not throw NoSuchElementException in ShortCircuitCache#close()

[ https://issues.apache.org/jira/browse/HDFS-15161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lisheng Sun updated HDFS-15161: --- Attachment: HDFS-15161.001.patch Status: Patch Available (was: Open) > When evictableMmapped

[jira] [Commented] (HDFS-15161) When evictableMmapped or evictable size is zero, do not throw NoSuchElementException in ShortCircuitCache#close()

[ https://issues.apache.org/jira/browse/HDFS-15161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17034237#comment-17034237 ] Ayush Saxena commented on HDFS-15161: - Seems the title of both JIRA's are same, what

[jira] [Commented] (HDFS-15161) When evictableMmapped or evictable size is zero, do not throw NoSuchElementException in ShortCircuitCache#close()

[ https://issues.apache.org/jira/browse/HDFS-15161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17034295#comment-17034295 ] Hadoop QA commented on HDFS-15161: -- | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote

[jira] [Commented] (HDFS-14476) lock too long when fix inconsistent blocks between disk and in-memory

[ https://issues.apache.org/jira/browse/HDFS-14476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17034391#comment-17034391 ] Sean Chow commented on HDFS-14476: -- Hi [~weichiu] , what I can do to make it build pass.

[jira] [Updated] (HDFS-14758) Decrease lease hard limit

[ https://issues.apache.org/jira/browse/HDFS-14758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] hemanthboyina updated HDFS-14758: - Attachment: HDFS-14758.006.patch > Decrease lease hard limit > - > >

[jira] [Commented] (HDFS-14758) Decrease lease hard limit

[ https://issues.apache.org/jira/browse/HDFS-14758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17034446#comment-17034446 ] hemanthboyina commented on HDFS-14758: -- failure test case was not related attached

[jira] [Commented] (HDFS-15161) When evictableMmapped or evictable size is zero, do not throw NoSuchElementException in ShortCircuitCache#close()

[ https://issues.apache.org/jira/browse/HDFS-15161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17034469#comment-17034469 ] Lisheng Sun commented on HDFS-15161: [~ayushtkn] HDFS-14541 left the the problem that

[jira] [Updated] (HDFS-15161) When evictableMmapped or evictable size is zero, do not throw NoSuchElementException in ShortCircuitCache#close()

[ https://issues.apache.org/jira/browse/HDFS-15161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lisheng Sun updated HDFS-15161: --- Attachment: HDFS-15161.002.patch > When evictableMmapped or evictable size is zero, do not throw > N

[jira] [Commented] (HDFS-15161) When evictableMmapped or evictable size is zero, do not throw NoSuchElementException in ShortCircuitCache#close()

[ https://issues.apache.org/jira/browse/HDFS-15161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17034545#comment-17034545 ] Hadoop QA commented on HDFS-15161: -- | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote

[jira] [Updated] (HDFS-15150) Introduce read write lock to Datanode

[ https://issues.apache.org/jira/browse/HDFS-15150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei-Chiu Chuang updated HDFS-15150: --- Fix Version/s: 3.3.0 Resolution: Fixed Status: Resolved (was: Patch Availab

[jira] [Commented] (HDFS-15150) Introduce read write lock to Datanode

[ https://issues.apache.org/jira/browse/HDFS-15150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17034582#comment-17034582 ] Hudson commented on HDFS-15150: --- SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #

[jira] [Commented] (HDFS-14758) Decrease lease hard limit

[ https://issues.apache.org/jira/browse/HDFS-14758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17034603#comment-17034603 ] Hadoop QA commented on HDFS-14758: -- | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote

[jira] [Commented] (HDFS-15161) When evictableMmapped or evictable size is zero, do not throw NoSuchElementException in ShortCircuitCache#close()

[ https://issues.apache.org/jira/browse/HDFS-15161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17034658#comment-17034658 ] Íñigo Goiri commented on HDFS-15161: Yes, we missed this in HDFS-14541. +1 on [^HDFS

[jira] [Updated] (HDFS-15086) Block scheduled counter never get decremet if the block got deleted before replication.

[ https://issues.apache.org/jira/browse/HDFS-15086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] hemanthboyina updated HDFS-15086: - Attachment: HDFS-15086.005.patch > Block scheduled counter never get decremet if the block got de

[jira] [Commented] (HDFS-15086) Block scheduled counter never get decremet if the block got deleted before replication.

[ https://issues.apache.org/jira/browse/HDFS-15086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17034669#comment-17034669 ] hemanthboyina commented on HDFS-15086: -- test failures are not related attached patc

[jira] [Updated] (HDFS-15160) Allow ReplicaMap and callers of ReplicaMap.replicas to use readLock

[ https://issues.apache.org/jira/browse/HDFS-15160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen O'Donnell updated HDFS-15160: - Status: Patch Available (was: Open) > Allow ReplicaMap and callers of ReplicaMap.replica

[jira] [Updated] (HDFS-15160) Allow ReplicaMap and callers of ReplicaMap.replicas to use readLock

[ https://issues.apache.org/jira/browse/HDFS-15160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen O'Donnell updated HDFS-15160: - Attachment: HDFS-15160.001.patch > Allow ReplicaMap and callers of ReplicaMap.replicas to

[jira] [Commented] (HDFS-15086) Block scheduled counter never get decremet if the block got deleted before replication.

[ https://issues.apache.org/jira/browse/HDFS-15086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17034694#comment-17034694 ] Íñigo Goiri commented on HDFS-15086: +1 on [^HDFS-15086.005.patch]. > Block schedul

[jira] [Commented] (HDFS-14758) Decrease lease hard limit

[ https://issues.apache.org/jira/browse/HDFS-14758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17034707#comment-17034707 ] Kihwal Lee commented on HDFS-14758: --- +1 The patch looks good. The white space warning i

[jira] [Commented] (HDFS-15127) RBF: Do not allow writes when a subcluster is unavailable for HASH_ALL mount points.

[ https://issues.apache.org/jira/browse/HDFS-15127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17034716#comment-17034716 ] Íñigo Goiri commented on HDFS-15127: Thanks [~ayushtkn] for the fix. Yes, [^HDFS-1512

[jira] [Created] (HDFS-15162) Optimize frequency of regular block reports

Ayush Saxena created HDFS-15162: --- Summary: Optimize frequency of regular block reports Key: HDFS-15162 URL: https://issues.apache.org/jira/browse/HDFS-15162 Project: Hadoop HDFS Issue Type: Imp

[jira] [Commented] (HDFS-15160) Allow ReplicaMap and callers of ReplicaMap.replicas to use readLock

[ https://issues.apache.org/jira/browse/HDFS-15160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17034753#comment-17034753 ] Hadoop QA commented on HDFS-15160: -- | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote

[jira] [Commented] (HDFS-14758) Decrease lease hard limit

[ https://issues.apache.org/jira/browse/HDFS-14758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17034789#comment-17034789 ] Hudson commented on HDFS-14758: --- SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #

[jira] [Commented] (HDFS-15086) Block scheduled counter never get decremet if the block got deleted before replication.

[ https://issues.apache.org/jira/browse/HDFS-15086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17034833#comment-17034833 ] Hadoop QA commented on HDFS-15086: -- | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote

[jira] [Updated] (HDFS-14758) Decrease lease hard limit

[ https://issues.apache.org/jira/browse/HDFS-14758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kihwal Lee updated HDFS-14758: -- Fix Version/s: 2.10.1 3.2.2 3.1.4 3.3.0 Ha

[jira] [Commented] (HDFS-14758) Decrease lease hard limit

[ https://issues.apache.org/jira/browse/HDFS-14758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17034937#comment-17034937 ] Kihwal Lee commented on HDFS-14758: --- Cherry-picked to branch-2.9 and branch-2.8 as well

[jira] [Updated] (HDFS-14758) Decrease lease hard limit

[ https://issues.apache.org/jira/browse/HDFS-14758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kihwal Lee updated HDFS-14758: -- Fix Version/s: 2.9.3 2.8.6 > Decrease lease hard limit > - >

[jira] [Commented] (HDFS-15160) Allow ReplicaMap and callers of ReplicaMap.replicas to use readLock

[ https://issues.apache.org/jira/browse/HDFS-15160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17034949#comment-17034949 ] Hadoop QA commented on HDFS-15160: -- | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote

[jira] [Commented] (HDFS-15086) Block scheduled counter never get decremet if the block got deleted before replication.

[ https://issues.apache.org/jira/browse/HDFS-15086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17035002#comment-17035002 ] Íñigo Goiri commented on HDFS-15086: TestDelegationTokensWithHA has been consistently

[jira] [Commented] (HDFS-15086) Block scheduled counter never get decremet if the block got deleted before replication.

[ https://issues.apache.org/jira/browse/HDFS-15086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17035025#comment-17035025 ] Ayush Saxena commented on HDFS-15086: - There was a discussion about it in some Jira c

[jira] [Updated] (HDFS-15135) EC : ArrayIndexOutOfBoundsException in BlockRecoveryWorker#RecoveryTaskStriped.

[ https://issues.apache.org/jira/browse/HDFS-15135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ravuri Sushma sree updated HDFS-15135: -- Attachment: HDFS-15135.003.patch > EC : ArrayIndexOutOfBoundsException in > BlockRecov

[jira] [Commented] (HDFS-15135) EC : ArrayIndexOutOfBoundsException in BlockRecoveryWorker#RecoveryTaskStriped.

[ https://issues.apache.org/jira/browse/HDFS-15135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17035050#comment-17035050 ] Hadoop QA commented on HDFS-15135: -- | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote

[jira] [Commented] (HDFS-15030) Add setQuota operation to HttpFS

[ https://issues.apache.org/jira/browse/HDFS-15030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17035071#comment-17035071 ] Takanobu Asanuma commented on HDFS-15030: - [~kihwal] Do you have any comments? >