Uploaded image for project: 'Hadoop HDFS'
  1. Hadoop HDFS
  2. HDFS-4942 Add retry cache support in Namenode
  3. HDFS-5025

Record ClientId and CallId in EditLog to enable rebuilding retry cache in case of HA failover

VotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 3.0.0-alpha1
    • 2.1.0-beta
    • ha, namenode
    • None
    • Reviewed

    Description

      In case of HA failover, we need to be able to rebuild the retry cache in the other Namenode. We thus need to record client id and call id in the edit log for those "AtMostOnce" operations.

      Attachments

        1. HDFS-5025.005.patch
          149 kB
          Jing Zhao
        2. HDFS-5025.004.patch
          148 kB
          Jing Zhao
        3. editsStored
          4 kB
          Jing Zhao
        4. HDFS-5025.003.patch
          147 kB
          Jing Zhao
        5. HDFS-5025.002.patch
          137 kB
          Jing Zhao
        6. HDFS-5025.001.patch
          91 kB
          Jing Zhao
        7. HDFS-5025.000.patch
          48 kB
          Jing Zhao

        Issue Links

        relates to

        Bug - A problem which impairs or prevents the functions of the product. HADOOP-9822 create constant MAX_CAPACITY in RetryCache rather than hard-coding 16 in RetryCache constructor

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

        Improvement - An improvement or enhancement to an existing feature or task. HADOOP-9821 ClientId should have getMsb/getLsb methods

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

        Improvement - An improvement or enhancement to an existing feature or task. HDFS-5045 Add more unit tests for retry cache to cover all AtMostOnce methods

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

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

          People

            jingzhao Jing Zhao
            jingzhao Jing Zhao
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment