[
https://issues.apache.org/jira/browse/AMBARI-14847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15124510#comment-15124510
]
Hadoop QA commented on AMBARI-14847:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12785232/AMBARI-14847.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/5122//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/5122//console
This message is automatically generated.
> Concurrent kinit Commands Cause Alerts To Randomly Trigger
> ----------------------------------------------------------
>
> Key: AMBARI-14847
> URL: https://issues.apache.org/jira/browse/AMBARI-14847
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
> Affects Versions: 2.0.0
> Reporter: Jonathan Hurley
> Assignee: Jonathan Hurley
> Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-14847.patch
>
>
> The alerts framework on each Ambari Agent runs alerts in a threadpool when
> the job triggers. This can cause the following error to randomly appear and
> the alert to go CRITICAL:
> {noformat}
> Connection failed to http://nat-rare-21-dvitiiuk-2-5.novalocal:8088
> (Execution of '/usr/bin/kinit -l 5m -c
> /var/lib/ambari-agent/tmp/web_alert_cc_f3f99363c3b7d1667f1287ce3a35aa52 -kt
> /etc/security/keytabs/spnego.service.keytab
> HTTP/[email protected] > /dev/null' returned 1.
> kinit: Internal credentials cache error while storing credentials while
> getting initial credentials)
> {noformat}
> The alerts would randomly go CRITICAL at the end of their ticket expiration
> time only to become OK again shortly after.
> The cause is that the {{kinit}} command being executed to create new
> credentials cannot be run concurrently for the same user.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
