[
https://issues.apache.org/jira/browse/HIVE-21908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16878273#comment-16878273
]
Hive QA commented on HIVE-21908:
--------------------------------
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12973571/HIVE-21908.02.patch
{color:green}SUCCESS:{color} +1 due to 1 test(s) being added or modified.
{color:red}ERROR:{color} -1 due to 1 failed/errored test(s), 16364 tests
executed
*Failed tests:*
{noformat}
org.apache.hadoop.hive.metastore.TestMetastoreHousekeepingLeaderEmptyConfig.testHouseKeepingThreadExistence
(batchId=242)
{noformat}
Test results:
https://builds.apache.org/job/PreCommit-HIVE-Build/17839/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/17839/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-17839/
Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.YetusPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
Tests exited with: TestsFailedException: 1 tests failed
{noformat}
This message is automatically generated.
ATTACHMENT ID: 12973571 - PreCommit-HIVE-Build
> 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: 0.5h
> 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)
