[jira] [Created] (HDFS-16422) Fix thread safety of EC decoding during concurrent preads

daimin created HDFS-16422: - Summary: Fix thread safety of EC decoding during concurrent preads Key: HDFS-16422 URL: https://issues.apache.org/jira/browse/HDFS-16422 Project: Hadoop HDFS Issue Type: B

[jira] [Resolved] (HDFS-16043) Add markedDeleteBlockScrubberThread to delete blocks asynchronously

[ https://issues.apache.org/jira/browse/HDFS-16043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He resolved HDFS-16043. Fix Version/s: 3.4.0 Hadoop Flags: Reviewed Resolution: Fixed Committed to trunk. Will

[jira] [Created] (HDFS-16421) RouterRpcFairnessConstants remove ConcurrentNS

Xiangyi Zhu created HDFS-16421: -- Summary: RouterRpcFairnessConstants remove ConcurrentNS Key: HDFS-16421 URL: https://issues.apache.org/jira/browse/HDFS-16421 Project: Hadoop HDFS Issue Type: I

Apache Hadoop qbt Report: trunk+JDK8 on Linux/x86_64

For more details, see https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java8-linux-x86_64/748/ [Jan 11, 2022 6:38:59 AM] (noreply) YARN-10632. Make auto queue creation maximum allowed depth configurable (#3859) -1 overall The following subsystems voted -1: blanks pathlen unit xml Th

Re: ElasticByteBufferPool is ever growing thus can cause memory leak.

DirectBufferPool does the weak refs effectively, but it only recycles buffers of the same size; the elastic one will return the first largest buffer. I think we may want to have a variant of the ElasticBufferPool which uses weak refs..we can adopt that and leave the (old) one alone. It is marked a

Re: ElasticByteBufferPool is ever growing thus can cause memory leak.

Thanks for discussing this, Mukund. Another difference between the 2 classes is that ElasticByteBufferPool supports a caller's preference for either on-heap or off-heap buffers and internally calls either allocate or allocateDirect. Do you intend to preserve that functionality too in a single merg

[jira] [Resolved] (HDFS-16419) Make HDFS data transfer tools cross platform

[ https://issues.apache.org/jira/browse/HDFS-16419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gautham Banasandra resolved HDFS-16419. --- Resolution: Fixed Merged https://github.com/apache/hadoop/pull/3873 to trunk. > Make

[jira] [Resolved] (HDFS-16019) HDFS: Inode CheckPoint

[ https://issues.apache.org/jira/browse/HDFS-16019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiangyi Zhu resolved HDFS-16019. Resolution: Later > HDFS: Inode CheckPoint > --- > > Key: HDFS

ElasticByteBufferPool is ever growing thus can cause memory leak.

Hello Everyone, I was just browsing through the code while doing my Vectored IO stuff. It seems like ElasticByteBufferPool is an ever growing pool and memory is not getting released as there is no WeakReference being maintained in the pool. This can cause memory leaks in the production environment.

Apache Hadoop qbt Report: branch-2.10+JDK7 on Linux/x86_64

For more details, see https://ci-hadoop.apache.org/job/hadoop-qbt-branch-2.10-java7-linux-x86_64/540/ No changes -1 overall The following subsystems voted -1: asflicense hadolint mvnsite pathlen unit The following subsystems voted -1 but were configured to be filtered/ignored: cc