Hadoop HDFS
  1. Hadoop HDFS
  2. HDFS-265 Revisit append
  3. HDFS-616

Create functional tests for new design of the block report

    Details

    • Type: Sub-task Sub-task
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 0.21.0, 0.22.0
    • Fix Version/s: 0.21.0
    • Component/s: test
    • Labels:
      None
    • Hadoop Flags:
      Reviewed
    1. HDFS-616.patch
      23 kB
      Konstantin Boudnik
    2. HDFS-616.patch
      24 kB
      Konstantin Boudnik
    3. HDFS-616.patch
      24 kB
      Konstantin Boudnik
    4. HDFS-616.patch
      23 kB
      Konstantin Boudnik
    5. HDFS-616.patch
      23 kB
      Konstantin Boudnik
    6. HDFS-616.patch
      25 kB
      Konstantin Boudnik
    7. HDFS-616.patch
      38 kB
      Konstantin Boudnik
    8. HDFS-616.patch
      37 kB
      Konstantin Boudnik
    9. HDFS-616.patch
      35 kB
      Konstantin Boudnik
    10. HDFS-616.patch
      36 kB
      Konstantin Boudnik
    11. HDFS-616.patch
      35 kB
      Konstantin Boudnik
    12. HDFS-616.patch
      36 kB
      Konstantin Boudnik
    13. HDFS-616.patch
      37 kB
      Konstantin Shvachko
    14. HDFS-616.patch
      37 kB
      Konstantin Boudnik

      Issue Links

        Activity

        Hide
        Konstantin Boudnik added a comment -

        This patch adds BlockReport03 through BlockReport08 cases according to HDFS-551's test plan.
        The modifications are done against Append branch

        Show
        Konstantin Boudnik added a comment - This patch adds BlockReport03 through BlockReport08 cases according to HDFS-551 's test plan. The modifications are done against Append branch
        Hide
        Konstantin Boudnik added a comment -

        All testcases are now in place.
        3 of them keep failing for some of the functionality isn't yet implemented.

        Show
        Konstantin Boudnik added a comment - All testcases are now in place. 3 of them keep failing for some of the functionality isn't yet implemented.
        Hide
        Konstantin Boudnik added a comment -

        _03 test case if fixed: the actual # of pending deletion blocks should be equal to 1

        Show
        Konstantin Boudnik added a comment - _03 test case if fixed: the actual # of pending deletion blocks should be equal to 1
        Hide
        Konstantin Shvachko added a comment -
        1. iterBlkLocs() is not used anywhere.
        2. BlockReport_04() corrupts the data in the block. This is more testing of the block scanner than block report, because blockReport() does not verify crcs. So may be we should drop this test case.
        3. In BlockReport_07() you corrupt GS of secondDNblock, but you still report the old list of blocks with the old GS, so the NN does not get the message the block is corrupt.
        4. It would be better to name methods blockReport_**() - no capitalization for the first word.

        Other than that this is a good set of tests.

        Show
        Konstantin Shvachko added a comment - iterBlkLocs() is not used anywhere. BlockReport_04() corrupts the data in the block. This is more testing of the block scanner than block report, because blockReport() does not verify crcs. So may be we should drop this test case. In BlockReport_07() you corrupt GS of secondDNblock, but you still report the old list of blocks with the old GS, so the NN does not get the message the block is corrupt. It would be better to name methods blockReport_**() - no capitalization for the first word. Other than that this is a good set of tests.
        Hide
        Konstantin Boudnik added a comment -

        The patch addresses Konstantin's comments

        Show
        Konstantin Boudnik added a comment - The patch addresses Konstantin's comments
        Hide
        Konstantin Shvachko added a comment -

        blockReport_07() fails because in current block report implementation replicas with incorrect GS are considered invalid rather than corrupted. Here is a comment from the code:

        // This is a temporary hack until Block.equals() and compareTo()
        // are changed not to take into account the generation stamp for searching
        // in  blocksMap
        if(storedBlock.getGenerationStamp() != block.getGenerationStamp()) {
          toInvalidate.add(new Block(block));
          return storedBlock;
        }
        

        So may be for now we should modify the test case to check that the block is in BlockManager.recentInvalidateSets.
        By the way it would be also useful to print this list in printStats().

        Show
        Konstantin Shvachko added a comment - blockReport_07() fails because in current block report implementation replicas with incorrect GS are considered invalid rather than corrupted. Here is a comment from the code: // This is a temporary hack until Block.equals() and compareTo() // are changed not to take into account the generation stamp for searching // in blocksMap if (storedBlock.getGenerationStamp() != block.getGenerationStamp()) { toInvalidate.add( new Block(block)); return storedBlock; } So may be for now we should modify the test case to check that the block is in BlockManager.recentInvalidateSets . By the way it would be also useful to print this list in printStats() .
        Hide
        Konstantin Shvachko added a comment -

        One more thing. blockReport_08 and blockReport_09 fail when I run them with asserts on (-ea). This is because you use FSDataets.getReplica() which checks whether you hold the dataset lock, which you don't in the test. We should think how to fix it, the same problem is with TestInterdatanodeProtocol.

        Show
        Konstantin Shvachko added a comment - One more thing. blockReport_08 and blockReport_09 fail when I run them with asserts on (-ea). This is because you use FSDataets.getReplica() which checks whether you hold the dataset lock, which you don't in the test. We should think how to fix it, the same problem is with TestInterdatanodeProtocol.
        Hide
        Konstantin Boudnik added a comment -

        I've moved the test to namenode package in order to access the blockManager instance from Namesystem.
        However the size of recentInvalidateSets equals to 0. The content of this collection is updated by BlockManager.processReport and by the time the test's accessing it NN's blockreport is suppose to be complete. Which means that there might be a problem with DataNode.reportDiff() or else.

        As for getReplica() call: I agree that a replica's reference shouldn't be exposed outside of FSDataset.
        However, at the moment there's no alternative. Shall it be fixed separately?

        Show
        Konstantin Boudnik added a comment - I've moved the test to namenode package in order to access the blockManager instance from Namesystem . However the size of recentInvalidateSets equals to 0. The content of this collection is updated by BlockManager.processReport and by the time the test's accessing it NN's blockreport is suppose to be complete. Which means that there might be a problem with DataNode.reportDiff() or else. As for getReplica() call: I agree that a replica's reference shouldn't be exposed outside of FSDataset . However, at the moment there's no alternative. Shall it be fixed separately?
        Hide
        Konstantin Boudnik added a comment -

        blockReport_07() fails because in current block report implementation replicas with incorrect GS are considered invalid

        Also, it doesn't look like like such block is considered invalid but rather NN tries to replicate it. Test's printStats() shows the following:

        Missing 0
        Corrupted 0
        Under-replicated 0
        Pending delete 0
        Pending replications 1
        Excess 0
        Total 7
        
        Show
        Konstantin Boudnik added a comment - blockReport_07() fails because in current block report implementation replicas with incorrect GS are considered invalid Also, it doesn't look like like such block is considered invalid but rather NN tries to replicate it. Test's printStats() shows the following: Missing 0 Corrupted 0 Under-replicated 0 Pending delete 0 Pending replications 1 Excess 0 Total 7
        Hide
        Konstantin Boudnik added a comment -

        Merged with branch-0.21 (works for the trunk as well)

        Show
        Konstantin Boudnik added a comment - Merged with branch-0.21 (works for the trunk as well)
        Hide
        Konstantin Boudnik added a comment -

        This patch accommodates modifications of the tests for new design of BlockReport and fixes some bugs in the original two tests.

        Last two tests in this patch will have to fixed later on when a new access method to a replica's copy will be implemented as HDFS-680

        Show
        Konstantin Boudnik added a comment - This patch accommodates modifications of the tests for new design of BlockReport and fixes some bugs in the original two tests. Last two tests in this patch will have to fixed later on when a new access method to a replica's copy will be implemented as HDFS-680
        Hide
        Konstantin Boudnik added a comment -

        After HDFS-680 this test had to be moved to a.o.h.hdfs.server.datanode package to be able to access package-private methods of FSDataset

        All tests pass but blockReport_05 It is affected by infinite close file problem and by inability to access client's name from the current test's package.

        The latter problem might be solved either by changing the visibility of the field (bad idea!) or by injecting an access method for the field.

        Show
        Konstantin Boudnik added a comment - After HDFS-680 this test had to be moved to a.o.h.hdfs.server.datanode package to be able to access package-private methods of FSDataset All tests pass but blockReport_05 It is affected by infinite close file problem and by inability to access client's name from the current test's package. The latter problem might be solved either by changing the visibility of the field (bad idea!) or by injecting an access method for the field.
        Hide
        Konstantin Boudnik added a comment -

        blockReport_05() needs to be excluded from the test for it corrupts physical block's file but sends in-memory block report. To test the actual case it needs to wait for block scanner's next run. Thus it'll be actually testing of the block scanner rather than block report (similar to blockReport_05())

        Show
        Konstantin Boudnik added a comment - blockReport_05() needs to be excluded from the test for it corrupts physical block's file but sends in-memory block report. To test the actual case it needs to wait for block scanner's next run. Thus it'll be actually testing of the block scanner rather than block report (similar to blockReport_05() )
        Hide
        Konstantin Boudnik added a comment -

        This is more appropriate version of the patch for the last one was using new file from automatic refactoring thus was diff'ing nonexistent version from the new location.

        The content of the patch is the same but is expressed differently. Test-patch results and test results to follow shortly.

        Show
        Konstantin Boudnik added a comment - This is more appropriate version of the patch for the last one was using new file from automatic refactoring thus was diff'ing nonexistent version from the new location. The content of the patch is the same but is expressed differently. Test-patch results and test results to follow shortly.
        Hide
        Konstantin Boudnik added a comment -

        I ran test-patch on the current trunk

        There appear to be 104 release audit warnings before the patch and 104 release audit warnings after applying the patch.
        
        +1 overall.  
            +1 @author.  The patch does not contain any @author tags.
            +1 tests included.  The patch appears to include 6 new or modified tests.
            +1 javadoc.  The javadoc tool did not generate any warning messages.
            +1 javac.  The applied patch does not increase the total number of javac compiler warnings.
            +1 findbugs.  The patch does not introduce any new Findbugs warnings.
            +1 release audit.  The applied patch does not increase the total number of release audit warnings.
        
        ======================================================================
        ======================================================================
            Finished build.
        ======================================================================
        ======================================================================
        
        Show
        Konstantin Boudnik added a comment - I ran test-patch on the current trunk There appear to be 104 release audit warnings before the patch and 104 release audit warnings after applying the patch. +1 overall. +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 6 new or modified tests. +1 javadoc. The javadoc tool did not generate any warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. +1 findbugs. The patch does not introduce any new Findbugs warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. ====================================================================== ====================================================================== Finished build. ====================================================================== ======================================================================
        Hide
        Konstantin Boudnik added a comment -

        Have run all tests:

            [junit] Running org.apache.hadoop.hdfs.TestFiHFlush
            [junit] Tests run: 9, Failures: 0, Errors: 1, Time elapsed: 16.171 sec
            [junit] Test org.apache.hadoop.hdfs.TestFiHFlush FAILED
        

        one has failed but it isn't related to this patch introducing new tests.

        Show
        Konstantin Boudnik added a comment - Have run all tests: [junit] Running org.apache.hadoop.hdfs.TestFiHFlush [junit] Tests run: 9, Failures: 0, Errors: 1, Time elapsed: 16.171 sec [junit] Test org.apache.hadoop.hdfs.TestFiHFlush FAILED one has failed but it isn't related to this patch introducing new tests.
        Hide
        Konstantin Boudnik added a comment -

        Separate HDFS-706 has been opened for failing test

        Show
        Konstantin Boudnik added a comment - Separate HDFS-706 has been opened for failing test
        Hide
        Konstantin Boudnik added a comment -

        Some unused methods are removed from the patch. Also, new some useful methods are moved to the new GenericTestUtils class

        Show
        Konstantin Boudnik added a comment - Some unused methods are removed from the patch. Also, new some useful methods are moved to the new GenericTestUtils class
        Hide
        Konstantin Boudnik added a comment -

        The patch seems to be ready

        Show
        Konstantin Boudnik added a comment - The patch seems to be ready
        Hide
        Hadoop QA added a comment -

        -1 overall. Here are the results of testing the latest attachment
        http://issues.apache.org/jira/secure/attachment/12422280/HDFS-616.patch
        against trunk revision 826149.

        +1 @author. The patch does not contain any @author tags.

        +1 tests included. The patch appears to include 9 new or modified tests.

        +1 javadoc. The javadoc tool did not generate any warning messages.

        +1 javac. The applied patch does not increase the total number of javac compiler warnings.

        +1 findbugs. The patch does not introduce any new Findbugs warnings.

        +1 release audit. The applied patch does not increase the total number of release audit warnings.

        -1 core tests. The patch failed core unit tests.

        +1 contrib tests. The patch passed contrib unit tests.

        Test results: http://hudson.zones.apache.org/hudson/job/Hdfs-Patch-h2.grid.sp2.yahoo.net/31/testReport/
        Findbugs warnings: http://hudson.zones.apache.org/hudson/job/Hdfs-Patch-h2.grid.sp2.yahoo.net/31/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
        Checkstyle results: http://hudson.zones.apache.org/hudson/job/Hdfs-Patch-h2.grid.sp2.yahoo.net/31/artifact/trunk/build/test/checkstyle-errors.html
        Console output: http://hudson.zones.apache.org/hudson/job/Hdfs-Patch-h2.grid.sp2.yahoo.net/31/console

        This message is automatically generated.

        Show
        Hadoop QA added a comment - -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12422280/HDFS-616.patch against trunk revision 826149. +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 9 new or modified tests. +1 javadoc. The javadoc tool did not generate any warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. +1 findbugs. The patch does not introduce any new Findbugs warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. -1 core tests. The patch failed core unit tests. +1 contrib tests. The patch passed contrib unit tests. Test results: http://hudson.zones.apache.org/hudson/job/Hdfs-Patch-h2.grid.sp2.yahoo.net/31/testReport/ Findbugs warnings: http://hudson.zones.apache.org/hudson/job/Hdfs-Patch-h2.grid.sp2.yahoo.net/31/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html Checkstyle results: http://hudson.zones.apache.org/hudson/job/Hdfs-Patch-h2.grid.sp2.yahoo.net/31/artifact/trunk/build/test/checkstyle-errors.html Console output: http://hudson.zones.apache.org/hudson/job/Hdfs-Patch-h2.grid.sp2.yahoo.net/31/console This message is automatically generated.
        Hide
        Konstantin Boudnik added a comment -

        Tests won't timeout anymore. Instead prepareSecondReplica() will assert if at any point it has been waiting for more than 4 seconds

        Show
        Konstantin Boudnik added a comment - Tests won't timeout anymore. Instead prepareSecondReplica() will assert if at any point it has been waiting for more than 4 seconds
        Hide
        Konstantin Boudnik added a comment -

        Newer version of the patch is available

        Show
        Konstantin Boudnik added a comment - Newer version of the patch is available
        Hide
        Konstantin Boudnik added a comment -

        Latest version addresses the timeout problem

        Show
        Konstantin Boudnik added a comment - Latest version addresses the timeout problem
        Hide
        Hadoop QA added a comment -

        -1 overall. Here are the results of testing the latest attachment
        http://issues.apache.org/jira/secure/attachment/12422579/HDFS-616.patch
        against trunk revision 826149.

        +1 @author. The patch does not contain any @author tags.

        +1 tests included. The patch appears to include 6 new or modified tests.

        +1 javadoc. The javadoc tool did not generate any warning messages.

        -1 javac. The patch appears to cause tar ant target to fail.

        +1 findbugs. The patch does not introduce any new Findbugs warnings.

        +1 release audit. The applied patch does not increase the total number of release audit warnings.

        -1 core tests. The patch failed core unit tests.

        -1 contrib tests. The patch failed contrib unit tests.

        Test results: http://hudson.zones.apache.org/hudson/job/Hdfs-Patch-h2.grid.sp2.yahoo.net/34/testReport/
        Findbugs warnings: http://hudson.zones.apache.org/hudson/job/Hdfs-Patch-h2.grid.sp2.yahoo.net/34/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
        Checkstyle results: http://hudson.zones.apache.org/hudson/job/Hdfs-Patch-h2.grid.sp2.yahoo.net/34/artifact/trunk/build/test/checkstyle-errors.html
        Console output: http://hudson.zones.apache.org/hudson/job/Hdfs-Patch-h2.grid.sp2.yahoo.net/34/console

        This message is automatically generated.

        Show
        Hadoop QA added a comment - -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12422579/HDFS-616.patch against trunk revision 826149. +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 6 new or modified tests. +1 javadoc. The javadoc tool did not generate any warning messages. -1 javac. The patch appears to cause tar ant target to fail. +1 findbugs. The patch does not introduce any new Findbugs warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. -1 core tests. The patch failed core unit tests. -1 contrib tests. The patch failed contrib unit tests. Test results: http://hudson.zones.apache.org/hudson/job/Hdfs-Patch-h2.grid.sp2.yahoo.net/34/testReport/ Findbugs warnings: http://hudson.zones.apache.org/hudson/job/Hdfs-Patch-h2.grid.sp2.yahoo.net/34/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html Checkstyle results: http://hudson.zones.apache.org/hudson/job/Hdfs-Patch-h2.grid.sp2.yahoo.net/34/artifact/trunk/build/test/checkstyle-errors.html Console output: http://hudson.zones.apache.org/hudson/job/Hdfs-Patch-h2.grid.sp2.yahoo.net/34/console This message is automatically generated.
        Hide
        Konstantin Boudnik added a comment -

        A file has been missed in the previous patch. Fixed

        Show
        Konstantin Boudnik added a comment - A file has been missed in the previous patch. Fixed
        Hide
        Konstantin Boudnik added a comment -

        Missing file problem in the previous patch has been fixed. Resubmitting

        Show
        Konstantin Boudnik added a comment - Missing file problem in the previous patch has been fixed. Resubmitting
        Hide
        Hadoop QA added a comment -

        -1 overall. Here are the results of testing the latest attachment
        http://issues.apache.org/jira/secure/attachment/12422583/HDFS-616.patch
        against trunk revision 826149.

        +1 @author. The patch does not contain any @author tags.

        +1 tests included. The patch appears to include 9 new or modified tests.

        +1 javadoc. The javadoc tool did not generate any warning messages.

        +1 javac. The applied patch does not increase the total number of javac compiler warnings.

        +1 findbugs. The patch does not introduce any new Findbugs warnings.

        +1 release audit. The applied patch does not increase the total number of release audit warnings.

        -1 core tests. The patch failed core unit tests.

        +1 contrib tests. The patch passed contrib unit tests.

        Test results: http://hudson.zones.apache.org/hudson/job/Hdfs-Patch-h2.grid.sp2.yahoo.net/35/testReport/
        Findbugs warnings: http://hudson.zones.apache.org/hudson/job/Hdfs-Patch-h2.grid.sp2.yahoo.net/35/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
        Checkstyle results: http://hudson.zones.apache.org/hudson/job/Hdfs-Patch-h2.grid.sp2.yahoo.net/35/artifact/trunk/build/test/checkstyle-errors.html
        Console output: http://hudson.zones.apache.org/hudson/job/Hdfs-Patch-h2.grid.sp2.yahoo.net/35/console

        This message is automatically generated.

        Show
        Hadoop QA added a comment - -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12422583/HDFS-616.patch against trunk revision 826149. +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 9 new or modified tests. +1 javadoc. The javadoc tool did not generate any warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. +1 findbugs. The patch does not introduce any new Findbugs warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. -1 core tests. The patch failed core unit tests. +1 contrib tests. The patch passed contrib unit tests. Test results: http://hudson.zones.apache.org/hudson/job/Hdfs-Patch-h2.grid.sp2.yahoo.net/35/testReport/ Findbugs warnings: http://hudson.zones.apache.org/hudson/job/Hdfs-Patch-h2.grid.sp2.yahoo.net/35/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html Checkstyle results: http://hudson.zones.apache.org/hudson/job/Hdfs-Patch-h2.grid.sp2.yahoo.net/35/artifact/trunk/build/test/checkstyle-errors.html Console output: http://hudson.zones.apache.org/hudson/job/Hdfs-Patch-h2.grid.sp2.yahoo.net/35/console This message is automatically generated.
        Hide
        Konstantin Boudnik added a comment -

        Test failure is unrelated and an old one

        Show
        Konstantin Boudnik added a comment - Test failure is unrelated and an old one
        Hide
        Konstantin Shvachko added a comment -

        HDFS-512 broke case #3 here, because now blocks with incorrect GS are considered corrupt rather than invalid, which was intended from the very beginning, but was not possible to implement correctly until the block keys changed.
        I corrected the tets.
        It looks good now +1.

        Show
        Konstantin Shvachko added a comment - HDFS-512 broke case #3 here, because now blocks with incorrect GS are considered corrupt rather than invalid, which was intended from the very beginning, but was not possible to implement correctly until the block keys changed. I corrected the tets. It looks good now +1.
        Hide
        Konstantin Boudnik added a comment -

        I've modified the assertion message in case #3. Also, have added javadoc @param for new method in NameNodeAdapter

        Thanks for the review, Konstantin!

        Show
        Konstantin Boudnik added a comment - I've modified the assertion message in case #3. Also, have added javadoc @param for new method in NameNodeAdapter Thanks for the review, Konstantin!
        Hide
        Konstantin Boudnik added a comment -

        I've just committed this.

        Show
        Konstantin Boudnik added a comment - I've just committed this.
        Hide
        Hudson added a comment -

        Integrated in Hadoop-Hdfs-trunk-Commit #82 (See http://hudson.zones.apache.org/hudson/job/Hadoop-Hdfs-trunk-Commit/82/)
        . Create functional tests for new design of the block report. Contributed by Konstantin Boudnik

        Show
        Hudson added a comment - Integrated in Hadoop-Hdfs-trunk-Commit #82 (See http://hudson.zones.apache.org/hudson/job/Hadoop-Hdfs-trunk-Commit/82/ ) . Create functional tests for new design of the block report. Contributed by Konstantin Boudnik
        Hide
        Hudson added a comment -

        Integrated in Hdfs-Patch-h2.grid.sp2.yahoo.net #59 (See http://hudson.zones.apache.org/hudson/job/Hdfs-Patch-h2.grid.sp2.yahoo.net/59/)

        Show
        Hudson added a comment - Integrated in Hdfs-Patch-h2.grid.sp2.yahoo.net #59 (See http://hudson.zones.apache.org/hudson/job/Hdfs-Patch-h2.grid.sp2.yahoo.net/59/ )
        Hide
        Hudson added a comment -

        Integrated in Hadoop-Hdfs-trunk #120 (See http://hudson.zones.apache.org/hudson/job/Hadoop-Hdfs-trunk/120/)

        Show
        Hudson added a comment - Integrated in Hadoop-Hdfs-trunk #120 (See http://hudson.zones.apache.org/hudson/job/Hadoop-Hdfs-trunk/120/ )
        Hide
        Hudson added a comment -

        Integrated in Hdfs-Patch-h5.grid.sp2.yahoo.net #78 (See http://hudson.zones.apache.org/hudson/job/Hdfs-Patch-h5.grid.sp2.yahoo.net/78/)

        Show
        Hudson added a comment - Integrated in Hdfs-Patch-h5.grid.sp2.yahoo.net #78 (See http://hudson.zones.apache.org/hudson/job/Hdfs-Patch-h5.grid.sp2.yahoo.net/78/ )

          People

          • Assignee:
            Konstantin Boudnik
            Reporter:
            Konstantin Boudnik
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development