Re: [VOTE] Apache Hadoop Ozone 0.4.2-alpha RC0

2020-02-04 Thread Dinesh Chitlangia
The vote ended with lone vote of 0 from Marton. As highlighted by Marton, artifacts with Snapshot dependencies can't be uploaded to Maven Central, we will roll out a new RC after ratis-0.5 has been released. Issue of missing README will also be addressed in the new RC. Thank you. Dinesh On Thu,

[jira] [Created] (HDFS-15153) TestDelegationTokensWithHA.testObserverReadProxyProviderWithDT fails intermittently

2020-02-04 Thread Chen Liang (Jira)
Chen Liang created HDFS-15153: - Summary: TestDelegationTokensWithHA.testObserverReadProxyProviderWithDT fails intermittently Key: HDFS-15153 URL: https://issues.apache.org/jira/browse/HDFS-15153

Re: Alternative Decommission Monitor Implementation

2020-02-04 Thread Wei-Chiu Chuang
@Akira Ajisaka you said you'd be interested, right? Are you planning to adopt this feature? On Tue, Feb 4, 2020 at 10:41 AM Stephen O'Donnell wrote: > Hi All, > > In https://issues.apache.org/jira/browse/HDFS-14854 we committed a new > decommission monitor to trunk, which is disabled by

Re: Introduce Read Write Lock to Datanode

2020-02-04 Thread Wei-Chiu Chuang
Thanks for initiating this discussion here. I am +1 to the general approach proposed. With DN getting denser, this is necessary more than ever. On Tue, Feb 4, 2020 at 10:33 AM Stephen O'Donnell wrote: > I would like to reopen an old topic, which is to introduce a Read Write > lock to the

Alternative Decommission Monitor Implementation

2020-02-04 Thread Stephen O'Donnell
Hi All, In https://issues.apache.org/jira/browse/HDFS-14854 we committed a new decommission monitor to trunk, which is disabled by default. The new implementation hopes to be an improvement over the original monitor, but without running it on a real cluster it is hard to know for sure. I would

Introduce Read Write Lock to Datanode

2020-02-04 Thread Stephen O'Donnell
I would like to reopen an old topic, which is to introduce a Read Write lock to the datanode. In the current trunk, a RentrentLock is used, so it is always exclusive. However there are many code paths in the DN where an exclusive lock is not necessary and a read lock would suffice. We know the

Apache Hadoop qbt Report: branch2.10+JDK7 on Linux/x86

2020-02-04 Thread Apache Jenkins Server
For more details, see https://builds.apache.org/job/hadoop-qbt-branch-2.10-java7-linux-x86/587/ No changes -1 overall The following subsystems voted -1: asflicense findbugs hadolint pathlen unit xml The following subsystems voted -1 but were configured to be filtered/ignored: cc

Restrict Frequency of BlockReport To Namenode startup and failover

2020-02-04 Thread Ayush Saxena
Hi All, Me and Surendra have been lately trying to minimise the impact of Block Reports on Namenode in huge cluster. We observed in a huge cluster, about 10k datanodes, the periodic block reports impact the Namenode performance adversely. We have been thinking to restrict the block reports to be