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

Quota by storage type usage incorrectly initialized upon namenode restart

VotersStop watchingWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 2.7.0
    • 2.8.0, 2.7.2, 3.0.0-alpha1
    • namenode
    • None
    • Reviewed

    Description

      This was found by Kihwal Lee as part of HDFS-8865 work in this comment.

      The unit test testQuotaByStorageTypePersistenceInFsImage/testQuotaByStorageTypePersistenceInFsEdit failed to detect this because they were using an obsolete
      FsDirectory instance. Once added the highlighted line below, the issue can be reproed.

      ++++>fsdir = cluster.getNamesystem().getFSDirectory();
      INode testDirNodeAfterNNRestart = fsdir.getINode4Write(testDir.toString());
      

      Attachments

        1. HDFS-8879.01.patch
          3 kB
          Xiaoyu Yao

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            xyao Xiaoyu Yao
            kihwal Kihwal Lee
            Votes:
            0 Vote for this issue
            Watchers:
            4 Stop watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment