ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-18935) 'HAWQ segments unregistered' shows incorrect alert
Date Fri, 18 Nov 2016 19:58:59 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-18935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15677592#comment-15677592
] 

Hudson commented on AMBARI-18935:
---------------------------------

FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #365 (See [https://builds.apache.org/job/Ambari-branch-2.5/365/])
AMBARI-18935: 'HAWQ segments unregistered' shows incorrect alert (matt: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=a5d4c695799bed4e0e06252cd960c59ede90d356])
* (edit) ambari-server/src/test/python/common-services/HAWQ/test_alert_segment_registration_status.py
* (edit) ambari-server/src/main/resources/common-services/HAWQ/2.0.0/package/alerts/alert_segment_registration_status.py


> 'HAWQ segments unregistered' shows incorrect alert
> --------------------------------------------------
>
>                 Key: AMBARI-18935
>                 URL: https://issues.apache.org/jira/browse/AMBARI-18935
>             Project: Ambari
>          Issue Type: Bug
>          Components: stacks
>            Reporter: Matt
>            Assignee: Matt
>             Fix For: trunk, 2.5.0
>
>         Attachments: AMBARI-18935-trunk-orig.patch
>
>
> The alert is caused because of the mismatch in case between HAWQ segment hostnames mentioned
in the slaves file and the data stored in the DB



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message