[
https://issues.apache.org/jira/browse/HIVE-21823?focusedWorklogId=253828&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-253828
]
ASF GitHub Bot logged work on HIVE-21823:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 04/Jun/19 16:12
Start Date: 04/Jun/19 16:12
Worklog Time Spent: 10m
Work Description: pvary commented on pull request #660: HIVE-21823: New
metrics to get the average queue length / free executor number for a given time
window
URL: https://github.com/apache/hive/pull/660
The patch contains the following changes:
- Created TimedAverageMetrics to calculate average value above time.
- Added 2 configurations to set the size of the time window:
- LLAP_DAEMON_METRICS_AVERAGE_DATA_SIZE - the number of data points to
retain
- LLAP_DAEMON_METRICS_AVERAGE_TIME_WINDOW - the time window to calculate
the average
- Added new metrics to the LlapDaemonExecutorMetrics
----------------------------------------------------------------
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:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 253828)
Time Spent: 10m
Remaining Estimate: 0h
> New metrics to get the average queue length / free executor number for a
> given time window
> ------------------------------------------------------------------------------------------
>
> Key: HIVE-21823
> URL: https://issues.apache.org/jira/browse/HIVE-21823
> Project: Hive
> Issue Type: Sub-task
> Components: llap
> Reporter: Peter Vary
> Assignee: Peter Vary
> Priority: Major
> Labels: pull-request-available
> Attachments: HIVE-21823.patch
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> We need to calculate the average queue size / free executor size for a window
> to have good data for making routing decisions.
> Interesting things to consider:
> * The time gap between arriving request can be different, so simple average
> is not enough to have correct data
> * We need to have 2 parameters
> ** Time window length
> ** Maximum data point numbers - so we will not collect "infinite" amount of
> data at high load
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
