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

Meta scanner should use its own threadpool

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.1.0, 2.0.0
    • Component/s: None
    • Labels:
      None

      Description

      Currently, during region location lookups, the meta is scanned and for this the scanner submits a request to the thread pool of the table in question. Sometimes, it might happen that many scan requests are simultaneously submitted on the table - let's say 256, and this is the max size of the thread pool. Each of these scan requests would in turn submit meta scan requests on the same thread pool, but they will be in the queue. The meta scans will not happen and the original table scans would lock up. The meta scans should use a different thread pool.

        Attachments

        1. 13036-2.txt
          9 kB
          Devaraj Das
        2. 13036-1.txt
          9 kB
          Devaraj Das

          Issue Links

            Activity

              People

              • Assignee:
                ddas Devaraj Das
                Reporter:
                ddas Devaraj Das
              • Votes:
                0 Vote for this issue
                Watchers:
                6 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: