Uploaded image for project: 'HBase'
  1. HBase
  2. HBASE-15829

hbase.client.retries.number has different meanings in branch-1 and master

Log workAgile BoardRank to TopRank to BottomAttach filesAttach ScreenshotBulk Copy AttachmentsBulk Move AttachmentsVotersWatch issueWatchersCreate sub-taskConvert to sub-taskMoveLinkCloneLabelsUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Minor
    • Resolution: Invalid
    • 2.0.0
    • None
    • Client
    • None

    Description

      The comment of hbase.client.retries.number is:

        /**  
         * Parameter name for maximum retries, used as maximum for all retryable
         * operations such as fetching of the root region from root region server,
         * getting a cell's value, starting a row update, etc.
         */
        public static final String HBASE_CLIENT_RETRIES_NUMBER = "hbase.client.retries.number";
      

      In branch-1, the max attempts number equals with hbase.client.retries.number. But in master, the max attempts number equals with hbase.client.retries.number + 1.

      For RpcRetryingCaller.

      this.retries = retries; // branch-1
      
      this.maxAttempts = retries + 1; // master
      

      For AsyncProcess:

          this.numTries = conf.getInt(HConstants.HBASE_CLIENT_RETRIES_NUMBER,
              HConstants.DEFAULT_HBASE_CLIENT_RETRIES_NUMBER); // branch-1
      
          // how many times we could try in total, one more than retry number
          this.numTries = conf.getInt(HConstants.HBASE_CLIENT_RETRIES_NUMBER,
              HConstants.DEFAULT_HBASE_CLIENT_RETRIES_NUMBER) + 1; // master
      

      Attachments

        Issue Links

        Activity

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

          People

            Unassigned Unassigned Assign to me
            zghao Guanghao Zhang
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment