Uploaded image for project: 'Hadoop HDFS'
  1. Hadoop HDFS
  2. HDFS-1197

Blocks are considered "complete" prematurely after commitBlockSynchronization or DN restart

    XMLWordPrintableJSON

Details

    Description

      I saw this failure once on my internal Hudson job that runs the append tests 48 times a day:
      junit.framework.AssertionFailedError: expected:<114688> but was:<98304>
      at org.apache.hadoop.hdfs.AppendTestUtil.check(AppendTestUtil.java:112)
      at org.apache.hadoop.hdfs.TestFileAppend3.testTC2(TestFileAppend3.java:116)

      Attachments

        1. hdfs-1197.txt
          27 kB
          Todd Lipcon
        2. HDFS-1197-20s.2.patch
          26 kB
          Jitendra Nath Pandey
        3. HDFS-1197-20s.3.patch
          25 kB
          Jitendra Nath Pandey
        4. hdfs-1197-test-changes.txt
          10 kB
          Todd Lipcon
        5. HDFS-1197-without-addStoredBlock-change.1.patch
          15 kB
          Jitendra Nath Pandey
        6. testTC2-failure.txt
          131 kB
          Todd Lipcon

        Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. HDFS-1779 After NameNode restart , Clients can not read partial files even after client invokes Sync.

          • Major - Major loss of function.
          • Closed

          Test - A new unit, integration or system test. HDFS-1243 0.20 append: Replication tests in TestFileAppend4 should not expect immediate replication

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved

          Activity

            People

              tlipcon Todd Lipcon
              tlipcon Todd Lipcon
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: