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

Secondary namenode may retain old tokens

VotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Critical
    • Resolution: Fixed
    • 0.23.0, 2.0.0-alpha, 3.0.0-alpha1
    • 2.1.0-beta, 0.23.8
    • security
    • None
    • Reviewed

    Description

      Upon inspection of a fsimage created by a secondary namenode, we've discovered it contains very old tokens. These are probably the ones that were not explicitly canceled. It may be related to the optimization done to avoid loading fsimage from scratch every time checkpointing.

      Attachments

        1. HDFS-4477.branch-23.patch
          9 kB
          Daryn Sharp
        2. HDFS-4477.patch
          9 kB
          Daryn Sharp
        3. HDFS-4477.patch
          9 kB
          Daryn Sharp
        4. HDFS-4477.patch
          5 kB
          Daryn Sharp
        5. HDFS-4477.patch
          9 kB
          Daryn Sharp
        6. HDFS-4477.patch
          3 kB
          Daryn Sharp

        Issue Links

        Activity

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

          People

            daryn Daryn Sharp
            kihwal Kihwal Lee
            Votes:
            0 Vote for this issue
            Watchers:
            12 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment