Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Thu, 5 Jan 2017 16:18:58 +0000 (UTC)
From: "Hadoop QA (JIRA)" <jira@apache.org>
To: issues@ambari.apache.org
Message-ID: <JIRA.13032284.1483630142000.651439.1483633138461@Atlassian.JIRA>
In-Reply-To: <JIRA.13032284.1483630142000@Atlassian.JIRA>
References: <JIRA.13032284.1483630142000@Atlassian.JIRA> <JIRA.13032284.1483630142307@arcas>
Subject: [jira] [Commented] (AMBARI-19388) PERF: disabling security fails
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 05 Jan 2017 16:19:00 -0000


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

Hadoop QA commented on AMBARI-19388:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12845815/AMBARI-19388.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include any new or modified tests.
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    {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:red}-1 core tests{color}.  The test build failed in ambari-server 

Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/9922//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/9922//console

This message is automatically generated.

> PERF: disabling security fails
> ------------------------------
>
>                 Key: AMBARI-19388
>                 URL: https://issues.apache.org/jira/browse/AMBARI-19388
>             Project: Ambari
>          Issue Type: Bug
>    Affects Versions: 2.5.0
>            Reporter: Dmytro Sen
>            Assignee: Dmytro Sen
>            Priority: Critical
>             Fix For: 2.5.0
>
>         Attachments: AMBARI-19388.patch
>
>
> When you are trying to disable security om perf cluster it fails.
> 1) For cluster with 1200 agents it works fine but for cluster with 1850 agents it fails.
> 2) According to what i found, root cause is PUT request to http://<ambari_server_host>:8080/api/v1/clusters/<cluster_name> with data like "security_type" : "NONE". So, this request trying to change security type from KERBEROS to NONE and fails by timeout of three minutes.
> 3) Interesting thing, request to change security type fails and UI showing Error on disable security window. But in the same time in BG operations process which destroying keytabs proceed work.
> 4) One more thing. After failed disabling kerberos, if you will click restart the same request(update security type) will finish work in a few seconds.
> So, what we need to do is to connect profiler and find out what exactly take so much time for request to change security type.


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