hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Work logged] (HIVE-21908) LlapDaemon node status should be reflected in the metrics
Date Wed, 03 Jul 2019 13:12:00 GMT

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

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

                Author: ASF GitHub Bot
            Created on: 03/Jul/19 13:11
            Start Date: 03/Jul/19 13:11
    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
 
 
   
 
----------------------------------------------------------------
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: 271617)
            Time Spent: 10m
    Remaining Estimate: 0h

> 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
>
>          Time Spent: 10m
>  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)

Mime
View raw message