[jira] Updated: (HDFS-1691) double static declaration in Configuration.addDefaultResource(hdfs-default.xml);

[ https://issues.apache.org/jira/browse/HDFS-1691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Diomin updated HDFS-1691: Attachment: HDFS-1691.patch double static declaration in

[jira] Commented: (HDFS-693) java.net.SocketTimeoutException: 480000 millis timeout while waiting for channel to be ready for write exceptions were cast when trying to read file via StreamFile.

[ https://issues.apache.org/jira/browse/HDFS-693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13001979#comment-13001979 ] Uma Maheswara Rao G commented on HDFS-693: -- In our observation this issue came in

[jira] Commented: (HDFS-1691) double static declaration in Configuration.addDefaultResource(hdfs-default.xml);

[ https://issues.apache.org/jira/browse/HDFS-1691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13001992#comment-13001992 ] Hadoop QA commented on HDFS-1691: - -1 overall. Here are the results of testing the latest

[jira] Updated: (HDFS-1521) Persist transaction ID on disk between NN restarts

[ https://issues.apache.org/jira/browse/HDFS-1521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Kelly updated HDFS-1521: - Status: Open (was: Patch Available) Persist transaction ID on disk between NN restarts

[jira] Updated: (HDFS-1521) Persist transaction ID on disk between NN restarts

[ https://issues.apache.org/jira/browse/HDFS-1521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Kelly updated HDFS-1521: - Status: Patch Available (was: Open) Persist transaction ID on disk between NN restarts

[jira] Updated: (HDFS-1521) Persist transaction ID on disk between NN restarts

[ https://issues.apache.org/jira/browse/HDFS-1521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Kelly updated HDFS-1521: - Attachment: HDFS-1521.diff Solved control op problem by simply not beginning a transaction if opcode

[jira] Updated: (HDFS-1580) Add interface for generic Write Ahead Logging mechanisms

[ https://issues.apache.org/jira/browse/HDFS-1580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Kelly updated HDFS-1580: - Attachment: HDFS-1580+1521.diff HDFS-1580.diff Initial work on 1580. This work is on top

[jira] Updated: (HDFS-1691) double static declaration in Configuration.addDefaultResource(hdfs-default.xml);

[ https://issues.apache.org/jira/browse/HDFS-1691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo (Nicholas), SZE updated HDFS-1691: - Resolution: Fixed Fix Version/s: 0.23.0 Status: Resolved (was:

[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

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

[ https://issues.apache.org/jira/browse/HDFS-1708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13002105#comment-13002105 ] Suresh Srinivas commented on HDFS-1708: --- +1 for the patch. The testpatch result is

[jira] Commented: (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:comment-tabpanelfocusedCommentId=13002112#comment-13002112 ] Tsz Wo (Nicholas), SZE commented on HDFS-1684: -- Thanks Suresh for reviewing

[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:

[jira] Updated: (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 updated HDFS-1709: --- Attachment: HDFS-1709.3.patch Patch rebased against latest state of the branch.

[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] Commented: (HDFS-1521) Persist transaction ID on disk between NN restarts

[ https://issues.apache.org/jira/browse/HDFS-1521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13002121#comment-13002121 ] Hadoop QA commented on HDFS-1521: - -1 overall. Here are the results of testing the latest

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

[ https://issues.apache.org/jira/browse/HDFS-1711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13002127#comment-13002127 ] Suresh Srinivas commented on HDFS-1711: --- +1 for the patch. create method for

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

[ https://issues.apache.org/jira/browse/HDFS-1711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Boris Shkolnik updated HDFS-1711: - Attachment: HDFS-1711.patch create method for updating machine name in DataNode.java

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

[ https://issues.apache.org/jira/browse/HDFS-1711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Boris Shkolnik updated HDFS-1711: - Attachment: HDFS-1711-1.patch merged with branch create method for updating machine name in

[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

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

[ https://issues.apache.org/jira/browse/HDFS-1712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Boris Shkolnik updated HDFS-1712: - Attachment: HDFS-1712.patch currently , in this test, we compare DataNodeInfo, but we should

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

[ https://issues.apache.org/jira/browse/HDFS-1711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13002158#comment-13002158 ] Boris Shkolnik commented on HDFS-1711: -- committed to Federation branch HDFS

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

[ https://issues.apache.org/jira/browse/HDFS-1711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Boris Shkolnik updated HDFS-1711: - Summary: HDFS Federation: create method for updating machine name in DataNode.java (was: create

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

[ https://issues.apache.org/jira/browse/HDFS-1712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Boris Shkolnik updated HDFS-1712: - Hadoop Flags: [Reviewed] Summary: HDFS Federation: when looking up datanode we should use

[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] Commented: (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:comment-tabpanelfocusedCommentId=13002168#comment-13002168 ] Suresh Srinivas commented on HDFS-1709: --- +1 for the change. Error nnaddr url param

[jira] Updated: (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 updated HDFS-1713: --- Attachment: HDFS-1713.1.patch Patch uploaded. Hdfs Federation: Prevent

[jira] Commented: (HDFS-1697) HDFS federation: fix testBlockRecovery

[ https://issues.apache.org/jira/browse/HDFS-1697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13002172#comment-13002172 ] Boris Shkolnik commented on HDFS-1697: -- committed to Federation branch HDFS

[jira] Commented: (HDFS-1697) HDFS federation: fix testBlockRecovery

[ https://issues.apache.org/jira/browse/HDFS-1697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13002171#comment-13002171 ] Boris Shkolnik commented on HDFS-1697: -- Datanode doesn't have namenode field anymore,

[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

[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:

[jira] Commented: (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:comment-tabpanelfocusedCommentId=13002175#comment-13002175 ] Jitendra Nath Pandey commented on HDFS-1709: -1 overall. +1 @author.

[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

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

[ https://issues.apache.org/jira/browse/HDFS-1714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Boris Shkolnik updated HDFS-1714: - Attachment: HDFS-1714.patch Currently there is single Upgrade object in the DataNode. And it

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

[ https://issues.apache.org/jira/browse/HDFS-1714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13002180#comment-13002180 ] Suresh Srinivas commented on HDFS-1714: --- +1 for the patch. HDFS Federation:

[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:

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

[ https://issues.apache.org/jira/browse/HDFS-1715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Boris Shkolnik updated HDFS-1715: - Attachment: HDFS-1715.patch HDFS Federation: warning/error not generated when datanode sees

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

[ https://issues.apache.org/jira/browse/HDFS-1714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13002191#comment-13002191 ] Boris Shkolnik commented on HDFS-1714: -- committed to Federation branch. HDFS

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

[ https://issues.apache.org/jira/browse/HDFS-1715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13002189#comment-13002189 ] Suresh Srinivas commented on HDFS-1715: --- +1 for the change. HDFS Federation:

[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

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

[ https://issues.apache.org/jira/browse/HDFS-1716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suresh Srinivas updated HDFS-1716: -- Attachment: HDFS-1716.patch Attached patch adds decommision tests for a federated cluster.

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

[ https://issues.apache.org/jira/browse/HDFS-1716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suresh Srinivas updated HDFS-1716: -- Description: Need tests for decommissioning that uses a cluster with multiple federated

[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] Updated: (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 updated HDFS-1717: -- Attachment: HDFS-1717.patch In the attached patch: - Access to FSDataset#volumeMap is always

[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] Updated: (HDFS-1718) HDFS Federation: MiniDFSCluster#waitActive() bug causes some tests to fail

[ https://issues.apache.org/jira/browse/HDFS-1718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suresh Srinivas updated HDFS-1718: -- Attachment: HDFS-1718.patch Attached patch fixes the test failure. HDFS Federation:

[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] Commented: (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:comment-tabpanelfocusedCommentId=13002213#comment-13002213 ] Tsz Wo (Nicholas), SZE commented on HDFS-1717: -- +1 patch looks good.

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

[ https://issues.apache.org/jira/browse/HDFS-1719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suresh Srinivas updated HDFS-1719: -- Attachment: HDFS-1719.patch # Getting rid of Datanode#datanodeID field. # Added proper

[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] Commented: (HDFS-1716) Federation: Add decommission tests for federated namenodes

[ https://issues.apache.org/jira/browse/HDFS-1716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13002223#comment-13002223 ] Jitendra Nath Pandey commented on HDFS-1716: +1 for the patch. Federation:

[jira] Commented: (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:comment-tabpanelfocusedCommentId=13002225#comment-13002225 ] Jitendra Nath Pandey commented on HDFS-1713: The patch adds a sleep before

[jira] Commented: (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:comment-tabpanelfocusedCommentId=13002227#comment-13002227 ] Suresh Srinivas commented on HDFS-1713: --- +1 for the patch. Hdfs Federation: Prevent

[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:

[jira] Updated: (HDFS-1686) Federation: Add more Balancer tests with federation setting

[ https://issues.apache.org/jira/browse/HDFS-1686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo (Nicholas), SZE updated HDFS-1686: - Attachment: h1686_20110303.patch h1686_20110303.patch: updated with the branch.

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

[ https://issues.apache.org/jira/browse/HDFS-1718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13002263#comment-13002263 ] Boris Shkolnik commented on HDFS-1718: -- +1 HDFS Federation:

[jira] Updated: (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 updated HDFS-1721: --- Attachment: HDFS-1721.1.patch patch uploaded. Hdfs Federation: Configuration for

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

[ https://issues.apache.org/jira/browse/HDFS-1715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Boris Shkolnik updated HDFS-1715: - Attachment: HDFS-1715-1.patch also added test for mismatched cluster id. HDFS Federation:

[jira] Commented: (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:comment-tabpanelfocusedCommentId=13002304#comment-13002304 ] Jitendra Nath Pandey commented on HDFS-1713: -1 overall. +1 @author.

[jira] Updated: (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 updated HDFS-1721: --- Attachment: HDFS-1721.2.patch Patch rebased against latest state of the branch.

[jira] Commented: (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:comment-tabpanelfocusedCommentId=13002314#comment-13002314 ] Suresh Srinivas commented on HDFS-1721: --- +1 for the patch. Hdfs Federation:

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

[ https://issues.apache.org/jira/browse/HDFS-1716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13002315#comment-13002315 ] Suresh Srinivas commented on HDFS-1716: --- test-patch result: -1 overall. +1

[jira] Updated: (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 updated HDFS-1717: -- Attachment: HDFS-1717.1.patch Updated patch for federation branch. Federation: FSDataset

[jira] Commented: (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:comment-tabpanelfocusedCommentId=13002322#comment-13002322 ] Jitendra Nath Pandey commented on HDFS-1721: -1 overall. +1 @author.

[jira] Updated: (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 updated HDFS-1717: -- Attachment: HDFS-1717.2.patch Updated patch. Federation: FSDataset volumeMap access is not

[jira] Commented: (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:comment-tabpanelfocusedCommentId=13002331#comment-13002331 ] Suresh Srinivas commented on HDFS-1717: --- [exec] -1 overall. [exec]

[jira] Updated: (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 updated HDFS-1717: -- Attachment: HDFS-1717.3.patch Adding a change that was missed in previous version of the patch.

[jira] Commented: (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:comment-tabpanelfocusedCommentId=13002341#comment-13002341 ] Tsz Wo (Nicholas), SZE commented on HDFS-1717: -- +1 HDFS-1717.3.patch looks

[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:

[jira] Updated: (HDFS-1700) Federation: fsck needs to work with federation configuration

[ https://issues.apache.org/jira/browse/HDFS-1700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suresh Srinivas updated HDFS-1700: -- Summary: Federation: fsck needs to work with federation configuration (was: HDFS Federation:

[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:

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

[ https://issues.apache.org/jira/browse/HDFS-1722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Boris Shkolnik updated HDFS-1722: - Attachment: HDFS-1722.patch For non-federated mode we keep old style set-up for backward

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

[ https://issues.apache.org/jira/browse/HDFS-1722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Boris Shkolnik updated HDFS-1722: - Attachment: HDFS-1722.patch HDFS Federation: Add flag to MiniDFSCluster to differentiate between

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

[ https://issues.apache.org/jira/browse/HDFS-1722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13002388#comment-13002388 ] Boris Shkolnik commented on HDFS-1722: -- without a flag MiniDFScluster will try to

[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

[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

[jira] Updated: (HDFS-1480) All replicas for a block end up in same rack

[ https://issues.apache.org/jira/browse/HDFS-1480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo (Nicholas), SZE updated HDFS-1480: - Component/s: name-node Description: It appears that all replicas

[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

[jira] Commented: (HDFS-1312) Re-balance disks within a Datanode

[ https://issues.apache.org/jira/browse/HDFS-1312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13002437#comment-13002437 ] Wang Xu commented on HDFS-1312: --- Hi Allen, For the cluster monitoring issue, we could not

[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

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

[ https://issues.apache.org/jira/browse/HDFS-1724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uma Maheswara Rao G updated HDFS-1724: -- Summary: Can not browse the Data Node blocks from NameNode UI if there is no Data Node

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

[ https://issues.apache.org/jira/browse/HDFS-1722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13002492#comment-13002492 ] Suresh Srinivas commented on HDFS-1722: --- +1 for the patch. HDFS Federation: Add