hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Work logged] (HIVE-21822) Expose LlapDaemon metrics through a new API method
Date Tue, 04 Jun 2019 18:18:00 GMT


ASF GitHub Bot logged work on HIVE-21822:

                Author: ASF GitHub Bot
            Created on: 04/Jun/19 18:17
            Start Date: 04/Jun/19 18:17
    Worklog Time Spent: 10m 
      Work Description: odraese commented on pull request #657: HIVE-21822: Expose LlapDaemon
metrics through a new API method

 File path: llap-common/src/protobuf/LlapDaemonProtocol.proto
 @@ -211,6 +211,14 @@ message PurgeCacheResponseProto {
   optional int64 purged_memory_bytes = 1;
+message GetLoadMetricsRequestProto {
+message GetLoadMetricsResponseProto {
+  optional int64 num_executors_available = 1;
 Review comment:
   i would change this to a Map<String,int64> for numeric values and add map entries
for each counter/metric rather than listing out each of them as separate  message values.
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

Issue Time Tracking

    Worklog Id:     (was: 253904)
    Time Spent: 20m  (was: 10m)

> Expose LlapDaemon metrics through a new API method
> --------------------------------------------------
>                 Key: HIVE-21822
>                 URL:
>             Project: Hive
>          Issue Type: Sub-task
>          Components: llap
>            Reporter: Peter Vary
>            Assignee: Peter Vary
>            Priority: Major
>              Labels: pull-request-available
>         Attachments: HIVE-21822.patch
>          Time Spent: 20m
>  Remaining Estimate: 0h
> We should add a new API method to access specific LlapDaemon metrics which would provide
information to TezAMs to make good decisions on load balancing tasks

This message was sent by Atlassian JIRA

View raw message