[jira] [Resolved] (HDFS-17405) [FGL] Using different metric name to trace FGL and Global lock

2024-03-05 Thread Hui Fei (Jira)
[ https://issues.apache.org/jira/browse/HDFS-17405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hui Fei resolved HDFS-17405. Resolution: Fixed > [FGL] Using different metric name to trace FGL and Global lock > --

Re: Discussion about NameNode Fine-grained locking

2024-03-05 Thread Yuanbo Liu
I've heard zgc is better in jdk17 or above, so I think the major problem is that we have to upgrade hadoop code to fit in jdk17. We were using jdk11 with zgc to test NN, and didn't see an impressive improvement. On Wed, Mar 6, 2024 at 11:53 AM Takanobu Asanuma wrote: > > We're trying tuning gc o

Re: [DISCUSS] Support/Fate of HBase v1 in Hadoop

2024-03-05 Thread slfan1989
+1 Option2 I also agree with the idea of upgrading hbase 2.2 to 2.5. Shilun Fan. > Hbase v1 is EOL for a while now, so option 2 probably makes sense. While > you are at it you should probably update the hbase2 version, because 2.2.x > is also very old and EOL. 2.5.x is the currently maintained r

Re: Discussion about NameNode Fine-grained locking

2024-03-05 Thread Takanobu Asanuma
> We're trying tuning gc options and even new gc engine like zgc, but they are not very helpful. I'm afraid this is a digression, but could you elaborate on using ZGC for NameNode? Did you encounter any problems? I've never heard of using ZGC for NameNode in practice, so I'm curious about it. Reg

Re: Discussion about NameNode Fine-grained locking

2024-03-05 Thread Yuanbo Liu
> a. Snapshot, Symbolic link and reserved feature are not mentioned at the design doc, should it be considered Yes, I agree. Since the snapshot、symbol link is not popular in HADOOP, we can try to use global lock(write lock of root inode?). In our production env, we just ignore those features, but i

Re: Discussion about NameNode Fine-grained locking

2024-03-05 Thread Hui Fei
Thanks for suggestions. Actually Started working on this improvement. And cut the development branch :) >From the proposal doc and the current reviewing work, seems that it doesn't touch the existing logic codes too much. It keeps the original logic there. @Yuanbo @Zengqiang XU Could you share

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

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

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

2024-03-05 Thread Apache Jenkins Server
For more details, see https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java11-linux-x86_64/640/ 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:

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

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

[jira] [Resolved] (HDFS-17404) Add Namenode info to log message when setting block keys from active nn

2024-03-05 Thread Chris Trezzo (Jira)
[ https://issues.apache.org/jira/browse/HDFS-17404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Trezzo resolved HDFS-17404. - Resolution: Fixed > Add Namenode info to log message when setting block keys from active nn > ---

[jira] [Created] (HDFS-17409) TestDFSAdmin has couple of flaky tests.

2024-03-05 Thread Rushabh Shah (Jira)
Rushabh Shah created HDFS-17409: --- Summary: TestDFSAdmin has couple of flaky tests. Key: HDFS-17409 URL: https://issues.apache.org/jira/browse/HDFS-17409 Project: Hadoop HDFS Issue Type: Bug

[jira] [Reopened] (HDFS-17384) [FGL] Replace the global lock with global FS Lock and global BM lock

2024-03-05 Thread Hui Fei (Jira)
[ https://issues.apache.org/jira/browse/HDFS-17384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hui Fei reopened HDFS-17384: > [FGL] Replace the global lock with global FS Lock and global BM lock > --

[jira] [Resolved] (HDFS-17384) [FGL] Replace the global lock with global FS Lock and global BM lock

2024-03-05 Thread Hui Fei (Jira)
[ https://issues.apache.org/jira/browse/HDFS-17384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hui Fei resolved HDFS-17384. Resolution: Fixed > [FGL] Replace the global lock with global FS Lock and global BM lock >

Re: [DISCUSS] Support/Fate of HBase v1 in Hadoop

2024-03-05 Thread Bryan Beaudreault
Hbase v1 is EOL for a while now, so option 2 probably makes sense. While you are at it you should probably update the hbase2 version, because 2.2.x is also very old and EOL. 2.5.x is the currently maintained release for hbase2, with 2.5.7 being the latest. We’re soon going to release 2.6.0 as well.

[DISCUSS] Support/Fate of HBase v1 in Hadoop

2024-03-05 Thread Ayush Saxena
Hi Folks, As of now we have two profiles for HBase: one for HBase v1(1.7.1) & other for v2(2.2.4). The versions are specified over here: [1], how to build is mentioned over here: [2] As of now we by default run our Jenkins "only" for HBase v1, so we have seen HBase v2 profile silently breaking a c

Re: HDFS test builds always fails

2024-03-05 Thread Ayush Saxena
Hi, We have a PR [1] which is gonna fix those tests related to those java ByteBuffer, I will follow up on that & get it merged. -Ayush [1] https://github.com/apache/hadoop/pull/6593 On Tue, 5 Mar 2024 at 12:59, 王磊 wrote: > Hi, I found some tests always fails in some pull requests such as > had