Uploaded image for project: 'Hive'
  1. Hive
  2. HIVE-10725

Better resource management in HiveServer2

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 1.3.0
    • Fix Version/s: None
    • Component/s: HiveServer2, JDBC
    • Labels:
      None

      Description

      We have various ways to control the number of queries that can be run on one HS2 instance (max threads, thread pool queuing etc). We also have ways to run multiple HS2 instances using dynamic service discovery. We should do a better job at:
      1. Monitoring resource utilization (sessions, ophandles, memory, threads etc).
      2. Being upfront to the client when we cannot accept new queries.
      3. Throttle among different server instances in case dynamic service discovery is used.
      4. Consolidate existing ways to control #queries into a simpler model.
      5. See if we can recommend reasonable values for OS resources or provide alerts if we run out of those.
      6. Health reports, server status API (to get number of queries, sessions etc).

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                vgumashta Vaibhav Gumashta
              • Votes:
                0 Vote for this issue
                Watchers:
                12 Start watching this issue

                Dates

                • Created:
                  Updated: