[
https://issues.apache.org/jira/browse/HIVE-21908?focusedWorklogId=272122&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-272122
]
ASF GitHub Bot logged work on HIVE-21908:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 04/Jul/19 10:53
Start Date: 04/Jul/19 10:53
Worklog Time Spent: 10m
Work Description: asinkovits commented on pull request #699: HIVE-21908:
LlapDaemon node status should be reflected in the metrics
URL: https://github.com/apache/hive/pull/699#discussion_r300345174
##########
File path:
llap-server/src/java/org/apache/hadoop/hive/llap/daemon/impl/TaskExecutorService.java
##########
@@ -213,6 +215,10 @@ public synchronized void setCapacity(int newNumExecutors,
int newWaitQueueSize)
numSlotsAvailable.addAndGet(newNumExecutors - maxParallelExecutors);
maxParallelExecutors = newNumExecutors;
waitQueue.setWaitQueueSize(newWaitQueueSize);
+ if (metrics != null) {
Review comment:
Yes, this makes sense. I think removing all those null checks just makes the
code more readable. Done.
----------------------------------------------------------------
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: 272122)
Time Spent: 50m (was: 40m)
> LlapDaemon node status should be reflected in the metrics
> ---------------------------------------------------------
>
> Key: HIVE-21908
> URL: https://issues.apache.org/jira/browse/HIVE-21908
> Project: Hive
> Issue Type: Sub-task
> Components: llap
> Reporter: Peter Vary
> Assignee: Antal Sinkovits
> Priority: Major
> Labels: pull-request-available
> Attachments: HIVE-21908.01.patch, HIVE-21908.02.patch,
> HIVE-21908.03.patch
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> When we enable/disable a node it should be reflected in the LlapDaemon
> metrics, so the administrator can act upon the disabled nodes. They can
> manually check the status and either reenable them by restart, or fix the
> existing issues causing the problems
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
