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

See https://hudson.apache.org/hudson/job/Hadoop-Hdfs-trunk/595/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 740316 lines...] [junit] at org.apache.had

Hadoop-Hdfs-trunk-Commit - Build # 551 - Failure

See https://hudson.apache.org/hudson/job/Hadoop-Hdfs-trunk-Commit/551/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 1408 lines...] clean-sign: sign: signandd

[jira] Resolved: (HDFS-1706) Hdfs Federation: TestFileAppend2, TestFileAppend3 and TestBlockTokenWithDFS failing

[ https://issues.apache.org/jira/browse/HDFS-1706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jitendra Nath Pandey resolved HDFS-1706. Resolution: Fixed I have committed this. > Hdfs Federation: TestFileAppend2, TestFi

[jira] Resolved: (HDFS-1707) Hdfs Federation: Failure in browsing data on new namenodes

[ https://issues.apache.org/jira/browse/HDFS-1707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jitendra Nath Pandey resolved HDFS-1707. Resolution: Fixed Hadoop Flags: [Reviewed] I have committed this. > Hdfs Fede

[jira] Resolved: (HDFS-1684) Federation: Balancer cannot start with with multiple namenodes.

[ https://issues.apache.org/jira/browse/HDFS-1684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo (Nicholas), SZE resolved HDFS-1684. -- Resolution: Fixed Fix Version/s: Federation Branch Hadoop Flags: [Rev

[jira] Resolved: (HDFS-1708) Federation: remove datanode's datanodeId TODOs

[ https://issues.apache.org/jira/browse/HDFS-1708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Boris Shkolnik resolved HDFS-1708. -- Resolution: Invalid this issue is invalid, because most of the stuff is fixed somewhere else. >

[jira] Created: (HDFS-1711) create method for updating machine name in DataNode.java

create method for updating machine name in DataNode.java Key: HDFS-1711 URL: https://issues.apache.org/jira/browse/HDFS-1711 Project: Hadoop HDFS Issue Type: Sub-task Repor

[jira] Created: (HDFS-1712) when looking up datanode we should use machineNmae (in testOverReplicatedBlocks)

when looking up datanode we should use machineNmae (in testOverReplicatedBlocks) - Key: HDFS-1712 URL: https://issues.apache.org/jira/browse/HDFS-1712 Project: Hadoop HD

[jira] Created: (HDFS-1713) Hdfs Federation: Prevent DataBlockScanner from running in tight loop

Hdfs Federation: Prevent DataBlockScanner from running in tight loop - Key: HDFS-1713 URL: https://issues.apache.org/jira/browse/HDFS-1713 Project: Hadoop HDFS Issue Type:

[jira] Resolved: (HDFS-1634) HDFS Federation: Convert single threaded DataNode into per BlockPool thread model.

[ https://issues.apache.org/jira/browse/HDFS-1634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Boris Shkolnik resolved HDFS-1634. -- Resolution: Fixed Hadoop Flags: [Reviewed] > HDFS Federation: Convert single threaded Data

[jira] Resolved: (HDFS-1670) HDFS Federation: remove dnRegistration from Datanode

[ https://issues.apache.org/jira/browse/HDFS-1670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Boris Shkolnik resolved HDFS-1670. -- Resolution: Fixed Hadoop Flags: [Reviewed] > HDFS Federation: remove dnRegistration from D

[jira] Created: (HDFS-1714) HDFS Federation: refactor upgrade object in DataNode

HDFS Federation: refactor upgrade object in DataNode Key: HDFS-1714 URL: https://issues.apache.org/jira/browse/HDFS-1714 Project: Hadoop HDFS Issue Type: Sub-task Reporter: Bor

[jira] Resolved: (HDFS-1709) Error "nnaddr url param is null" when clicking on a node from NN Live Node Link

[ https://issues.apache.org/jira/browse/HDFS-1709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jitendra Nath Pandey resolved HDFS-1709. Resolution: Fixed Hadoop Flags: [Reviewed] I have committed this. > Error "nn

[jira] Created: (HDFS-1715) HDFS Federation: warning/error not generated when datanode sees inconsistent/different Cluster ID between namenodes

HDFS Federation: warning/error not generated when datanode sees inconsistent/different Cluster ID between namenodes Key: HDFS-1715 URL: https://i

[jira] Created: (HDFS-1716) Federation: Add decommission tests for federated namenodes

Federation: Add decommission tests for federated namenodes -- Key: HDFS-1716 URL: https://issues.apache.org/jira/browse/HDFS-1716 Project: Hadoop HDFS Issue Type: Sub-task Com

[jira] Created: (HDFS-1717) Federation: FSDataset volumeMap access is not correctly synchronized

Federation: FSDataset volumeMap access is not correctly synchronized - Key: HDFS-1717 URL: https://issues.apache.org/jira/browse/HDFS-1717 Project: Hadoop HDFS Issue Type:

[jira] Created: (HDFS-1718) HDFS Federation: MiniDFSCluster#waitActive() bug causes some tests to fail

HDFS Federation: MiniDFSCluster#waitActive() bug causes some tests to fail --- Key: HDFS-1718 URL: https://issues.apache.org/jira/browse/HDFS-1718 Project: Hadoop HDFS

[jira] Created: (HDFS-1719) Federation: TestDFSRemove fails intermittently

Federation: TestDFSRemove fails intermittently --- Key: HDFS-1719 URL: https://issues.apache.org/jira/browse/HDFS-1719 Project: Hadoop HDFS Issue Type: Sub-task Components: data-node

[jira] Created: (HDFS-1720) Federation: FSVolumeSet volumes is not synchronized correctly

Federation: FSVolumeSet volumes is not synchronized correctly -- Key: HDFS-1720 URL: https://issues.apache.org/jira/browse/HDFS-1720 Project: Hadoop HDFS Issue Type: Sub-task

[jira] Created: (HDFS-1721) Hdfs Federation: Configuration for principal names should not be namenode specific.

Hdfs Federation: Configuration for principal names should not be namenode specific. --- Key: HDFS-1721 URL: https://issues.apache.org/jira/browse/HDFS-1721 Project: Hadoo

Merging Namenode Federation feature (HDFS-1052) to trunk

We have started pushing changes for namenode federation in to the feature branch HDFS-1052. The work items are created as subtask of the jira HDFS-1052 and are based on the design document published in the same jira. By the end of this week, we will complete pushing the changes to HDFS-1052 bran

[jira] Resolved: (HDFS-1717) Federation: FSDataset volumeMap access is not correctly synchronized

[ https://issues.apache.org/jira/browse/HDFS-1717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suresh Srinivas resolved HDFS-1717. --- Resolution: Fixed Hadoop Flags: [Reviewed] I committed the patch. > Federation: FSDatas

[jira] Created: (HDFS-1722) HDFS Federation: Add flag to MiniDFSCluster to differentiate between two different modes-Federation and not.

HDFS Federation: Add flag to MiniDFSCluster to differentiate between two different modes-Federation and not. - Key: HDFS-1722 URL: https://issues.apache.o

[jira] Resolved: (HDFS-1713) Hdfs Federation: Prevent DataBlockScanner from running in tight loop

[ https://issues.apache.org/jira/browse/HDFS-1713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jitendra Nath Pandey resolved HDFS-1713. Resolution: Fixed Hadoop Flags: [Reviewed] I have committed this. > Hdfs Fede

[jira] Resolved: (HDFS-1721) Hdfs Federation: Configuration for principal names should not be namenode specific.

[ https://issues.apache.org/jira/browse/HDFS-1721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jitendra Nath Pandey resolved HDFS-1721. Resolution: Fixed Hadoop Flags: [Reviewed] I have committed this. > Hdfs Fede

[jira] Created: (HDFS-1723) quota errors messages should use the same scale

quota errors messages should use the same scale --- Key: HDFS-1723 URL: https://issues.apache.org/jira/browse/HDFS-1723 Project: Hadoop HDFS Issue Type: Improvement Reporter: Allen Witt

[jira] Created: (HDFS-1724) Can not browse the Data Node blocks if there is no Data Node hostname mappings in clients.

Can not browse the Data Node blocks if there is no Data Node hostname mappings in clients. -- Key: HDFS-1724 URL: https://issues.apache.org/jira/browse/HDFS-1724