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

Locate region should fail fast if underlying Connection already closed

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

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 1.1.7, 1.2.4
    • Fix Version/s: 1.4.0, 1.2.5, 0.98.24, 1.1.8, 2.0.0
    • Component/s: None
    • Labels:
      None
    • Hadoop Flags:
      Reviewed

      Description

      Currently if try to locate region when underlying connection is closed, we will retry and wait at least 10s for each round until exhausted (refer to the catch clause of RpcRetryingCallerImpl#callWithRetries and RegionServerCallable#sleep for more details), which is unnecessary and time-costing.

      The issue is caused by user incorrectly manipulating connection, which shows the disadvantage of force user to handle connection life cycle and proves the necessity to support auto-managed connection as we did before, as indicated in HBASE-17009

      In this JIRA we will make it fail fast in the above case.

        Attachments

        1. HBASE-17127.patch
          3 kB
          Yu Li

        Issue Links

          Activity

            People

            • Assignee:
              liyu Yu Li
              Reporter:
              liyu Yu Li

              Dates

              • Created:
                Updated:
                Resolved:

                Issue deployment