For more details, see
https://ci-hadoop.apache.org/job/hadoop-qbt-branch-3.2-java8-linux-x86_64/29/
[Jan 5, 2022 4:02:49 PM] (Stephen O'Donnell) HDFS-16408. Ensure
LeaseRecheckIntervalMs is greater than zero (#3856)
[Jan 10, 2022 5:14:52 PM] (Akira Ajisaka) HDFS-16410. Insecure Xml parsing in
O
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
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
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
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.
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
[
https://issues.apache.org/jira/browse/HADOOP-18077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wei-Chiu Chuang resolved HADOOP-18077.
--
Fix Version/s: 3.4.0
Resolution: Fixed
> ProfileOutputServlet unable to procee
