Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Mon, 1 Aug 2016 00:07:20 +0000 (UTC)
From: "Alejandro Fernandez (JIRA)" <jira@apache.org>
To: issues@ambari.apache.org
Message-ID: <JIRA.12993834.1470009650000.182054.1470010040664@Atlassian.JIRA>
In-Reply-To: <JIRA.12993834.1470009650000@Atlassian.JIRA>
References: <JIRA.12993834.1470009650000@Atlassian.JIRA> <JIRA.12993834.1470009650133@arcas>
Subject: [jira] [Updated] (AMBARI-17972) Add kerberos.json file for Sqoop in
 HDP 2.5 needed by Atlas
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Mon, 01 Aug 2016 00:07:22 -0000


     [ https://issues.apache.org/jira/browse/AMBARI-17972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alejandro Fernandez updated AMBARI-17972:
-----------------------------------------
    Status: Patch Available  (was: Open)

> Add kerberos.json file for Sqoop in HDP 2.5 needed by Atlas
> -----------------------------------------------------------
>
>                 Key: AMBARI-17972
>                 URL: https://issues.apache.org/jira/browse/AMBARI-17972
>             Project: Ambari
>          Issue Type: Bug
>          Components: stacks
>    Affects Versions: 2.4.0
>            Reporter: Alejandro Fernandez
>            Assignee: Alejandro Fernandez
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-17972.patch
>
>
> AMBARI-17782 made changes so that HDP 2.5 with Sqoop in a kerberized cluster would set configs in sqoop-atlas-application.properties:
> atlas.jaas.KafkaClient.option.useTicketCache=true
> atlas.jaas.KafkaClient.option.renewTicket=true
> However, the kerberos.json file that was added broke some tests and had to be reverted because it didn't contain any identities or components. Now, readd the file and add some unit tests so that a kerberos.json file without any components is supported.
> {code}
> 27 Jul 2016 05:28:14,166  WARN [pool-17-thread-1] ClusterTopologyImpl:180 - HostGroup add-host not found, when checking for hosts for component KERBEROS_CLIENT
> 27 Jul 2016 05:28:14,166  WARN [pool-17-thread-1] ClusterTopologyImpl:180 - HostGroup add-host not found, when checking for hosts for component LOGSEARCH_LOGFEEDER
> 27 Jul 2016 05:28:14,177 ERROR [pool-17-thread-1] TopologyManager:916 - TopologyManager.ConfigureClusterTask: An exception occurred while attempting to process cluster configs and set on cluster: 
> java.lang.NullPointerException
> 	at org.apache.ambari.server.controller.KerberosHelperImpl.ensureHeadlessIdentities(KerberosHelperImpl.java:755)
> 	at org.apache.ambari.server.topology.ClusterConfigurationRequest.configureKerberos(ClusterConfigurationRequest.java:178)
> 	at org.apache.ambari.server.topology.ClusterConfigurationRequest.process(ClusterConfigurationRequest.java:145)
> 	at org.apache.ambari.server.topology.TopologyManager$ConfigureClusterTask.call(TopologyManager.java:914)
> 	at org.apache.ambari.server.topology.TopologyManager$ConfigureClusterTask.call(TopologyManager.java:888)
> 	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> 	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
> 	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
> 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> 	at java.lang.Thread.run(Thread.java:745)
> 27 Jul 2016 05:28:14,177  INFO [pool-3-thread-1] AsyncCallableService:111 - Exception during task execution: 
> java.util.concurrent.ExecutionException: java.lang.Exception: java.lang.NullPointerException
> 	at java.util.concurrent.FutureTask.report(FutureTask.java:122)
> 	at java.util.concurrent.FutureTask.get(FutureTask.java:206)
> 	at org.apache.ambari.server.topology.AsyncCallableService.taskCompleted(AsyncCallableService.java:103)
> 	at org.apache.ambari.server.topology.AsyncCallableService.call(AsyncCallableService.java:74)
> 	at org.apache.ambari.server.topology.AsyncCallableService.call(AsyncCallableService.java:37)
> 	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> 	at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.Exception: java.lang.NullPointerException
> 	at org.apache.ambari.server.topology.TopologyManager$ConfigureClusterTask.call(TopologyManager.java:920)
> 	at org.apache.ambari.server.topology.TopologyManager$ConfigureClusterTask.call(TopologyManager.java:888)
> 	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> 	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
> 	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
> 	... 3 more
> Caused by: java.lang.NullPointerException
> 	at org.apache.ambari.server.controller.KerberosHelperImpl.ensureHeadlessIdentities(KerberosHelperImpl.java:755)
> 	at org.apache.ambari.server.topology.ClusterConfigurationRequest.configureKerberos(ClusterConfigurationRequest.java:178)
> 	at org.apache.ambari.server.topology.ClusterConfigurationRequest.process(ClusterConfigurationRequest.java:145)
> 	at org.apache.ambari.server.topology.TopologyManager$ConfigureClusterTask.call(TopologyManager.java:914)
> 	... 7 more
> {code}


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