[jira] [Commented] (HDFS-2572) Unnecessary double-check in DN#getHostName

[ https://issues.apache.org/jira/browse/HDFS-2572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13153744#comment-13153744 ] Eli Collins commented on HDFS-2572: --- +1 nit: you can put the assignment and declaration

[jira] [Commented] (HDFS-2567) When 0 DNs are available, show a proper error when trying to browse DFS via web UI

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

[jira] [Updated] (HDFS-2572) Unnecessary double-check in DN#getHostName

[ https://issues.apache.org/jira/browse/HDFS-2572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J updated HDFS-2572: -- Attachment: HDFS-2572.patch > Unnecessary double-check in DN#getHostName > -

[jira] [Updated] (HDFS-2572) Unnecessary double-check in DN#getHostName

[ https://issues.apache.org/jira/browse/HDFS-2572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J updated HDFS-2572: -- Status: Patch Available (was: Open) > Unnecessary double-check in DN#getHostName >

[jira] [Created] (HDFS-2572) Unnecessary double-check in DN#getHostName

Unnecessary double-check in DN#getHostName -- Key: HDFS-2572 URL: https://issues.apache.org/jira/browse/HDFS-2572 Project: Hadoop HDFS Issue Type: Improvement Components: data-node Affect

[jira] [Commented] (HDFS-2567) When 0 DNs are available, show a proper error when trying to browse DFS via web UI

[ https://issues.apache.org/jira/browse/HDFS-2567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13153739#comment-13153739 ] Hudson commented on HDFS-2567: -- Integrated in Hadoop-Mapreduce-trunk-Commit #1317 (See [https

[jira] [Commented] (HDFS-2570) Add descriptions for dfs.*.https.address in hdfs-default.xml

[ https://issues.apache.org/jira/browse/HDFS-2570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13153740#comment-13153740 ] Hudson commented on HDFS-2570: -- Integrated in Hadoop-Mapreduce-trunk-Commit #1317 (See [https

[jira] [Commented] (HDFS-2570) Add descriptions for dfs.*.https.address in hdfs-default.xml

[ https://issues.apache.org/jira/browse/HDFS-2570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13153736#comment-13153736 ] Hudson commented on HDFS-2570: -- Integrated in Hadoop-Mapreduce-0.23-Commit #200 (See [https:/

[jira] [Commented] (HDFS-2567) When 0 DNs are available, show a proper error when trying to browse DFS via web UI

[ https://issues.apache.org/jira/browse/HDFS-2567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13153735#comment-13153735 ] Hudson commented on HDFS-2567: -- Integrated in Hadoop-Mapreduce-0.23-Commit #200 (See [https:/

[jira] [Commented] (HDFS-2567) When 0 DNs are available, show a proper error when trying to browse DFS via web UI

[ https://issues.apache.org/jira/browse/HDFS-2567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13153733#comment-13153733 ] Hudson commented on HDFS-2567: -- Integrated in Hadoop-Hdfs-0.23-Commit #187 (See [https://buil

[jira] [Commented] (HDFS-2570) Add descriptions for dfs.*.https.address in hdfs-default.xml

[ https://issues.apache.org/jira/browse/HDFS-2570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13153734#comment-13153734 ] Hudson commented on HDFS-2570: -- Integrated in Hadoop-Hdfs-0.23-Commit #187 (See [https://buil

[jira] [Commented] (HDFS-2567) When 0 DNs are available, show a proper error when trying to browse DFS via web UI

[ https://issues.apache.org/jira/browse/HDFS-2567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13153731#comment-13153731 ] Hudson commented on HDFS-2567: -- Integrated in Hadoop-Hdfs-trunk-Commit #1367 (See [https://bu

[jira] [Commented] (HDFS-2570) Add descriptions for dfs.*.https.address in hdfs-default.xml

[ https://issues.apache.org/jira/browse/HDFS-2570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13153732#comment-13153732 ] Hudson commented on HDFS-2570: -- Integrated in Hadoop-Hdfs-trunk-Commit #1367 (See [https://bu

[jira] [Commented] (HDFS-2570) Add descriptions for dfs.*.https.address in hdfs-default.xml

[ https://issues.apache.org/jira/browse/HDFS-2570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13153728#comment-13153728 ] Hudson commented on HDFS-2570: -- Integrated in Hadoop-Common-0.23-Commit #188 (See [https://bu

[jira] [Commented] (HDFS-2570) Add descriptions for dfs.*.https.address in hdfs-default.xml

[ https://issues.apache.org/jira/browse/HDFS-2570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13153730#comment-13153730 ] Hudson commented on HDFS-2570: -- Integrated in Hadoop-Common-trunk-Commit #1293 (See [https://

[jira] [Commented] (HDFS-2567) When 0 DNs are available, show a proper error when trying to browse DFS via web UI

[ https://issues.apache.org/jira/browse/HDFS-2567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13153727#comment-13153727 ] Hudson commented on HDFS-2567: -- Integrated in Hadoop-Common-0.23-Commit #188 (See [https://bu

[jira] [Commented] (HDFS-2567) When 0 DNs are available, show a proper error when trying to browse DFS via web UI

[ https://issues.apache.org/jira/browse/HDFS-2567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13153729#comment-13153729 ] Hudson commented on HDFS-2567: -- Integrated in Hadoop-Common-trunk-Commit #1293 (See [https://

[jira] [Updated] (HDFS-2567) When 0 DNs are available, show a proper error when trying to browse DFS via web UI

[ https://issues.apache.org/jira/browse/HDFS-2567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eli Collins updated HDFS-2567: -- Resolution: Fixed Fix Version/s: (was: 0.24.0) 0.23.1 Hadoop Flags: Re

[jira] [Commented] (HDFS-2567) When 0 DNs are available, show a proper error when trying to browse DFS via web UI

[ https://issues.apache.org/jira/browse/HDFS-2567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13153725#comment-13153725 ] Eli Collins commented on HDFS-2567: --- +1 Not sure the other methods need to check if we'

[jira] [Updated] (HDFS-2570) Add descriptions for dfs.*.https.address in hdfs-default.xml

[ https://issues.apache.org/jira/browse/HDFS-2570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eli Collins updated HDFS-2570: -- Resolution: Fixed Status: Resolved (was: Patch Available) I've committed this. Thanks Harsh!

[jira] [Updated] (HDFS-2570) Add descriptions for dfs.*.https.address in hdfs-default.xml

[ https://issues.apache.org/jira/browse/HDFS-2570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eli Collins updated HDFS-2570: -- Target Version/s: (was: 0.23.1) Fix Version/s: 0.23.1 > Add descriptions for dfs.*.https.ad

[jira] [Updated] (HDFS-2570) Add descriptions for dfs.*.https.address in hdfs-default.xml

[ https://issues.apache.org/jira/browse/HDFS-2570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eli Collins updated HDFS-2570: -- Status: Patch Available (was: Open) > Add descriptions for dfs.*.https.address in hdfs-default.xml

[jira] [Updated] (HDFS-1172) Blocks in newly completed files are considered under-replicated too quickly

[ https://issues.apache.org/jira/browse/HDFS-1172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eli Collins updated HDFS-1172: -- Attachment: hdfs-1172.txt Updated patch rebased on trunk. > Blocks in newly completed f

[jira] [Assigned] (HDFS-2567) When 0 DNs are available, show a proper error when trying to browse DFS via web UI

[ https://issues.apache.org/jira/browse/HDFS-2567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J reassigned HDFS-2567: - Assignee: Harsh J > When 0 DNs are available, show a proper error when trying to browse DFS via > web

[jira] [Commented] (HDFS-2567) When 0 DNs are available, show a proper error when trying to browse DFS via web UI

[ https://issues.apache.org/jira/browse/HDFS-2567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13153717#comment-13153717 ] Harsh J commented on HDFS-2567: --- But ideally, the sub functions should be aware of these thin

[jira] [Updated] (HDFS-2567) When 0 DNs are available, show a proper error when trying to browse DFS via web UI

[ https://issues.apache.org/jira/browse/HDFS-2567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J updated HDFS-2567: -- Attachment: HDFS-2567.patch Agreed Eli, was silly of me (I hesitated in using up the nn object upfront :)) Patc

[jira] [Resolved] (HDFS-129) NPE in FSNamesystem.checkDecommissionStateInternal

[ https://issues.apache.org/jira/browse/HDFS-129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J resolved HDFS-129. -- Resolution: Not A Problem This appears to have been fixed. On current branch-0.20-security, I see a proper disal

[jira] [Commented] (HDFS-2246) Shortcut a local client reads to a Datanodes files directly

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

[jira] [Commented] (HDFS-2282) Semi-harmless race between block reports and block invalidation

[ https://issues.apache.org/jira/browse/HDFS-2282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13153709#comment-13153709 ] Eli Collins commented on HDFS-2282: --- Looks like this was fixed in HDFS-2379.

[jira] [Updated] (HDFS-2246) Shortcut a local client reads to a Datanodes files directly

[ https://issues.apache.org/jira/browse/HDFS-2246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jitendra Nath Pandey updated HDFS-2246: --- Target Version/s: 0.20.205.1, 0.24.0, 0.23.1 (was: 0.23.1, 0.24.0, 0.20.205.1)

[jira] [Updated] (HDFS-2246) Shortcut a local client reads to a Datanodes files directly

[ https://issues.apache.org/jira/browse/HDFS-2246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jitendra Nath Pandey updated HDFS-2246: --- Target Version/s: 0.20.205.1, 0.24.0, 0.23.1 (was: 0.23.1, 0.24.0, 0.20.205.1)

[jira] [Updated] (HDFS-2246) Shortcut a local client reads to a Datanodes files directly

[ https://issues.apache.org/jira/browse/HDFS-2246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jitendra Nath Pandey updated HDFS-2246: --- Attachment: HDFS-2246-trunk.patch Alright, here is an updated trunk patch which addres

[jira] [Commented] (HDFS-2454) Move maxXceiverCount check to before starting the thread in dataXceiver

[ https://issues.apache.org/jira/browse/HDFS-2454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13153706#comment-13153706 ] Hudson commented on HDFS-2454: -- Integrated in Hadoop-Mapreduce-trunk-Commit #1316 (See [https

[jira] [Commented] (HDFS-2568) Use a set to manage child sockets in XceiverServer

[ https://issues.apache.org/jira/browse/HDFS-2568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13153707#comment-13153707 ] Hudson commented on HDFS-2568: -- Integrated in Hadoop-Mapreduce-trunk-Commit #1316 (See [https

[jira] [Updated] (HDFS-2570) Add descriptions for dfs.*.https.address in hdfs-default.xml

[ https://issues.apache.org/jira/browse/HDFS-2570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J updated HDFS-2570: -- Hadoop Flags: Reviewed > Add descriptions for dfs.*.https.address in hdfs-default.xml >

[jira] [Commented] (HDFS-2570) Add descriptions for dfs.*.https.address in hdfs-default.xml

[ https://issues.apache.org/jira/browse/HDFS-2570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13153702#comment-13153702 ] Harsh J commented on HDFS-2570: --- +1 Eli, descriptions lgtm. > Add descriptio

[jira] [Created] (HDFS-2571) Error encountered while attempting a dfsadmin -report

Error encountered while attempting a dfsadmin -report - Key: HDFS-2571 URL: https://issues.apache.org/jira/browse/HDFS-2571 Project: Hadoop HDFS Issue Type: Bug Components: name-n

[jira] [Commented] (HDFS-2569) DN decommissioning quirks

[ https://issues.apache.org/jira/browse/HDFS-2569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13153698#comment-13153698 ] Harsh J commented on HDFS-2569: --- The write error is pretty misleading for this case as well:

[jira] [Commented] (HDFS-2569) DN decommissioning quirks

[ https://issues.apache.org/jira/browse/HDFS-2569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13153701#comment-13153701 ] Harsh J commented on HDFS-2569: --- Restarting DN, makes it join back the cluster. No disallow e

[jira] [Commented] (HDFS-208) name node should warn if only one dir is listed in dfs.name.dir

[ https://issues.apache.org/jira/browse/HDFS-208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13153699#comment-13153699 ] Hudson commented on HDFS-208: - Integrated in Hadoop-Mapreduce-trunk-Commit #1315 (See [https://

[jira] [Commented] (HDFS-2536) Remove unused imports

[ https://issues.apache.org/jira/browse/HDFS-2536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13153700#comment-13153700 ] Hudson commented on HDFS-2536: -- Integrated in Hadoop-Mapreduce-trunk-Commit #1315 (See [https

[jira] [Commented] (HDFS-2454) Move maxXceiverCount check to before starting the thread in dataXceiver

[ https://issues.apache.org/jira/browse/HDFS-2454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13153695#comment-13153695 ] Hudson commented on HDFS-2454: -- Integrated in Hadoop-Mapreduce-0.23-Commit #199 (See [https:/

[jira] [Commented] (HDFS-2454) Move maxXceiverCount check to before starting the thread in dataXceiver

[ https://issues.apache.org/jira/browse/HDFS-2454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13153697#comment-13153697 ] Hudson commented on HDFS-2454: -- Integrated in Hadoop-Common-0.23-Commit #187 (See [https://bu

[jira] [Created] (HDFS-2570) Add descriptions for dfs.*.https.address in hdfs-default.xml

Add descriptions for dfs.*.https.address in hdfs-default.xml Key: HDFS-2570 URL: https://issues.apache.org/jira/browse/HDFS-2570 Project: Hadoop HDFS Issue Type: Improvement

[jira] [Updated] (HDFS-2570) Add descriptions for dfs.*.https.address in hdfs-default.xml

[ https://issues.apache.org/jira/browse/HDFS-2570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eli Collins updated HDFS-2570: -- Attachment: hdfs-2570-1.patch Patch attached. > Add descriptions for dfs.*.https.addres

[jira] [Commented] (HDFS-2454) Move maxXceiverCount check to before starting the thread in dataXceiver

[ https://issues.apache.org/jira/browse/HDFS-2454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13153694#comment-13153694 ] Hudson commented on HDFS-2454: -- Integrated in Hadoop-Hdfs-0.23-Commit #186 (See [https://buil

[jira] [Commented] (HDFS-2454) Move maxXceiverCount check to before starting the thread in dataXceiver

[ https://issues.apache.org/jira/browse/HDFS-2454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13153693#comment-13153693 ] Hudson commented on HDFS-2454: -- Integrated in Hadoop-Common-trunk-Commit #1292 (See [https://

[jira] [Commented] (HDFS-2541) For a sufficiently large value of blocks, the DN Scanner may request a random number with a negative seed value.

[ https://issues.apache.org/jira/browse/HDFS-2541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13153692#comment-13153692 ] Eli Collins commented on HDFS-2541: --- Good idea, please open a new ticket.

[jira] [Commented] (HDFS-2454) Move maxXceiverCount check to before starting the thread in dataXceiver

[ https://issues.apache.org/jira/browse/HDFS-2454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13153691#comment-13153691 ] Hudson commented on HDFS-2454: -- Integrated in Hadoop-Hdfs-trunk-Commit #1366 (See [https://bu

[jira] [Updated] (HDFS-2454) Move maxXceiverCount check to before starting the thread in dataXceiver

[ https://issues.apache.org/jira/browse/HDFS-2454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eli Collins updated HDFS-2454: -- Resolution: Fixed Status: Resolved (was: Patch Available) I've committed this. Thanks Harsh!

[jira] [Commented] (HDFS-2568) Use a set to manage child sockets in XceiverServer

[ https://issues.apache.org/jira/browse/HDFS-2568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13153688#comment-13153688 ] Hudson commented on HDFS-2568: -- Integrated in Hadoop-Common-trunk-Commit #1291 (See [https://

[jira] [Commented] (HDFS-2568) Use a set to manage child sockets in XceiverServer

[ https://issues.apache.org/jira/browse/HDFS-2568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13153687#comment-13153687 ] Hudson commented on HDFS-2568: -- Integrated in Hadoop-Mapreduce-0.23-Commit #198 (See [https:/

[jira] [Commented] (HDFS-2568) Use a set to manage child sockets in XceiverServer

[ https://issues.apache.org/jira/browse/HDFS-2568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13153686#comment-13153686 ] Hudson commented on HDFS-2568: -- Integrated in Hadoop-Hdfs-0.23-Commit #185 (See [https://buil

[jira] [Updated] (HDFS-2454) Move maxXceiverCount check to before starting the thread in dataXceiver

[ https://issues.apache.org/jira/browse/HDFS-2454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eli Collins updated HDFS-2454: -- Description: We can hoist the maxXceiverCount out of DataXceiverServer#run, there's no need to che

[jira] [Commented] (HDFS-2568) Use a set to manage child sockets in XceiverServer

[ https://issues.apache.org/jira/browse/HDFS-2568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13153684#comment-13153684 ] Hudson commented on HDFS-2568: -- Integrated in Hadoop-Common-0.23-Commit #186 (See [https://bu

[jira] [Commented] (HDFS-2568) Use a set to manage child sockets in XceiverServer

[ https://issues.apache.org/jira/browse/HDFS-2568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13153683#comment-13153683 ] Hudson commented on HDFS-2568: -- Integrated in Hadoop-Hdfs-trunk-Commit #1365 (See [https://bu

[jira] [Updated] (HDFS-2568) Use a set to manage child sockets in XceiverServer

[ https://issues.apache.org/jira/browse/HDFS-2568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eli Collins updated HDFS-2568: -- Resolution: Fixed Status: Resolved (was: Patch Available) I've committed this. Thanks Harsh!

[jira] [Commented] (HDFS-2502) hdfs-default.xml should include dfs.name.dir.restore

[ https://issues.apache.org/jira/browse/HDFS-2502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13153680#comment-13153680 ] Hudson commented on HDFS-2502: -- Integrated in Hadoop-Mapreduce-trunk-Commit #1314 (See [https

[jira] [Updated] (HDFS-2568) Use a set to manage child sockets in XceiverServer

[ https://issues.apache.org/jira/browse/HDFS-2568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eli Collins updated HDFS-2568: -- Fix Version/s: (was: 0.24.0) 0.23.1 Hadoop Flags: Reviewed +1 lgtm

[jira] [Created] (HDFS-2569) DN decommissioning quirks

DN decommissioning quirks - Key: HDFS-2569 URL: https://issues.apache.org/jira/browse/HDFS-2569 Project: Hadoop HDFS Issue Type: Bug Components: data-node Affects Versions: 0.23.0 Reporter: H

[jira] [Commented] (HDFS-2536) Remove unused imports

[ https://issues.apache.org/jira/browse/HDFS-2536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13153677#comment-13153677 ] Hudson commented on HDFS-2536: -- Integrated in Hadoop-Common-trunk-Commit #1290 (See [https://

[jira] [Commented] (HDFS-2536) Remove unused imports

[ https://issues.apache.org/jira/browse/HDFS-2536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13153676#comment-13153676 ] Hudson commented on HDFS-2536: -- Integrated in Hadoop-Hdfs-trunk-Commit #1364 (See [https://bu

[jira] [Updated] (HDFS-2536) Remove unused imports

[ https://issues.apache.org/jira/browse/HDFS-2536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eli Collins updated HDFS-2536: -- Hadoop Flags: Reviewed Summary: Remove unused imports (was: FSImageTransactionalStorageInspect

[jira] [Commented] (HDFS-2536) Remove unused imports

[ https://issues.apache.org/jira/browse/HDFS-2536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13153675#comment-13153675 ] Eli Collins commented on HDFS-2536: --- I've committed this to trunk, leaving open for the p

[jira] [Updated] (HDFS-2536) FSImageTransactionalStorageInspector has a bunch of unused imports

[ https://issues.apache.org/jira/browse/HDFS-2536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eli Collins updated HDFS-2536: -- Target Version/s: 0.23.1 Fix Version/s: (was: 0.24.0) +1 mind generating a patch for 23 as w

[jira] [Commented] (HDFS-2567) When 0 DNs are available, show a proper error when trying to browse DFS via web UI

[ https://issues.apache.org/jira/browse/HDFS-2567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13153673#comment-13153673 ] Eli Collins commented on HDFS-2567: --- Why not explicitly check if there are any available

[jira] [Commented] (HDFS-2430) The number of failed or low-resource volumes the NN can tolerate should be configurable

[ https://issues.apache.org/jira/browse/HDFS-2430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13153672#comment-13153672 ] Eli Collins commented on HDFS-2430: --- Per HDFS-208 might be worth considering other warnin

[jira] [Updated] (HDFS-208) name node should warn if only one dir is listed in dfs.name.dir

[ https://issues.apache.org/jira/browse/HDFS-208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eli Collins updated HDFS-208: - Resolution: Fixed Fix Version/s: (was: 0.23.1) 0.24.0 Hadoop Flags: Revie

[jira] [Commented] (HDFS-208) name node should warn if only one dir is listed in dfs.name.dir

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

[jira] [Commented] (HDFS-2541) For a sufficiently large value of blocks, the DN Scanner may request a random number with a negative seed value.

[ https://issues.apache.org/jira/browse/HDFS-2541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13153669#comment-13153669 ] Harsh J commented on HDFS-2541: --- Thanks Eli! Would it also make sense if we 'warn' when bloc

[jira] [Commented] (HDFS-208) name node should warn if only one dir is listed in dfs.name.dir

[ https://issues.apache.org/jira/browse/HDFS-208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13153668#comment-13153668 ] Hudson commented on HDFS-208: - Integrated in Hadoop-Common-trunk-Commit #1289 (See [https://bui

[jira] [Commented] (HDFS-208) name node should warn if only one dir is listed in dfs.name.dir

[ https://issues.apache.org/jira/browse/HDFS-208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13153667#comment-13153667 ] Hudson commented on HDFS-208: - Integrated in Hadoop-Hdfs-trunk-Commit #1363 (See [https://build

[jira] [Updated] (HDFS-208) name node should warn if only one dir is listed in dfs.name.dir

[ https://issues.apache.org/jira/browse/HDFS-208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eli Collins updated HDFS-208: - Attachment: hdfs-208.patch Minor update that's a little more explicit (warns of data loss vs nn corruption

[jira] [Updated] (HDFS-208) name node should warn if only one dir is listed in dfs.name.dir

[ https://issues.apache.org/jira/browse/HDFS-208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eli Collins updated HDFS-208: - Fix Version/s: (was: 0.24.0) 0.23.1 Issue Type: Improvement (was: New Feature

[jira] [Commented] (HDFS-2502) hdfs-default.xml should include dfs.name.dir.restore

[ https://issues.apache.org/jira/browse/HDFS-2502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13153665#comment-13153665 ] Hudson commented on HDFS-2502: -- Integrated in Hadoop-Mapreduce-0.23-Commit #197 (See [https:/

[jira] [Commented] (HDFS-2502) hdfs-default.xml should include dfs.name.dir.restore

[ https://issues.apache.org/jira/browse/HDFS-2502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13153664#comment-13153664 ] Hudson commented on HDFS-2502: -- Integrated in Hadoop-Common-trunk-Commit #1288 (See [https://

[jira] [Commented] (HDFS-2502) hdfs-default.xml should include dfs.name.dir.restore

[ https://issues.apache.org/jira/browse/HDFS-2502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13153661#comment-13153661 ] Hudson commented on HDFS-2502: -- Integrated in Hadoop-Common-0.23-Commit #185 (See [https://bu

[jira] [Commented] (HDFS-2541) For a sufficiently large value of blocks, the DN Scanner may request a random number with a negative seed value.

[ https://issues.apache.org/jira/browse/HDFS-2541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13153662#comment-13153662 ] Hudson commented on HDFS-2541: -- Integrated in Hadoop-Mapreduce-trunk-Commit #1313 (See [https

[jira] [Commented] (HDFS-2502) hdfs-default.xml should include dfs.name.dir.restore

[ https://issues.apache.org/jira/browse/HDFS-2502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13153660#comment-13153660 ] Hudson commented on HDFS-2502: -- Integrated in Hadoop-Hdfs-trunk-Commit #1362 (See [https://bu

[jira] [Commented] (HDFS-2502) hdfs-default.xml should include dfs.name.dir.restore

[ https://issues.apache.org/jira/browse/HDFS-2502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13153659#comment-13153659 ] Hudson commented on HDFS-2502: -- Integrated in Hadoop-Hdfs-0.23-Commit #184 (See [https://buil

[jira] [Updated] (HDFS-2502) hdfs-default.xml should include dfs.name.dir.restore

[ https://issues.apache.org/jira/browse/HDFS-2502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eli Collins updated HDFS-2502: -- Resolution: Fixed Fix Version/s: (was: 0.24.0) 0.23.1 Hadoop Flags: Re

[jira] [Commented] (HDFS-2502) hdfs-default.xml should include dfs.name.dir.restore

[ https://issues.apache.org/jira/browse/HDFS-2502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13153657#comment-13153657 ] Eli Collins commented on HDFS-2502: --- Btw I removed the last bit of the comment about requ

[jira] [Commented] (HDFS-2502) hdfs-default.xml should include dfs.name.dir.restore

[ https://issues.apache.org/jira/browse/HDFS-2502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13153656#comment-13153656 ] Eli Collins commented on HDFS-2502: --- +1test failure is unrelated > h

[jira] [Commented] (HDFS-2541) For a sufficiently large value of blocks, the DN Scanner may request a random number with a negative seed value.

[ https://issues.apache.org/jira/browse/HDFS-2541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13153654#comment-13153654 ] Hudson commented on HDFS-2541: -- Integrated in Hadoop-Mapreduce-0.23-Commit #196 (See [https:/

[jira] [Commented] (HDFS-2541) For a sufficiently large value of blocks, the DN Scanner may request a random number with a negative seed value.

[ https://issues.apache.org/jira/browse/HDFS-2541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13153653#comment-13153653 ] Hudson commented on HDFS-2541: -- Integrated in Hadoop-Hdfs-0.23-Commit #183 (See [https://buil

[jira] [Commented] (HDFS-2541) For a sufficiently large value of blocks, the DN Scanner may request a random number with a negative seed value.

[ https://issues.apache.org/jira/browse/HDFS-2541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13153651#comment-13153651 ] Hudson commented on HDFS-2541: -- Integrated in Hadoop-Common-0.23-Commit #184 (See [https://bu

[jira] [Commented] (HDFS-2541) For a sufficiently large value of blocks, the DN Scanner may request a random number with a negative seed value.

[ https://issues.apache.org/jira/browse/HDFS-2541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13153652#comment-13153652 ] Hudson commented on HDFS-2541: -- Integrated in Hadoop-Common-trunk-Commit #1287 (See [https://

[jira] [Updated] (HDFS-2541) For a sufficiently large value of blocks, the DN Scanner may request a random number with a negative seed value.

[ https://issues.apache.org/jira/browse/HDFS-2541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eli Collins updated HDFS-2541: -- Resolution: Fixed Fix Version/s: (was: 0.24.0) 0.23.1 0.

[jira] [Commented] (HDFS-2541) For a sufficiently large value of blocks, the DN Scanner may request a random number with a negative seed value.

[ https://issues.apache.org/jira/browse/HDFS-2541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13153649#comment-13153649 ] Hudson commented on HDFS-2541: -- Integrated in Hadoop-Hdfs-trunk-Commit #1361 (See [https://bu

[jira] [Commented] (HDFS-2566) Move BPOfferService to be a non-inner class

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

[jira] [Updated] (HDFS-2566) Move BPOfferService to be a non-inner class

[ https://issues.apache.org/jira/browse/HDFS-2566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon updated HDFS-2566: -- Attachment: hdfs-2566.txt new rev - this conflicted with HDFS-2564 in one place (trivial whitespace con

[jira] [Commented] (HDFS-2566) Move BPOfferService to be a non-inner class

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

[jira] [Commented] (HDFS-2246) Shortcut a local client reads to a Datanodes files directly

[ https://issues.apache.org/jira/browse/HDFS-2246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13153623#comment-13153623 ] Todd Lipcon commented on HDFS-2246: --- I agree with Eli. What's the point in defining a pol

[jira] [Updated] (HDFS-2566) Move BPOfferService to be a non-inner class

[ https://issues.apache.org/jira/browse/HDFS-2566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon updated HDFS-2566: -- Attachment: hdfs-2566.txt On the above run, TestDistributedUpgrade timed out, but it seems to pass here

[jira] [Commented] (HDFS-442) dfsthroughput in test.jar throws NPE

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

[jira] [Commented] (HDFS-2502) hdfs-default.xml should include dfs.name.dir.restore

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

[jira] [Commented] (HDFS-2568) Use a set to manage child sockets in XceiverServer

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

[jira] [Updated] (HDFS-2502) hdfs-default.xml should include dfs.name.dir.restore

[ https://issues.apache.org/jira/browse/HDFS-2502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J updated HDFS-2502: -- Attachment: HDFS-2502.patch > hdfs-default.xml should include dfs.name.dir.restore > ---

[jira] [Updated] (HDFS-2502) hdfs-default.xml should include dfs.name.dir.restore

[ https://issues.apache.org/jira/browse/HDFS-2502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J updated HDFS-2502: -- Fix Version/s: 0.24.0 Assignee: Harsh J Status: Patch Available (was: Open) > hdfs-defa

[jira] [Commented] (HDFS-2454) Move maxXceiverCount check to before starting the thread in dataXceiver

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

  1   2   >