[jira] [Created] (HDFS-14780) make the information of SlowPeersReport in namenode's jmx more specific

HaiBin Huang created HDFS-14780: --- Summary: make the information of SlowPeersReport in namenode's jmx more specific Key: HDFS-14780 URL: https://issues.apache.org/jira/browse/HDFS-14780 Project: Hadoop H

[jira] [Created] (HDDS-2043) "VOLUME_NOT_FOUND" exception thrown while listing volumes

Nilotpal Nandi created HDDS-2043: Summary: "VOLUME_NOT_FOUND" exception thrown while listing volumes Key: HDDS-2043 URL: https://issues.apache.org/jira/browse/HDDS-2043 Project: Hadoop Distributed Data

[jira] [Created] (HDFS-14781) DN Web UI : Navigate to Live Nodes in Datanodes Page when click on Live Nodes in Overview

hemanthboyina created HDFS-14781: Summary: DN Web UI : Navigate to Live Nodes in Datanodes Page when click on Live Nodes in Overview Key: HDFS-14781 URL: https://issues.apache.org/jira/browse/HDFS-14781

[Help] NameNode error

Hi committee, We encountered a NN error as below, The primary NN was shut down last Thursday and we recover it by remove some OP in the edit log.. But today the standby NN was shut down again by the same error... could you pls help address the possible root cause? 2019-08-27 09:51:14,075 ERROR

[jira] [Resolved] (HDFS-14770) Erasure Coding: reconstructed internal block is error

[ https://issues.apache.org/jira/browse/HDFS-14770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] HuangTao resolved HDFS-14770. - Resolution: Not A Problem > Erasure Coding: reconstructed internal block is error > -

[jira] [Created] (HDFS-14782) Add a new fsck command to get detailed decommission information.

Jinglun created HDFS-14782: -- Summary: Add a new fsck command to get detailed decommission information. Key: HDFS-14782 URL: https://issues.apache.org/jira/browse/HDFS-14782 Project: Hadoop HDFS Iss

[jira] [Created] (HDFS-14783) expired SlowPeersReport will keep staying on namenode's jmx

HaiBin Huang created HDFS-14783: --- Summary: expired SlowPeersReport will keep staying on namenode's jmx Key: HDFS-14783 URL: https://issues.apache.org/jira/browse/HDFS-14783 Project: Hadoop HDFS

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

For more details, see https://builds.apache.org/job/hadoop-qbt-branch2-java7-linux-x86/426/ [Aug 26, 2019 9:32:27 PM] (cliang) HDFS-13977. NameNode can kill itself if it tries to send too many txns [Aug 26, 2019 11:05:25 PM] (jhung) YARN-9775. RMWebServices /scheduler-conf GET returns all hadoo

Re: [Help] NameNode error

That's not supposed to happen. What version of Hadoop are you using? It Please file a jira with details including how the namenodes are configured. For the recovery: First and foremost, do not shut down the active namenode. Put it into safe mode and issue a saveNamespace command to create a checkp

[jira] [Created] (HDFS-14784) Add more methods to WebHdfsTestUtil to support tests outside of package

Chen Zhang created HDFS-14784: - Summary: Add more methods to WebHdfsTestUtil to support tests outside of package Key: HDFS-14784 URL: https://issues.apache.org/jira/browse/HDFS-14784 Project: Hadoop HDFS

[jira] [Created] (HDDS-2044) Remove 'ozone' from the recon module names.

Aravindan Vijayan created HDDS-2044: --- Summary: Remove 'ozone' from the recon module names. Key: HDDS-2044 URL: https://issues.apache.org/jira/browse/HDDS-2044 Project: Hadoop Distributed Data Store

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

For more details, see https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/1241/ [Aug 26, 2019 10:37:26 AM] (ewan.higgs) Revert "HADOOP-16193. Add extra S3A MPU test to see what happens if a [Aug 26, 2019 3:36:15 PM] (rohithsharmaks) YARN-8917. Absolute (maximum) capacity of level3+ q

[jira] [Created] (HDDS-2045) Partially started compose cluster left running

Doroszlai, Attila created HDDS-2045: --- Summary: Partially started compose cluster left running Key: HDDS-2045 URL: https://issues.apache.org/jira/browse/HDDS-2045 Project: Hadoop Distributed Data Stor

[DISCUSS] GitHub PRs without JIRA number

Hi, There are hundreds of GitHub PRs pending review. Many of them just sit there wasting Jenkins resources. I suggest: (1) close PRs that went stale (i.e. doesn't compile). Or even close PRs that hasn't been reviewed for more than a year. (1) close PRs that doesn't have a JIRA number. No one is go

[jira] [Created] (HDDS-2046) Fix NOTICE file

Arpit Agarwal created HDDS-2046: --- Summary: Fix NOTICE file Key: HDDS-2046 URL: https://issues.apache.org/jira/browse/HDDS-2046 Project: Hadoop Distributed Data Store Issue Type: Bug Affects

[jira] [Created] (HDFS-14785) [SBN read] Change client logging to be less aggressive

Chen Liang created HDFS-14785: - Summary: [SBN read] Change client logging to be less aggressive Key: HDFS-14785 URL: https://issues.apache.org/jira/browse/HDFS-14785 Project: Hadoop HDFS Issue Ty

Re: [VOTE] Mark 2.6, 2.7, 3.0 release lines EOL

+1 for the proposal. I thought we already EOL-ed 2.6 though some time ago. Thanks, --Konstantin On Tue, Aug 20, 2019 at 8:03 PM Wangda Tan wrote: > Hi all, > > This is a vote thread to mark any versions smaller than 2.7 (inclusive), > and 3.0 EOL. This is based on discussions of [1] > > This d

Re: [VOTE] Merge YARN-8200 to branch-2 and branch-3.0

+1 for the merge. We probably should not bother with branch-3.0 merge since it's been voted EOL. Thanks, --Konstantin On Thu, Aug 22, 2019 at 4:43 PM Jonathan Hung wrote: > Hi folks, > > As per [1], starting a vote to merge YARN-8200 (and YARN-8200.branch3) > feature branch to branch-2 (and br

Re: [DISCUSS] GitHub PRs without JIRA number

I wouldn't go for #3 and always require a JIRA for a PR. In general, I think we should state the best practices for using GitHub PRs. There were some guidelines but they were kind of open For example, adding always a link to the JIRA to the description. I think PRs can have a template as a start.

[jira] [Created] (HDDS-2047) Datanodes fail to come up after 10 retries in a secure environment

Vivek Ratnavel Subramanian created HDDS-2047: Summary: Datanodes fail to come up after 10 retries in a secure environment Key: HDDS-2047 URL: https://issues.apache.org/jira/browse/HDDS-2047

branch-3. Was it a created by mistake?

I just realized there is a branch-3 in the Hadoop repo. Was this created by mistake? I don't think we've decided to create a branch-3. It also looks like the branch is rarely used. The last commit was commit bf90a27b51b1f1ac102fa861eb28025d21aad19b (origin/branch-3, branch-3) Author: Chen Liang

[jira] [Created] (HDFS-14786) A new block placement policy tolerating availability zone failure

Mingliang Liu created HDFS-14786: Summary: A new block placement policy tolerating availability zone failure Key: HDFS-14786 URL: https://issues.apache.org/jira/browse/HDFS-14786 Project: Hadoop HDFS

[jira] [Created] (HDFS-14787) [Help] NameNode error

: namenode Affects Versions: 3.0.0 Reporter: Cao, Lionel Attachments: core-site.xml, hadoop-cmf-hdfs-NAMENODE-smc-nn02.jq.log.out.20190827, hdfs-site.xml, move&concat.java, rt-Append.txt Hi committee, We encountered a NN error as below, The primary NN was shut down

Re: [Help] NameNode error

Hi Kihwal, Thank you for the quick response. I have created a Jira ticket https://issues.apache.org/jira/browse/HDFS-14787 In this ticket I attached some log, configuration file and code. We did some append or concat operation on hdfs file and I'm not sure whether the NN shutdown was caused by t

Re: [Help] NameNode error

sorry missed the version 3.0.0-cdh6.0.1 From: "whuca...@outlook.com" mailto:whuca...@outlook.com>> Date: Wednesday, 28 August 2019 at 10:53 AM To: Kihwal Lee mailto:kih...@verizonmedia.com>> Cc: "hdfs-dev@hadoop.apache.org" mailto:h

Re: branch-3. Was it a created by mistake?

IIRC, This was created accidentally. You should take a look at earlier discussion thread for more info i.e https://s.apache.org/zla4u -Rohith Sharma K S On Wed, 28 Aug 2019 at 04:54, Wei-Chiu Chuang wrote: > I just realized there is a branch-3 in the Hadoop repo. Was this created by > mistake