[jira] [Created] (HDFS-17469) Audit log for reportBadBlocks RPC

2024-04-15 Thread dzcxzl (Jira)
dzcxzl created HDFS-17469:
-

 Summary: Audit log for reportBadBlocks RPC
 Key: HDFS-17469
 URL: https://issues.apache.org/jira/browse/HDFS-17469
 Project: Hadoop HDFS
  Issue Type: Improvement
  Components: namenode
Reporter: dzcxzl


After [HDFS-10347|https://issues.apache.org/jira/browse/HDFS-10347], we can 
know the DN corresponding to the reported bad block, but we do not know the 
reported Client IP.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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



[jira] [Updated] (HDFS-16672) Fix lease interval comparison in BlockReportLeaseManager

2022-07-20 Thread dzcxzl (Jira)


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

dzcxzl updated HDFS-16672:
--
Description: 
monotonicNowMs is generated by System.nanoTime(), direct comparison is not 
recommended.

 

org.apache.hadoop.hdfs.server.blockmanagement.BlockReportLeaseManager#pruneIfExpired
{code:java}
if (monotonicNowMs < node.leaseTimeMs + leaseExpiryMs) {
  return false;
} {code}

  was:
org.apache.hadoop.hdfs.server.blockmanagement.BlockReportLeaseManager#pruneIfExpired
{code:java}
if (monotonicNowMs < node.leaseTimeMs + leaseExpiryMs) {
  return false;
} {code}


> Fix lease interval comparison in BlockReportLeaseManager
> 
>
> Key: HDFS-16672
> URL: https://issues.apache.org/jira/browse/HDFS-16672
> Project: Hadoop HDFS
>  Issue Type: Bug
>  Components: namenode
>Reporter: dzcxzl
>Assignee: dzcxzl
>Priority: Trivial
>  Labels: pull-request-available
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> monotonicNowMs is generated by System.nanoTime(), direct comparison is not 
> recommended.
>  
> org.apache.hadoop.hdfs.server.blockmanagement.BlockReportLeaseManager#pruneIfExpired
> {code:java}
> if (monotonicNowMs < node.leaseTimeMs + leaseExpiryMs) {
>   return false;
> } {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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



[jira] [Assigned] (HDFS-16672) Fix lease interval comparison in BlockReportLeaseManager

2022-07-20 Thread dzcxzl (Jira)


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

dzcxzl reassigned HDFS-16672:
-

Assignee: dzcxzl

> Fix lease interval comparison in BlockReportLeaseManager
> 
>
> Key: HDFS-16672
> URL: https://issues.apache.org/jira/browse/HDFS-16672
> Project: Hadoop HDFS
>  Issue Type: Bug
>  Components: namenode
>Reporter: dzcxzl
>Assignee: dzcxzl
>Priority: Trivial
>
> org.apache.hadoop.hdfs.server.blockmanagement.BlockReportLeaseManager#pruneIfExpired
> {code:java}
> if (monotonicNowMs < node.leaseTimeMs + leaseExpiryMs) {
>   return false;
> } {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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



[jira] [Created] (HDFS-16672) Fix lease interval comparison in BlockReportLeaseManager

2022-07-20 Thread dzcxzl (Jira)
dzcxzl created HDFS-16672:
-

 Summary: Fix lease interval comparison in BlockReportLeaseManager
 Key: HDFS-16672
 URL: https://issues.apache.org/jira/browse/HDFS-16672
 Project: Hadoop HDFS
  Issue Type: Bug
  Components: namenode
Reporter: dzcxzl


org.apache.hadoop.hdfs.server.blockmanagement.BlockReportLeaseManager#pruneIfExpired
{code:java}
if (monotonicNowMs < node.leaseTimeMs + leaseExpiryMs) {
  return false;
} {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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



[jira] [Created] (HDFS-16638) Add isDebugEnabled check for debug blockLogs in BlockManager

2022-06-21 Thread dzcxzl (Jira)
dzcxzl created HDFS-16638:
-

 Summary: Add isDebugEnabled check for debug blockLogs in 
BlockManager
 Key: HDFS-16638
 URL: https://issues.apache.org/jira/browse/HDFS-16638
 Project: Hadoop HDFS
  Issue Type: Improvement
  Components: namenode
Reporter: dzcxzl


There are lots of concatenating Strings using blockLog.debug in BlockManager.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

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



[jira] [Commented] (HDFS-15472) Erasure Coding: Support fallback read when zero copy is not supported

2021-03-22 Thread dzcxzl (Jira)


[ 
https://issues.apache.org/jira/browse/HDFS-15472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17305983#comment-17305983
 ] 

dzcxzl commented on HDFS-15472:
---

Can you review this patch when you are free? [~ayushtkn] [~weichiu]

> Erasure Coding: Support fallback read when zero copy is not supported
> -
>
> Key: HDFS-15472
> URL: https://issues.apache.org/jira/browse/HDFS-15472
> Project: Hadoop HDFS
>  Issue Type: Bug
>Reporter: dzcxzl
>Priority: Trivial
> Attachments: HDFS-15472.000.patch, HDFS-15472.001.patch
>
>
> [HDFS-8203|https://issues.apache.org/jira/browse/HDFS-8203] 
> ec does not support zeor copy read, but currently does not support fallback 
> read, it will throw an exception.
> {code:java}
> Caused by: java.lang.UnsupportedOperationException: Not support enhanced byte 
> buffer access.
> at 
> org.apache.hadoop.hdfs.DFSStripedInputStream.read(DFSStripedInputStream.java:524)
> at org.apache.hadoop.fs.FSDataInputStream.read(FSDataInputStream.java:188)
> at 
> org.apache.hadoop.hive.shims.ZeroCopyShims$ZeroCopyAdapter.readBuffer(ZeroCopyShims.java:79)
> {code}
>  



--
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] [Commented] (HDFS-15472) Erasure Coding: Support fallback read when zero copy is not supported

2020-07-21 Thread dzcxzl (Jira)


[ 
https://issues.apache.org/jira/browse/HDFS-15472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17162045#comment-17162045
 ] 

dzcxzl commented on HDFS-15472:
---

I moved the logic of fallback read to DFSStripedInputStream and added a unit 
test to it.

> Erasure Coding: Support fallback read when zero copy is not supported
> -
>
> Key: HDFS-15472
> URL: https://issues.apache.org/jira/browse/HDFS-15472
> Project: Hadoop HDFS
>  Issue Type: Bug
>Reporter: dzcxzl
>Priority: Trivial
> Attachments: HDFS-15472.000.patch, HDFS-15472.001.patch
>
>
> [HDFS-8203|https://issues.apache.org/jira/browse/HDFS-8203] 
> ec does not support zeor copy read, but currently does not support fallback 
> read, it will throw an exception.
> {code:java}
> Caused by: java.lang.UnsupportedOperationException: Not support enhanced byte 
> buffer access.
> at 
> org.apache.hadoop.hdfs.DFSStripedInputStream.read(DFSStripedInputStream.java:524)
> at org.apache.hadoop.fs.FSDataInputStream.read(FSDataInputStream.java:188)
> at 
> org.apache.hadoop.hive.shims.ZeroCopyShims$ZeroCopyAdapter.readBuffer(ZeroCopyShims.java:79)
> {code}
>  



--
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-15472) Erasure Coding: Support fallback read when zero copy is not supported

2020-07-21 Thread dzcxzl (Jira)


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

dzcxzl updated HDFS-15472:
--
Attachment: HDFS-15472.001.patch

> Erasure Coding: Support fallback read when zero copy is not supported
> -
>
> Key: HDFS-15472
> URL: https://issues.apache.org/jira/browse/HDFS-15472
> Project: Hadoop HDFS
>  Issue Type: Bug
>Reporter: dzcxzl
>Priority: Trivial
> Attachments: HDFS-15472.000.patch, HDFS-15472.001.patch
>
>
> [HDFS-8203|https://issues.apache.org/jira/browse/HDFS-8203] 
> ec does not support zeor copy read, but currently does not support fallback 
> read, it will throw an exception.
> {code:java}
> Caused by: java.lang.UnsupportedOperationException: Not support enhanced byte 
> buffer access.
> at 
> org.apache.hadoop.hdfs.DFSStripedInputStream.read(DFSStripedInputStream.java:524)
> at org.apache.hadoop.fs.FSDataInputStream.read(FSDataInputStream.java:188)
> at 
> org.apache.hadoop.hive.shims.ZeroCopyShims$ZeroCopyAdapter.readBuffer(ZeroCopyShims.java:79)
> {code}
>  



--
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-15472) Erasure Coding: Support fallback read when zero copy is not supported

2020-07-15 Thread dzcxzl (Jira)


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

dzcxzl updated HDFS-15472:
--
Attachment: HDFS-15472.000.patch

> Erasure Coding: Support fallback read when zero copy is not supported
> -
>
> Key: HDFS-15472
> URL: https://issues.apache.org/jira/browse/HDFS-15472
> Project: Hadoop HDFS
>  Issue Type: Bug
>Reporter: dzcxzl
>Priority: Trivial
> Attachments: HDFS-15472.000.patch
>
>
> [HDFS-8203|https://issues.apache.org/jira/browse/HDFS-8203] 
> ec does not support zeor copy read, but currently does not support fallback 
> read, it will throw an exception.
> {code:java}
> Caused by: java.lang.UnsupportedOperationException: Not support enhanced byte 
> buffer access.
> at 
> org.apache.hadoop.hdfs.DFSStripedInputStream.read(DFSStripedInputStream.java:524)
> at org.apache.hadoop.fs.FSDataInputStream.read(FSDataInputStream.java:188)
> at 
> org.apache.hadoop.hive.shims.ZeroCopyShims$ZeroCopyAdapter.readBuffer(ZeroCopyShims.java:79)
> {code}
>  



--
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] [Created] (HDFS-15472) Erasure Coding: Support fallback read when zero copy is not supported

2020-07-15 Thread dzcxzl (Jira)
dzcxzl created HDFS-15472:
-

 Summary: Erasure Coding: Support fallback read when zero copy is 
not supported
 Key: HDFS-15472
 URL: https://issues.apache.org/jira/browse/HDFS-15472
 Project: Hadoop HDFS
  Issue Type: Bug
Reporter: dzcxzl


[HDFS-8203|https://issues.apache.org/jira/browse/HDFS-8203] 

ec does not support zeor copy read, but currently does not support fallback 
read, it will throw an exception.
{code:java}
Caused by: java.lang.UnsupportedOperationException: Not support enhanced byte 
buffer access.
at 
org.apache.hadoop.hdfs.DFSStripedInputStream.read(DFSStripedInputStream.java:524)
at org.apache.hadoop.fs.FSDataInputStream.read(FSDataInputStream.java:188)
at 
org.apache.hadoop.hive.shims.ZeroCopyShims$ZeroCopyAdapter.readBuffer(ZeroCopyShims.java:79)
{code}
 



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