You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2020/06/02 06:59:00 UTC

[jira] [Work logged] (HIVE-21908) LlapDaemon node status should be reflected in the metrics

     [ https://issues.apache.org/jira/browse/HIVE-21908?focusedWorklogId=439943&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-439943 ]

ASF GitHub Bot logged work on HIVE-21908:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 02/Jun/20 06:58
            Start Date: 02/Jun/20 06:58
    Worklog Time Spent: 10m 
      Work Description: asinkovits closed pull request #699:
URL: https://github.com/apache/hive/pull/699


   


----------------------------------------------------------------
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:
users@infra.apache.org


Issue Time Tracking
-------------------

    Worklog Id:     (was: 439943)
    Time Spent: 1h 50m  (was: 1h 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
>             Fix For: 4.0.0
>
>         Attachments: HIVE-21908.01.patch, HIVE-21908.02.patch, HIVE-21908.03.patch, HIVE-21908.04.patch, HIVE-21908.05.patch, HIVE-21908.06.patch
>
>          Time Spent: 1h 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
(v8.3.4#803005)