HBase
  1. HBase
  2. HBASE-4805

Allow better control of resource consumption in HTable

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 0.92.0, 0.94.0
    • Fix Version/s: 0.92.0, 0.94.0
    • Component/s: Client
    • Labels:
      None
    • Hadoop Flags:
      Reviewed

      Description

      From some internal discussions at Salesforce we concluded that we need better control over the resources (mostly threads) consumed by HTable when used in a AppServer with many client threads.

      Since HTable is not thread safe, the only options are cache them (in a custom thread local or using HTablePool) or to create them on-demand.

      I propose a simple change: Add a new constructor to HTable that takes an optional ExecutorService and HConnection instance. That would make HTable a pretty lightweight object and we would manage the ES and HC separately.

      I'll upload a patch a soon to get some feedback.

      1. 4805-v5.txt
        12 kB
        Lars Hofhansl
      2. 4805-v4.txt
        12 kB
        Lars Hofhansl
      3. 4805-v3.txt
        12 kB
        Lars Hofhansl
      4. 4805-v2.txt
        5 kB
        Lars Hofhansl
      5. 4805.txt
        5 kB
        Lars Hofhansl

        Issue Links

          Activity

            People

            • Assignee:
              Lars Hofhansl
              Reporter:
              Lars Hofhansl
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development