XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • 2.0.0-beta-2, 2.0.0
    • None
    • None
    • Hide
      Completes keep-alive logic and then enables it; ProcedureExecutor Workers will spin up more threads when need settling back to the core count after the burst in demand has passed. Default keep-alive is one minute. Default core-count is CPUs/4 or 16, which ever is greater. Maximum is an arbitrary core-count * 10 (a limit that should never be hit and if it is, there is something else very wrong).
      Show
      Completes keep-alive logic and then enables it; ProcedureExecutor Workers will spin up more threads when need settling back to the core count after the burst in demand has passed. Default keep-alive is one minute. Default core-count is CPUs/4 or 16, which ever is greater. Maximum is an arbitrary core-count * 10 (a limit that should never be hit and if it is, there is something else very wrong).

    Description

      The worker thread will just exit after keep alive time, and we never add it back. The only way to add it back is through the stuck checker, this is not correct. Here we should start new worker thread if it is under the core pool size and there are pending procedures.

      For now the default keep alive time is Long.MAX_VALUE which means no timeout so no problem, but we do allow users to set it so we need to fix it.

      Attachments

        1. HBASE-19978.patch
          39 kB
          Duo Zhang
        2. HBASE-19978-v1.patch
          39 kB
          Duo Zhang
        3. HBASE-19978-v2.patch
          40 kB
          Duo Zhang

        Issue Links

          Activity

            People

              zhangduo Duo Zhang
              zhangduo Duo Zhang
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: