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

Make ClientProtocol#abandonBlock() idempotent

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

Details

    • Improvement
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 3.0.0-alpha1
    • 2.1.0-beta
    • namenode
    • None
    • Reviewed

    Description

      Currently when abandonBlock is called, if the block does not exist, then the namenode throws an exception. I propose making it idempotent, by returning success if the block that is being abandoned does not exist.

      Thoughts?

      Attachments

        1. HDFS-5008.001.patch
          11 kB
          Jing Zhao
        2. HDFS-5008.002.patch
          13 kB
          Jing Zhao

        Issue Links

        Activity

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

          People

            jingzhao Jing Zhao
            sureshms Suresh Srinivas
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment