[
https://issues.apache.org/jira/browse/HDFS-15878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ayush Saxena resolved HDFS-15878.
-
Fix Version/s: 3.4.0
Hadoop Flags: Reviewed
Resolution: Fixed
> RBF: Fix TestRouterWe
ZanderXu created HDFS-16601:
---
Summary: Failed to replace a bad datanode on the existing pipeline
due to no more good datanodes being available to try
Key: HDFS-16601
URL: https://issues.apache.org/jira/browse/HDFS-16601
[
https://issues.apache.org/jira/browse/HDFS-16597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
fanshilun resolved HDFS-16597.
--
Resolution: Fixed
> RBF: Improve RouterRpcServer#reload With Lambda
> -
[
https://issues.apache.org/jira/browse/HDFS-16587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ayush Saxena resolved HDFS-16587.
-
Fix Version/s: 3.4.0
Hadoop Flags: Reviewed
Resolution: Fixed
> Allow configuring Han
ZanderXu created HDFS-16600:
---
Summary: Deadlock on DataNode
Key: HDFS-16600
URL: https://issues.apache.org/jira/browse/HDFS-16600
Project: Hadoop HDFS
Issue Type: Bug
Reporter: ZanderXu
fanshilun created HDFS-16599:
Summary: Fix typo in RouterRpcClient
Key: HDFS-16599
URL: https://issues.apache.org/jira/browse/HDFS-16599
Project: Hadoop HDFS
Issue Type: Improvement
Affects V
For more details, see
https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java11-linux-x86_64/309/
[May 25, 2022 8:31:18 AM] (noreply) HADOOP-18240. Upgrade Yetus to 0.14.0
(#4328)
[May 26, 2022 3:23:30 AM] (noreply) HADOOP-18251. Fix failure of extracting
JIRA id from commit message in git_jira_
ZanderXu created HDFS-16598:
---
Summary: All datanodes
[DatanodeInfoWithStorage[127.0.0.1:57448,DS-1b5f7e33-a2bf-4edc-9122-a74c995a99f5,DISK]]
are bad. Aborting...
Key: HDFS-16598
URL: https://issues.apache.org/jira/brow
Sounds good, yes they both are not blocker issues for release anyways
(hence +0), just wanted to get more insights. Thanks for the detailed
clarifications Ayush!
Changing my vote to +1 (non-binding).
On Fri, May 27, 2022 at 1:24 PM Ayush Saxena wrote:
> The checksum stuff was addressed in HADO
The checksum stuff was addressed in HADOOP-16985, so that filename stuff is
sorted only post 3.3.x
BTW it is a known issue:
https://issues.apache.org/jira/browse/HADOOP-16494?focusedCommentId=16927236&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16927236
Must not
+0 (non-binding),
* Signature/Checksum looks good, though I am not sure where
"target/artifacts" is coming from for the tars, here is the diff (this was
the case for 2.10.1 as well but checksum was correct):
1c1
< SHA512 (hadoop-2.10.2-site.tar.gz) =
3055a830003f5012660d92da68a317e15da5b73301c2c7
+1 from myself.
* launched pseudo distributed cluster including kms and httpfs with Kerberos
and SSL enabled.
* created encryption zone, put and read files via httpfs.
* ran example MR wordcount over encryption zone.
* skimmed the contents of site documentation.
* built HBase 1.5.0, Hive 2
For more details, see
https://ci-hadoop.apache.org/job/hadoop-qbt-branch-2.10-java7-linux-x86_64/674/
[May 26, 2022 3:31:46 AM] (Masatake Iwasaki) HADOOP-18251. Fix failure of
extracting JIRA id from commit message in git_jira_fix_version_check.py. (#4344)
-1 overall
The following subsyste
13 matches
Mail list logo
