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

Block information displayed in UI is incorrect

        Details

        • Type: Bug
        • Status: Resolved
        • Priority: Minor
        • Resolution: Duplicate
        • Affects Version/s: 0.20-append
        • Fix Version/s: 0.20-append
        • Component/s: namenode
        • Labels:
          None
        • Hadoop Flags:
          Reviewed
        • Tags:
          namenode UI

          Description

          Problem statement
          ================
          Deleted blocks are not removed from the blockmap.
          Solution
          =======
          Whenever delete is called the block entry must be removed from the block map and also move it to invalidates.

          1. Text File
            HDFS-1924.patch
            6 kB
            ramkrishna.s.vasudevan

            Issue Links

            duplicates

            Bug - A problem which impairs or prevents the functions of the product. HDFS-140 When a file is deleted, its blocks remain in the blocksmap till the next block report from Datanode

            • Major - Major loss of function.
            • Resolved

              Activity

              Ascending order - Click to sort in descending order
              Hide
              Permalink
              hadoopqa Hadoop QA added a comment -

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

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

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

              -1 patch. The patch command could not apply the patch.

              Console output: https://builds.apache.org/hudson/job/PreCommit-HDFS-Build/601//console

              This message is automatically generated.

              Show
              hadoopqa Hadoop QA added a comment - -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12479916/HDFS-1924.patch against trunk revision 1125217. +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 7 new or modified tests. -1 patch. The patch command could not apply the patch. Console output: https://builds.apache.org/hudson/job/PreCommit-HDFS-Build/601//console This message is automatically generated.
              Hide
              Permalink
              ram_krish ramkrishna.s.vasudevan added a comment -

              This patch is for 0.20-append branch

              Show
              ram_krish ramkrishna.s.vasudevan added a comment - This patch is for 0.20-append branch
              Hide
              Permalink
              tlipcon Todd Lipcon added a comment -

              This patch looks similar to HDFS-381. I'm hesitant to include it in 0.20-append since it has no serious ramifications and touches NN internals. Have you tested it on a real cluster for any length of time?

              Show
              tlipcon Todd Lipcon added a comment - This patch looks similar to HDFS-381 . I'm hesitant to include it in 0.20-append since it has no serious ramifications and touches NN internals. Have you tested it on a real cluster for any length of time?
              Hide
              Permalink
              ram_krish ramkrishna.s.vasudevan added a comment -

              Thanks Todd for your comments.
              We have tested in our cluster in long run scenarios also.

              But i will check the HDFS-381 defect also.

              Show
              ram_krish ramkrishna.s.vasudevan added a comment - Thanks Todd for your comments. We have tested in our cluster in long run scenarios also. But i will check the HDFS-381 defect also.
              Hide
              Permalink
              umamaheswararao Uma Maheswara Rao G added a comment -

              After the analysis, the root cause for this issue should be HDFS-140, So, closing this as duplicate.

              Show
              umamaheswararao Uma Maheswara Rao G added a comment - After the analysis, the root cause for this issue should be HDFS-140 , So, closing this as duplicate.

                People

                • Assignee:
                  umamaheswararao Uma Maheswara Rao G
                  Reporter:
                  ram_krish ramkrishna.s.vasudevan
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  7 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:

                    Development