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

2024-11-11 Thread Apache Jenkins Server
For more details, see https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java8-linux-x86_64/1758/ No changes -1 overall The following subsystems voted -1: blanks hadolint pathlen xml The following subsystems voted -1 but were configured to be filtered/ignored: cc checkstyle javac j

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

2024-11-11 Thread Apache Jenkins Server
For more details, see https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java11-linux-x86_64/768/ No changes -1 overall The following subsystems voted -1: blanks hadolint mvnsite pathlen spotbugs unit xml The following subsystems voted -1 but were configured to be filtered/ignored:

[jira] [Created] (HDFS-17662) Block recovery inter-datanode operations should have higher priority than DataXceiver

2024-11-11 Thread Shangshu Qian (Jira)
Shangshu Qian created HDFS-17662: Summary: Block recovery inter-datanode operations should have higher priority than DataXceiver Key: HDFS-17662 URL: https://issues.apache.org/jira/browse/HDFS-17662 P

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

2024-11-11 Thread Apache Jenkins Server
For more details, see https://ci-hadoop.apache.org/job/hadoop-qbt-branch-2.10-java7-linux-x86_64/1573/ 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

[jira] [Resolved] (HDFS-17596) [ARR] RouterStoragePolicy supports asynchronous rpc.

2024-11-11 Thread Jian Zhang (Jira)
[ https://issues.apache.org/jira/browse/HDFS-17596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian Zhang resolved HDFS-17596. --- Fix Version/s: HDFS-17531 Resolution: Done > [ARR] RouterStoragePolicy supports asynchronous r

Question regarding HDFS HA setup in a peculiar state

2024-11-11 Thread Gaurav Mittal
Hi hdfs-devs, I am reaching out to better understand how to resolve the following scenario where one of the JournalNodes has fallen behind (NameNode is no longer writing to it) and is no longer able to sync to the latest state. We are considering a couple of options: 1. Shutdown the JN that has f