[jira] [Created] (HDFS-3644) OEV should recognize and deal with 0.20.20x opcode versions

Todd Lipcon created HDFS-3644: - Summary: OEV should recognize and deal with 0.20.20x opcode versions Key: HDFS-3644 URL: https://issues.apache.org/jira/browse/HDFS-3644 Project: Hadoop HDFS

Build failed in Jenkins: Hadoop-Hdfs-trunk #1101

See https://builds.apache.org/job/Hadoop-Hdfs-trunk/1101/changes Changes: [atm] HADOOP-8541. Better high-percentile latency metrics. Contributed by Andrew Wang. [atm] HADOOP-8585. Fix initialization circularity between UserGroupInformation and HadoopConfiguration. Contributed by Colin Patrick

Hadoop-Hdfs-trunk - Build # 1101 - Still Failing

See https://builds.apache.org/job/Hadoop-Hdfs-trunk/1101/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 11650 lines...] [INFO] ---

Jenkins build is back to stable : Hadoop-Hdfs-0.23-Build #311

See https://builds.apache.org/job/Hadoop-Hdfs-0.23-Build/311/changes

[jira] [Created] (HDFS-3646) LeaseRenewer can hold reference to inactive DFSClient instances

Kihwal Lee created HDFS-3646: Summary: LeaseRenewer can hold reference to inactive DFSClient instances Key: HDFS-3646 URL: https://issues.apache.org/jira/browse/HDFS-3646 Project: Hadoop HDFS

StreamXMLRecordReader

Guys, Can you please explain, why StreamXMLRecordReader class is removed from Hadoop 2.0.0 Version.? Is it good go for Mahout XMLInputFormat API ? Thanks, Siv

[jira] [Resolved] (HDFS-3644) OEV should recognize and deal with 0.20.20x opcode versions

[ https://issues.apache.org/jira/browse/HDFS-3644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suresh Srinivas resolved HDFS-3644. --- Resolution: Won't Fix This jira is not necessary. The conflict code was only in 0.20.203.

[jira] [Reopened] (HDFS-3644) OEV should recognize and deal with 0.20.20x opcode versions

[ https://issues.apache.org/jira/browse/HDFS-3644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon reopened HDFS-3644: --- I disagree. There are people running systems with LV -19 which has the conflicted opcodes. Currently if

[jira] [Created] (HDFS-3647) Expose dfs.datanode.max.xcievers as metric

Steve Hoffman created HDFS-3647: --- Summary: Expose dfs.datanode.max.xcievers as metric Key: HDFS-3647 URL: https://issues.apache.org/jira/browse/HDFS-3647 Project: Hadoop HDFS Issue Type:

[jira] [Created] (HDFS-3648) TestRaidNode.testDistRaid fails

Eli Collins created HDFS-3648: - Summary: TestRaidNode.testDistRaid fails Key: HDFS-3648 URL: https://issues.apache.org/jira/browse/HDFS-3648 Project: Hadoop HDFS Issue Type: Bug Affects

[jira] [Resolved] (HDFS-3648) TestRaidNode.testDistRaid fails

[ https://issues.apache.org/jira/browse/HDFS-3648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe resolved HDFS-3648. -- Resolution: Duplicate TestRaidNode.testDistRaid fails ---

[jira] [Created] (HDFS-3649) Port HDFS-385 to branch-1-win

Sumadhur Reddy Bolli created HDFS-3649: -- Summary: Port HDFS-385 to branch-1-win Key: HDFS-3649 URL: https://issues.apache.org/jira/browse/HDFS-3649 Project: Hadoop HDFS Issue Type:

[jira] [Created] (HDFS-3650) Use MutableQuantiles to provide latency histograms for various operations

Andrew Wang created HDFS-3650: - Summary: Use MutableQuantiles to provide latency histograms for various operations Key: HDFS-3650 URL: https://issues.apache.org/jira/browse/HDFS-3650 Project: Hadoop HDFS

[jira] [Created] (HDFS-3651) optionally, the NameNode should invoke saveNamespace after getting a SIGTERM

Colin Patrick McCabe created HDFS-3651: -- Summary: optionally, the NameNode should invoke saveNamespace after getting a SIGTERM Key: HDFS-3651 URL: https://issues.apache.org/jira/browse/HDFS-3651

[jira] [Created] (HDFS-3652) 1.x: FSEditLog failure removes the wrong edit stream when storage dirs have same name

Todd Lipcon created HDFS-3652: - Summary: 1.x: FSEditLog failure removes the wrong edit stream when storage dirs have same name Key: HDFS-3652 URL: https://issues.apache.org/jira/browse/HDFS-3652 Project:

[jira] [Created] (HDFS-3653) 1.x: Add a retention period for purged edit logs

Todd Lipcon created HDFS-3653: - Summary: 1.x: Add a retention period for purged edit logs Key: HDFS-3653 URL: https://issues.apache.org/jira/browse/HDFS-3653 Project: Hadoop HDFS Issue Type:

[jira] [Created] (HDFS-3654) TestJspHelper#testGetUgi may fail

Eli Collins created HDFS-3654: - Summary: TestJspHelper#testGetUgi may fail Key: HDFS-3654 URL: https://issues.apache.org/jira/browse/HDFS-3654 Project: Hadoop HDFS Issue Type: Improvement

[jira] [Created] (HDFS-3655) datenode recoverRbw could hang sometime

Ming Ma created HDFS-3655: - Summary: datenode recoverRbw could hang sometime Key: HDFS-3655 URL: https://issues.apache.org/jira/browse/HDFS-3655 Project: Hadoop HDFS Issue Type: Bug

[jira] [Reopened] (HDFS-799) libhdfs must call DetachCurrentThread when a thread is destroyed

[ https://issues.apache.org/jira/browse/HDFS-799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin Patrick McCabe reopened HDFS-799: --- reopening to remove unnecessary if statement (as adi pointed out)

Re: StreamXMLRecordReader

Hi Siv, Moving this to mapreduce-user@, please use developer lists only for project development questions. The class StreamXmlRecordReader is still present in 2.0.0 and will continue to be present. Why do you say it has been removed? It now resides in the hadoop-tools jar (which is what carries

[jira] [Resolved] (HDFS-3652) 1.x: FSEditLog failure removes the wrong edit stream when storage dirs have same name

[ https://issues.apache.org/jira/browse/HDFS-3652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon resolved HDFS-3652. --- Resolution: Fixed Fix Version/s: 1.2.0 1.1.0 1.0.4