[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-tabpanelfocusedCommentId=13153746#comment-13153746 ] Hadoop QA commented on HDFS-2572: - -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-tabpanelfocusedCommentId=13153761#comment-13153761 ] Todd Lipcon commented on HDFS-2282: --- Yea, fixed it in 20 with HDFS-2379, but might still

[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-tabpanelfocusedCommentId=13153776#comment-13153776 ] Hudson commented on HDFS-2454: -- Integrated in Hadoop-Hdfs-trunk #869 (See

[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-tabpanelfocusedCommentId=13153778#comment-13153778 ] Hudson commented on HDFS-2568: -- Integrated in Hadoop-Hdfs-trunk #869 (See

[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-tabpanelfocusedCommentId=13153777#comment-13153777 ] Hudson commented on HDFS-2567: -- Integrated in Hadoop-Hdfs-trunk #869 (See

[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-tabpanelfocusedCommentId=13153779#comment-13153779 ] Hudson commented on HDFS-208: - Integrated in Hadoop-Hdfs-trunk #869 (See

[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-tabpanelfocusedCommentId=13153780#comment-13153780 ] Hudson commented on HDFS-2502: -- Integrated in Hadoop-Hdfs-trunk #869 (See

[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-tabpanelfocusedCommentId=13153781#comment-13153781 ] Hudson commented on HDFS-2541: -- Integrated in Hadoop-Hdfs-trunk #869 (See

[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-tabpanelfocusedCommentId=13153786#comment-13153786 ] Hudson commented on HDFS-2567: -- Integrated in Hadoop-Hdfs-0.23-Build #82 (See

[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-tabpanelfocusedCommentId=13153788#comment-13153788 ] Hudson commented on HDFS-2502: -- Integrated in Hadoop-Hdfs-0.23-Build #82 (See

[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-tabpanelfocusedCommentId=13153785#comment-13153785 ] Hudson commented on HDFS-2454: -- Integrated in Hadoop-Hdfs-0.23-Build #82 (See

[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-tabpanelfocusedCommentId=13153787#comment-13153787 ] Hudson commented on HDFS-2568: -- Integrated in Hadoop-Hdfs-0.23-Build #82 (See

[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-tabpanelfocusedCommentId=13153789#comment-13153789 ] Hudson commented on HDFS-2541: -- Integrated in Hadoop-Hdfs-0.23-Build #82 (See

[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-tabpanelfocusedCommentId=13153790#comment-13153790 ] Hudson commented on HDFS-2570: -- Integrated in Hadoop-Hdfs-0.23-Build #82 (See

[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-tabpanelfocusedCommentId=13153793#comment-13153793 ] Hudson commented on HDFS-2454: -- Integrated in Hadoop-Mapreduce-0.23-Build #99 (See

[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-tabpanelfocusedCommentId=13153796#comment-13153796 ] Hudson commented on HDFS-2502: -- Integrated in Hadoop-Mapreduce-0.23-Build #99 (See

[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-tabpanelfocusedCommentId=13153794#comment-13153794 ] Hudson commented on HDFS-2567: -- Integrated in Hadoop-Mapreduce-0.23-Build #99 (See

[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-tabpanelfocusedCommentId=13153797#comment-13153797 ] Hudson commented on HDFS-2541: -- Integrated in Hadoop-Mapreduce-0.23-Build #99 (See

[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-tabpanelfocusedCommentId=13153795#comment-13153795 ] Hudson commented on HDFS-2568: -- Integrated in Hadoop-Mapreduce-0.23-Build #99 (See

[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-tabpanelfocusedCommentId=13153798#comment-13153798 ] Hudson commented on HDFS-2570: -- Integrated in Hadoop-Mapreduce-0.23-Build #99 (See

[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-tabpanelfocusedCommentId=13153802#comment-13153802 ] Hudson commented on HDFS-2454: -- Integrated in Hadoop-Mapreduce-trunk #903 (See

[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-tabpanelfocusedCommentId=13153804#comment-13153804 ] Hudson commented on HDFS-2568: -- Integrated in Hadoop-Mapreduce-trunk #903 (See

[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-tabpanelfocusedCommentId=13153803#comment-13153803 ] Hudson commented on HDFS-2567: -- Integrated in Hadoop-Mapreduce-trunk #903 (See

[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-tabpanelfocusedCommentId=13153806#comment-13153806 ] Hudson commented on HDFS-2502: -- Integrated in Hadoop-Mapreduce-trunk #903 (See

[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-tabpanelfocusedCommentId=13153805#comment-13153805 ] Hudson commented on HDFS-208: - Integrated in Hadoop-Mapreduce-trunk #903 (See

[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-tabpanelfocusedCommentId=13153807#comment-13153807 ] Hudson commented on HDFS-2541: -- Integrated in Hadoop-Mapreduce-trunk #903 (See

[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-tabpanelfocusedCommentId=13153809#comment-13153809 ] Hudson commented on HDFS-2570: -- Integrated in Hadoop-Mapreduce-trunk #903 (See

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

[ https://issues.apache.org/jira/browse/HDFS-2536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13153808#comment-13153808 ] Hudson commented on HDFS-2536: -- Integrated in Hadoop-Mapreduce-trunk #903 (See

[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 Nit fixed. Committing to trunk. Unnecessary double-check in

[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: -- Resolution: Fixed Status: Resolved (was: Patch Available) Unnecessary double-check in

[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-tabpanelfocusedCommentId=13153817#comment-13153817 ] Hudson commented on HDFS-2572: -- Integrated in Hadoop-Hdfs-trunk-Commit #1368 (See

[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-tabpanelfocusedCommentId=13153818#comment-13153818 ] Hudson commented on HDFS-2572: -- Integrated in Hadoop-Common-trunk-Commit #1294 (See

[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-tabpanelfocusedCommentId=13153819#comment-13153819 ] Harsh J commented on HDFS-2572: --- Failing test is unrelated btw: {code} java.lang.Exception:

[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-tabpanelfocusedCommentId=13153820#comment-13153820 ] Hudson commented on HDFS-2572: -- Integrated in Hadoop-Mapreduce-trunk-Commit #1318 (See

[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-tabpanelfocusedCommentId=13153824#comment-13153824 ] Hadoop QA commented on HDFS-2572: - -1 overall. Here are the results of testing the latest

[jira] [Updated] (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:all-tabpanel ] Eli Collins updated HDFS-2282: -- Target Version/s: 0.24.0 Semi-harmless race between block reports and block invalidation

[jira] [Created] (HDFS-2573) TestFiDataXceiverServer is failing, not testing OOME

TestFiDataXceiverServer is failing, not testing OOME Key: HDFS-2573 URL: https://issues.apache.org/jira/browse/HDFS-2573 Project: Hadoop HDFS Issue Type: Bug Components:

[jira] [Commented] (HDFS-2573) TestFiDataXceiverServer is failing, not testing OOME

[ https://issues.apache.org/jira/browse/HDFS-2573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13153860#comment-13153860 ] Konstantin Shvachko commented on HDFS-2573: --- The test was introduced in HDFS-2451

[jira] [Updated] (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:all-tabpanel ] Eli Collins updated HDFS-2282: -- Fix Version/s: 0.20.206.0 Cool.. using our new fancy fix/target scheme to indicate this was fixed in

[jira] [Commented] (HDFS-2573) TestFiDataXceiverServer is failing, not testing OOME

[ https://issues.apache.org/jira/browse/HDFS-2573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13153864#comment-13153864 ] Konstantin Boudnik commented on HDFS-2573: -- I agree with your analysis Konstantin:

[jira] [Commented] (HDFS-2573) TestFiDataXceiverServer is failing, not testing OOME

[ https://issues.apache.org/jira/browse/HDFS-2573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13153867#comment-13153867 ] Konstantin Boudnik commented on HDFS-2573: -- I think there's a couple of approaches

[jira] [Commented] (HDFS-2573) TestFiDataXceiverServer is failing, not testing OOME

[ https://issues.apache.org/jira/browse/HDFS-2573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13153877#comment-13153877 ] Konstantin Shvachko commented on HDFS-2573: --- I was thinking along these lines,

[jira] [Updated] (HDFS-2573) TestFiDataXceiverServer is failing, not testing OOME

[ https://issues.apache.org/jira/browse/HDFS-2573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Boudnik updated HDFS-2573: - Attachment: HDFS-2573.patch Good riddance. TestFiDataXceiverServer is

[jira] [Commented] (HDFS-2573) TestFiDataXceiverServer is failing, not testing OOME

[ https://issues.apache.org/jira/browse/HDFS-2573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13153883#comment-13153883 ] Konstantin Boudnik commented on HDFS-2573: -- The patch to remove the test has been

[jira] [Commented] (HDFS-2573) TestFiDataXceiverServer is failing, not testing OOME

[ https://issues.apache.org/jira/browse/HDFS-2573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13153885#comment-13153885 ] Konstantin Shvachko commented on HDFS-2573: --- Agreed. +1 for the patch.

[jira] [Resolved] (HDFS-2573) TestFiDataXceiverServer is failing, not testing OOME

[ https://issues.apache.org/jira/browse/HDFS-2573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Boudnik resolved HDFS-2573. -- Resolution: Fixed Assignee: Konstantin Boudnik Hadoop Flags: Reviewed I

[jira] [Commented] (HDFS-2573) TestFiDataXceiverServer is failing, not testing OOME

[ https://issues.apache.org/jira/browse/HDFS-2573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13153912#comment-13153912 ] Hudson commented on HDFS-2573: -- Integrated in Hadoop-Hdfs-22-branch #111 (See

[jira] [Commented] (HDFS-2415) Move MiniDFS out of test JAR and into the main hadoop-hdfs JAR

[ https://issues.apache.org/jira/browse/HDFS-2415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13153995#comment-13153995 ] Harsh J commented on HDFS-2415: --- Why do we need to do this when folks can use the test jar in

[jira] [Updated] (HDFS-2517) Protobuf - Add protocol service for JournalProtocol

[ https://issues.apache.org/jira/browse/HDFS-2517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suresh Srinivas updated HDFS-2517: -- Status: Patch Available (was: Open) Protobuf - Add protocol service for JournalProtocol

[jira] [Updated] (HDFS-2532) TestDfsOverAvroRpc timing out in trunk

[ https://issues.apache.org/jira/browse/HDFS-2532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon updated HDFS-2532: -- Resolution: Fixed Fix Version/s: 0.24.0 Hadoop Flags: Reviewed Status: Resolved

[jira] [Updated] (HDFS-2514) Link resolution bug for intermediate symlinks with relative targets

[ https://issues.apache.org/jira/browse/HDFS-2514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eli Collins updated HDFS-2514: -- Attachment: hdfs-2514-3.patch Thanks for the review Konst! Updated to take your suggestion wrt creating

[jira] [Commented] (HDFS-2532) TestDfsOverAvroRpc timing out in trunk

[ https://issues.apache.org/jira/browse/HDFS-2532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13154024#comment-13154024 ] Hudson commented on HDFS-2532: -- Integrated in Hadoop-Common-trunk-Commit #1297 (See

[jira] [Commented] (HDFS-2532) TestDfsOverAvroRpc timing out in trunk

[ https://issues.apache.org/jira/browse/HDFS-2532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13154027#comment-13154027 ] Hudson commented on HDFS-2532: -- Integrated in Hadoop-Hdfs-trunk-Commit #1371 (See

[jira] [Commented] (HDFS-2517) Protobuf - Add protocol service for JournalProtocol

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

[jira] [Commented] (HDFS-2514) Link resolution bug for intermediate symlinks with relative targets

[ https://issues.apache.org/jira/browse/HDFS-2514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13154032#comment-13154032 ] Hudson commented on HDFS-2514: -- Integrated in Hadoop-Hdfs-trunk-Commit #1372 (See

[jira] [Commented] (HDFS-2514) Link resolution bug for intermediate symlinks with relative targets

[ https://issues.apache.org/jira/browse/HDFS-2514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13154034#comment-13154034 ] Hudson commented on HDFS-2514: -- Integrated in Hadoop-Common-trunk-Commit #1298 (See

[jira] [Commented] (HDFS-2514) Link resolution bug for intermediate symlinks with relative targets

[ https://issues.apache.org/jira/browse/HDFS-2514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13154035#comment-13154035 ] Hudson commented on HDFS-2514: -- Integrated in Hadoop-Mapreduce-0.23-Commit #203 (See

[jira] [Commented] (HDFS-2514) Link resolution bug for intermediate symlinks with relative targets

[ https://issues.apache.org/jira/browse/HDFS-2514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13154037#comment-13154037 ] Hudson commented on HDFS-2514: -- Integrated in Hadoop-Hdfs-0.23-Commit #190 (See

[jira] [Commented] (HDFS-2532) TestDfsOverAvroRpc timing out in trunk

[ https://issues.apache.org/jira/browse/HDFS-2532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13154038#comment-13154038 ] Hudson commented on HDFS-2532: -- Integrated in Hadoop-Mapreduce-trunk-Commit #1320 (See

[jira] [Resolved] (HDFS-2514) Link resolution bug for intermediate symlinks with relative targets

[ https://issues.apache.org/jira/browse/HDFS-2514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eli Collins resolved HDFS-2514. --- Resolution: Fixed Target Version/s: 0.22.0, 0.23.1 (was: 0.23.0, 0.22.0) Hadoop

[jira] [Resolved] (HDFS-41) fsimage,fstime not replicated when edit file is empty.

[ https://issues.apache.org/jira/browse/HDFS-41?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J resolved HDFS-41. - Resolution: Cannot Reproduce Looks like this was fixed quite a while ago. Not reproducible on trunk nor a current

[jira] [Updated] (HDFS-2575) DFSTestUtil may create empty files

[ https://issues.apache.org/jira/browse/HDFS-2575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon updated HDFS-2575: -- Attachment: hdfs-2575.txt trivial change to make the minSize be 1 byte. I think this should be fine for

[jira] [Commented] (HDFS-2575) DFSTestUtil may create empty files

[ https://issues.apache.org/jira/browse/HDFS-2575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13154058#comment-13154058 ] Eli Collins commented on HDFS-2575: --- +1 lgtm DFSTestUtil may create

[jira] [Commented] (HDFS-2514) Link resolution bug for intermediate symlinks with relative targets

[ https://issues.apache.org/jira/browse/HDFS-2514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13154062#comment-13154062 ] Hudson commented on HDFS-2514: -- Integrated in Hadoop-Mapreduce-trunk-Commit #1321 (See