[jira] [Assigned] (AMBARI-16030) Ambari operation history: Add ambari_operation_history table for record keeping history of ambari versions and operations

[Sumit Mohanty (Jira)]

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

Sumit Mohanty reassigned AMBARI-16030:
--

Assignee: (was: Sumit Mohanty)

> Ambari operation history: Add ambari_operation_history table for record 
> keeping history of ambari versions and operations
> -
>
> Key: AMBARI-16030
> URL: https://issues.apache.org/jira/browse/AMBARI-16030
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Nahappan Somasundaram
>Priority: Major
> Fix For: 3.0.0
>
>
> When investigating upgrade issues, information about history about Ambari 
> versions is missing. Also information about when the Ambari upgrades actually 
> happened in the past is completely missing. 
> Instead of relying on this information to be provided, Ambari should record 
> Ambari upgrade history in Ambari DB. 
> {noformat}
> ambari_version_history
> VersionDateNotes
> 2.2.2.0-102/09/2015 01:00:00Clean Install
> 2.2.3.0-203/10/2015 01:00:00Upgraded 2.2.2.0-1 -> 
> 2.2.3.0-2
> 2.4.0.0-306/09/2015 01:00:00Upgraded 2.2.3.0-2 -> 
> 2.4.0.0-3
> {noformat}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org

[jira] [Assigned] (AMBARI-17069) Recovery Manager: Refactor desired state transitions into a state table

[Sumit Mohanty (Jira)]

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

Sumit Mohanty reassigned AMBARI-17069:
--

Assignee: (was: Sumit Mohanty)

> Recovery Manager: Refactor desired state transitions into a state table
> ---
>
> Key: AMBARI-17069
> URL: https://issues.apache.org/jira/browse/AMBARI-17069
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-agent
>Affects Versions: 2.4.0
>Reporter: Nahappan Somasundaram
>Priority: Major
> Fix For: 3.0.0
>
>
> The desired state transitions for various auto start types are computed using 
> a big if-else block which is difficult to maintain as we keep adding newer 
> features. Move the state transition to a state machine for easy lookup.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org

[jira] [Resolved] (AMBARI-25656) DP Pavingny

[Sumit Mohanty (Jira)]

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

Sumit Mohanty resolved AMBARI-25656.

Resolution: Won't Fix

> DP Pavingny
> ---
>
> Key: AMBARI-25656
> URL: https://issues.apache.org/jira/browse/AMBARI-25656
> Project: Ambari
>  Issue Type: Documentation
>Reporter: Ethel Blackwell
>Priority: Major
>
> It's Ethel Blackwell here from NY and i am doing marketing since 2015 and 
> currently i am doing marketing for Dp Pavingny.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (AMBARI-25657) DP Pavingny

[Sumit Mohanty (Jira)]

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

Sumit Mohanty resolved AMBARI-25657.

Resolution: Won't Fix

> DP Pavingny
> ---
>
> Key: AMBARI-25657
> URL: https://issues.apache.org/jira/browse/AMBARI-25657
> Project: Ambari
>  Issue Type: Documentation
>Reporter: Ethel Blackwell
>Priority: Major
>
> It's Ethel Blackwell here from NY and i am doing marketing since 2015 and 
> currently i am doing marketing for Dp Pavingny.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Assigned] (AMBARI-13901) CLONE - The definition and hadling of hadoop-env should not be restrictive to HDFS

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty reassigned AMBARI-13901:
--

Assignee: (was: Sumit Mohanty)

> CLONE - The definition and hadling of hadoop-env should not be restrictive to 
> HDFS
> --
>
> Key: AMBARI-13901
> URL: https://issues.apache.org/jira/browse/AMBARI-13901
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.1.0
>Reporter: Nathan Falk
> Fix For: trunk
>
>
> This defect is cloned from AMBARI-12851. Here is the original description:
> Hadoop Env configuration defined at the stack level is managed only if HDFS  
> service is slected as part of the deployment. If HDFS is disabled and any 
> alternate FS includes hadoop-env in the stack, the configuration should be 
> understood by the Ambari code and corresponding hadoop-env.sh should be 
> created properly on the hadoop/ambari agent machines.
> I do not believe that the issue has been fully addressed by AMBARI-12837.
> If a filesystem service is replacing HDFS, then it has to manage the 
> core-site and hadoop-env configurations, and possibly hdfs-site as well. Many 
> of these properties are defined in site_properties.js, but are defined as 
> having a 'serviceName' of 'HDFS'. When it comes time for Ambari to display 
> these properties in the UI, they get left out. This is true both on the 
> customize services page of the installation wizard and on the Configs tab for 
> the HCFS service.
> On installation, anything that the HCFS service has defined in the stack in 
> core-site.xml, hdfs-site.xml or hadoop-env.xml does get saved to the 
> database, even if some of the properties do not appear on the Customize 
> Services page.
> However, if the admin tries to change any properties later (for example, the 
> hadoop-env.sh content), then only those properties which are displayed by the 
> UI, which are those properties that are NOT defined in site_properties.js, 
> are saved.
> The issue seems to be in these areas of the code, all in 
> ambari-web/app/utils/config.js:
> mergePredefinedWithSaved
> mergePredefinedWithLoaded
> serviceConfigUiAttributes
> All 3 of these functions will set 'serviceName' in the serviceConfigObj to 
> the serviceName from the pre-defined config properties in configsPropertyDef.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (AMBARI-13163) check_fs_root for HIVE service should also support HCFS type

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty reassigned AMBARI-13163:
--

Assignee: (was: Sumit Mohanty)

> check_fs_root for HIVE service should also support HCFS type
> 
>
> Key: AMBARI-13163
> URL: https://issues.apache.org/jira/browse/AMBARI-13163
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk
>Reporter: Vijay Srinivasaraghavan
> Fix For: 2.3.0
>
>
> check_fs_root includes the logic to modify the FS path when it changes. The 
> current implementation only supports it for hdfs. Instead of filtering the FS 
> root by "hdfs", the value should be read from cluster-env for any HCFS type 
> to identify the FS namespace or it could simple tokenize DefaultFS and find 
> string before "://".



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (AMBARI-12293) Allow auto execution of command/task at specific life cycle stages of a cluster

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty resolved AMBARI-12293.

Resolution: Won't Fix

> Allow auto execution of command/task at specific life cycle stages of a 
> cluster
> ---
>
> Key: AMBARI-12293
> URL: https://issues.apache.org/jira/browse/AMBARI-12293
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server, stacks
>Affects Versions: 2.1.0
>Reporter: Sumit Mohanty
>Assignee: Sumit Mohanty
>Priority: Critical
> Fix For: 2.3.0
>
>
> During cluster creation (or add hosts), especially in the hosted clusters in 
> cloud environment, it is a requirement to execute tasks/commands at specific 
> life-cycle stages.
> Samples of such stages are:
> * pre-install - before any components are installed
> * post-install - after all components are installed
> * pre-start - before starting any components
> * post-start - after all starts are complete
> These tasks are generally expected to be executed for each host and at least 
> once. It is expected that these tasks be auto-executed. In addition if these 
> tasks fail it may result in fast fail - aborting any other tasks following 
> these.
> Samples of such tasks are -
> * perform host level setup (create local users, files, and folders)
> * perform custom health checks
> To support auto-execution, it is also necessary to allow saved configuration 
> for the tasks being auto-executed.
> While it may not be necessary, it will be good to allow execution of the 
> above tasks at any other time through explicit API calls.  
> Ambari today has support for custom command/action. Custom actions can be 
> defined as stand alone tasks that can be invoked anytime through APIs. Custom 
> commands are commands associated with specific services. The design of this 
> feature should take into account the existing capabilities.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-18574) Set hbase.hregion.memstore.chunkpool.maxsize to 1.0

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty updated AMBARI-18574:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

Committed to trunk and branch-2.6

> Set hbase.hregion.memstore.chunkpool.maxsize to 1.0
> ---
>
> Key: AMBARI-18574
> URL: https://issues.apache.org/jira/browse/AMBARI-18574
> Project: Ambari
>  Issue Type: Bug
>Reporter: Ted Yu
>Assignee: Yao Lei
> Fix For: 2.6.0
>
> Attachments: AMBARI-18574_2.patch, AMBARI-18574.patch
>
>
> The default value for hbase.hregion.memstore.chunkpool.maxsize is:
> {code}
>   final static float POOL_MAX_SIZE_DEFAULT = 0.0f;
> {code}
> This would result in chunk pool being disabled, leading to excessive 
> MemStoreLAB chunk allocations.
> Ambari should set the value to 1.0



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (AMBARI-18574) Set hbase.hregion.memstore.chunkpool.maxsize to 1.0

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty commented on AMBARI-18574:


LGTM, +1 to 
https://issues.apache.org/jira/secure/attachment/12883663/AMBARI-18574_2.patch

> Set hbase.hregion.memstore.chunkpool.maxsize to 1.0
> ---
>
> Key: AMBARI-18574
> URL: https://issues.apache.org/jira/browse/AMBARI-18574
> Project: Ambari
>  Issue Type: Bug
>Reporter: Ted Yu
>Assignee: Yao Lei
> Fix For: 2.6.0
>
> Attachments: AMBARI-18574_2.patch, AMBARI-18574.patch
>
>
> The default value for hbase.hregion.memstore.chunkpool.maxsize is:
> {code}
>   final static float POOL_MAX_SIZE_DEFAULT = 0.0f;
> {code}
> This would result in chunk pool being disabled, leading to excessive 
> MemStoreLAB chunk allocations.
> Ambari should set the value to 1.0



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (AMBARI-21793) Add support for variables used by Knox topology template

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty commented on AMBARI-21793:


LGTM, +1

> Add support for variables used by Knox topology template
> 
>
> Key: AMBARI-21793
> URL: https://issues.apache.org/jira/browse/AMBARI-21793
> Project: Ambari
>  Issue Type: Bug
>Reporter: Sandeep More
>Assignee: Sandeep More
> Fix For: 2.6.0
>
> Attachments: AMBARI-21793.001.patch
>
>
> Currently Knox template within Ambari uses some hardcoded values such as http 
> schemes, this bug is to add variables which would would make Knox template 
> within Ambari more dynamic.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-21793) Add support for variables used by Knox topology template

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty updated AMBARI-21793:
---
Fix Version/s: 2.6.0

> Add support for variables used by Knox topology template
> 
>
> Key: AMBARI-21793
> URL: https://issues.apache.org/jira/browse/AMBARI-21793
> Project: Ambari
>  Issue Type: Bug
>Reporter: Sandeep More
>Assignee: Sandeep More
> Fix For: 2.6.0
>
> Attachments: AMBARI-21793.001.patch
>
>
> Currently Knox template within Ambari uses some hardcoded values such as http 
> schemes, this bug is to add variables which would would make Knox template 
> within Ambari more dynamic.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-21793) Add support for variables used by Knox topology template

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty updated AMBARI-21793:
---
Status: Patch Available  (was: Open)

> Add support for variables used by Knox topology template
> 
>
> Key: AMBARI-21793
> URL: https://issues.apache.org/jira/browse/AMBARI-21793
> Project: Ambari
>  Issue Type: Bug
>Reporter: Sandeep More
>Assignee: Sandeep More
> Attachments: AMBARI-21793.001.patch
>
>
> Currently Knox template within Ambari uses some hardcoded values such as http 
> schemes, this bug is to add variables which would would make Knox template 
> within Ambari more dynamic.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-21793) Add support for variables used by Knox topology template

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty updated AMBARI-21793:
---
Attachment: AMBARI-21793.001.patch

> Add support for variables used by Knox topology template
> 
>
> Key: AMBARI-21793
> URL: https://issues.apache.org/jira/browse/AMBARI-21793
> Project: Ambari
>  Issue Type: Bug
>Reporter: Sandeep More
>Assignee: Sandeep More
> Attachments: AMBARI-21793.001.patch
>
>
> Currently Knox template within Ambari uses some hardcoded values such as http 
> schemes, this bug is to add variables which would would make Knox template 
> within Ambari more dynamic.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-21569) Users randomly getting "HDFS020 Could not write file" exceptions while running query from Hive View

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty updated AMBARI-21569:
---
Fix Version/s: (was: 2.5.3)
   2.6.0

> Users randomly getting "HDFS020 Could not write file" exceptions while 
> running query from Hive View
> ---
>
> Key: AMBARI-21569
> URL: https://issues.apache.org/jira/browse/AMBARI-21569
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Gaurav Nagar
>Assignee: venkat
> Fix For: 2.6.0
>
> Attachments: AMBARI-21569.branch-2.5.patch, AMBARI-21569-trunk.patch
>
>
>  Running queries from Hive View are reporting intermittent issues with the 
> Hive view. They get the exceptions as reported below
> {code:java}
> ServiceFormattedException:100 - 
> org.apache.ambari.view.utils.hdfs.HdfsApiException: HDFS020 Could not write 
> file /user/user/hive/jobs/hive-job-5290-2017-03-22_02-35/logs
> org.apache.ambari.view.utils.hdfs.HdfsApiException: HDFS020 Could not write 
> file /user/user/hive/jobs/hive-job-5290-2017-03-22_02-35/logs
> at 
> org.apache.ambari.view.utils.hdfs.HdfsUtil.putStringToFile(HdfsUtil.java:51)
> at 
> org.apache.ambari.view.hive.resources.jobs.viewJobs.JobControllerImpl.updateOperationLogs(JobControllerImpl.java:202)
> at 
> org.apache.ambari.view.hive.resources.jobs.viewJobs.JobControllerImpl.update(JobControllerImpl.java:160)
> at 
> org.apache.ambari.view.hive.resources.jobs.viewJobs.JobResourceManager.read(JobResourceManager.java:79)
> at 
> org.apache.ambari.view.hive.resources.jobs.viewJobs.JobResourceManager.readController(JobResourceManager.java:95)
> at 
> org.apache.ambari.view.hive.resources.jobs.JobService.getOne(JobService.java:133)
> at sun.reflect.GeneratedMethodAccessor191.invoke(Unknown Source)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at 
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
> at 
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
> at 
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
> at 
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
> at 
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
> at 
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
> at 
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
> at 
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)
> at 
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)
> at 
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)
> at 
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)
> at 
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
> at 
> org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:684)
> at 
> 

[jira] [Commented] (AMBARI-18574) Set hbase.hregion.memstore.chunkpool.maxsize to 1.0

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty commented on AMBARI-18574:


The patch, as such, looks good. Not sure if its intentional but with this 
change when Ambari is upgraded the property will show up in HBase config and 
require HBase restart. In general, HBase restart is not as problematic as HDFS 
but most users do not like to restart any service after Ambari upgrade. So if 
you want to avoid HBase restart after Ambari upgrade and rather "fix" this as 
part of a stack upgrade then you should set {{}} and make upgrade pack changes to add the config when stack is 
upgraded.

> Set hbase.hregion.memstore.chunkpool.maxsize to 1.0
> ---
>
> Key: AMBARI-18574
> URL: https://issues.apache.org/jira/browse/AMBARI-18574
> Project: Ambari
>  Issue Type: Bug
>Reporter: Ted Yu
>Assignee: Yao Lei
> Fix For: 2.6.0
>
> Attachments: AMBARI-18574.patch
>
>
> The default value for hbase.hregion.memstore.chunkpool.maxsize is:
> {code}
>   final static float POOL_MAX_SIZE_DEFAULT = 0.0f;
> {code}
> This would result in chunk pool being disabled, leading to excessive 
> MemStoreLAB chunk allocations.
> Ambari should set the value to 1.0



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (AMBARI-21794) Post Ambari upgrade on a migration cluster Oozie failed to restart when LZO compression is enabled

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty commented on AMBARI-21794:


https://issues.apache.org/jira/secure/attachment/12883432/AMBARI-21794-1.patch 
looks good, +1.

> Post Ambari upgrade on a migration cluster Oozie failed to restart when LZO 
> compression is enabled
> --
>
> Key: AMBARI-21794
> URL: https://issues.apache.org/jira/browse/AMBARI-21794
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Di Li
>Assignee: Siddharth Wagle
> Fix For: 2.6.0
>
> Attachments: AMBARI-21794-1.patch, AMBARI-21794.patch
>
>
> This is specifically a migration issue. This should be similar to 
> https://issues.apache.org/jira/browse/AMBARI-21624
> I had IOP + Big SQL 4.2.5 installed with LDAP and Kerberos enabled. The 
> Ambari build used is Ambari 2.5.2-280.  Post Ambari upgrade, all services can 
> be restarted, except Oozie (during "Restart Oozie Server")
> {noformat}
> Traceback (most recent call last):
>   File 
> "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_server.py",
>  line 159, in 
> OozieServer().execute()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 329, in execute
> method(env)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 865, in restart
> self.start(env, upgrade_type=upgrade_type)
>   File 
> "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_server.py",
>  line 84, in start
> self.configure(env)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 119, in locking_configure
> original_configure(obj, *args, **kw)
>   File 
> "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_server.py",
>  line 78, in configure
> oozie(is_server=True, upgrade_type=upgrade_type)
>   File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py", 
> line 89, in thunk
> return fn(*args, **kwargs)
>   File 
> "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie.py",
>  line 193, in oozie
> oozie_server_specific(upgrade_type)
>   File 
> "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie.py",
>  line 311, in oozie_server_specific
> retry_count=params.agent_stack_retry_count)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/base.py", 
> line 125, in __new__
> cls(names_list.pop(0), env, provider, **kwargs)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/base.py", 
> line 166, in __init__
> self.env.run()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
> line 160, in run
> self.run_action(resource, action)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
> line 124, in run_action
> provider_action()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/package/__init__.py",
>  line 54, in action_install
> self.install_package(package_name, self.resource.use_repos, 
> self.resource.skip_repos)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/package/yumrpm.py",
>  line 53, in install_package
> self.checked_call_with_retries(cmd, sudo=True, 
> logoutput=self.get_logoutput())
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/package/__init__.py",
>  line 86, in checked_call_with_retries
> return self._call_with_retries(cmd, is_checked=True, **kwargs)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/package/__init__.py",
>  line 98, in _call_with_retries
> code, out = func(cmd, **kwargs)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 72, in inner
> result = function(command, **kwargs)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 102, in checked_call
> tries=tries, try_sleep=try_sleep, 
> timeout_kill_strategy=timeout_kill_strategy)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 150, in _call_wrapper
> result = _call(command, **kwargs_copy)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 303, in _call
> raise ExecutionFailed(err_msg, code, out, err)
> resource_management.core.exceptions.ExecutionFailed: Execution of 
> '/usr/bin/yum -d 0 -e 0 -y install hadooplzo_4_2_5_IBM_1_1' returned 1. 
> Error: 

[jira] [Updated] (AMBARI-21569) Users randomly getting "HDFS020 Could not write file" exceptions while running query from Hive View

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty updated AMBARI-21569:
---
Fix Version/s: 2.5.3

> Users randomly getting "HDFS020 Could not write file" exceptions while 
> running query from Hive View
> ---
>
> Key: AMBARI-21569
> URL: https://issues.apache.org/jira/browse/AMBARI-21569
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Gaurav Nagar
>Assignee: venkat
> Fix For: 2.5.3
>
> Attachments: AMBARI-21569.branch-2.5.patch, AMBARI-21569-trunk.patch
>
>
>  Running queries from Hive View are reporting intermittent issues with the 
> Hive view. They get the exceptions as reported below
> {code:java}
> ServiceFormattedException:100 - 
> org.apache.ambari.view.utils.hdfs.HdfsApiException: HDFS020 Could not write 
> file /user/user/hive/jobs/hive-job-5290-2017-03-22_02-35/logs
> org.apache.ambari.view.utils.hdfs.HdfsApiException: HDFS020 Could not write 
> file /user/user/hive/jobs/hive-job-5290-2017-03-22_02-35/logs
> at 
> org.apache.ambari.view.utils.hdfs.HdfsUtil.putStringToFile(HdfsUtil.java:51)
> at 
> org.apache.ambari.view.hive.resources.jobs.viewJobs.JobControllerImpl.updateOperationLogs(JobControllerImpl.java:202)
> at 
> org.apache.ambari.view.hive.resources.jobs.viewJobs.JobControllerImpl.update(JobControllerImpl.java:160)
> at 
> org.apache.ambari.view.hive.resources.jobs.viewJobs.JobResourceManager.read(JobResourceManager.java:79)
> at 
> org.apache.ambari.view.hive.resources.jobs.viewJobs.JobResourceManager.readController(JobResourceManager.java:95)
> at 
> org.apache.ambari.view.hive.resources.jobs.JobService.getOne(JobService.java:133)
> at sun.reflect.GeneratedMethodAccessor191.invoke(Unknown Source)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at 
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
> at 
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
> at 
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
> at 
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
> at 
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
> at 
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
> at 
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
> at 
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)
> at 
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)
> at 
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)
> at 
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)
> at 
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
> at 
> org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:684)
> at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1507)
>  

[jira] [Resolved] (AMBARI-13135) Provide recommendation w.r.t. CMSInitiatingOccupancy for HBase

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty resolved AMBARI-13135.

Resolution: Fixed

Committed to branch-2.6 and trunk

> Provide recommendation w.r.t. CMSInitiatingOccupancy for HBase
> --
>
> Key: AMBARI-13135
> URL: https://issues.apache.org/jira/browse/AMBARI-13135
> Project: Ambari
>  Issue Type: Improvement
>Reporter: Ted Yu
>Assignee: Yao Lei
> Fix For: 2.6.0
>
> Attachments: AMBARI-13135.patch, sample1.png, sample2.png, 
> sample3.png, sample4.png, sample5.png
>
>
> The following options are recommended for HBase when ConcMarkSweepGC is used:
> {code}
> -XX:CMSInitiatingOccupancyFraction=50
> -XX:+UseCMSInitiatingOccupancyOnly
> {code}
> The band for CMSInitiatingOccupancyFraction is [40, 60], depending on 
> workload.
> This should be reflected in stack_advisor.py



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (AMBARI-13135) Provide recommendation w.r.t. CMSInitiatingOccupancy for HBase

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty commented on AMBARI-13135:


Ran UT
test_yaml_property_escaping (TestYAMLUtils.TestYAMLUtils) ... ok

--
Ran 272 tests in 7.368s

OK
--
Total run:1178
Total errors:0
Total failures:0
OK

> Provide recommendation w.r.t. CMSInitiatingOccupancy for HBase
> --
>
> Key: AMBARI-13135
> URL: https://issues.apache.org/jira/browse/AMBARI-13135
> Project: Ambari
>  Issue Type: Improvement
>Reporter: Ted Yu
>Assignee: Yao Lei
> Fix For: 2.6.0
>
> Attachments: AMBARI-13135.patch, sample1.png, sample2.png, 
> sample3.png, sample4.png, sample5.png
>
>
> The following options are recommended for HBase when ConcMarkSweepGC is used:
> {code}
> -XX:CMSInitiatingOccupancyFraction=50
> -XX:+UseCMSInitiatingOccupancyOnly
> {code}
> The band for CMSInitiatingOccupancyFraction is [40, 60], depending on 
> workload.
> This should be reflected in stack_advisor.py



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (AMBARI-13135) Provide recommendation w.r.t. CMSInitiatingOccupancy for HBase

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty reassigned AMBARI-13135:
--

Assignee: Ted Yu

> Provide recommendation w.r.t. CMSInitiatingOccupancy for HBase
> --
>
> Key: AMBARI-13135
> URL: https://issues.apache.org/jira/browse/AMBARI-13135
> Project: Ambari
>  Issue Type: Improvement
>Reporter: Ted Yu
>Assignee: Ted Yu
> Fix For: 2.6.0
>
> Attachments: AMBARI-13135.patch, sample1.png, sample2.png, 
> sample3.png, sample4.png, sample5.png
>
>
> The following options are recommended for HBase when ConcMarkSweepGC is used:
> {code}
> -XX:CMSInitiatingOccupancyFraction=50
> -XX:+UseCMSInitiatingOccupancyOnly
> {code}
> The band for CMSInitiatingOccupancyFraction is [40, 60], depending on 
> workload.
> This should be reflected in stack_advisor.py



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (AMBARI-13135) Provide recommendation w.r.t. CMSInitiatingOccupancy for HBase

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty reassigned AMBARI-13135:
--

Assignee: Yao Lei  (was: Ted Yu)

> Provide recommendation w.r.t. CMSInitiatingOccupancy for HBase
> --
>
> Key: AMBARI-13135
> URL: https://issues.apache.org/jira/browse/AMBARI-13135
> Project: Ambari
>  Issue Type: Improvement
>Reporter: Ted Yu
>Assignee: Yao Lei
> Fix For: 2.6.0
>
> Attachments: AMBARI-13135.patch, sample1.png, sample2.png, 
> sample3.png, sample4.png, sample5.png
>
>
> The following options are recommended for HBase when ConcMarkSweepGC is used:
> {code}
> -XX:CMSInitiatingOccupancyFraction=50
> -XX:+UseCMSInitiatingOccupancyOnly
> {code}
> The band for CMSInitiatingOccupancyFraction is [40, 60], depending on 
> workload.
> This should be reflected in stack_advisor.py



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (AMBARI-13135) Provide recommendation w.r.t. CMSInitiatingOccupancy for HBase

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty commented on AMBARI-13135:


LGTM, +1

> Provide recommendation w.r.t. CMSInitiatingOccupancy for HBase
> --
>
> Key: AMBARI-13135
> URL: https://issues.apache.org/jira/browse/AMBARI-13135
> Project: Ambari
>  Issue Type: Improvement
>Reporter: Ted Yu
> Fix For: 2.6.0
>
> Attachments: AMBARI-13135.patch, sample1.png, sample2.png, 
> sample3.png, sample4.png, sample5.png
>
>
> The following options are recommended for HBase when ConcMarkSweepGC is used:
> {code}
> -XX:CMSInitiatingOccupancyFraction=50
> -XX:+UseCMSInitiatingOccupancyOnly
> {code}
> The band for CMSInitiatingOccupancyFraction is [40, 60], depending on 
> workload.
> This should be reflected in stack_advisor.py



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-21779) Storm should not have ranger 'ranger-admin-site' and 'ranger-ugsync-site' dependencies

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty updated AMBARI-21779:
---
Fix Version/s: 2.6.0

> Storm should not have ranger 'ranger-admin-site' and 'ranger-ugsync-site' 
> dependencies
> --
>
> Key: AMBARI-21779
> URL: https://issues.apache.org/jira/browse/AMBARI-21779
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk, 2.5.1
> Environment: All
>Reporter: JaySenSharma
>Assignee: JaySenSharma
> Fix For: 2.6.0
>
> Attachments: AMBARI-21779.patch
>
>
> - Storm should not include the following *""*
> {code}
> ranger-ugsync-site
> ranger-admin-site
> {code}
> - Else making any configuration change in Ranger service  (for example:  
> *"Ranger User Info"* ) will ask Storm service to be restarted.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-21675) Add Secure Flag to Cookie / JSESSIONID in Zeppelin

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty updated AMBARI-21675:
---
Fix Version/s: 2.6.0

> Add Secure Flag to Cookie / JSESSIONID in Zeppelin
> --
>
> Key: AMBARI-21675
> URL: https://issues.apache.org/jira/browse/AMBARI-21675
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Reporter: Prabhjyot Singh
>Assignee: Prabhjyot Singh
> Fix For: 2.6.0
>
>
> The secure flag attribute must be set on session cookies containing session 
> tokens for Zeppelin Application



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (AMBARI-21750) HDFS restart fails after migration if WebHDFS is disabled

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty commented on AMBARI-21750:


LGTM, +1

> HDFS restart fails after migration if WebHDFS is disabled
> -
>
> Key: AMBARI-21750
> URL: https://issues.apache.org/jira/browse/AMBARI-21750
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Siddharth Wagle
>Assignee: Siddharth Wagle
>Priority: Critical
> Fix For: 2.5.2
>
> Attachments: AMBARI-21750.patch
>
>
> *STR*:
> - Install IOP 4.2.5 cluster with HDFS and ZK 
> - Disable WebHDFS and Restart affected services
> - Upgrade to Ambari 2.5.2 (latest build)
> - Check the fast-hdfs-resource jar exists:
> {code}
> ls -l 
> /var/lib/ambari-agent/cache/stacks/BigInsights/4.2.5/hooks/before-START/files/fast-hdfs-resource.jar
> {code}
> - Restart amabri agent. The file is deleted after restart.
> - Results in the following error:
> {code}
> raceback (most recent call last):
>   File 
> "/var/lib/ambari-agent/cache/stacks/BigInsights/4.2.5/hooks/before-START/scripts/hook.py",
>  line 41, in 
> BeforeStartHook().execute()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 329, in execute
> method(env)
>   File 
> "/var/lib/ambari-agent/cache/stacks/BigInsights/4.2.5/hooks/before-START/scripts/hook.py",
>  line 34, in hook
> setup_hadoop()
>   File 
> "/var/lib/ambari-agent/cache/stacks/BigInsights/4.2.5/hooks/before-START/scripts/shared_initialization.py",
>  line 71, in setup_hadoop
> content=StaticFile("fast-hdfs-resource.jar")
>   File "/usr/lib/python2.6/site-packages/resource_management/core/base.py", 
> line 166, in __init__
> self.env.run()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
> line 160, in run
> self.run_action(resource, action)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
> line 124, in run_action
> provider_action()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
>  line 123, in action_create
> content = self._get_content()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
>  line 160, in _get_content
> return content()
>   File "/usr/lib/python2.6/site-packages/resource_management/core/source.py", 
> line 52, in __call__
> return self.get_content()
>   File "/usr/lib/python2.6/site-packages/resource_management/core/source.py", 
> line 76, in get_content
> raise Fail("{0} Source file {1} is not found".format(repr(self), path))
> resource_management.core.exceptions.Fail: 
> StaticFile('fast-hdfs-resource.jar') Source file 
> /var/lib/ambari-agent/cache/stacks/BigInsights/4.2.5/hooks/before-START/files/fast-hdfs-resource.jar
>  is not found
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (AMBARI-21751) Fix regression caused by AMBARI-21045

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty commented on AMBARI-21751:


LGTM +1

> Fix regression caused by AMBARI-21045
> -
>
> Key: AMBARI-21751
> URL: https://issues.apache.org/jira/browse/AMBARI-21751
> Project: Ambari
>  Issue Type: Bug
>  Components: service-advisor
>Affects Versions: 2.5.2
>Reporter: Yusaku Sako
>Assignee: Yusaku Sako
>Priority: Critical
> Fix For: 2.5.2
>
> Attachments: AMBARI-21751.patch
>
>
> AMBARI-21045 caused a regression where it masks the Beacon mpack service 
> advisor from getting invoked.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-19430) Use common property for principal name prefix to help with customization of unique principal names

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty updated AMBARI-19430:
---
Fix Version/s: 2.5.0

> Use common property for principal name prefix to help with customization of 
> unique principal names
> --
>
> Key: AMBARI-19430
> URL: https://issues.apache.org/jira/browse/AMBARI-19430
> Project: Ambari
>  Issue Type: Bug
>Reporter: Robert Levas
>Assignee: Robert Levas
>  Labels: kerberos, kerberos_descriptor
> Fix For: 2.5.0
>
> Attachments: AMBARI-19430_branch-2.5_01.patch, 
> AMBARI-19430_trunk_01.patch
>
>
> Use common property for principal name prefix to help with customization of 
> unique principal names.  
> All _headless_ Kerberos identities have a non-unique principal name (across 
> clusters). To help this issue, the cluster name is appended to these 
> principal names by adding "-$\{cluster-name|toLower()\}" after the principal 
> name component. If the user wants to change this convention, they will need 
> to find all _headless_ principals and make the change. On top of that, when 
> adding new components, they will need to remember to make the change to new 
> _headless_ principal names. 
> A better solution is to provide a _global_ property named "principal_suffix" 
> and use that in each _headless_ principal name. By default the value for this 
> property will be
> {code}
> principal_suffix="-${cluster_name|toLower()}"
> {code}
> If the user would like not use a prefix (in the event there is only a single 
> cluster connecting to the KDC), the value can be changed to
> {code}
> principal_suffix=""
> {code}
> Finally if the user would like to use some other randomizer, they can set the 
> value to something else. For example
> {code}
> principal_suffix="_12345"
> {code}
> The property is set in the Kerberos descriptor's "properties" block.   For 
> example:
> {code}
> {
>   "properties": {
> "realm": "${kerberos-env/realm}",
> ...,
> "principal_suffix": "${cluster_name|toLower()}"
>   },
>   "identities": [
> ..., 
> {
>   "name": "smokeuser",
>   "principal": {
> "value": "${cluster-env/smokeuser}-${principal_suffix}@${realm}",
> "type": "user",
> "configuration": "cluster-env/smokeuser_principal_name",
> "local_username": "${cluster-env/smokeuser}"
>   },
>   ...
> }
>   ],
>   "services": [
> {
> {code} 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (AMBARI-21045) Enable Storm's AutoTGT configs in secure mode

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty commented on AMBARI-21045:


https://issues.apache.org/jira/secure/attachment/12882035/AMBARI-21045-2.5-maint.patch
 is good for backport +1

> Enable Storm's AutoTGT configs in secure mode
> -
>
> Key: AMBARI-21045
> URL: https://issues.apache.org/jira/browse/AMBARI-21045
> Project: Ambari
>  Issue Type: Bug
>Reporter: Sriharsha Chintalapani
>Assignee: Sriharsha Chintalapani
>Priority: Critical
> Fix For: 2.5.2
>
> Attachments: AMBARI-21045-2.5-maint.patch, 
> AMBARI-21045.branch-2.5.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-20534) Enable Ambari builds on ARM64 and PPC

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty updated AMBARI-20534:
---
Fix Version/s: (was: 2.5.2)
   2.6.0

> Enable Ambari builds on ARM64 and PPC
> -
>
> Key: AMBARI-20534
> URL: https://issues.apache.org/jira/browse/AMBARI-20534
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-admin, ambari-web
>Affects Versions: 2.4.2
>Reporter: Roman Shaposhnik
>Assignee: Roman Shaposhnik
> Fix For: 2.6.0
>
> Attachments: AMBARI-20534.patch.txt
>
>
> Currently Ambari fails to build on ARM64 and PPC in big part because of 
> dependency on the old version of com.github.eirslett:frontend-maven-plugin 
> Bumping the version to 1.3 solves this issue and doesn't seem to affect the 
> build in any other way.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-20702) User should be prompted for confirmation before closing the browser window

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty updated AMBARI-20702:
---
Fix Version/s: (was: 2.5.2)
   2.6.0

> User should be prompted for confirmation before closing the browser window
> --
>
> Key: AMBARI-20702
> URL: https://issues.apache.org/jira/browse/AMBARI-20702
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Supreeth Sharma
>Assignee: Pallav Kulshreshtha
>  Labels: WFD, WFM
> Fix For: 2.6.0
>
> Attachments: AMBARI-20702-branch-2-5.patch
>
>
> User should be prompted for confirmation before closing the browser window. 
> If user is in designer page and in middle of workflow creation and he clicks 
> on closing browser window or browser instance, he should be prompted for 
> confirmation before actually closing the window.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-20706) Workflow manager is not prompting for custom properties if its part of an expression

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty updated AMBARI-20706:
---
Fix Version/s: (was: 2.5.2)
   3.0.0

> Workflow manager is not prompting for custom properties if its part of an 
> expression
> 
>
> Key: AMBARI-20706
> URL: https://issues.apache.org/jira/browse/AMBARI-20706
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Supreeth Sharma
>Assignee: Belliraj HB
>Priority: Critical
>  Labels: WFD, WFM
> Fix For: 3.0.0
>
>
> Workflow manager is not prompting for custom properties if its part of an 
> expression. 
> Workflow manager should identify all the properties and prompt them during 
> workflow submission.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-20708) Need to show appropriate error when views are not able to read the encrypted file

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty updated AMBARI-20708:
---
Fix Version/s: (was: 2.5.2)
   3.0.0

> Need to show appropriate error when views are not able to read the encrypted 
> file
> -
>
> Key: AMBARI-20708
> URL: https://issues.apache.org/jira/browse/AMBARI-20708
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Supreeth Sharma
>Assignee: DIPAYAN BHOWMICK
>Priority: Critical
>  Labels: HiveView2.0
> Fix For: 3.0.0
>
>
> Need to show appropriate error message on the UI when ambari views are not 
> able to read the encrypted file.
> Issue Scenario 1 : Try to upload/download file from encrypted zone using 
> 'Files view'
> Issue Scenario 2 : Try to create a table from using a file from encrypted 
> zone using 'Hive View'
> Issue Scenario 3 : Try to access workflows from encrypted zone in 'Workflow 
> Manager View'
> Steps to reproduce :
> 1) Encrypt a folder using the steps as defined in 
> https://github.com/abajwa-hw/security-workshops/blob/master/Setup-TDE-23.md
> 2) Add a new file to this location.
> 3) Now try to access this file from different views as described in above 
> scenario.
> UI simply fails without showing any error message. Need to show appropriate 
> message to the user to indicating the cause of failure.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-21043) Backport Ambari-17694 - Kafka listeners property does not show SASL_PLAINTEXT protocol when Kerberos is enabled

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty updated AMBARI-21043:
---
Fix Version/s: (was: 2.5.2)

> Backport Ambari-17694 - Kafka listeners property does not show SASL_PLAINTEXT 
> protocol when Kerberos is enabled
> ---
>
> Key: AMBARI-21043
> URL: https://issues.apache.org/jira/browse/AMBARI-21043
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.1
>Reporter: Robert Levas
>Assignee: Sriharsha Chintalapani
>Priority: Blocker
> Fix For: 3.0.0
>
> Attachments: AMBARI-21043_branch-2.5_01.patch, 
> AMBARI-21043_branch-2.5_02.patch, AMBARI-21043_trunk_01.patch
>
>
> Backport Ambari-17694 to Ambari 2.5.1 because the patch was never committed 
> to branch-2.5 and thus did not make it into Ambari 2.5.0.  
> Most of the changes from Ambari 2.4.x applied without much additional work, 
> however an upgrade path from Ambari 2.5.0 to Ambari 2.5.1 has been created 
> since users of Ambari 2.5.1 may have missed out on the needed changes. This 
> additional work was essentially copying 
> {{org.apache.ambari.server.upgrade.UpgradeCatalog240#updateKAFKAConfigs}} to 
> {{org.apache.ambari.server.upgrade.UpgradeCatalog251#updateKAFKAConfigs} and 
> adding to the unit tests in 
> {{org.apache.ambari.server.upgrade.UpgradeCatalog251Test}}.
> See AMBARI-17694 for more information about the changes. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-20709) Incorrect job completion state for pig - Intermittent issue

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty updated AMBARI-20709:
---
Fix Version/s: (was: 2.5.2)
   3.0.0

> Incorrect job completion state for pig - Intermittent issue
> ---
>
> Key: AMBARI-20709
> URL: https://issues.apache.org/jira/browse/AMBARI-20709
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Supreeth Sharma
>Assignee: Nitiraj Singh Rathore
>  Labels: pig-view
> Fix For: 3.0.0
>
>
> Job state is shown incorrectly after running the pig script. Even though job 
> has completed successfully and script has returned the result, job state is 
> being shown as SUBMIT_FAILED.
> I dont see any error in pig logs.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-21045) Enable Storm's AutoTGT configs in secure mode

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty updated AMBARI-21045:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Enable Storm's AutoTGT configs in secure mode
> -
>
> Key: AMBARI-21045
> URL: https://issues.apache.org/jira/browse/AMBARI-21045
> Project: Ambari
>  Issue Type: Bug
>Reporter: Sriharsha Chintalapani
>Assignee: Sriharsha Chintalapani
>Priority: Critical
> Fix For: 2.5.2
>
> Attachments: AMBARI-21045.branch-2.5.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-21498) DB consistency checker throws errors for missing 'product-info' configs after Ambari upgrade

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty updated AMBARI-21498:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> DB consistency checker throws errors for missing 'product-info' configs after 
> Ambari upgrade
> 
>
> Key: AMBARI-21498
> URL: https://issues.apache.org/jira/browse/AMBARI-21498
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
>Priority: Blocker
> Fix For: 2.5.2
>
> Attachments: AMBARI-21498.patch
>
>
> DB consistency checker throws errors for missing 'product-info' configs after 
> Ambari upgrade
> AMBARI-21364 fixed the missing 'parquet-logging' but 'product-info' is still 
> missing for Smartsense
> STR
> Deployed cluster with Ambari version: 2.5.1.0-159 and HDP version: 2.6.1.0-129
> Upgrade Ambari to 2.5.2.0-105
> Run "ambari-server start"
> Live openstack cluster : 172.22.124.150 (Ambari Server)
> ambari-server-check-database.log
> {code}
> 2017-07-07 18:09:05,678 ERROR - Required config(s): product-info is(are) not 
> available for service SMARTSENSE with service config version 1 in cluster cl1
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-21110) ambari-server setup fails with default postgres

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty updated AMBARI-21110:
---
Resolution: Cannot Reproduce
Status: Resolved  (was: Patch Available)

> ambari-server setup fails with default postgres
> ---
>
> Key: AMBARI-21110
> URL: https://issues.apache.org/jira/browse/AMBARI-21110
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.5.2
>
> Attachments: AMBARI-21110.patch
>
>
> Thisis the first run with oracle12. Initially infra sets up Ambari with
> default postgres and later on ambari setup happens with Oracle12. But now the
> first setup with default postgres is failing with below error
> 
> 
> 
> root@172.27.24.11 "ambari-server setup 
> --java-home=/base/tools/jdk1.8.0_112 -s"
> 2017-05-22 10:57:54.032 Using python  /usr/bin/python
> 2017-05-22 10:57:54.032 Setup ambari-server
> 2017-05-22 10:58:14.299 Checking SELinux...
> 2017-05-22 10:58:14.299 SELinux status is 'disabled'
> 2017-05-22 10:58:14.299 Customize user account for ambari-server daemon 
> [y/n] (n)? 
> 2017-05-22 10:58:14.299 Adjusting ambari-server permissions and 
> ownership...
> 2017-05-22 10:58:14.299 Checking firewall status...
> 2017-05-22 10:58:14.299 FATAL: Could not load 
> /lib/modules/3.10.0-327.13.1.el7.x86_64/modules.dep: No such file or directory
> 2017-05-22 10:58:14.299 iptables v1.4.7: can't initialize iptables table 
> `nat': Permission denied (you must be root)
> 2017-05-22 10:58:14.299 Perhaps iptables or your kernel needs to be 
> upgraded.
> 2017-05-22 10:58:14.299 FATAL: Could not load 
> /lib/modules/3.10.0-327.13.1.el7.x86_64/modules.dep: No such file or directory
> 2017-05-22 10:58:14.299 iptables v1.4.7: can't initialize iptables table 
> `filter': Permission denied (you must be root)
> 2017-05-22 10:58:14.299 Perhaps iptables or your kernel needs to be 
> upgraded.
> 2017-05-22 10:58:14.299 WARNING: iptables is running. Confirm the 
> necessary Ambari ports are accessible. Refer to the Ambari documentation for 
> more details on ports.
> 2017-05-22 10:58:14.299 OK to continue [y/n] (y)? 
> 2017-05-22 10:58:14.299 Checking JDK...
> 2017-05-22 10:58:14.299 WARNING: JAVA_HOME /base/tools/jdk1.8.0_112 must 
> be valid on ALL hosts
> 2017-05-22 10:58:14.299 WARNING: JCE Policy files are required for 
> configuring Kerberos security. If you plan to use Kerberos,please make sure 
> JCE Unlimited Strength Jurisdiction Policy Files are valid on all hosts.
> 2017-05-22 10:58:14.299 Completing setup...
> 2017-05-22 10:58:14.299 Configuring database...
> 2017-05-22 10:58:14.299 Enter advanced database configuration [y/n] (n)? 
> 2017-05-22 10:58:14.299 Configuring database...
> 2017-05-22 10:58:14.299 Default properties detected. Using built-in 
> database.
> 2017-05-22 10:58:14.299 Configuring ambari database...
> 2017-05-22 10:58:14.299 Checking PostgreSQL...
> 2017-05-22 10:58:14.299 Running initdb: This may take up to a minute.
> 2017-05-22 10:58:14.299 Initializing database: [  OK  ]
> 2017-05-22 10:58:14.299 
> 2017-05-22 10:58:14.299 About to start PostgreSQL
> 2017-05-22 10:58:14.299 Configuring local database...
> 2017-05-22 10:58:14.299 Configuring PostgreSQL...
> 2017-05-22 10:58:14.299 Creating schema and user...
> 2017-05-22 10:58:14.299 ERROR: Failed to execute 
> command:['ambari-sudo.sh', 'su', 'postgres', '-', '--command=psql -f 
> /var/lib/ambari-server/resources/Ambari-DDL-Postgres-EMBEDDED-CREATE.sql -v 
> username=\'"ambari"\' -v password="\'bigdata\'" -v dbname="ambari"']
> 2017-05-22 10:58:14.299 ERROR: stderr:could not change directory to 
> "/root"
> 2017-05-22 10:58:14.299 psql: could not connect to server: No such file 
> or directory
> 2017-05-22 10:58:14.299   Is the server running locally and accepting
> 2017-05-22 10:58:14.299   connections on Unix domain socket 
> "/tmp/.s.PGSQL.5432"?
> 2017-05-22 10:58:14.299 
> 2017-05-22 10:58:14.299 ERROR: stdout:
> 2017-05-22 10:58:14.299 failed to execute queries ...retrying (1)
> 2017-05-22 10:58:14.299 Creating schema and user...
> 2017-05-22 10:58:14.299 ERROR: Failed to execute 
> command:['ambari-sudo.sh', 'su', 'postgres', '-', '--command=psql -f 
> /var/lib/ambari-server/resources/Ambari-DDL-Postgres-EMBEDDED-CREATE.sql -v 
> username=\'"ambari"\' -v password="\'bigdata\'" -v dbname="ambari"']
> 2017-05-22 10:58:14.299 ERROR: stderr:could not change directory to 
> "/root"
> 2017-05-22 10:58:14.299 psql: could not connect to server: No such file 
> or directory
> 2017-05-22 10:58:14.299   Is the server running locally and 

[jira] [Updated] (AMBARI-21565) RU: Hive service check was failed during RU

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty updated AMBARI-21565:
---
Description: 
Std.err




Exception in thread Thread-4:
Traceback (most recent call last):
  File "/usr/lib64/python2.6/threading.py", line 532, in __bootstrap_inner
self.run()
  File "/usr/lib64/python2.6/threading.py", line 736, in run
self.function(*self.args, **self.kwargs)
  File 
"/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 383, 
in _on_timeout
terminate_process(proc, terminate_strategy)
  File 
"/usr/lib/python2.6/site-packages/resource_management/core/signal_utils.py", 
line 48, in terminate_process
kill_process_tree(proc)
  File 
"/usr/lib/python2.6/site-packages/resource_management/core/signal_utils.py", 
line 91, in kill_process_tree
shell.checked_call(["bash", kill_tree_script, str(proc.pid), 
str(signal.SIGKILL)])
  File 
"/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 72, 
in inner
result = function(command, **kwargs)
  File 
"/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 102, 
in checked_call
tries=tries, try_sleep=try_sleep, 
timeout_kill_strategy=timeout_kill_strategy)
  File 
"/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 150, 
in _call_wrapper
result = _call(command, **kwargs_copy)
  File 
"/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 303, 
in _call
raise ExecutionFailed(err_msg, code, out, err)
ExecutionFailed: Execution of 'bash 
/usr/lib/python2.6/site-packages/resource_management/core/files/killtree.sh 
6363 9' returned 1. kill: top: invalid signal
Try `kill --help' for more information.

Exception in thread Thread-5:
Traceback (most recent call last):
  File "/usr/lib64/python2.6/threading.py", line 532, in __bootstrap_inner
self.run()
  File "/usr/lib64/python2.6/threading.py", line 736, in run
self.function(*self.args, **self.kwargs)
  File 
"/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 383, 
in _on_timeout
terminate_process(proc, terminate_strategy)
  File 
"/usr/lib/python2.6/site-packages/resource_management/core/signal_utils.py", 
line 48, in terminate_process
kill_process_tree(proc)
  File 
"/usr/lib/python2.6/site-packages/resource_management/core/signal_utils.py", 
line 91, in kill_process_tree
shell.checked_call(["bash", kill_tree_script, str(proc.pid), 
str(signal.SIGKILL)])
  File 
"/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 72, 
in inner
result = function(command, **kwargs)
  File 
"/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 102, 
in checked_call
tries=tries, try_sleep=try_sleep, 
timeout_kill_strategy=timeout_kill_strategy)
  File 
"/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 150, 
in _call_wrapper
result = _call(command, **kwargs_copy)
  File 
"/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 303, 
in _call
raise ExecutionFailed(err_msg, code, out, err)
ExecutionFailed: Execution of 'bash 
/usr/lib/python2.6/site-packages/resource_management/core/files/killtree.sh 
8306 9' returned 1. kill: top: invalid signal
Try `kill --help' for more information.

Exception in thread Thread-6:
Traceback (most recent call last):
  File "/usr/lib64/python2.6/threading.py", line 532, in __bootstrap_inner
self.run()
  File "/usr/lib64/python2.6/threading.py", line 736, in run
self.function(*self.args, **self.kwargs)
  File 
"/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 383, 
in _on_timeout
terminate_process(proc, terminate_strategy)
  File 
"/usr/lib/python2.6/site-packages/resource_management/core/signal_utils.py", 
line 48, in terminate_process
kill_process_tree(proc)
  File 
"/usr/lib/python2.6/site-packages/resource_management/core/signal_utils.py", 
line 91, in kill_process_tree
shell.checked_call(["bash", kill_tree_script, str(proc.pid), 
str(signal.SIGKILL)])
  File 
"/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 72, 
in inner
result = function(command, **kwargs)
  File 
"/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 102, 
in checked_call
tries=tries, try_sleep=try_sleep, 
timeout_kill_strategy=timeout_kill_strategy)
  File 
"/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 150, 
in _call_wrapper
result = _call(command, **kwargs_copy)
  File 
"/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 

[jira] [Updated] (AMBARI-21565) RU: Hive service check was failed during RU

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty updated AMBARI-21565:
---
Fix Version/s: (was: 2.5.2)
   3.0.0

> RU: Hive service check was failed during RU
> ---
>
> Key: AMBARI-21565
> URL: https://issues.apache.org/jira/browse/AMBARI-21565
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 3.0.0
>
>
> Cluster: 172.22.117.104:8080 - nats11-46-vdms-erm16tofnsec-s11 - 48h  
> Job: 
> Std.err
> 
> 
> 
> Exception in thread Thread-4:
> Traceback (most recent call last):
>   File "/usr/lib64/python2.6/threading.py", line 532, in __bootstrap_inner
> self.run()
>   File "/usr/lib64/python2.6/threading.py", line 736, in run
> self.function(*self.args, **self.kwargs)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 
> 383, in _on_timeout
> terminate_process(proc, terminate_strategy)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/signal_utils.py", 
> line 48, in terminate_process
> kill_process_tree(proc)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/signal_utils.py", 
> line 91, in kill_process_tree
> shell.checked_call(["bash", kill_tree_script, str(proc.pid), 
> str(signal.SIGKILL)])
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 
> 72, in inner
> result = function(command, **kwargs)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 
> 102, in checked_call
> tries=tries, try_sleep=try_sleep, 
> timeout_kill_strategy=timeout_kill_strategy)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 
> 150, in _call_wrapper
> result = _call(command, **kwargs_copy)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 
> 303, in _call
> raise ExecutionFailed(err_msg, code, out, err)
> ExecutionFailed: Execution of 'bash 
> /usr/lib/python2.6/site-packages/resource_management/core/files/killtree.sh 
> 6363 9' returned 1. kill: top: invalid signal
> Try `kill --help' for more information.
> 
> Exception in thread Thread-5:
> Traceback (most recent call last):
>   File "/usr/lib64/python2.6/threading.py", line 532, in __bootstrap_inner
> self.run()
>   File "/usr/lib64/python2.6/threading.py", line 736, in run
> self.function(*self.args, **self.kwargs)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 
> 383, in _on_timeout
> terminate_process(proc, terminate_strategy)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/signal_utils.py", 
> line 48, in terminate_process
> kill_process_tree(proc)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/signal_utils.py", 
> line 91, in kill_process_tree
> shell.checked_call(["bash", kill_tree_script, str(proc.pid), 
> str(signal.SIGKILL)])
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 
> 72, in inner
> result = function(command, **kwargs)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 
> 102, in checked_call
> tries=tries, try_sleep=try_sleep, 
> timeout_kill_strategy=timeout_kill_strategy)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 
> 150, in _call_wrapper
> result = _call(command, **kwargs_copy)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 
> 303, in _call
> raise ExecutionFailed(err_msg, code, out, err)
> ExecutionFailed: Execution of 'bash 
> /usr/lib/python2.6/site-packages/resource_management/core/files/killtree.sh 
> 8306 9' returned 1. kill: top: invalid signal
> Try `kill --help' for more information.
> 
> Exception in thread Thread-6:
> Traceback (most recent call last):
>   File "/usr/lib64/python2.6/threading.py", line 532, in __bootstrap_inner
> self.run()
>   File "/usr/lib64/python2.6/threading.py", line 736, in run
> self.function(*self.args, **self.kwargs)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 
> 383, in _on_timeout
> terminate_process(proc, terminate_strategy)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/signal_utils.py", 
> line 48, in terminate_process
> kill_process_tree(proc)
>   File 
> 

[jira] [Resolved] (AMBARI-21711) Seeing SQL errors in ambari server log when installing HDF 3.1

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty resolved AMBARI-21711.

Resolution: Fixed

Committed to trunk, branch-2.5, branch-2.6

> Seeing SQL errors in ambari server log when installing HDF 3.1
> --
>
> Key: AMBARI-21711
> URL: https://issues.apache.org/jira/browse/AMBARI-21711
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.5.2
>Reporter: Arpit Gupta
>Assignee: Sumit Mohanty
>Priority: Critical
> Fix For: 2.5.2
>
> Attachments: AMBARI-21711.patch
>
>
> {code}
> 09 Aug 2017 17:38:17,151 ERROR [alert-event-bus-1] 
> AmbariJpaLocalTxnInterceptor:180 - [DETAILED ERROR] Rollback reason:
> Local Exception Stack:
> Exception [EclipseLink-4002] (Eclipse Persistence Services - 
> 2.6.2.v20151217-774c696): org.eclipse.persistence.exceptions.DatabaseException
> Internal Exception: 
> com.mysql.jdbc.exceptions.jdbc4.MySQLIntegrityConstraintViolationException: 
> Column 'alert_state' cannot be null
> Error Code: 1048
> Call: INSERT INTO alert_history (alert_id, alert_instance, alert_label, 
> alert_state, alert_text, alert_timestamp, cluster_id, component_name, 
> host_name, service_name, alert_definition_id) VALUES (?, ?, ?, ?, ?, ?, ?, ?, 
> ?, ?, ?)
> bind => [11 parameters bound]
> Query: InsertObjectQuery(AlertCurrentEntity{alertId=1, 
> name=ambari_agent_disk_usage, state=null, latestTimestamp=1502300296216})
> at 
> org.eclipse.persistence.exceptions.DatabaseException.sqlException(DatabaseException.java:331)
> at 
> org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.executeDirectNoSelect(DatabaseAccessor.java:902)
> at 
> org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.executeNoSelect(DatabaseAccessor.java:964)
> at 
> org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.basicExecuteCall(DatabaseAccessor.java:633)
> at 
> org.eclipse.persistence.internal.databaseaccess.ParameterizedSQLBatchWritingMechanism.executeBatch(ParameterizedSQLBatchWritingMechanism.java:149)
> at 
> org.eclipse.persistence.internal.databaseaccess.ParameterizedSQLBatchWritingMechanism.executeBatchedStatements(ParameterizedSQLBatchWritingMechanism.java:134)
> at 
> org.eclipse.persistence.internal.databaseaccess.ParameterizedSQLBatchWritingMechanism.appendCall(ParameterizedSQLBatchWritingMechanism.java:82)
> at 
> org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.basicExecuteCall(DatabaseAccessor.java:605)
> at 
> org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.executeCall(DatabaseAccessor.java:560)
> at 
> org.eclipse.persistence.internal.sessions.AbstractSession.basicExecuteCall(AbstractSession.java:2055)
> at 
> org.eclipse.persistence.sessions.server.ClientSession.executeCall(ClientSession.java:306)
> at 
> org.eclipse.persistence.internal.queries.DatasourceCallQueryMechanism.executeCall(DatasourceCallQueryMechanism.java:242)
> at 
> org.eclipse.persistence.internal.queries.DatasourceCallQueryMechanism.executeCall(DatasourceCallQueryMechanism.java:228)
> at 
> org.eclipse.persistence.internal.queries.DatasourceCallQueryMechanism.insertObject(DatasourceCallQueryMechanism.java:377)
> at 
> org.eclipse.persistence.internal.queries.StatementQueryMechanism.insertObject(StatementQueryMechanism.java:165)
> at 
> org.eclipse.persistence.internal.queries.StatementQueryMechanism.insertObject(StatementQueryMechanism.java:180)
> at 
> org.eclipse.persistence.internal.queries.DatabaseQueryMechanism.insertObjectForWrite(DatabaseQueryMechanism.java:489)
> at 
> org.eclipse.persistence.queries.InsertObjectQuery.executeCommit(InsertObjectQuery.java:80)
> at 
> org.eclipse.persistence.queries.InsertObjectQuery.executeCommitWithChangeSet(InsertObjectQuery.java:90)
> at 
> org.eclipse.persistence.internal.queries.DatabaseQueryMechanism.executeWriteWithChangeSet(DatabaseQueryMechanism.java:301)
> at 
> org.eclipse.persistence.queries.WriteObjectQuery.executeDatabaseQuery(WriteObjectQuery.java:58)
> at 
> org.eclipse.persistence.queries.DatabaseQuery.execute(DatabaseQuery.java:904)
> at 
> org.eclipse.persistence.queries.DatabaseQuery.executeInUnitOfWork(DatabaseQuery.java:803)
> at 
> org.eclipse.persistence.queries.ObjectLevelModifyQuery.executeInUnitOfWorkObjectLevelModifyQuery(ObjectLevelModifyQuery.java:108)
> at 
> org.eclipse.persistence.queries.ObjectLevelModifyQuery.executeInUnitOfWork(ObjectLevelModifyQuery.java:85)
> at 
> 

[jira] [Updated] (AMBARI-21711) Seeing SQL errors in ambari server log when installing HDF 3.1

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty updated AMBARI-21711:
---
Attachment: AMBARI-21711.patch

> Seeing SQL errors in ambari server log when installing HDF 3.1
> --
>
> Key: AMBARI-21711
> URL: https://issues.apache.org/jira/browse/AMBARI-21711
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.5.2
>Reporter: Arpit Gupta
>Assignee: Sumit Mohanty
>Priority: Critical
> Fix For: 2.5.2
>
> Attachments: AMBARI-21711.patch
>
>
> {code}
> 09 Aug 2017 17:38:17,151 ERROR [alert-event-bus-1] 
> AmbariJpaLocalTxnInterceptor:180 - [DETAILED ERROR] Rollback reason:
> Local Exception Stack:
> Exception [EclipseLink-4002] (Eclipse Persistence Services - 
> 2.6.2.v20151217-774c696): org.eclipse.persistence.exceptions.DatabaseException
> Internal Exception: 
> com.mysql.jdbc.exceptions.jdbc4.MySQLIntegrityConstraintViolationException: 
> Column 'alert_state' cannot be null
> Error Code: 1048
> Call: INSERT INTO alert_history (alert_id, alert_instance, alert_label, 
> alert_state, alert_text, alert_timestamp, cluster_id, component_name, 
> host_name, service_name, alert_definition_id) VALUES (?, ?, ?, ?, ?, ?, ?, ?, 
> ?, ?, ?)
> bind => [11 parameters bound]
> Query: InsertObjectQuery(AlertCurrentEntity{alertId=1, 
> name=ambari_agent_disk_usage, state=null, latestTimestamp=1502300296216})
> at 
> org.eclipse.persistence.exceptions.DatabaseException.sqlException(DatabaseException.java:331)
> at 
> org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.executeDirectNoSelect(DatabaseAccessor.java:902)
> at 
> org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.executeNoSelect(DatabaseAccessor.java:964)
> at 
> org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.basicExecuteCall(DatabaseAccessor.java:633)
> at 
> org.eclipse.persistence.internal.databaseaccess.ParameterizedSQLBatchWritingMechanism.executeBatch(ParameterizedSQLBatchWritingMechanism.java:149)
> at 
> org.eclipse.persistence.internal.databaseaccess.ParameterizedSQLBatchWritingMechanism.executeBatchedStatements(ParameterizedSQLBatchWritingMechanism.java:134)
> at 
> org.eclipse.persistence.internal.databaseaccess.ParameterizedSQLBatchWritingMechanism.appendCall(ParameterizedSQLBatchWritingMechanism.java:82)
> at 
> org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.basicExecuteCall(DatabaseAccessor.java:605)
> at 
> org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.executeCall(DatabaseAccessor.java:560)
> at 
> org.eclipse.persistence.internal.sessions.AbstractSession.basicExecuteCall(AbstractSession.java:2055)
> at 
> org.eclipse.persistence.sessions.server.ClientSession.executeCall(ClientSession.java:306)
> at 
> org.eclipse.persistence.internal.queries.DatasourceCallQueryMechanism.executeCall(DatasourceCallQueryMechanism.java:242)
> at 
> org.eclipse.persistence.internal.queries.DatasourceCallQueryMechanism.executeCall(DatasourceCallQueryMechanism.java:228)
> at 
> org.eclipse.persistence.internal.queries.DatasourceCallQueryMechanism.insertObject(DatasourceCallQueryMechanism.java:377)
> at 
> org.eclipse.persistence.internal.queries.StatementQueryMechanism.insertObject(StatementQueryMechanism.java:165)
> at 
> org.eclipse.persistence.internal.queries.StatementQueryMechanism.insertObject(StatementQueryMechanism.java:180)
> at 
> org.eclipse.persistence.internal.queries.DatabaseQueryMechanism.insertObjectForWrite(DatabaseQueryMechanism.java:489)
> at 
> org.eclipse.persistence.queries.InsertObjectQuery.executeCommit(InsertObjectQuery.java:80)
> at 
> org.eclipse.persistence.queries.InsertObjectQuery.executeCommitWithChangeSet(InsertObjectQuery.java:90)
> at 
> org.eclipse.persistence.internal.queries.DatabaseQueryMechanism.executeWriteWithChangeSet(DatabaseQueryMechanism.java:301)
> at 
> org.eclipse.persistence.queries.WriteObjectQuery.executeDatabaseQuery(WriteObjectQuery.java:58)
> at 
> org.eclipse.persistence.queries.DatabaseQuery.execute(DatabaseQuery.java:904)
> at 
> org.eclipse.persistence.queries.DatabaseQuery.executeInUnitOfWork(DatabaseQuery.java:803)
> at 
> org.eclipse.persistence.queries.ObjectLevelModifyQuery.executeInUnitOfWorkObjectLevelModifyQuery(ObjectLevelModifyQuery.java:108)
> at 
> org.eclipse.persistence.queries.ObjectLevelModifyQuery.executeInUnitOfWork(ObjectLevelModifyQuery.java:85)
> at 
> org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.internalExecuteQuery(UnitOfWorkImpl.java:2896)
> at 
> 

[jira] [Created] (AMBARI-21711) Seeing SQL errors in ambari server log when installing HDF 3.1

[Sumit Mohanty (JIRA)]

Sumit Mohanty created AMBARI-21711:
--

 Summary: Seeing SQL errors in ambari server log when installing 
HDF 3.1
 Key: AMBARI-21711
 URL: https://issues.apache.org/jira/browse/AMBARI-21711
 Project: Ambari
  Issue Type: Bug
  Components: stacks
Affects Versions: 2.5.2
Reporter: Arpit Gupta
Assignee: Sumit Mohanty
Priority: Critical
 Fix For: 2.5.2


{code}
09 Aug 2017 17:38:17,151 ERROR [alert-event-bus-1] 
AmbariJpaLocalTxnInterceptor:180 - [DETAILED ERROR] Rollback reason:
Local Exception Stack:
Exception [EclipseLink-4002] (Eclipse Persistence Services - 
2.6.2.v20151217-774c696): org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: 
com.mysql.jdbc.exceptions.jdbc4.MySQLIntegrityConstraintViolationException: 
Column 'alert_state' cannot be null
Error Code: 1048
Call: INSERT INTO alert_history (alert_id, alert_instance, alert_label, 
alert_state, alert_text, alert_timestamp, cluster_id, component_name, 
host_name, service_name, alert_definition_id) VALUES (?, ?, ?, ?, ?, ?, ?, ?, 
?, ?, ?)
bind => [11 parameters bound]
Query: InsertObjectQuery(AlertCurrentEntity{alertId=1, 
name=ambari_agent_disk_usage, state=null, latestTimestamp=1502300296216})
at 
org.eclipse.persistence.exceptions.DatabaseException.sqlException(DatabaseException.java:331)
at 
org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.executeDirectNoSelect(DatabaseAccessor.java:902)
at 
org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.executeNoSelect(DatabaseAccessor.java:964)
at 
org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.basicExecuteCall(DatabaseAccessor.java:633)
at 
org.eclipse.persistence.internal.databaseaccess.ParameterizedSQLBatchWritingMechanism.executeBatch(ParameterizedSQLBatchWritingMechanism.java:149)
at 
org.eclipse.persistence.internal.databaseaccess.ParameterizedSQLBatchWritingMechanism.executeBatchedStatements(ParameterizedSQLBatchWritingMechanism.java:134)
at 
org.eclipse.persistence.internal.databaseaccess.ParameterizedSQLBatchWritingMechanism.appendCall(ParameterizedSQLBatchWritingMechanism.java:82)
at 
org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.basicExecuteCall(DatabaseAccessor.java:605)
at 
org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.executeCall(DatabaseAccessor.java:560)
at 
org.eclipse.persistence.internal.sessions.AbstractSession.basicExecuteCall(AbstractSession.java:2055)
at 
org.eclipse.persistence.sessions.server.ClientSession.executeCall(ClientSession.java:306)
at 
org.eclipse.persistence.internal.queries.DatasourceCallQueryMechanism.executeCall(DatasourceCallQueryMechanism.java:242)
at 
org.eclipse.persistence.internal.queries.DatasourceCallQueryMechanism.executeCall(DatasourceCallQueryMechanism.java:228)
at 
org.eclipse.persistence.internal.queries.DatasourceCallQueryMechanism.insertObject(DatasourceCallQueryMechanism.java:377)
at 
org.eclipse.persistence.internal.queries.StatementQueryMechanism.insertObject(StatementQueryMechanism.java:165)
at 
org.eclipse.persistence.internal.queries.StatementQueryMechanism.insertObject(StatementQueryMechanism.java:180)
at 
org.eclipse.persistence.internal.queries.DatabaseQueryMechanism.insertObjectForWrite(DatabaseQueryMechanism.java:489)
at 
org.eclipse.persistence.queries.InsertObjectQuery.executeCommit(InsertObjectQuery.java:80)
at 
org.eclipse.persistence.queries.InsertObjectQuery.executeCommitWithChangeSet(InsertObjectQuery.java:90)
at 
org.eclipse.persistence.internal.queries.DatabaseQueryMechanism.executeWriteWithChangeSet(DatabaseQueryMechanism.java:301)
at 
org.eclipse.persistence.queries.WriteObjectQuery.executeDatabaseQuery(WriteObjectQuery.java:58)
at 
org.eclipse.persistence.queries.DatabaseQuery.execute(DatabaseQuery.java:904)
at 
org.eclipse.persistence.queries.DatabaseQuery.executeInUnitOfWork(DatabaseQuery.java:803)
at 
org.eclipse.persistence.queries.ObjectLevelModifyQuery.executeInUnitOfWorkObjectLevelModifyQuery(ObjectLevelModifyQuery.java:108)
at 
org.eclipse.persistence.queries.ObjectLevelModifyQuery.executeInUnitOfWork(ObjectLevelModifyQuery.java:85)
at 
org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.internalExecuteQuery(UnitOfWorkImpl.java:2896)
at 
org.eclipse.persistence.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:1857)
at 
org.eclipse.persistence.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:1839)
at 
org.eclipse.persistence.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:1790)
at 

[jira] [Updated] (AMBARI-21471) ATS going down due to missing org.apache.spark.deploy.history.yarn.plugin.SparkATSPlugin

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty updated AMBARI-21471:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> ATS going down due to missing 
> org.apache.spark.deploy.history.yarn.plugin.SparkATSPlugin
> 
>
> Key: AMBARI-21471
> URL: https://issues.apache.org/jira/browse/AMBARI-21471
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.5.2
>Reporter: Sumit Mohanty
>Assignee: Sumit Mohanty
> Fix For: 2.5.2
>
> Attachments: AMBARI-21471.patch
>
>
> ATS is going down with
> {code}
> 2017-07-12 02:48:01,542 FATAL 
> applicationhistoryservice.ApplicationHistoryServer 
> (ApplicationHistoryServer.java:launchAppHistoryServer(177)) - Error starting 
> ApplicationHistoryServer
> java.lang.RuntimeException: No class defined for 
> org.apache.spark.deploy.history.yarn.plugin.SparkATSPlugin
> at 
> org.apache.hadoop.yarn.server.timeline.EntityGroupFSTimelineStore.loadPlugIns(EntityGroupFSTimelineStore.java:256)
> at 
> org.apache.hadoop.yarn.server.timeline.EntityGroupFSTimelineStore.serviceInit(EntityGroupFSTimelineStore.java:196)
> at 
> org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
> at 
> org.apache.hadoop.service.CompositeService.serviceInit(CompositeService.java:107)
> at 
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.serviceInit(ApplicationHistoryServer.java:111)
> at 
> org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
> at 
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.launchAppHistoryServer(ApplicationHistoryServer.java:174)
> at 
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.main(ApplicationHistoryServer.java:184)
> Caused by: java.lang.ClassNotFoundException: 
> org.apache.spark.deploy.history.yarn.plugin.SparkATSPlugin
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:335)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at 
> org.apache.hadoop.util.ApplicationClassLoader.loadClass(ApplicationClassLoader.java:197)
> at 
> org.apache.hadoop.util.ApplicationClassLoader.loadClass(ApplicationClassLoader.java:165)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:348)
> at 
> org.apache.hadoop.yarn.server.timeline.EntityGroupFSTimelineStore.loadPlugIns(EntityGroupFSTimelineStore.java:243)
> ... 7 more
> 2017-07-12 02:48:01,544 INFO  util.ExitUtil (ExitUtil.java:terminate(124)) - 
> Exiting with status -1
> 2017-07-12 02:48:01,551 INFO  
> applicationhistoryservice.ApplicationHistoryServer (LogAdapter.java:info(45)) 
> - SHUTDOWN_MSG:
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-21707) Update stack_tools and stack_features in HDF mpack to support Ambari-2.5.2 changes

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty updated AMBARI-21707:
---
Reporter: Arpit Gupta  (was: Madhuvanthi Radhakrishnan)

> Update stack_tools and stack_features in HDF mpack to support Ambari-2.5.2 
> changes
> --
>
> Key: AMBARI-21707
> URL: https://issues.apache.org/jira/browse/AMBARI-21707
> Project: Ambari
>  Issue Type: Bug
>Reporter: Arpit Gupta
>Assignee: Madhuvanthi Radhakrishnan
> Fix For: 2.5.2
>
>
> Refer : https://issues.apache.org/jira/browse/AMBARI-21430
> Changes are required in the HDF stack definition so that Ambari is able to 
> parse the stack_features and tools correctly.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-21707) Update stack_tools and stack_features in HDF mpack to support Ambari-2.5.2 changes

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty updated AMBARI-21707:
---
Fix Version/s: 2.5.2

> Update stack_tools and stack_features in HDF mpack to support Ambari-2.5.2 
> changes
> --
>
> Key: AMBARI-21707
> URL: https://issues.apache.org/jira/browse/AMBARI-21707
> Project: Ambari
>  Issue Type: Bug
>Reporter: Arpit Gupta
>Assignee: Madhuvanthi Radhakrishnan
> Fix For: 2.5.2
>
>
> Refer : https://issues.apache.org/jira/browse/AMBARI-21430
> Changes are required in the HDF stack definition so that Ambari is able to 
> parse the stack_features and tools correctly.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-21707) Update stack_tools and stack_features in HDF mpack to support Ambari-2.5.2 changes

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty updated AMBARI-21707:
---
Priority: Critical  (was: Major)

> Update stack_tools and stack_features in HDF mpack to support Ambari-2.5.2 
> changes
> --
>
> Key: AMBARI-21707
> URL: https://issues.apache.org/jira/browse/AMBARI-21707
> Project: Ambari
>  Issue Type: Bug
>Reporter: Arpit Gupta
>Assignee: Madhuvanthi Radhakrishnan
>Priority: Critical
> Fix For: 2.5.2
>
>
> Refer : https://issues.apache.org/jira/browse/AMBARI-21430
> Changes are required in the HDF stack definition so that Ambari is able to 
> parse the stack_features and tools correctly.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (AMBARI-21664) HDFS namenode rpc and connection load metrics are not showing

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty commented on AMBARI-21664:


LGTM, +1 for 
https://issues.apache.org/jira/secure/attachment/12881320/AMBARI-21664-1.patch

> HDFS namenode rpc and connection load metrics are not showing
> -
>
> Key: AMBARI-21664
> URL: https://issues.apache.org/jira/browse/AMBARI-21664
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics
>Affects Versions: 2.5.2
> Environment: CentOS 7, IOP 4.2 upgrade to Ambari 2.5.2
>Reporter: Eric Yang
>Assignee: Siddharth Wagle
> Fix For: 2.5.2
>
> Attachments: AMBARI-21664-1.patch, AMBARI-21664.patch, 
> AMBARI-21664_trunk.patch
>
>
> After upgrading from IOP 4.2 to HDP 2.6 with Ambari 2.5.2, there are two 
> metrics widget don't show the right results.
> Namenode RPC and Namenode Connection Load graph don't show any data.  This 
> might be caused by different implementation to fetch metrics data for those 
> two graphs in IOP.  Check if there is a way to bridge the gap by updating 
> widget information or document this and ask user to remove the widget.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-21696) Spark thrift service was alerting for connectivity for all newly created clusters

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty updated AMBARI-21696:
---
Attachment: AMBARI-21696.patch

> Spark thrift service was alerting for connectivity for all newly created 
> clusters
> -
>
> Key: AMBARI-21696
> URL: https://issues.apache.org/jira/browse/AMBARI-21696
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Mingjie Tang
>Assignee: Mingjie Tang
> Fix For: 2.5.2
>
> Attachments: AMBARI-21696.patch
>
>
> Error: Could not open client transport with JDBC Uri: 
> jdbc:hive2://hn0-salqa0.lv5aupozrfhezhozcxr3xjcwqe.dx.internal.cloudapp.net:10016/default:
>  java.net.ConnectException: Connection refused (Connection refused) 
> (state=08S01,code=0)
> This is belong to the alert service does not change the port number based on 
> model. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (AMBARI-21696) Spark thrift service was alerting for connectivity for all newly created clusters

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty reassigned AMBARI-21696:
--

Assignee: Mingjie Tang

> Spark thrift service was alerting for connectivity for all newly created 
> clusters
> -
>
> Key: AMBARI-21696
> URL: https://issues.apache.org/jira/browse/AMBARI-21696
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Mingjie Tang
>Assignee: Mingjie Tang
> Fix For: 2.5.2
>
>
> Error: Could not open client transport with JDBC Uri: 
> jdbc:hive2://hn0-salqa0.lv5aupozrfhezhozcxr3xjcwqe.dx.internal.cloudapp.net:10016/default:
>  java.net.ConnectException: Connection refused (Connection refused) 
> (state=08S01,code=0)
> This is belong to the alert service does not change the port number based on 
> model. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-21696) Spark thrift service was alerting for connectivity for all newly created clusters

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty updated AMBARI-21696:
---
Fix Version/s: 2.5.2

> Spark thrift service was alerting for connectivity for all newly created 
> clusters
> -
>
> Key: AMBARI-21696
> URL: https://issues.apache.org/jira/browse/AMBARI-21696
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Mingjie Tang
>Assignee: Mingjie Tang
> Fix For: 2.5.2
>
>
> Error: Could not open client transport with JDBC Uri: 
> jdbc:hive2://hn0-salqa0.lv5aupozrfhezhozcxr3xjcwqe.dx.internal.cloudapp.net:10016/default:
>  java.net.ConnectException: Connection refused (Connection refused) 
> (state=08S01,code=0)
> This is belong to the alert service does not change the port number based on 
> model. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-21663) Livy2 should probably use the same keytab as Livy

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty updated AMBARI-21663:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

Committed to trunk and branch-2.5

> Livy2 should probably use the same keytab as Livy
> -
>
> Key: AMBARI-21663
> URL: https://issues.apache.org/jira/browse/AMBARI-21663
> Project: Ambari
>  Issue Type: Bug
>Reporter: Bikas Saha
>Assignee: Bikas Saha
>Priority: Critical
> Fix For: 2.5.2
>
> Attachments: AMBARI-21663.1.patch
>
>
> Noticed that when Livy2 server is started on the same node as livy server 
> then it fails to install as it complains that it cannot create 
> livy2.service.keytab.
> Perhaps creating that keytab with the same principal as livy.service.keytab 
> is failing.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-21663) Livy2 should probably use the same keytab as Livy

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty updated AMBARI-21663:
---
Fix Version/s: 2.5.2

> Livy2 should probably use the same keytab as Livy
> -
>
> Key: AMBARI-21663
> URL: https://issues.apache.org/jira/browse/AMBARI-21663
> Project: Ambari
>  Issue Type: Bug
>Reporter: Bikas Saha
>Assignee: Bikas Saha
>Priority: Critical
> Fix For: 2.5.2
>
> Attachments: AMBARI-21663.1.patch
>
>
> Noticed that when Livy2 server is started on the same node as livy server 
> then it fails to install as it complains that it cannot create 
> livy2.service.keytab.
> Perhaps creating that keytab with the same principal as livy.service.keytab 
> is failing.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (AMBARI-21663) Livy2 should probably use the same keytab as Livy

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty commented on AMBARI-21663:


Similar to AMBARI-20140. +1.

> Livy2 should probably use the same keytab as Livy
> -
>
> Key: AMBARI-21663
> URL: https://issues.apache.org/jira/browse/AMBARI-21663
> Project: Ambari
>  Issue Type: Bug
>Reporter: Bikas Saha
>Assignee: Bikas Saha
>Priority: Critical
> Fix For: 2.5.2
>
> Attachments: AMBARI-21663.1.patch
>
>
> Noticed that when Livy2 server is started on the same node as livy server 
> then it fails to install as it complains that it cannot create 
> livy2.service.keytab.
> Perhaps creating that keytab with the same principal as livy.service.keytab 
> is failing.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-21637) Maintain default hive.execution.engine as MR for IOP upgrade

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty updated AMBARI-21637:
---
Fix Version/s: 2.5.2

> Maintain default hive.execution.engine as MR for IOP upgrade
> 
>
> Key: AMBARI-21637
> URL: https://issues.apache.org/jira/browse/AMBARI-21637
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-upgrade
>Reporter: Aswathy Chellammal Sreekumar
> Fix For: 2.5.2
>
>
> During IOP upgrade to HDP hive.execution.engine is being set to tez which 
> prevents hive cli from coming with below error
> {noformat}
> Exception in thread "main" java.lang.RuntimeException: java.io.IOException: 
> Previous writer likely failed to write 
> hdfs://nat-r6-macs-webhcat-4.openstacklocal:8020/tmp/hive/hrt_qa/_tez_session_dir/af63f8a7--4252-bf22-4fffddae4680/hbase-client.jar.
>  Failing because I am unlikely to write too.
>   at 
> org.apache.hadoop.hive.ql.session.SessionState.start(SessionState.java:560)
>   at org.apache.hadoop.hive.cli.CliDriver.run(CliDriver.java:681)
>   at org.apache.hadoop.hive.cli.CliDriver.main(CliDriver.java:625)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at org.apache.hadoop.util.RunJar.run(RunJar.java:233)
>   at org.apache.hadoop.util.RunJar.main(RunJar.java:148)
> Caused by: java.io.IOException: Previous writer likely failed to write 
> hdfs://nat-r6-macs-webhcat-4.openstacklocal:8020/tmp/hive/hrt_qa/_tez_session_dir/af63f8a7--4252-bf22-4fffddae4680/hbase-client.jar.
>  Failing because I am unlikely to write too.
>   at 
> org.apache.hadoop.hive.ql.exec.tez.DagUtils.localizeResource(DagUtils.java:1002)
>   at 
> org.apache.hadoop.hive.ql.exec.tez.DagUtils.addTempResources(DagUtils.java:882)
>   at 
> org.apache.hadoop.hive.ql.exec.tez.DagUtils.localizeTempFilesFromConf(DagUtils.java:809)
>   at 
> org.apache.hadoop.hive.ql.exec.tez.TezSessionState.refreshLocalResourcesFromConf(TezSessionState.java:258)
>   at 
> org.apache.hadoop.hive.ql.exec.tez.TezSessionState.open(TezSessionState.java:157)
>   at 
> org.apache.hadoop.hive.ql.exec.tez.TezSessionState.open(TezSessionState.java:116)
>   at 
> org.apache.hadoop.hive.ql.session.SessionState.start(SessionState.java:557)
>   ... 8 more
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-21605) Regression : Missing Kerberos configs for Spark2

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty updated AMBARI-21605:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

Committed to trunk and branch-2.5

> Regression : Missing Kerberos configs for Spark2
> 
>
> Key: AMBARI-21605
> URL: https://issues.apache.org/jira/browse/AMBARI-21605
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.5.1
>Reporter: Bikas Saha
>Assignee: Bikas Saha
>Priority: Blocker
> Fix For: 2.5.2
>
> Attachments: AMBARI-21605.1.patch
>
>
> Looks like a couple of typos went into the last release that caused a 
> regression.
> spark-defaults and spark-thrift-sparkconf config files dont exist in the 
> Spark2 stack definition. So the configuration items are missing in the final 
> conf fies.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-21563) Copy Hadoop core-site.xml to Atlas conf when hadoop is configured for LDAP/AD

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty updated AMBARI-21563:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

Committed to trunk and branch-2.5

> Copy Hadoop core-site.xml to Atlas conf when hadoop is configured for LDAP/AD
> -
>
> Key: AMBARI-21563
> URL: https://issues.apache.org/jira/browse/AMBARI-21563
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Vishal Suvagia
>Assignee: Vishal Suvagia
> Fix For: 2.5.2
>
> Attachments: AMBARI-21563-branch-2.5.1.patch, 
> AMBARI-21563-branch-2.5.patch, AMBARI-21563-trunk.1.patch, 
> AMBARI-21563-trunk.patch
>
>
> Atlas use user groups synced in hadoopUGI for authentication and 
> authorization process for LDAP/Kerberos type.
> As core-site.xml was available in HBase conf which is in Atlas classpath and 
> so core.site.xml configs were available. But now as core-site.xml is not 
> available in Hbase conf, to fix this issue hadoop core-site.xml need to be 
> copied to Atlas conf directory by Ambari.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (AMBARI-21583) Hive server configurations not applied to all the nodes for HS2 HA deployment

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty commented on AMBARI-21583:


LGTM, +1

> Hive server configurations not applied to all the nodes for HS2 HA deployment
> -
>
> Key: AMBARI-21583
> URL: https://issues.apache.org/jira/browse/AMBARI-21583
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.3, 2.5.2
>Reporter: Siddharth Wagle
>Assignee: Siddharth Wagle
>Priority: Critical
> Fix For: 2.5.2
>
> Attachments: AMBARI-21583.patch
>
>
> PROBLEM: Can't apply changed configurations to 2nd Hive Server nodes.
> STEPS TO REPRODUCE: 
> 1.Change the content of hive-log4j in ambari.
> 2.restart affected services.
> 3.check configuration file /etc/hive/conf/conf.server/hive-log4j.properties 
> on each HS2 node.
> 4.you will see changed configuration only applies to one node.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-21557) Logging cleanup around reading config properties file

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty updated AMBARI-21557:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

Committed to branch-2.5 and trunk

> Logging cleanup around reading config properties file
> -
>
> Key: AMBARI-21557
> URL: https://issues.apache.org/jira/browse/AMBARI-21557
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0, 2.5.0, 2.5.1
>Reporter: Sumit Mohanty
>Assignee: Sumit Mohanty
> Fix For: 2.5.2
>
> Attachments: AMBARI-21557.patch
>
>
> Logging cleanup around reading config properties file.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-21557) Logging cleanup around reading config properties file

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty updated AMBARI-21557:
---
Status: Patch Available  (was: Open)

> Logging cleanup around reading config properties file
> -
>
> Key: AMBARI-21557
> URL: https://issues.apache.org/jira/browse/AMBARI-21557
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0, 2.5.0, 2.5.1
>Reporter: Sumit Mohanty
>Assignee: Sumit Mohanty
> Fix For: 2.5.2
>
> Attachments: AMBARI-21557.patch
>
>
> Logging cleanup around reading config properties file.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-21557) Logging cleanup around reading config properties file

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty updated AMBARI-21557:
---
Attachment: AMBARI-21557.patch

> Logging cleanup around reading config properties file
> -
>
> Key: AMBARI-21557
> URL: https://issues.apache.org/jira/browse/AMBARI-21557
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0, 2.5.0, 2.5.1
>Reporter: Sumit Mohanty
>Assignee: Sumit Mohanty
> Fix For: 2.5.2
>
> Attachments: AMBARI-21557.patch
>
>
> Logging cleanup around reading config properties file.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (AMBARI-21557) Logging cleanup around reading config properties file

[Sumit Mohanty (JIRA)]

Sumit Mohanty created AMBARI-21557:
--

 Summary: Logging cleanup around reading config properties file
 Key: AMBARI-21557
 URL: https://issues.apache.org/jira/browse/AMBARI-21557
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: 2.4.0, 2.5.0, 2.5.1
Reporter: Sumit Mohanty
Assignee: Sumit Mohanty
 Fix For: 2.5.2


Logging cleanup around reading config properties file.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (AMBARI-21556) Critical alert about Metrics Collector ZooKeeper Server Process due to unsubstituted variable

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty commented on AMBARI-21556:


LGTM, +1

> Critical alert about Metrics Collector ZooKeeper Server Process due to 
> unsubstituted variable
> -
>
> Key: AMBARI-21556
> URL: https://issues.apache.org/jira/browse/AMBARI-21556
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics
>Affects Versions: 2.5.2
>Reporter: Siddharth Wagle
>Assignee: Siddharth Wagle
>Priority: Critical
> Fix For: 2.5.2
>
> Attachments: AMBARI-21556.pach
>
>
> STR:
> * Install BI 4.2 with Ambari 2.2
> * Install BI 4.2 cluster with ZooKeeper, Ambari Metrics
> * Upgrade to Ambari 2.5.2
> Result: _Metrics Collector - ZooKeeper Server Process_ alert goes to 
> _Critical_ status
> {noformat:title=alert response}
> Connection failed: [Errno -2] Name or service not known to 
> {{zookeeper_clientPort}}:61181
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-21544) HiveServer2 fails to start with webhdfs call to create /hdp/apps/..jar files fails with org.apache.hadoop.hdfs.server.namenode.LeaseExpiredException

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty updated AMBARI-21544:
---
Reporter: Dileep Kumar Chiguruvada  (was: Andrew Onischuk)

> HiveServer2 fails to start with webhdfs call to create /hdp/apps/..jar files  
> fails with  org.apache.hadoop.hdfs.server.namenode.LeaseExpiredException
> --
>
> Key: AMBARI-21544
> URL: https://issues.apache.org/jira/browse/AMBARI-21544
> Project: Ambari
>  Issue Type: Bug
>Reporter: Dileep Kumar Chiguruvada
>Assignee: Andrew Onischuk
> Fix For: 2.5.2
>
> Attachments: AMBARI-21544.patch
>
>
> HiveServer2 fails to start with webhdfs call to create /hdp/apps/..jar files
> fails with org.apache.hadoop.hdfs.server.namenode.LeaseExpiredException.
> Seeing this specifically on HA cluster where one instance of HiveServer2 fails
> to start.
> HiveServer2 start error...
> 
> 
> 
> 2017-07-18 05:27:36,795 - NameNode HA states: active_namenodes = 
> [(u'nn2', 'ctr-e134-1499953498516-16356-01-05.hwx.site:20070')], 
> standby_namenodes = [(u'nn1', 
> 'ctr-e134-1499953498516-16356-01-04.hwx.site:20070')], unknown_namenodes 
> = []
> 2017-07-18 05:27:36,797 - call['ambari-sudo.sh su hdfs -l -s /bin/bash -c 
> 'curl -sS -L -w '"'"'%{http_code}'"'"' -X GET --negotiate -u : 
> '"'"'http://ctr-e134-1499953498516-16356-01-05.hwx.site:20070/webhdfs/v1/hdp/apps/2.6.3.0-61/mapreduce/hadoop-streaming.jar?op=GETFILESTATUS'"'"'
>  1>/tmp/tmpvtBOI9 2>/tmp/tmpMbcTp1''] {'logoutput': None, 'quiet': False}
> 2017-07-18 05:27:36,885 - call returned (0, '')
> 2017-07-18 05:27:36,886 - Creating new file 
> /hdp/apps/2.6.3.0-61/mapreduce/hadoop-streaming.jar in DFS
> 2017-07-18 05:27:36,887 - call['ambari-sudo.sh su hdfs -l -s /bin/bash -c 
> 'curl -sS -L -w '"'"'%{http_code}'"'"' -X PUT --data-binary 
> @/usr/hdp/2.6.3.0-61/hadoop-mapreduce/hadoop-streaming.jar -H 
> '"'"'Content-Type: application/octet-stream'"'"' --negotiate -u : 
> '"'"'http://ctr-e134-1499953498516-16356-01-05.hwx.site:20070/webhdfs/v1/hdp/apps/2.6.3.0-61/mapreduce/hadoop-streaming.jar?op=CREATE=True=444'"'"'
>  1>/tmp/tmpqYkC_P 2>/tmp/tmpT30u8x''] {'logoutput': None, 'quiet': False}
> 2017-07-18 05:27:37,135 - call returned (0, '')
> 
> self._create_file(self.main_resource.resource.target, 
> source=self.main_resource.resource.source, mode=self.mode)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
>  line 423, in _create_file
> self.util.run_command(target, 'CREATE', method='PUT', overwrite=True, 
> assertable_result=False, file_to_put=source, **kwargs)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
>  line 204, in run_command
> raise Fail(err_msg)
> resource_management.core.exceptions.Fail: Execution of 'curl -sS -L -w 
> '%{http_code}' -X PUT --data-binary 
> @/usr/hdp/2.6.3.0-61/hadoop-mapreduce/hadoop-streaming.jar -H 'Content-Type: 
> application/octet-stream' --negotiate -u : 
> 'http://ctr-e134-1499953498516-16356-01-05.hwx.site:20070/webhdfs/v1/hdp/apps/2.6.3.0-61/mapreduce/hadoop-streaming.jar?op=CREATE=True=444''
>  returned status_code=403. 
> {
>   "RemoteException": {
> "exception": "LeaseExpiredException", 
> "javaClassName": 
> "org.apache.hadoop.hdfs.server.namenode.LeaseExpiredException", 
> "message": "No lease on 
> /hdp/apps/2.6.3.0-61/mapreduce/hadoop-streaming.jar (inode 16566): File does 
> not exist. Holder DFSClient_NONMAPREDUCE_1130121686_152 does not have any 
> open files.\n\tat 
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.checkLease(FSNamesystem.java:3660)\n\tat
>  
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.analyzeFileState(FSNamesystem.java:3463)\n\tat
>  
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getNewBlockTargets(FSNamesystem.java:3301)\n\tat
>  
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getAdditionalBlock(FSNamesystem.java:3261)\n\tat
>  
> org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.addBlock(NameNodeRpcServer.java:850)\n\tat
>  
> org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolServerSideTranslatorPB.addBlock(ClientNamenodeProtocolServerSideTranslatorPB.java:503)\n\tat
>  
> org.apache.hadoop.hdfs.protocol.proto.ClientNamenodeProtocolProtos$ClientNamenodeProtocol$2.callBlockingMethod(ClientNamenodeProtocolProtos.java)\n\tat
>  
> org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:640)\n\tat
>  org.apache.hadoop.ipc.RPC$Server.call(RPC.java:982)\n\tat 
> 

[jira] [Updated] (AMBARI-21539) Resource Manager fails to restart properly during an IOP to HDP upgrade

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty updated AMBARI-21539:
---
Priority: Critical  (was: Major)

> Resource Manager fails to restart properly during an IOP to HDP upgrade
> ---
>
> Key: AMBARI-21539
> URL: https://issues.apache.org/jira/browse/AMBARI-21539
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Tim Thorpe
>Assignee: Attila Magyar
>Priority: Critical
> Fix For: 2.5.2
>
>
> 2017-07-20 06:19:28,250 INFO  service.AbstractService 
> (AbstractService.java:noteFailure(272)) - Service 
> org.apache.hadoop.yarn.server.resourcemanager.recovery.RMStateStore failed in 
> state STARTED; cause: org.apache.zookeeper.KeeperException$NoAuthException: 
> KeeperErrorCode = NoAuth for /rmstore/ZKRMStateRoot
> org.apache.zookeeper.KeeperException$NoAuthException: KeeperErrorCode = 
> NoAuth for /rmstore/ZKRMStateRoot
>   at org.apache.zookeeper.KeeperException.create(KeeperException.java:113)
>   at org.apache.zookeeper.KeeperException.create(KeeperException.java:51)
>   at org.apache.zookeeper.ZooKeeper.setACL(ZooKeeper.java:1399)
>   at 
> org.apache.hadoop.yarn.server.resourcemanager.recovery.ZKRMStateStore$3.run(ZKRMStateStore.java:372)
> Workaround:
> /usr/hdp/current/zookeeper-server/bin/zkCli.sh -server 127.0.0.1:2181
> rmr /rmstore
> This workaround fails in a kerberized environment with this error:
> Authentication is not valid : /rmstore/ZKRMStateRoot



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-21539) Resource Manager fails to restart properly during an IOP to HDP upgrade

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty updated AMBARI-21539:
---
Fix Version/s: 2.5.2

> Resource Manager fails to restart properly during an IOP to HDP upgrade
> ---
>
> Key: AMBARI-21539
> URL: https://issues.apache.org/jira/browse/AMBARI-21539
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Tim Thorpe
>Assignee: Attila Magyar
> Fix For: 2.5.2
>
>
> 2017-07-20 06:19:28,250 INFO  service.AbstractService 
> (AbstractService.java:noteFailure(272)) - Service 
> org.apache.hadoop.yarn.server.resourcemanager.recovery.RMStateStore failed in 
> state STARTED; cause: org.apache.zookeeper.KeeperException$NoAuthException: 
> KeeperErrorCode = NoAuth for /rmstore/ZKRMStateRoot
> org.apache.zookeeper.KeeperException$NoAuthException: KeeperErrorCode = 
> NoAuth for /rmstore/ZKRMStateRoot
>   at org.apache.zookeeper.KeeperException.create(KeeperException.java:113)
>   at org.apache.zookeeper.KeeperException.create(KeeperException.java:51)
>   at org.apache.zookeeper.ZooKeeper.setACL(ZooKeeper.java:1399)
>   at 
> org.apache.hadoop.yarn.server.resourcemanager.recovery.ZKRMStateStore$3.run(ZKRMStateStore.java:372)
> Workaround:
> /usr/hdp/current/zookeeper-server/bin/zkCli.sh -server 127.0.0.1:2181
> rmr /rmstore
> This workaround fails in a kerberized environment with this error:
> Authentication is not valid : /rmstore/ZKRMStateRoot



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (AMBARI-21539) Resource Manager fails to restart properly during an IOP to HDP upgrade

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty reassigned AMBARI-21539:
--

Assignee: Attila Magyar

> Resource Manager fails to restart properly during an IOP to HDP upgrade
> ---
>
> Key: AMBARI-21539
> URL: https://issues.apache.org/jira/browse/AMBARI-21539
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Tim Thorpe
>Assignee: Attila Magyar
> Fix For: 2.5.2
>
>
> 2017-07-20 06:19:28,250 INFO  service.AbstractService 
> (AbstractService.java:noteFailure(272)) - Service 
> org.apache.hadoop.yarn.server.resourcemanager.recovery.RMStateStore failed in 
> state STARTED; cause: org.apache.zookeeper.KeeperException$NoAuthException: 
> KeeperErrorCode = NoAuth for /rmstore/ZKRMStateRoot
> org.apache.zookeeper.KeeperException$NoAuthException: KeeperErrorCode = 
> NoAuth for /rmstore/ZKRMStateRoot
>   at org.apache.zookeeper.KeeperException.create(KeeperException.java:113)
>   at org.apache.zookeeper.KeeperException.create(KeeperException.java:51)
>   at org.apache.zookeeper.ZooKeeper.setACL(ZooKeeper.java:1399)
>   at 
> org.apache.hadoop.yarn.server.resourcemanager.recovery.ZKRMStateStore$3.run(ZKRMStateStore.java:372)
> Workaround:
> /usr/hdp/current/zookeeper-server/bin/zkCli.sh -server 127.0.0.1:2181
> rmr /rmstore
> This workaround fails in a kerberized environment with this error:
> Authentication is not valid : /rmstore/ZKRMStateRoot



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-21512) Stack Advisor reported an error: KeyError: 'stack_name' while Issued INSTALLED as new state for NODEMANAGER

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty updated AMBARI-21512:
---
Attachment: AMBARI-21512.patch

> Stack Advisor reported an error: KeyError: 'stack_name' while Issued 
> INSTALLED as new state for NODEMANAGER
> ---
>
> Key: AMBARI-21512
> URL: https://issues.apache.org/jira/browse/AMBARI-21512
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.5.2
>Reporter: Srikanth Janardhan
>Assignee: Sumit Mohanty
> Fix For: 2.5.2
>
> Attachments: AMBARI-21512.patch
>
>
> While In build #139, performing an [AUTHORIZED, HOST_ADD_DELETE_COMPONENTS] 
> operation in RBAC for NODEMANAGER failed for AMBARI_ADMINISTRATOR role.
> Test Logs:
> {code}
> 2017-07-18 03:12:42,062|INFO|MainThread|machine.py:159 - 
> run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|INFO: Requesting put on 
> Request path : 
> http://172.27.22.82:8080/api/v1/clusters/cl1/hosts/ctr-e134-1499953498516-15485-01-03.hwx.site/host_components/NODEMANAGER
> 2017-07-18 03:12:43,053|INFO|MainThread|machine.py:159 - 
> run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|Jul 18, 2017 3:12:43 AM 
> com.hwx.utils.logging.LogManager log
> 2017-07-18 03:12:43,053|INFO|MainThread|machine.py:159 - 
> run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|INFO: Response body : {
> 2017-07-18 03:12:43,053|INFO|MainThread|machine.py:159 - 
> run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|"href" : 
> "http://172.27.22.82:8080/api/v1/clusters/cl1/requests/44;,
> 2017-07-18 03:12:43,053|INFO|MainThread|machine.py:159 - 
> run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|"Requests" : {
> 2017-07-18 03:12:43,053|INFO|MainThread|machine.py:159 - 
> run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|"id" : 44,
> 2017-07-18 03:12:43,053|INFO|MainThread|machine.py:159 - 
> run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|"status" : "Accepted"
> 2017-07-18 03:12:43,054|INFO|MainThread|machine.py:159 - 
> run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|}
> 2017-07-18 03:12:43,054|INFO|MainThread|machine.py:159 - 
> run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|}
> 2017-07-18 03:12:43,054|INFO|MainThread|machine.py:159 - 
> run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|Jul 18, 2017 3:12:43 AM 
> com.hwx.utils.logging.LogManager log
> 2017-07-18 03:12:43,054|INFO|MainThread|machine.py:159 - 
> run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|INFO: Response body : {
> 2017-07-18 03:12:43,054|INFO|MainThread|machine.py:159 - 
> run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|"href" : 
> "http://172.27.22.82:8080/api/v1/clusters/cl1/requests/44;,
> 2017-07-18 03:12:43,054|INFO|MainThread|machine.py:159 - 
> run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|"Requests" : {
> 2017-07-18 03:12:43,054|INFO|MainThread|machine.py:159 - 
> run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|"id" : 44,
> 2017-07-18 03:12:43,054|INFO|MainThread|machine.py:159 - 
> run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|"status" : "Accepted"
> 2017-07-18 03:12:43,054|INFO|MainThread|machine.py:159 - 
> run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|}
> 2017-07-18 03:12:43,054|INFO|MainThread|machine.py:159 - 
> run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|}
> 2017-07-18 03:12:43,055|INFO|MainThread|machine.py:159 - 
> run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|Jul 18, 2017 3:12:43 AM 
> com.hwx.utils.logging.LogManager log
> 2017-07-18 03:12:43,055|INFO|MainThread|machine.py:159 - 
> run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|INFO: Service URL : 
> http://172.27.22.82:8080/api/v1/clusters/cl1/requests/44
> 2017-07-18 03:13:13,099|INFO|MainThread|machine.py:159 - 
> run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|Jul 18, 2017 3:13:13 AM 
> com.hwx.utils.logging.LogManager log
> 2017-07-18 03:13:13,099|INFO|MainThread|machine.py:159 - 
> run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|INFO: Wait for 30 seconds. 
> Total Wait Time : 30 seconds
> 2017-07-18 03:13:43,390|INFO|MainThread|machine.py:159 - 
> run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|Jul 18, 2017 3:13:43 AM 
> com.hwx.utils.logging.LogManager log
> 2017-07-18 03:13:43,390|INFO|MainThread|machine.py:159 - 
> run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|INFO: Wait for 30 seconds. 
> Total Wait Time : 60 seconds
> 2017-07-18 03:13:43,521|INFO|MainThread|machine.py:159 - 
> run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|Jul 18, 2017 3:13:43 AM 
> com.hwx.utils.logging.LogManager log
> 2017-07-18 03:13:43,521|INFO|MainThread|machine.py:159 - 
> run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|SEVERE: Failed task while 
> Issued INSTALLED as new state for NODEMANAGER
> 2017-07-18 03:13:43,655|INFO|MainThread|machine.py:159 - 
> 

[jira] [Updated] (AMBARI-21512) Stack Advisor reported an error: KeyError: 'stack_name' while Issued INSTALLED as new state for NODEMANAGER

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty updated AMBARI-21512:
---
Status: Patch Available  (was: Open)

> Stack Advisor reported an error: KeyError: 'stack_name' while Issued 
> INSTALLED as new state for NODEMANAGER
> ---
>
> Key: AMBARI-21512
> URL: https://issues.apache.org/jira/browse/AMBARI-21512
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.5.2
>Reporter: Srikanth Janardhan
>Assignee: Sumit Mohanty
> Fix For: 2.5.2
>
> Attachments: AMBARI-21512.patch
>
>
> While In build #139, performing an [AUTHORIZED, HOST_ADD_DELETE_COMPONENTS] 
> operation in RBAC for NODEMANAGER failed for AMBARI_ADMINISTRATOR role.
> Test Logs:
> {code}
> 2017-07-18 03:12:42,062|INFO|MainThread|machine.py:159 - 
> run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|INFO: Requesting put on 
> Request path : 
> http://172.27.22.82:8080/api/v1/clusters/cl1/hosts/ctr-e134-1499953498516-15485-01-03.hwx.site/host_components/NODEMANAGER
> 2017-07-18 03:12:43,053|INFO|MainThread|machine.py:159 - 
> run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|Jul 18, 2017 3:12:43 AM 
> com.hwx.utils.logging.LogManager log
> 2017-07-18 03:12:43,053|INFO|MainThread|machine.py:159 - 
> run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|INFO: Response body : {
> 2017-07-18 03:12:43,053|INFO|MainThread|machine.py:159 - 
> run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|"href" : 
> "http://172.27.22.82:8080/api/v1/clusters/cl1/requests/44;,
> 2017-07-18 03:12:43,053|INFO|MainThread|machine.py:159 - 
> run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|"Requests" : {
> 2017-07-18 03:12:43,053|INFO|MainThread|machine.py:159 - 
> run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|"id" : 44,
> 2017-07-18 03:12:43,053|INFO|MainThread|machine.py:159 - 
> run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|"status" : "Accepted"
> 2017-07-18 03:12:43,054|INFO|MainThread|machine.py:159 - 
> run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|}
> 2017-07-18 03:12:43,054|INFO|MainThread|machine.py:159 - 
> run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|}
> 2017-07-18 03:12:43,054|INFO|MainThread|machine.py:159 - 
> run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|Jul 18, 2017 3:12:43 AM 
> com.hwx.utils.logging.LogManager log
> 2017-07-18 03:12:43,054|INFO|MainThread|machine.py:159 - 
> run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|INFO: Response body : {
> 2017-07-18 03:12:43,054|INFO|MainThread|machine.py:159 - 
> run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|"href" : 
> "http://172.27.22.82:8080/api/v1/clusters/cl1/requests/44;,
> 2017-07-18 03:12:43,054|INFO|MainThread|machine.py:159 - 
> run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|"Requests" : {
> 2017-07-18 03:12:43,054|INFO|MainThread|machine.py:159 - 
> run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|"id" : 44,
> 2017-07-18 03:12:43,054|INFO|MainThread|machine.py:159 - 
> run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|"status" : "Accepted"
> 2017-07-18 03:12:43,054|INFO|MainThread|machine.py:159 - 
> run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|}
> 2017-07-18 03:12:43,054|INFO|MainThread|machine.py:159 - 
> run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|}
> 2017-07-18 03:12:43,055|INFO|MainThread|machine.py:159 - 
> run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|Jul 18, 2017 3:12:43 AM 
> com.hwx.utils.logging.LogManager log
> 2017-07-18 03:12:43,055|INFO|MainThread|machine.py:159 - 
> run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|INFO: Service URL : 
> http://172.27.22.82:8080/api/v1/clusters/cl1/requests/44
> 2017-07-18 03:13:13,099|INFO|MainThread|machine.py:159 - 
> run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|Jul 18, 2017 3:13:13 AM 
> com.hwx.utils.logging.LogManager log
> 2017-07-18 03:13:13,099|INFO|MainThread|machine.py:159 - 
> run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|INFO: Wait for 30 seconds. 
> Total Wait Time : 30 seconds
> 2017-07-18 03:13:43,390|INFO|MainThread|machine.py:159 - 
> run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|Jul 18, 2017 3:13:43 AM 
> com.hwx.utils.logging.LogManager log
> 2017-07-18 03:13:43,390|INFO|MainThread|machine.py:159 - 
> run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|INFO: Wait for 30 seconds. 
> Total Wait Time : 60 seconds
> 2017-07-18 03:13:43,521|INFO|MainThread|machine.py:159 - 
> run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|Jul 18, 2017 3:13:43 AM 
> com.hwx.utils.logging.LogManager log
> 2017-07-18 03:13:43,521|INFO|MainThread|machine.py:159 - 
> run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|SEVERE: Failed task while 
> Issued INSTALLED as new state for NODEMANAGER
> 2017-07-18 03:13:43,655|INFO|MainThread|machine.py:159 - 
> 

[jira] [Updated] (AMBARI-21512) Stack Advisor reported an error: KeyError: 'stack_name' while Issued INSTALLED as new state for NODEMANAGER

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty updated AMBARI-21512:
---
Reporter: Srikanth Janardhan  (was: Sumit Mohanty)

> Stack Advisor reported an error: KeyError: 'stack_name' while Issued 
> INSTALLED as new state for NODEMANAGER
> ---
>
> Key: AMBARI-21512
> URL: https://issues.apache.org/jira/browse/AMBARI-21512
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.5.2
>Reporter: Srikanth Janardhan
>Assignee: Sumit Mohanty
> Fix For: 2.5.2
>
>
> While In build #139, performing an [AUTHORIZED, HOST_ADD_DELETE_COMPONENTS] 
> operation in RBAC for NODEMANAGER failed for AMBARI_ADMINISTRATOR role.
> Test Logs:
> {code}
> 2017-07-18 03:12:42,062|INFO|MainThread|machine.py:159 - 
> run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|INFO: Requesting put on 
> Request path : 
> http://172.27.22.82:8080/api/v1/clusters/cl1/hosts/ctr-e134-1499953498516-15485-01-03.hwx.site/host_components/NODEMANAGER
> 2017-07-18 03:12:43,053|INFO|MainThread|machine.py:159 - 
> run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|Jul 18, 2017 3:12:43 AM 
> com.hwx.utils.logging.LogManager log
> 2017-07-18 03:12:43,053|INFO|MainThread|machine.py:159 - 
> run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|INFO: Response body : {
> 2017-07-18 03:12:43,053|INFO|MainThread|machine.py:159 - 
> run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|"href" : 
> "http://172.27.22.82:8080/api/v1/clusters/cl1/requests/44;,
> 2017-07-18 03:12:43,053|INFO|MainThread|machine.py:159 - 
> run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|"Requests" : {
> 2017-07-18 03:12:43,053|INFO|MainThread|machine.py:159 - 
> run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|"id" : 44,
> 2017-07-18 03:12:43,053|INFO|MainThread|machine.py:159 - 
> run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|"status" : "Accepted"
> 2017-07-18 03:12:43,054|INFO|MainThread|machine.py:159 - 
> run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|}
> 2017-07-18 03:12:43,054|INFO|MainThread|machine.py:159 - 
> run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|}
> 2017-07-18 03:12:43,054|INFO|MainThread|machine.py:159 - 
> run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|Jul 18, 2017 3:12:43 AM 
> com.hwx.utils.logging.LogManager log
> 2017-07-18 03:12:43,054|INFO|MainThread|machine.py:159 - 
> run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|INFO: Response body : {
> 2017-07-18 03:12:43,054|INFO|MainThread|machine.py:159 - 
> run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|"href" : 
> "http://172.27.22.82:8080/api/v1/clusters/cl1/requests/44;,
> 2017-07-18 03:12:43,054|INFO|MainThread|machine.py:159 - 
> run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|"Requests" : {
> 2017-07-18 03:12:43,054|INFO|MainThread|machine.py:159 - 
> run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|"id" : 44,
> 2017-07-18 03:12:43,054|INFO|MainThread|machine.py:159 - 
> run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|"status" : "Accepted"
> 2017-07-18 03:12:43,054|INFO|MainThread|machine.py:159 - 
> run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|}
> 2017-07-18 03:12:43,054|INFO|MainThread|machine.py:159 - 
> run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|}
> 2017-07-18 03:12:43,055|INFO|MainThread|machine.py:159 - 
> run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|Jul 18, 2017 3:12:43 AM 
> com.hwx.utils.logging.LogManager log
> 2017-07-18 03:12:43,055|INFO|MainThread|machine.py:159 - 
> run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|INFO: Service URL : 
> http://172.27.22.82:8080/api/v1/clusters/cl1/requests/44
> 2017-07-18 03:13:13,099|INFO|MainThread|machine.py:159 - 
> run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|Jul 18, 2017 3:13:13 AM 
> com.hwx.utils.logging.LogManager log
> 2017-07-18 03:13:13,099|INFO|MainThread|machine.py:159 - 
> run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|INFO: Wait for 30 seconds. 
> Total Wait Time : 30 seconds
> 2017-07-18 03:13:43,390|INFO|MainThread|machine.py:159 - 
> run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|Jul 18, 2017 3:13:43 AM 
> com.hwx.utils.logging.LogManager log
> 2017-07-18 03:13:43,390|INFO|MainThread|machine.py:159 - 
> run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|INFO: Wait for 30 seconds. 
> Total Wait Time : 60 seconds
> 2017-07-18 03:13:43,521|INFO|MainThread|machine.py:159 - 
> run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|Jul 18, 2017 3:13:43 AM 
> com.hwx.utils.logging.LogManager log
> 2017-07-18 03:13:43,521|INFO|MainThread|machine.py:159 - 
> run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|SEVERE: Failed task while 
> Issued INSTALLED as new state for NODEMANAGER
> 2017-07-18 03:13:43,655|INFO|MainThread|machine.py:159 - 
> 

[jira] [Created] (AMBARI-21512) Stack Advisor reported an error: KeyError: 'stack_name' while Issued INSTALLED as new state for NODEMANAGER

[Sumit Mohanty (JIRA)]

Sumit Mohanty created AMBARI-21512:
--

 Summary: Stack Advisor reported an error: KeyError: 'stack_name' 
while Issued INSTALLED as new state for NODEMANAGER
 Key: AMBARI-21512
 URL: https://issues.apache.org/jira/browse/AMBARI-21512
 Project: Ambari
  Issue Type: Bug
  Components: stacks
Affects Versions: 2.5.2
Reporter: Sumit Mohanty
Assignee: Sumit Mohanty
 Fix For: 2.5.2


While In build #139, performing an [AUTHORIZED, HOST_ADD_DELETE_COMPONENTS] 
operation in RBAC for NODEMANAGER failed for AMBARI_ADMINISTRATOR role.

Test Logs:
{code}
2017-07-18 03:12:42,062|INFO|MainThread|machine.py:159 - 
run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|INFO: Requesting put on 
Request path : 
http://172.27.22.82:8080/api/v1/clusters/cl1/hosts/ctr-e134-1499953498516-15485-01-03.hwx.site/host_components/NODEMANAGER
2017-07-18 03:12:43,053|INFO|MainThread|machine.py:159 - 
run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|Jul 18, 2017 3:12:43 AM 
com.hwx.utils.logging.LogManager log
2017-07-18 03:12:43,053|INFO|MainThread|machine.py:159 - 
run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|INFO: Response body : {
2017-07-18 03:12:43,053|INFO|MainThread|machine.py:159 - 
run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|"href" : 
"http://172.27.22.82:8080/api/v1/clusters/cl1/requests/44;,
2017-07-18 03:12:43,053|INFO|MainThread|machine.py:159 - 
run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|"Requests" : {
2017-07-18 03:12:43,053|INFO|MainThread|machine.py:159 - 
run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|"id" : 44,
2017-07-18 03:12:43,053|INFO|MainThread|machine.py:159 - 
run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|"status" : "Accepted"
2017-07-18 03:12:43,054|INFO|MainThread|machine.py:159 - 
run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|}
2017-07-18 03:12:43,054|INFO|MainThread|machine.py:159 - 
run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|}
2017-07-18 03:12:43,054|INFO|MainThread|machine.py:159 - 
run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|Jul 18, 2017 3:12:43 AM 
com.hwx.utils.logging.LogManager log
2017-07-18 03:12:43,054|INFO|MainThread|machine.py:159 - 
run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|INFO: Response body : {
2017-07-18 03:12:43,054|INFO|MainThread|machine.py:159 - 
run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|"href" : 
"http://172.27.22.82:8080/api/v1/clusters/cl1/requests/44;,
2017-07-18 03:12:43,054|INFO|MainThread|machine.py:159 - 
run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|"Requests" : {
2017-07-18 03:12:43,054|INFO|MainThread|machine.py:159 - 
run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|"id" : 44,
2017-07-18 03:12:43,054|INFO|MainThread|machine.py:159 - 
run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|"status" : "Accepted"
2017-07-18 03:12:43,054|INFO|MainThread|machine.py:159 - 
run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|}
2017-07-18 03:12:43,054|INFO|MainThread|machine.py:159 - 
run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|}
2017-07-18 03:12:43,055|INFO|MainThread|machine.py:159 - 
run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|Jul 18, 2017 3:12:43 AM 
com.hwx.utils.logging.LogManager log
2017-07-18 03:12:43,055|INFO|MainThread|machine.py:159 - 
run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|INFO: Service URL : 
http://172.27.22.82:8080/api/v1/clusters/cl1/requests/44
2017-07-18 03:13:13,099|INFO|MainThread|machine.py:159 - 
run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|Jul 18, 2017 3:13:13 AM 
com.hwx.utils.logging.LogManager log
2017-07-18 03:13:13,099|INFO|MainThread|machine.py:159 - 
run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|INFO: Wait for 30 seconds. 
Total Wait Time : 30 seconds
2017-07-18 03:13:43,390|INFO|MainThread|machine.py:159 - 
run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|Jul 18, 2017 3:13:43 AM 
com.hwx.utils.logging.LogManager log
2017-07-18 03:13:43,390|INFO|MainThread|machine.py:159 - 
run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|INFO: Wait for 30 seconds. 
Total Wait Time : 60 seconds
2017-07-18 03:13:43,521|INFO|MainThread|machine.py:159 - 
run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|Jul 18, 2017 3:13:43 AM 
com.hwx.utils.logging.LogManager log
2017-07-18 03:13:43,521|INFO|MainThread|machine.py:159 - 
run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|SEVERE: Failed task while 
Issued INSTALLED as new state for NODEMANAGER
2017-07-18 03:13:43,655|INFO|MainThread|machine.py:159 - 
run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|Jul 18, 2017 3:13:43 AM 
com.hwx.utils.logging.LogManager log
2017-07-18 03:13:43,655|INFO|MainThread|machine.py:159 - 
run()||GUID=2d76c48d-01f4-4740-bf4c-a0c9170ca246|SEVERE: Error while processing 
host component NODEMANAGER state change request to INSTALLED
{code}

API Logs:
{code}
03:12:41 AM 07-18-2017 ServiceManager INFO - Action :adding component 
NODEMANAGER to the host 

[jira] [Commented] (AMBARI-21501) Make HSI's 'hive.llap.zk.sm.keytab' and 'hive.service.keytab' group readable.

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty commented on AMBARI-21501:


Patch looks good, +1.

> Make HSI's 'hive.llap.zk.sm.keytab' and 'hive.service.keytab' group readable.
> -
>
> Key: AMBARI-21501
> URL: https://issues.apache.org/jira/browse/AMBARI-21501
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk, 2.5.1
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Blocker
> Fix For: trunk, 2.5.2
>
> Attachments: AMBARI-21501.patch
>
>
> As part of multiple fixes in AMBARI-21445, HSI's 'hive.llap.zk.sm.keytab' and 
> 'hive.service.keytab' were made non-group readable, which caused LLAP 
> deployment failures.
> Reverting this specific sub change.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (AMBARI-21482) Blueprints: HSI config 'num_llap_nodes' and 'num_llap_nodes_for_llap_daemons' should be calculated and recommended via Stack Advisor during Blueprint install only if

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty commented on AMBARI-21482:


LGTM, +1

> Blueprints: HSI config 'num_llap_nodes' and 'num_llap_nodes_for_llap_daemons' 
> should be calculated and recommended via Stack Advisor during Blueprint 
> install only if 'num_llap_nodes' config value is not provided in Blueprint.
> -
>
> Key: AMBARI-21482
> URL: https://issues.apache.org/jira/browse/AMBARI-21482
> Project: Ambari
>  Issue Type: Bug
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Attachments: AMBARI-21482.patch
>
>
> *Current:* HSI config *'num_llap_nodes_for_llap_daemons*' is calculated and 
> recommended via Stack Advisor during Blueprint install and 
> *''num_llap_nodes''*  value is not used for 
> *'num_llap_nodes_for_llap_daemons*' calculation, if available in Blueprint.
> *Issue* :  This creates the problem of calculating value for 
> *'num_llap_nodes_for_llap_daemons'*, in which calculation doesn't includes 
> using the *'num_llap_nodes'* value.
> We need to use *'num_llap_nodes'* config value (if provided in BP) while 
> calculating value for *'num_llap_nodes_for_llap_daemons'* during cluster 
> creation call to Stack Advisor.
> *Fix* : During BP cluster install call to SA, recommendation for 
> *'num_llap_nodes_for_llap_daemons'* should use value of *'num_llap_nodes'* 
> config if specified in the cluster BP call.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-21460) Add new kafka client properties to the ambari managed atlas config

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty updated AMBARI-21460:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

Committed to trunk and branch-2.5

> Add new kafka client properties to the ambari managed atlas config
> --
>
> Key: AMBARI-21460
> URL: https://issues.apache.org/jira/browse/AMBARI-21460
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Ayub Pathan
>Assignee: Vishal Suvagia
> Fix For: trunk, 2.5.2
>
> Attachments: AMBARI-21460_branch-2.5.patch, AMBARI-21460.patch, 
> AMBARI-21460_trunk.patch
>
>
> As part of this 
> [commit|https://github.com/apache/incubator-atlas/commit/0e7f8ea4603c858cc295259bbd1a22314b732f62],
>  below new kafka client properties are introduced, need to add this to the 
> ambari managed atlas config.
> atlas.kafka.enable.auto.commit=false
> atlas.kafka.session.timeout.ms=3
> atlas.kafka.auto.commit.enable is deleted



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-21471) ATS going down due to missing org.apache.spark.deploy.history.yarn.plugin.SparkATSPlugin

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty updated AMBARI-21471:
---
Attachment: (was: AMBARI-21471.patch)

> ATS going down due to missing 
> org.apache.spark.deploy.history.yarn.plugin.SparkATSPlugin
> 
>
> Key: AMBARI-21471
> URL: https://issues.apache.org/jira/browse/AMBARI-21471
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.5.2
>Reporter: Sumit Mohanty
>Assignee: Sumit Mohanty
> Fix For: 2.5.2
>
> Attachments: AMBARI-21471.patch
>
>
> ATS is going down with
> {code}
> 2017-07-12 02:48:01,542 FATAL 
> applicationhistoryservice.ApplicationHistoryServer 
> (ApplicationHistoryServer.java:launchAppHistoryServer(177)) - Error starting 
> ApplicationHistoryServer
> java.lang.RuntimeException: No class defined for 
> org.apache.spark.deploy.history.yarn.plugin.SparkATSPlugin
> at 
> org.apache.hadoop.yarn.server.timeline.EntityGroupFSTimelineStore.loadPlugIns(EntityGroupFSTimelineStore.java:256)
> at 
> org.apache.hadoop.yarn.server.timeline.EntityGroupFSTimelineStore.serviceInit(EntityGroupFSTimelineStore.java:196)
> at 
> org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
> at 
> org.apache.hadoop.service.CompositeService.serviceInit(CompositeService.java:107)
> at 
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.serviceInit(ApplicationHistoryServer.java:111)
> at 
> org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
> at 
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.launchAppHistoryServer(ApplicationHistoryServer.java:174)
> at 
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.main(ApplicationHistoryServer.java:184)
> Caused by: java.lang.ClassNotFoundException: 
> org.apache.spark.deploy.history.yarn.plugin.SparkATSPlugin
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:335)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at 
> org.apache.hadoop.util.ApplicationClassLoader.loadClass(ApplicationClassLoader.java:197)
> at 
> org.apache.hadoop.util.ApplicationClassLoader.loadClass(ApplicationClassLoader.java:165)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:348)
> at 
> org.apache.hadoop.yarn.server.timeline.EntityGroupFSTimelineStore.loadPlugIns(EntityGroupFSTimelineStore.java:243)
> ... 7 more
> 2017-07-12 02:48:01,544 INFO  util.ExitUtil (ExitUtil.java:terminate(124)) - 
> Exiting with status -1
> 2017-07-12 02:48:01,551 INFO  
> applicationhistoryservice.ApplicationHistoryServer (LogAdapter.java:info(45)) 
> - SHUTDOWN_MSG:
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-21471) ATS going down due to missing org.apache.spark.deploy.history.yarn.plugin.SparkATSPlugin

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty updated AMBARI-21471:
---
Attachment: AMBARI-21471.patch

> ATS going down due to missing 
> org.apache.spark.deploy.history.yarn.plugin.SparkATSPlugin
> 
>
> Key: AMBARI-21471
> URL: https://issues.apache.org/jira/browse/AMBARI-21471
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.5.2
>Reporter: Sumit Mohanty
>Assignee: Sumit Mohanty
> Fix For: 2.5.2
>
> Attachments: AMBARI-21471.patch
>
>
> ATS is going down with
> {code}
> 2017-07-12 02:48:01,542 FATAL 
> applicationhistoryservice.ApplicationHistoryServer 
> (ApplicationHistoryServer.java:launchAppHistoryServer(177)) - Error starting 
> ApplicationHistoryServer
> java.lang.RuntimeException: No class defined for 
> org.apache.spark.deploy.history.yarn.plugin.SparkATSPlugin
> at 
> org.apache.hadoop.yarn.server.timeline.EntityGroupFSTimelineStore.loadPlugIns(EntityGroupFSTimelineStore.java:256)
> at 
> org.apache.hadoop.yarn.server.timeline.EntityGroupFSTimelineStore.serviceInit(EntityGroupFSTimelineStore.java:196)
> at 
> org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
> at 
> org.apache.hadoop.service.CompositeService.serviceInit(CompositeService.java:107)
> at 
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.serviceInit(ApplicationHistoryServer.java:111)
> at 
> org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
> at 
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.launchAppHistoryServer(ApplicationHistoryServer.java:174)
> at 
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.main(ApplicationHistoryServer.java:184)
> Caused by: java.lang.ClassNotFoundException: 
> org.apache.spark.deploy.history.yarn.plugin.SparkATSPlugin
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:335)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at 
> org.apache.hadoop.util.ApplicationClassLoader.loadClass(ApplicationClassLoader.java:197)
> at 
> org.apache.hadoop.util.ApplicationClassLoader.loadClass(ApplicationClassLoader.java:165)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:348)
> at 
> org.apache.hadoop.yarn.server.timeline.EntityGroupFSTimelineStore.loadPlugIns(EntityGroupFSTimelineStore.java:243)
> ... 7 more
> 2017-07-12 02:48:01,544 INFO  util.ExitUtil (ExitUtil.java:terminate(124)) - 
> Exiting with status -1
> 2017-07-12 02:48:01,551 INFO  
> applicationhistoryservice.ApplicationHistoryServer (LogAdapter.java:info(45)) 
> - SHUTDOWN_MSG:
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-21471) ATS going down due to missing org.apache.spark.deploy.history.yarn.plugin.SparkATSPlugin

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty updated AMBARI-21471:
---
Status: Patch Available  (was: Open)

> ATS going down due to missing 
> org.apache.spark.deploy.history.yarn.plugin.SparkATSPlugin
> 
>
> Key: AMBARI-21471
> URL: https://issues.apache.org/jira/browse/AMBARI-21471
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.5.2
>Reporter: Sumit Mohanty
>Assignee: Sumit Mohanty
> Fix For: 2.5.2
>
> Attachments: AMBARI-21471.patch
>
>
> ATS is going down with
> {code}
> 2017-07-12 02:48:01,542 FATAL 
> applicationhistoryservice.ApplicationHistoryServer 
> (ApplicationHistoryServer.java:launchAppHistoryServer(177)) - Error starting 
> ApplicationHistoryServer
> java.lang.RuntimeException: No class defined for 
> org.apache.spark.deploy.history.yarn.plugin.SparkATSPlugin
> at 
> org.apache.hadoop.yarn.server.timeline.EntityGroupFSTimelineStore.loadPlugIns(EntityGroupFSTimelineStore.java:256)
> at 
> org.apache.hadoop.yarn.server.timeline.EntityGroupFSTimelineStore.serviceInit(EntityGroupFSTimelineStore.java:196)
> at 
> org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
> at 
> org.apache.hadoop.service.CompositeService.serviceInit(CompositeService.java:107)
> at 
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.serviceInit(ApplicationHistoryServer.java:111)
> at 
> org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
> at 
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.launchAppHistoryServer(ApplicationHistoryServer.java:174)
> at 
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.main(ApplicationHistoryServer.java:184)
> Caused by: java.lang.ClassNotFoundException: 
> org.apache.spark.deploy.history.yarn.plugin.SparkATSPlugin
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:335)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at 
> org.apache.hadoop.util.ApplicationClassLoader.loadClass(ApplicationClassLoader.java:197)
> at 
> org.apache.hadoop.util.ApplicationClassLoader.loadClass(ApplicationClassLoader.java:165)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:348)
> at 
> org.apache.hadoop.yarn.server.timeline.EntityGroupFSTimelineStore.loadPlugIns(EntityGroupFSTimelineStore.java:243)
> ... 7 more
> 2017-07-12 02:48:01,544 INFO  util.ExitUtil (ExitUtil.java:terminate(124)) - 
> Exiting with status -1
> 2017-07-12 02:48:01,551 INFO  
> applicationhistoryservice.ApplicationHistoryServer (LogAdapter.java:info(45)) 
> - SHUTDOWN_MSG:
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (AMBARI-21471) ATS going down due to missing org.apache.spark.deploy.history.yarn.plugin.SparkATSPlugin

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty reassigned AMBARI-21471:
--

Assignee: Sumit Mohanty

> ATS going down due to missing 
> org.apache.spark.deploy.history.yarn.plugin.SparkATSPlugin
> 
>
> Key: AMBARI-21471
> URL: https://issues.apache.org/jira/browse/AMBARI-21471
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.5.2
>Reporter: Sumit Mohanty
>Assignee: Sumit Mohanty
> Fix For: 2.5.2
>
> Attachments: AMBARI-21471.patch
>
>
> ATS is going down with
> {code}
> 2017-07-12 02:48:01,542 FATAL 
> applicationhistoryservice.ApplicationHistoryServer 
> (ApplicationHistoryServer.java:launchAppHistoryServer(177)) - Error starting 
> ApplicationHistoryServer
> java.lang.RuntimeException: No class defined for 
> org.apache.spark.deploy.history.yarn.plugin.SparkATSPlugin
> at 
> org.apache.hadoop.yarn.server.timeline.EntityGroupFSTimelineStore.loadPlugIns(EntityGroupFSTimelineStore.java:256)
> at 
> org.apache.hadoop.yarn.server.timeline.EntityGroupFSTimelineStore.serviceInit(EntityGroupFSTimelineStore.java:196)
> at 
> org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
> at 
> org.apache.hadoop.service.CompositeService.serviceInit(CompositeService.java:107)
> at 
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.serviceInit(ApplicationHistoryServer.java:111)
> at 
> org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
> at 
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.launchAppHistoryServer(ApplicationHistoryServer.java:174)
> at 
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.main(ApplicationHistoryServer.java:184)
> Caused by: java.lang.ClassNotFoundException: 
> org.apache.spark.deploy.history.yarn.plugin.SparkATSPlugin
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:335)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at 
> org.apache.hadoop.util.ApplicationClassLoader.loadClass(ApplicationClassLoader.java:197)
> at 
> org.apache.hadoop.util.ApplicationClassLoader.loadClass(ApplicationClassLoader.java:165)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:348)
> at 
> org.apache.hadoop.yarn.server.timeline.EntityGroupFSTimelineStore.loadPlugIns(EntityGroupFSTimelineStore.java:243)
> ... 7 more
> 2017-07-12 02:48:01,544 INFO  util.ExitUtil (ExitUtil.java:terminate(124)) - 
> Exiting with status -1
> 2017-07-12 02:48:01,551 INFO  
> applicationhistoryservice.ApplicationHistoryServer (LogAdapter.java:info(45)) 
> - SHUTDOWN_MSG:
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-21471) ATS going down due to missing org.apache.spark.deploy.history.yarn.plugin.SparkATSPlugin

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty updated AMBARI-21471:
---
Attachment: AMBARI-21471.patch

> ATS going down due to missing 
> org.apache.spark.deploy.history.yarn.plugin.SparkATSPlugin
> 
>
> Key: AMBARI-21471
> URL: https://issues.apache.org/jira/browse/AMBARI-21471
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.5.2
>Reporter: Sumit Mohanty
> Fix For: 2.5.2
>
> Attachments: AMBARI-21471.patch
>
>
> ATS is going down with
> {code}
> 2017-07-12 02:48:01,542 FATAL 
> applicationhistoryservice.ApplicationHistoryServer 
> (ApplicationHistoryServer.java:launchAppHistoryServer(177)) - Error starting 
> ApplicationHistoryServer
> java.lang.RuntimeException: No class defined for 
> org.apache.spark.deploy.history.yarn.plugin.SparkATSPlugin
> at 
> org.apache.hadoop.yarn.server.timeline.EntityGroupFSTimelineStore.loadPlugIns(EntityGroupFSTimelineStore.java:256)
> at 
> org.apache.hadoop.yarn.server.timeline.EntityGroupFSTimelineStore.serviceInit(EntityGroupFSTimelineStore.java:196)
> at 
> org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
> at 
> org.apache.hadoop.service.CompositeService.serviceInit(CompositeService.java:107)
> at 
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.serviceInit(ApplicationHistoryServer.java:111)
> at 
> org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
> at 
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.launchAppHistoryServer(ApplicationHistoryServer.java:174)
> at 
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.main(ApplicationHistoryServer.java:184)
> Caused by: java.lang.ClassNotFoundException: 
> org.apache.spark.deploy.history.yarn.plugin.SparkATSPlugin
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:335)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at 
> org.apache.hadoop.util.ApplicationClassLoader.loadClass(ApplicationClassLoader.java:197)
> at 
> org.apache.hadoop.util.ApplicationClassLoader.loadClass(ApplicationClassLoader.java:165)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:348)
> at 
> org.apache.hadoop.yarn.server.timeline.EntityGroupFSTimelineStore.loadPlugIns(EntityGroupFSTimelineStore.java:243)
> ... 7 more
> 2017-07-12 02:48:01,544 INFO  util.ExitUtil (ExitUtil.java:terminate(124)) - 
> Exiting with status -1
> 2017-07-12 02:48:01,551 INFO  
> applicationhistoryservice.ApplicationHistoryServer (LogAdapter.java:info(45)) 
> - SHUTDOWN_MSG:
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (AMBARI-21471) ATS going down due to missing org.apache.spark.deploy.history.yarn.plugin.SparkATSPlugin

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty commented on AMBARI-21471:


This is because the following config property has a wrong value
{code}

  
yarn.timeline-service.entity-group-fs-store.group-id-plugin-classpath
  
{HDP:/usr/hdp}/${hdp.version}/spark/hdpLib/*

{code}

This is because the stack advisor needs a logic to parse out the root path per 
stack.

> ATS going down due to missing 
> org.apache.spark.deploy.history.yarn.plugin.SparkATSPlugin
> 
>
> Key: AMBARI-21471
> URL: https://issues.apache.org/jira/browse/AMBARI-21471
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.5.2
>Reporter: Sumit Mohanty
> Fix For: 2.5.2
>
>
> ATS is going down with
> {code}
> 2017-07-12 02:48:01,542 FATAL 
> applicationhistoryservice.ApplicationHistoryServer 
> (ApplicationHistoryServer.java:launchAppHistoryServer(177)) - Error starting 
> ApplicationHistoryServer
> java.lang.RuntimeException: No class defined for 
> org.apache.spark.deploy.history.yarn.plugin.SparkATSPlugin
> at 
> org.apache.hadoop.yarn.server.timeline.EntityGroupFSTimelineStore.loadPlugIns(EntityGroupFSTimelineStore.java:256)
> at 
> org.apache.hadoop.yarn.server.timeline.EntityGroupFSTimelineStore.serviceInit(EntityGroupFSTimelineStore.java:196)
> at 
> org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
> at 
> org.apache.hadoop.service.CompositeService.serviceInit(CompositeService.java:107)
> at 
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.serviceInit(ApplicationHistoryServer.java:111)
> at 
> org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
> at 
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.launchAppHistoryServer(ApplicationHistoryServer.java:174)
> at 
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.main(ApplicationHistoryServer.java:184)
> Caused by: java.lang.ClassNotFoundException: 
> org.apache.spark.deploy.history.yarn.plugin.SparkATSPlugin
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:335)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at 
> org.apache.hadoop.util.ApplicationClassLoader.loadClass(ApplicationClassLoader.java:197)
> at 
> org.apache.hadoop.util.ApplicationClassLoader.loadClass(ApplicationClassLoader.java:165)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:348)
> at 
> org.apache.hadoop.yarn.server.timeline.EntityGroupFSTimelineStore.loadPlugIns(EntityGroupFSTimelineStore.java:243)
> ... 7 more
> 2017-07-12 02:48:01,544 INFO  util.ExitUtil (ExitUtil.java:terminate(124)) - 
> Exiting with status -1
> 2017-07-12 02:48:01,551 INFO  
> applicationhistoryservice.ApplicationHistoryServer (LogAdapter.java:info(45)) 
> - SHUTDOWN_MSG:
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-21471) ATS going down due to missing org.apache.spark.deploy.history.yarn.plugin.SparkATSPlugin

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty updated AMBARI-21471:
---
Description: 
ATS is going down with
{code}
2017-07-12 02:48:01,542 FATAL 
applicationhistoryservice.ApplicationHistoryServer 
(ApplicationHistoryServer.java:launchAppHistoryServer(177)) - Error starting 
ApplicationHistoryServer
java.lang.RuntimeException: No class defined for 
org.apache.spark.deploy.history.yarn.plugin.SparkATSPlugin
at 
org.apache.hadoop.yarn.server.timeline.EntityGroupFSTimelineStore.loadPlugIns(EntityGroupFSTimelineStore.java:256)
at 
org.apache.hadoop.yarn.server.timeline.EntityGroupFSTimelineStore.serviceInit(EntityGroupFSTimelineStore.java:196)
at 
org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
at 
org.apache.hadoop.service.CompositeService.serviceInit(CompositeService.java:107)
at 
org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.serviceInit(ApplicationHistoryServer.java:111)
at 
org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
at 
org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.launchAppHistoryServer(ApplicationHistoryServer.java:174)
at 
org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.main(ApplicationHistoryServer.java:184)
Caused by: java.lang.ClassNotFoundException: 
org.apache.spark.deploy.history.yarn.plugin.SparkATSPlugin
at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:335)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
at 
org.apache.hadoop.util.ApplicationClassLoader.loadClass(ApplicationClassLoader.java:197)
at 
org.apache.hadoop.util.ApplicationClassLoader.loadClass(ApplicationClassLoader.java:165)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:348)
at 
org.apache.hadoop.yarn.server.timeline.EntityGroupFSTimelineStore.loadPlugIns(EntityGroupFSTimelineStore.java:243)
... 7 more
2017-07-12 02:48:01,544 INFO  util.ExitUtil (ExitUtil.java:terminate(124)) - 
Exiting with status -1
2017-07-12 02:48:01,551 INFO  
applicationhistoryservice.ApplicationHistoryServer (LogAdapter.java:info(45)) - 
SHUTDOWN_MSG:
{code}

> ATS going down due to missing 
> org.apache.spark.deploy.history.yarn.plugin.SparkATSPlugin
> 
>
> Key: AMBARI-21471
> URL: https://issues.apache.org/jira/browse/AMBARI-21471
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.5.2
>Reporter: Sumit Mohanty
> Fix For: 2.5.2
>
>
> ATS is going down with
> {code}
> 2017-07-12 02:48:01,542 FATAL 
> applicationhistoryservice.ApplicationHistoryServer 
> (ApplicationHistoryServer.java:launchAppHistoryServer(177)) - Error starting 
> ApplicationHistoryServer
> java.lang.RuntimeException: No class defined for 
> org.apache.spark.deploy.history.yarn.plugin.SparkATSPlugin
> at 
> org.apache.hadoop.yarn.server.timeline.EntityGroupFSTimelineStore.loadPlugIns(EntityGroupFSTimelineStore.java:256)
> at 
> org.apache.hadoop.yarn.server.timeline.EntityGroupFSTimelineStore.serviceInit(EntityGroupFSTimelineStore.java:196)
> at 
> org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
> at 
> org.apache.hadoop.service.CompositeService.serviceInit(CompositeService.java:107)
> at 
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.serviceInit(ApplicationHistoryServer.java:111)
> at 
> org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
> at 
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.launchAppHistoryServer(ApplicationHistoryServer.java:174)
> at 
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.main(ApplicationHistoryServer.java:184)
> Caused by: java.lang.ClassNotFoundException: 
> org.apache.spark.deploy.history.yarn.plugin.SparkATSPlugin
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:335)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at 
> org.apache.hadoop.util.ApplicationClassLoader.loadClass(ApplicationClassLoader.java:197)
> at 
> org.apache.hadoop.util.ApplicationClassLoader.loadClass(ApplicationClassLoader.java:165)
> at java.lang.Class.forName0(Native 

[jira] [Created] (AMBARI-21471) ATS going down due to missing org.apache.spark.deploy.history.yarn.plugin.SparkATSPlugin

[Sumit Mohanty (JIRA)]

Sumit Mohanty created AMBARI-21471:
--

 Summary: ATS going down due to missing 
org.apache.spark.deploy.history.yarn.plugin.SparkATSPlugin
 Key: AMBARI-21471
 URL: https://issues.apache.org/jira/browse/AMBARI-21471
 Project: Ambari
  Issue Type: Bug
  Components: stacks
Affects Versions: 2.5.2
Reporter: Sumit Mohanty
 Fix For: 2.5.2






--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (AMBARI-21454) hive20 and wfmanager views fails to build with issue missing module "babel-plugin-transform-es2015-block-scoping"

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty resolved AMBARI-21454.

Resolution: Fixed

Committed to trunk.

> hive20 and wfmanager views fails to build with issue missing module 
> "babel-plugin-transform-es2015-block-scoping"
> -
>
> Key: AMBARI-21454
> URL: https://issues.apache.org/jira/browse/AMBARI-21454
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Reporter: Vijay Kumar
>Assignee: Vijay Kumar
> Fix For: trunk
>
> Attachments: 0001-AMBARI-21454-fix-the-missing-module-issue.patch
>
>
> {code}
> #1 Failure.
> 22:41:37 2017/06/23 05:41:36 INFO: [INFO] --- 
> exec-maven-plugin:1.3.2:exec (Hive build) @ hive20 ---
> 22:41:44 2017/06/23 05:41:43 INFO: Could not start watchman; falling back 
> to NodeWatcher for file system events.
> 22:41:44 2017/06/23 05:41:43 INFO: Visit 
> http://ember-cli.com/user-guide/#watchman for more info.
> 22:41:45 2017/06/23 05:41:45 INFO: Cannot find module 
> 'babel-plugin-transform-es2015-block-scoping'
> 22:41:45 2017/06/23 05:41:45 INFO: Error: Cannot find module 
> 'babel-plugin-transform-es2015-block-scoping'
> 22:41:45 2017/06/23 05:41:45 INFO: at 
> Function.Module._resolveFilename (module.js:325:15)
> 22:41:45 2017/06/23 05:41:45 INFO: at Function.Module._load 
> (module.js:276:25)
> 22:41:45 2017/06/23 05:41:45 INFO: at Module.require 
> (module.js:353:17)
> 22:41:45 2017/06/23 05:41:45 INFO: at require 
> (internal/module.js:12:17)
> 22:41:45 2017/06/23 05:41:45 INFO: at Object. 
> (/grid/0/jenkins/workspace/AMBARI-build-python-ubuntu12/SOURCES/ambari/contrib/views/hive20/src/main/resources/ui/node_modules/ember-data/lib/stripped-build-plugins.js:7:29)
> 22:41:45 2017/06/23 05:41:45 INFO: at Module._compile 
> (module.js:409:26)
> 22:41:45 2017/06/23 05:41:45 INFO: at Object.Module._extensions..js 
> (module.js:416:10)
> 22:41:45 2017/06/23 05:41:45 INFO: at Module.load (module.js:343:32)
> 22:41:45 2017/06/23 05:41:45 INFO: at Function.Module._load 
> (module.js:300:12)
> 22:41:45 2017/06/23 05:41:45 INFO: at Module.require 
> (module.js:353:17)
> 22:41:45 2017/06/23 05:41:45 INFO: at require 
> (internal/module.js:12:17)
> 22:41:45 2017/06/23 05:41:45 INFO: [INFO] 
> 
> 22:41:45 2017/06/23 05:41:45 INFO: [INFO] Reactor Summary:
> 22:41:45 2017/06/23 05:41:45 INFO: [INFO] 
> 22:41:45 2017/06/23 05:41:45 INFO: [INFO] Apache Ambari Project POM 
> .. SUCCESS [  2.791 s]
> 22:41:45 2017/06/23 05:41:45 INFO: [INFO] Ambari Web 
> . SUCCESS [01:28 min]
> 22:41:45 2017/06/23 05:41:45 INFO: [INFO] Ambari Views 
> ... SUCCESS [  2.844 s]
> 22:41:45 2017/06/23 05:41:45 INFO: [INFO] Ambari Admin View 
> .. SUCCESS [02:14 min]
> 22:41:45 2017/06/23 05:41:45 INFO: [INFO] Ambari View Utils 
> .. SUCCESS [  4.083 s]
> 22:41:45 2017/06/23 05:41:45 INFO: [INFO] Ambari View Commons 
>  SUCCESS [  0.932 s]
> 22:41:45 2017/06/23 05:41:45 INFO: [INFO] Files 
> .. SUCCESS [05:30 min]
> 22:41:45 2017/06/23 05:41:45 INFO: [INFO] Pig 
>  SUCCESS [01:18 min]
> 22:41:45 2017/06/23 05:41:45 INFO: [INFO] Slider 
> . SUCCESS [01:07 min]
> 22:41:45 2017/06/23 05:41:45 INFO: [INFO] Capacity Scheduler 
> . SUCCESS [01:40 min]
> 22:41:45 2017/06/23 05:41:45 INFO: [INFO] Tez 
>  SUCCESS [ 15.600 s]
> 22:41:45 2017/06/23 05:41:45 INFO: [INFO] Storm_Monitoring 
> ... SUCCESS [  0.883 s]
> 22:41:45 2017/06/23 05:41:45 INFO: [INFO] hueambarimigration 
> . SUCCESS [04:08 min]
> 22:41:45 2017/06/23 05:41:45 INFO: [INFO] Hive Jdbc 
> .. SUCCESS [03:45 min]
> 22:41:45 2017/06/23 05:41:45 INFO: [INFO] Hive 2.0 
> ... FAILURE [14:47 min]
> {code}
> {code}
> #2 Failure.
> 06:01:53 2017/06/26 13:01:52 INFO: [INFO] --- 
> exec-maven-plugin:1.3.2:exec (Files build) @ wfmanager ---
> 06:02:00 2017/06/26 13:01:59 INFO: version: 2.3.0
> 06:02:00 2017/06/26 13:02:00 INFO: Could not start watchman; falling back 
> to NodeWatcher for file system 

[jira] [Commented] (AMBARI-21454) hive20 and wfmanager views fails to build with issue missing module "babel-plugin-transform-es2015-block-scoping"

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty commented on AMBARI-21454:


+1

> hive20 and wfmanager views fails to build with issue missing module 
> "babel-plugin-transform-es2015-block-scoping"
> -
>
> Key: AMBARI-21454
> URL: https://issues.apache.org/jira/browse/AMBARI-21454
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Reporter: Vijay Kumar
>Assignee: Vijay Kumar
> Fix For: trunk
>
> Attachments: 0001-AMBARI-21454-fix-the-missing-module-issue.patch
>
>
> {code}
> #1 Failure.
> 22:41:37 2017/06/23 05:41:36 INFO: [INFO] --- 
> exec-maven-plugin:1.3.2:exec (Hive build) @ hive20 ---
> 22:41:44 2017/06/23 05:41:43 INFO: Could not start watchman; falling back 
> to NodeWatcher for file system events.
> 22:41:44 2017/06/23 05:41:43 INFO: Visit 
> http://ember-cli.com/user-guide/#watchman for more info.
> 22:41:45 2017/06/23 05:41:45 INFO: Cannot find module 
> 'babel-plugin-transform-es2015-block-scoping'
> 22:41:45 2017/06/23 05:41:45 INFO: Error: Cannot find module 
> 'babel-plugin-transform-es2015-block-scoping'
> 22:41:45 2017/06/23 05:41:45 INFO: at 
> Function.Module._resolveFilename (module.js:325:15)
> 22:41:45 2017/06/23 05:41:45 INFO: at Function.Module._load 
> (module.js:276:25)
> 22:41:45 2017/06/23 05:41:45 INFO: at Module.require 
> (module.js:353:17)
> 22:41:45 2017/06/23 05:41:45 INFO: at require 
> (internal/module.js:12:17)
> 22:41:45 2017/06/23 05:41:45 INFO: at Object. 
> (/grid/0/jenkins/workspace/AMBARI-build-python-ubuntu12/SOURCES/ambari/contrib/views/hive20/src/main/resources/ui/node_modules/ember-data/lib/stripped-build-plugins.js:7:29)
> 22:41:45 2017/06/23 05:41:45 INFO: at Module._compile 
> (module.js:409:26)
> 22:41:45 2017/06/23 05:41:45 INFO: at Object.Module._extensions..js 
> (module.js:416:10)
> 22:41:45 2017/06/23 05:41:45 INFO: at Module.load (module.js:343:32)
> 22:41:45 2017/06/23 05:41:45 INFO: at Function.Module._load 
> (module.js:300:12)
> 22:41:45 2017/06/23 05:41:45 INFO: at Module.require 
> (module.js:353:17)
> 22:41:45 2017/06/23 05:41:45 INFO: at require 
> (internal/module.js:12:17)
> 22:41:45 2017/06/23 05:41:45 INFO: [INFO] 
> 
> 22:41:45 2017/06/23 05:41:45 INFO: [INFO] Reactor Summary:
> 22:41:45 2017/06/23 05:41:45 INFO: [INFO] 
> 22:41:45 2017/06/23 05:41:45 INFO: [INFO] Apache Ambari Project POM 
> .. SUCCESS [  2.791 s]
> 22:41:45 2017/06/23 05:41:45 INFO: [INFO] Ambari Web 
> . SUCCESS [01:28 min]
> 22:41:45 2017/06/23 05:41:45 INFO: [INFO] Ambari Views 
> ... SUCCESS [  2.844 s]
> 22:41:45 2017/06/23 05:41:45 INFO: [INFO] Ambari Admin View 
> .. SUCCESS [02:14 min]
> 22:41:45 2017/06/23 05:41:45 INFO: [INFO] Ambari View Utils 
> .. SUCCESS [  4.083 s]
> 22:41:45 2017/06/23 05:41:45 INFO: [INFO] Ambari View Commons 
>  SUCCESS [  0.932 s]
> 22:41:45 2017/06/23 05:41:45 INFO: [INFO] Files 
> .. SUCCESS [05:30 min]
> 22:41:45 2017/06/23 05:41:45 INFO: [INFO] Pig 
>  SUCCESS [01:18 min]
> 22:41:45 2017/06/23 05:41:45 INFO: [INFO] Slider 
> . SUCCESS [01:07 min]
> 22:41:45 2017/06/23 05:41:45 INFO: [INFO] Capacity Scheduler 
> . SUCCESS [01:40 min]
> 22:41:45 2017/06/23 05:41:45 INFO: [INFO] Tez 
>  SUCCESS [ 15.600 s]
> 22:41:45 2017/06/23 05:41:45 INFO: [INFO] Storm_Monitoring 
> ... SUCCESS [  0.883 s]
> 22:41:45 2017/06/23 05:41:45 INFO: [INFO] hueambarimigration 
> . SUCCESS [04:08 min]
> 22:41:45 2017/06/23 05:41:45 INFO: [INFO] Hive Jdbc 
> .. SUCCESS [03:45 min]
> 22:41:45 2017/06/23 05:41:45 INFO: [INFO] Hive 2.0 
> ... FAILURE [14:47 min]
> {code}
> {code}
> #2 Failure.
> 06:01:53 2017/06/26 13:01:52 INFO: [INFO] --- 
> exec-maven-plugin:1.3.2:exec (Files build) @ wfmanager ---
> 06:02:00 2017/06/26 13:01:59 INFO: version: 2.3.0
> 06:02:00 2017/06/26 13:02:00 INFO: Could not start watchman; falling back 
> to NodeWatcher for file system 

[jira] [Assigned] (AMBARI-21454) hive20 and wfmanager views fails to build with issue missing module "babel-plugin-transform-es2015-block-scoping"

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty reassigned AMBARI-21454:
--

Assignee: Vijay Kumar

> hive20 and wfmanager views fails to build with issue missing module 
> "babel-plugin-transform-es2015-block-scoping"
> -
>
> Key: AMBARI-21454
> URL: https://issues.apache.org/jira/browse/AMBARI-21454
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Reporter: Vijay Kumar
>Assignee: Vijay Kumar
> Fix For: trunk
>
> Attachments: 0001-AMBARI-21454-fix-the-missing-module-issue.patch
>
>
> {code}
> #1 Failure.
> 22:41:37 2017/06/23 05:41:36 INFO: [INFO] --- 
> exec-maven-plugin:1.3.2:exec (Hive build) @ hive20 ---
> 22:41:44 2017/06/23 05:41:43 INFO: Could not start watchman; falling back 
> to NodeWatcher for file system events.
> 22:41:44 2017/06/23 05:41:43 INFO: Visit 
> http://ember-cli.com/user-guide/#watchman for more info.
> 22:41:45 2017/06/23 05:41:45 INFO: Cannot find module 
> 'babel-plugin-transform-es2015-block-scoping'
> 22:41:45 2017/06/23 05:41:45 INFO: Error: Cannot find module 
> 'babel-plugin-transform-es2015-block-scoping'
> 22:41:45 2017/06/23 05:41:45 INFO: at 
> Function.Module._resolveFilename (module.js:325:15)
> 22:41:45 2017/06/23 05:41:45 INFO: at Function.Module._load 
> (module.js:276:25)
> 22:41:45 2017/06/23 05:41:45 INFO: at Module.require 
> (module.js:353:17)
> 22:41:45 2017/06/23 05:41:45 INFO: at require 
> (internal/module.js:12:17)
> 22:41:45 2017/06/23 05:41:45 INFO: at Object. 
> (/grid/0/jenkins/workspace/AMBARI-build-python-ubuntu12/SOURCES/ambari/contrib/views/hive20/src/main/resources/ui/node_modules/ember-data/lib/stripped-build-plugins.js:7:29)
> 22:41:45 2017/06/23 05:41:45 INFO: at Module._compile 
> (module.js:409:26)
> 22:41:45 2017/06/23 05:41:45 INFO: at Object.Module._extensions..js 
> (module.js:416:10)
> 22:41:45 2017/06/23 05:41:45 INFO: at Module.load (module.js:343:32)
> 22:41:45 2017/06/23 05:41:45 INFO: at Function.Module._load 
> (module.js:300:12)
> 22:41:45 2017/06/23 05:41:45 INFO: at Module.require 
> (module.js:353:17)
> 22:41:45 2017/06/23 05:41:45 INFO: at require 
> (internal/module.js:12:17)
> 22:41:45 2017/06/23 05:41:45 INFO: [INFO] 
> 
> 22:41:45 2017/06/23 05:41:45 INFO: [INFO] Reactor Summary:
> 22:41:45 2017/06/23 05:41:45 INFO: [INFO] 
> 22:41:45 2017/06/23 05:41:45 INFO: [INFO] Apache Ambari Project POM 
> .. SUCCESS [  2.791 s]
> 22:41:45 2017/06/23 05:41:45 INFO: [INFO] Ambari Web 
> . SUCCESS [01:28 min]
> 22:41:45 2017/06/23 05:41:45 INFO: [INFO] Ambari Views 
> ... SUCCESS [  2.844 s]
> 22:41:45 2017/06/23 05:41:45 INFO: [INFO] Ambari Admin View 
> .. SUCCESS [02:14 min]
> 22:41:45 2017/06/23 05:41:45 INFO: [INFO] Ambari View Utils 
> .. SUCCESS [  4.083 s]
> 22:41:45 2017/06/23 05:41:45 INFO: [INFO] Ambari View Commons 
>  SUCCESS [  0.932 s]
> 22:41:45 2017/06/23 05:41:45 INFO: [INFO] Files 
> .. SUCCESS [05:30 min]
> 22:41:45 2017/06/23 05:41:45 INFO: [INFO] Pig 
>  SUCCESS [01:18 min]
> 22:41:45 2017/06/23 05:41:45 INFO: [INFO] Slider 
> . SUCCESS [01:07 min]
> 22:41:45 2017/06/23 05:41:45 INFO: [INFO] Capacity Scheduler 
> . SUCCESS [01:40 min]
> 22:41:45 2017/06/23 05:41:45 INFO: [INFO] Tez 
>  SUCCESS [ 15.600 s]
> 22:41:45 2017/06/23 05:41:45 INFO: [INFO] Storm_Monitoring 
> ... SUCCESS [  0.883 s]
> 22:41:45 2017/06/23 05:41:45 INFO: [INFO] hueambarimigration 
> . SUCCESS [04:08 min]
> 22:41:45 2017/06/23 05:41:45 INFO: [INFO] Hive Jdbc 
> .. SUCCESS [03:45 min]
> 22:41:45 2017/06/23 05:41:45 INFO: [INFO] Hive 2.0 
> ... FAILURE [14:47 min]
> {code}
> {code}
> #2 Failure.
> 06:01:53 2017/06/26 13:01:52 INFO: [INFO] --- 
> exec-maven-plugin:1.3.2:exec (Files build) @ wfmanager ---
> 06:02:00 2017/06/26 13:01:59 INFO: version: 2.3.0
> 06:02:00 2017/06/26 13:02:00 INFO: Could not start watchman; falling back 
> to NodeWatcher for file system events.
> 

[jira] [Updated] (AMBARI-21454) hive20 and wfmanager views fails to build with issue missing module "babel-plugin-transform-es2015-block-scoping"

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty updated AMBARI-21454:
---
Fix Version/s: trunk

> hive20 and wfmanager views fails to build with issue missing module 
> "babel-plugin-transform-es2015-block-scoping"
> -
>
> Key: AMBARI-21454
> URL: https://issues.apache.org/jira/browse/AMBARI-21454
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Reporter: Vijay Kumar
> Fix For: trunk
>
> Attachments: 0001-AMBARI-21454-fix-the-missing-module-issue.patch
>
>
> {code}
> #1 Failure.
> 22:41:37 2017/06/23 05:41:36 INFO: [INFO] --- 
> exec-maven-plugin:1.3.2:exec (Hive build) @ hive20 ---
> 22:41:44 2017/06/23 05:41:43 INFO: Could not start watchman; falling back 
> to NodeWatcher for file system events.
> 22:41:44 2017/06/23 05:41:43 INFO: Visit 
> http://ember-cli.com/user-guide/#watchman for more info.
> 22:41:45 2017/06/23 05:41:45 INFO: Cannot find module 
> 'babel-plugin-transform-es2015-block-scoping'
> 22:41:45 2017/06/23 05:41:45 INFO: Error: Cannot find module 
> 'babel-plugin-transform-es2015-block-scoping'
> 22:41:45 2017/06/23 05:41:45 INFO: at 
> Function.Module._resolveFilename (module.js:325:15)
> 22:41:45 2017/06/23 05:41:45 INFO: at Function.Module._load 
> (module.js:276:25)
> 22:41:45 2017/06/23 05:41:45 INFO: at Module.require 
> (module.js:353:17)
> 22:41:45 2017/06/23 05:41:45 INFO: at require 
> (internal/module.js:12:17)
> 22:41:45 2017/06/23 05:41:45 INFO: at Object. 
> (/grid/0/jenkins/workspace/AMBARI-build-python-ubuntu12/SOURCES/ambari/contrib/views/hive20/src/main/resources/ui/node_modules/ember-data/lib/stripped-build-plugins.js:7:29)
> 22:41:45 2017/06/23 05:41:45 INFO: at Module._compile 
> (module.js:409:26)
> 22:41:45 2017/06/23 05:41:45 INFO: at Object.Module._extensions..js 
> (module.js:416:10)
> 22:41:45 2017/06/23 05:41:45 INFO: at Module.load (module.js:343:32)
> 22:41:45 2017/06/23 05:41:45 INFO: at Function.Module._load 
> (module.js:300:12)
> 22:41:45 2017/06/23 05:41:45 INFO: at Module.require 
> (module.js:353:17)
> 22:41:45 2017/06/23 05:41:45 INFO: at require 
> (internal/module.js:12:17)
> 22:41:45 2017/06/23 05:41:45 INFO: [INFO] 
> 
> 22:41:45 2017/06/23 05:41:45 INFO: [INFO] Reactor Summary:
> 22:41:45 2017/06/23 05:41:45 INFO: [INFO] 
> 22:41:45 2017/06/23 05:41:45 INFO: [INFO] Apache Ambari Project POM 
> .. SUCCESS [  2.791 s]
> 22:41:45 2017/06/23 05:41:45 INFO: [INFO] Ambari Web 
> . SUCCESS [01:28 min]
> 22:41:45 2017/06/23 05:41:45 INFO: [INFO] Ambari Views 
> ... SUCCESS [  2.844 s]
> 22:41:45 2017/06/23 05:41:45 INFO: [INFO] Ambari Admin View 
> .. SUCCESS [02:14 min]
> 22:41:45 2017/06/23 05:41:45 INFO: [INFO] Ambari View Utils 
> .. SUCCESS [  4.083 s]
> 22:41:45 2017/06/23 05:41:45 INFO: [INFO] Ambari View Commons 
>  SUCCESS [  0.932 s]
> 22:41:45 2017/06/23 05:41:45 INFO: [INFO] Files 
> .. SUCCESS [05:30 min]
> 22:41:45 2017/06/23 05:41:45 INFO: [INFO] Pig 
>  SUCCESS [01:18 min]
> 22:41:45 2017/06/23 05:41:45 INFO: [INFO] Slider 
> . SUCCESS [01:07 min]
> 22:41:45 2017/06/23 05:41:45 INFO: [INFO] Capacity Scheduler 
> . SUCCESS [01:40 min]
> 22:41:45 2017/06/23 05:41:45 INFO: [INFO] Tez 
>  SUCCESS [ 15.600 s]
> 22:41:45 2017/06/23 05:41:45 INFO: [INFO] Storm_Monitoring 
> ... SUCCESS [  0.883 s]
> 22:41:45 2017/06/23 05:41:45 INFO: [INFO] hueambarimigration 
> . SUCCESS [04:08 min]
> 22:41:45 2017/06/23 05:41:45 INFO: [INFO] Hive Jdbc 
> .. SUCCESS [03:45 min]
> 22:41:45 2017/06/23 05:41:45 INFO: [INFO] Hive 2.0 
> ... FAILURE [14:47 min]
> {code}
> {code}
> #2 Failure.
> 06:01:53 2017/06/26 13:01:52 INFO: [INFO] --- 
> exec-maven-plugin:1.3.2:exec (Files build) @ wfmanager ---
> 06:02:00 2017/06/26 13:01:59 INFO: version: 2.3.0
> 06:02:00 2017/06/26 13:02:00 INFO: Could not start watchman; falling back 
> to NodeWatcher for file system events.
> 06:02:00 2017/06/26 13:02:00 INFO: Visit 

[jira] [Commented] (AMBARI-21445) Fixes the following bugs : (1). Make Hive Kerberos keytab files group non-readable (2). HiveServer2 Authentication via LDAP to work correctly (3). Remove leading whil

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty commented on AMBARI-21445:


LGTM, +1

> Fixes the following bugs : (1). Make Hive Kerberos keytab files group 
> non-readable (2). HiveServer2 Authentication via LDAP to work correctly (3). 
> Remove leading while spaces for the hive-env and hive-interactive-env 
> template.
> --
>
> Key: AMBARI-21445
> URL: https://issues.apache.org/jira/browse/AMBARI-21445
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk, 2.5.2
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: trunk, 2.5.2
>
> Attachments: AMBARI-21445.patch
>
>
> (1). Make Hive Kerberos keytab files group non-readable 
> (2). HiveServer2 Authentication via LDAP to work correctly 
> (3). Remove leading while spaces for the hive-env and hive-interactive-env 
> template.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (AMBARI-21444) Hive warehouse fixes

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty commented on AMBARI-21444:


LGTM, +1

> Hive warehouse fixes
> 
>
> Key: AMBARI-21444
> URL: https://issues.apache.org/jira/browse/AMBARI-21444
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: 2.5.2
>
> Attachments: AMBARI-21444.patch
>
>
> Warehouse fixes.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (AMBARI-21370) Support VIPs instead of Host Names

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty commented on AMBARI-21370:


 1 for the addendum patch.

> Support VIPs instead of Host Names
> --
>
> Key: AMBARI-21370
> URL: https://issues.apache.org/jira/browse/AMBARI-21370
> Project: Ambari
>  Issue Type: Bug
>  Components: alerts, ambari-agent, ambari-server, metrics, stacks
>Affects Versions: 2.5.0
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
>Priority: Critical
> Fix For: 2.5.2
>
> Attachments: AMBARI-21370-addendum.patch, AMBARI-21370.patch
>
>
> User should be able to deploy a cluster and configure host components to use 
> VIPs instead of actual host names. For example {{http://nn1-vip-host:50070}} 
> instead of {{http://actual-host-1:50070}}. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (AMBARI-20291) Script-Based Alert Dispatchers support passing more parameters to script

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty commented on AMBARI-20291:


Back ported to 2.5
{code}
1 commit cba018eb6d5c4f2946998d083e92448f5e3770ad
  2 Author: Jonathan Hurley 
  3 Date:   Mon Mar 6 11:13:34 2017 -0500
  4
  5 AMBARI-20291 - Script-Based Alert Dispatchers support passing more 
parameters to script (Yao Lei via jonathanhurley)
{code}

> Script-Based Alert Dispatchers support passing more parameters to script
> 
>
> Key: AMBARI-20291
> URL: https://issues.apache.org/jira/browse/AMBARI-20291
> Project: Ambari
>  Issue Type: Improvement
>Affects Versions: trunk
>Reporter: Yao Lei
>Assignee: Yao Lei
>Priority: Minor
> Fix For: trunk, 2.5.2
>
> Attachments: AMBARI-20291_2.patch
>
>
> Script-Based Alert Dispatcher now pass five parameters to script,including 
> alert definition name, definition label,service name, alert state, and alert 
> text.
> But if script can receive other two parameters from dispather,it will be 
> better.
> 1.hostname.
> Because hostname the alert for is not always included in alert text,although 
> it may be null like aggregate alerts. 
>   With it we can more quick to find the related host that occured alert.
> 2.alert timestamp.
>   We may need to know the alert occurrence time ( state change time) more 
> exactly. After the alert happened,it will spend some time to schedule the 
> script to run.
>   Without it,we can only regard the script start time as the alert occurrence 
> time.
> We now use this feature to send alert information to mobile phone and suggest 
> also passing hostname and alert timestamp.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-20291) Script-Based Alert Dispatchers support passing more parameters to script

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty updated AMBARI-20291:
---
Fix Version/s: 2.5.2

> Script-Based Alert Dispatchers support passing more parameters to script
> 
>
> Key: AMBARI-20291
> URL: https://issues.apache.org/jira/browse/AMBARI-20291
> Project: Ambari
>  Issue Type: Improvement
>Affects Versions: trunk
>Reporter: Yao Lei
>Assignee: Yao Lei
>Priority: Minor
> Fix For: trunk, 2.5.2
>
> Attachments: AMBARI-20291_2.patch
>
>
> Script-Based Alert Dispatcher now pass five parameters to script,including 
> alert definition name, definition label,service name, alert state, and alert 
> text.
> But if script can receive other two parameters from dispather,it will be 
> better.
> 1.hostname.
> Because hostname the alert for is not always included in alert text,although 
> it may be null like aggregate alerts. 
>   With it we can more quick to find the related host that occured alert.
> 2.alert timestamp.
>   We may need to know the alert occurrence time ( state change time) more 
> exactly. After the alert happened,it will spend some time to schedule the 
> script to run.
>   Without it,we can only regard the script start time as the alert occurrence 
> time.
> We now use this feature to send alert information to mobile phone and suggest 
> also passing hostname and alert timestamp.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-20950) HdfsResource can not handle S3 URL when hbase.rootdir is set to S3 URL

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty updated AMBARI-20950:
---
Fix Version/s: 2.5.2

> HdfsResource can not handle S3 URL when hbase.rootdir is set to S3 URL
> --
>
> Key: AMBARI-20950
> URL: https://issues.apache.org/jira/browse/AMBARI-20950
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Xiang Li
>Assignee: Xiang Li
>Priority: Critical
> Fix For: 2.5.2
>
>
> HBASE-17437 enables HBASE to put its rootdir on S3. Ambari calls HdfsResource 
> to create the dir for HBase, but it can not handle S3.
> Almost the same as AMBARI-15157 for Hive.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (AMBARI-21099) Drop JDK 7 support for Ambari Server and Ambari managed services (AMS, LogSearch, Infra)

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty commented on AMBARI-21099:


Thanks [~oleewere]. So there are three driving factors:
* Ambari-3.x will require jdk8
* Some stacks it supports (say HDP-2.6) will require jdk7
* Some services within the stack may require jdk8 (they happen to be Ambari 
defaults but in general we can assume them to be a subset of services)

Today, the same jdk is used for both the Ambari and the services and we also 
expect that at some point in future Ambari and the stacks will converge back to 
using the same jdk. While this is not a must but in general users will prefer 
to supply a single jdk.

So, we are looking at users supplying multiple jdks. We can treat it such with 
one of them being the default. Existing command.json parameters can map to the 
default jdk (e.g. 7 for now). Ambari can demand jdk 8 for itself as part of 
upgrade or install. We need to figure out how a service can indicate that it 
needs jdk 8 (or a jdk version that is not registered yet). When jdk8 is 
installed lets just treat it as a second jdk, the same way we allow 
registration of multiple jdbc drivers. Let the services, that need jdk8, pick 
the right variables from comand json.

We can introduce the notion of a stack/service supplying a min version of jdk 
required with default being "don't care and use the user supplied default jdk"

> Drop JDK 7 support for Ambari Server and Ambari managed services (AMS, 
> LogSearch, Infra)
> 
>
> Key: AMBARI-21099
> URL: https://issues.apache.org/jira/browse/AMBARI-21099
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
> Fix For: 3.0.0
>
> Attachments: AMBARI-21099.patch
>
>
> Requirements:
> - ambari should drop JDK 7 support for ambari-server and ambari-managed 
> services (infra, ams, logsearch)
> - HDP 2.x should be still able to use JDK 1.7
> Changes in ambari setup:
> 1. First the usual ambari setup
> {code:java}
> Choose JDK for Ambari and Stack services:
> [1] Oracle JDK 1.8 + Java Cryptography Extension (JCE) Policy Files 8
> [2] Oracle JDK 1.7 + Java Cryptography Extension (JCE) Policy Files 7
> [3] Custom JDK
> {code}
> 2. If JDK 7 is picked, that cannot be used for ambari (only for the stack 
> services)
> {code:java}
> JDK 7 is detected (JDK 8 required for ambari-server), install JDK 8 as well:
> [1] Oracle JDK 1.8 + Java Cryptography Extension (JCE) Policy Files 8
> [3] Custom JDK
> {code}
> The following command also can work to setup custom java_home (for stacks + 
> ambari):
> {code:java}
> ambari-server setup -s --java-home=... --stack-java-home=...
> {code}
> After the commands are executed, the following properties would appear in 
> ambari.properties
> {code:java}
> stack.java.home=/usr/jdk64/jdk1.7.0_67
> stack.jdk.name=jdk-7u67linux-x64.tar.gz
> stack.jce.name=UnlimitedJCEPolicyJDK7.zip
> {code}
> During command.json generating, commandParameters would be filled with proper 
> ambari jdk,jce info (different for infra/logsearch/ams from other services) - 
> not hostLevelParams, as multiple command could use the same hostLevelParams 
> (like start all services: that can start zookeeper and ams as well with the 
> same hostLevelParams)
> On ambari-upgrade, ambari process wont be able to start with jdk7 so it will 
> be required to run ambari-server setup first (you can skip the first change 
> jdk part, but then the user will see its needed to setup a different jdk for 
> ambari)
> In the future, it will be recommended to do the JDK upgrade before upgrading 
> to HDP 3.0 (to avoid some issues during HDP upgrade)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-21335) Cannot start ambari server

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty updated AMBARI-21335:
---
Reporter: Sumana Sathish  (was: Vitaly Brodetskyi)

> Cannot start ambari server
> --
>
> Key: AMBARI-21335
> URL: https://issues.apache.org/jira/browse/AMBARI-21335
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Sumana Sathish
>Assignee: Vitaly Brodetskyi
>Priority: Blocker
> Fix For: 3.0.0
>
> Attachments: AMBARI-21335.patch
>
>
> ambari-server start fails with following error
> {Code}
> ambari-server start
> Using python  /usr/bin/python
> Starting ambari-server
> Ambari Server running with administrator privileges.
> Organizing resource files at /var/lib/ambari-server/resources...
> Ambari database consistency check started...
> Server PID at: /var/run/ambari-server/ambari-server.pid
> Server out at: /var/log/ambari-server/ambari-server.out
> Server log at: /var/log/ambari-server/ambari-server.log
> Waiting for server start.Unable to determine server PID. Retrying...
> ..Unable to determine server PID. Retrying...
> ..Unable to determine server PID. Retrying...
> ERROR: Exiting with exit code -1.
> REASON: Ambari Server java process died with exitcode 1. Check 
> /var/log/ambari-server/ambari-server.out for more information.
> {Code}
> logs in /var/log/ambari-server/ambari-server.out  shows
> {code}
> Jun 22, 2017 7:29:55 PM org.apache.ambari.server.configuration.Configuration 
> 
> INFO: Reading password from existing file
> Jun 22, 2017 7:29:55 PM org.apache.ambari.server.configuration.Configuration 
> getHostsMapFile
> INFO: Hosts Mapping File null
> Jun 22, 2017 7:29:55 PM org.apache.ambari.server.controller.HostsMap setupMap
> INFO: Using hostsmap file null
> Exception in thread "main" java.lang.NoSuchMethodError: 
> org.slf4j.helpers.MessageFormatter.format(Ljava/lang/String;Ljava/lang/Object;)Ljava/lang/String;
> at org.slf4j.impl.JDK14LoggerAdapter.info(JDK14LoggerAdapter.java:303)
> at 
> org.apache.ambari.server.controller.ControllerModule.getPersistenceProperties(ControllerModule.java:221)
> at 
> org.apache.ambari.server.controller.ControllerModule.buildJpaPersistModule(ControllerModule.java:416)
> at 
> org.apache.ambari.server.controller.ControllerModule.configure(ControllerModule.java:343)
> at com.google.inject.AbstractModule.configure(AbstractModule.java:59)
> at 
> com.google.inject.spi.Elements$RecordingBinder.install(Elements.java:223)
> at com.google.inject.spi.Elements.getElements(Elements.java:101)
> at 
> com.google.inject.internal.InjectorShell$Builder.build(InjectorShell.java:133)
> at 
> com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:103)
> at com.google.inject.Guice.createInjector(Guice.java:95)
> at com.google.inject.Guice.createInjector(Guice.java:72)
> at com.google.inject.Guice.createInjector(Guice.java:62)
> at 
> org.apache.ambari.server.controller.AmbariServer.main(AmbariServer.java:1060)
> ~
> {code}
> Ambari build used - 3.0.0.0-871



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-21335) Cannot start ambari server

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty updated AMBARI-21335:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

Committed.

> Cannot start ambari server
> --
>
> Key: AMBARI-21335
> URL: https://issues.apache.org/jira/browse/AMBARI-21335
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Blocker
> Fix For: 3.0.0
>
> Attachments: AMBARI-21335.patch
>
>
> ambari-server start fails with following error
> {Code}
> ambari-server start
> Using python  /usr/bin/python
> Starting ambari-server
> Ambari Server running with administrator privileges.
> Organizing resource files at /var/lib/ambari-server/resources...
> Ambari database consistency check started...
> Server PID at: /var/run/ambari-server/ambari-server.pid
> Server out at: /var/log/ambari-server/ambari-server.out
> Server log at: /var/log/ambari-server/ambari-server.log
> Waiting for server start.Unable to determine server PID. Retrying...
> ..Unable to determine server PID. Retrying...
> ..Unable to determine server PID. Retrying...
> ERROR: Exiting with exit code -1.
> REASON: Ambari Server java process died with exitcode 1. Check 
> /var/log/ambari-server/ambari-server.out for more information.
> {Code}
> logs in /var/log/ambari-server/ambari-server.out  shows
> {code}
> Jun 22, 2017 7:29:55 PM org.apache.ambari.server.configuration.Configuration 
> 
> INFO: Reading password from existing file
> Jun 22, 2017 7:29:55 PM org.apache.ambari.server.configuration.Configuration 
> getHostsMapFile
> INFO: Hosts Mapping File null
> Jun 22, 2017 7:29:55 PM org.apache.ambari.server.controller.HostsMap setupMap
> INFO: Using hostsmap file null
> Exception in thread "main" java.lang.NoSuchMethodError: 
> org.slf4j.helpers.MessageFormatter.format(Ljava/lang/String;Ljava/lang/Object;)Ljava/lang/String;
> at org.slf4j.impl.JDK14LoggerAdapter.info(JDK14LoggerAdapter.java:303)
> at 
> org.apache.ambari.server.controller.ControllerModule.getPersistenceProperties(ControllerModule.java:221)
> at 
> org.apache.ambari.server.controller.ControllerModule.buildJpaPersistModule(ControllerModule.java:416)
> at 
> org.apache.ambari.server.controller.ControllerModule.configure(ControllerModule.java:343)
> at com.google.inject.AbstractModule.configure(AbstractModule.java:59)
> at 
> com.google.inject.spi.Elements$RecordingBinder.install(Elements.java:223)
> at com.google.inject.spi.Elements.getElements(Elements.java:101)
> at 
> com.google.inject.internal.InjectorShell$Builder.build(InjectorShell.java:133)
> at 
> com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:103)
> at com.google.inject.Guice.createInjector(Guice.java:95)
> at com.google.inject.Guice.createInjector(Guice.java:72)
> at com.google.inject.Guice.createInjector(Guice.java:62)
> at 
> org.apache.ambari.server.controller.AmbariServer.main(AmbariServer.java:1060)
> ~
> {code}
> Ambari build used - 3.0.0.0-871



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (AMBARI-21335) Cannot start ambari server

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty commented on AMBARI-21335:


LGTM, +1

> Cannot start ambari server
> --
>
> Key: AMBARI-21335
> URL: https://issues.apache.org/jira/browse/AMBARI-21335
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Blocker
> Fix For: 3.0.0
>
> Attachments: AMBARI-21335.patch
>
>
> ambari-server start fails with following error
> {Code}
> ambari-server start
> Using python  /usr/bin/python
> Starting ambari-server
> Ambari Server running with administrator privileges.
> Organizing resource files at /var/lib/ambari-server/resources...
> Ambari database consistency check started...
> Server PID at: /var/run/ambari-server/ambari-server.pid
> Server out at: /var/log/ambari-server/ambari-server.out
> Server log at: /var/log/ambari-server/ambari-server.log
> Waiting for server start.Unable to determine server PID. Retrying...
> ..Unable to determine server PID. Retrying...
> ..Unable to determine server PID. Retrying...
> ERROR: Exiting with exit code -1.
> REASON: Ambari Server java process died with exitcode 1. Check 
> /var/log/ambari-server/ambari-server.out for more information.
> {Code}
> logs in /var/log/ambari-server/ambari-server.out  shows
> {code}
> Jun 22, 2017 7:29:55 PM org.apache.ambari.server.configuration.Configuration 
> 
> INFO: Reading password from existing file
> Jun 22, 2017 7:29:55 PM org.apache.ambari.server.configuration.Configuration 
> getHostsMapFile
> INFO: Hosts Mapping File null
> Jun 22, 2017 7:29:55 PM org.apache.ambari.server.controller.HostsMap setupMap
> INFO: Using hostsmap file null
> Exception in thread "main" java.lang.NoSuchMethodError: 
> org.slf4j.helpers.MessageFormatter.format(Ljava/lang/String;Ljava/lang/Object;)Ljava/lang/String;
> at org.slf4j.impl.JDK14LoggerAdapter.info(JDK14LoggerAdapter.java:303)
> at 
> org.apache.ambari.server.controller.ControllerModule.getPersistenceProperties(ControllerModule.java:221)
> at 
> org.apache.ambari.server.controller.ControllerModule.buildJpaPersistModule(ControllerModule.java:416)
> at 
> org.apache.ambari.server.controller.ControllerModule.configure(ControllerModule.java:343)
> at com.google.inject.AbstractModule.configure(AbstractModule.java:59)
> at 
> com.google.inject.spi.Elements$RecordingBinder.install(Elements.java:223)
> at com.google.inject.spi.Elements.getElements(Elements.java:101)
> at 
> com.google.inject.internal.InjectorShell$Builder.build(InjectorShell.java:133)
> at 
> com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:103)
> at com.google.inject.Guice.createInjector(Guice.java:95)
> at com.google.inject.Guice.createInjector(Guice.java:72)
> at com.google.inject.Guice.createInjector(Guice.java:62)
> at 
> org.apache.ambari.server.controller.AmbariServer.main(AmbariServer.java:1060)
> ~
> {code}
> Ambari build used - 3.0.0.0-871



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (AMBARI-21256) As part of START_ALL of services Ranger kms starts after hbase and hive causing operation failure

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty commented on AMBARI-21256:


LGTM, +1

> As part of START_ALL of services Ranger kms starts after hbase and hive 
> causing operation failure
> -
>
> Key: AMBARI-21256
> URL: https://issues.apache.org/jira/browse/AMBARI-21256
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Vishal Suvagia
>Assignee: Vishal Suvagia
> Fix For: 2.5.2
>
> Attachments: AMBARI-21256_branch-2.5.patch, AMBARI-21256_trunk.patch
>
>
> As part of START_ALL of services Ranger-KMS starts after Hbase and Hive 
> causing their start failure. 
> In an encrypted cluster where TDE is on, Hbase service seems to be dependent 
> on the Ranger-KMS service, but for a start-all services action Hbase service 
> starts before Ranger-KMS.
> So Hbase master goes down while connecting to KMS, since at the time of Hbase 
> start KMS is down , connection to KMS fails, and Hbase-Master fails to become 
> active.
> This in-turn causes Atlas service start failure which actually depends on 
> HBase and start_all flow fails for HBASE and HIVE.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (AMBARI-21277) Fail to create solr clients in Log Search / Log Feeder with openjdk8

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty commented on AMBARI-21277:


[~oleewere] I have committed the changes to branch-2.5 - it appears that it had 
all the +1s and needed this for a deployment.

> Fail to create solr clients in Log Search / Log Feeder with openjdk8
> 
>
> Key: AMBARI-21277
> URL: https://issues.apache.org/jira/browse/AMBARI-21277
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-logsearch
>Affects Versions: 3.0.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
> Fix For: 3.0.0, 2.5.2
>
>
> From Feeder log:
> {code}
> 2017-06-15 20:31:14,765 [main] FATAL org.apache.ambari.logfeeder.LogFeeder 
> (LogFeeder.java:88) - Caught exception in main.
> java.lang.VerifyError: Bad return type
> Exception Details:
>   Location:
> 
> org/apache/solr/client/solrj/impl/HttpClientUtil.createClient(Lorg/apache/solr/common/params/SolrParams;)Lorg/apache/http/impl/client/CloseableHttpClient;
>  @57: areturn
>   Reason:
> Type 'org/apache/http/impl/client/SystemDefaultHttpClient' (current 
> frame, stack[0]) is not assignable to 
> 'org/apache/http/impl/client/CloseableHttpClient' (from method signature)
>   Current Frame:
> bci: @57
> flags: { }
> locals: { 'org/apache/solr/common/params/SolrParams', 
> 'org/apache/solr/common/params/ModifiableSolrParams', 
> 'org/apache/http/impl/client/SystemDefaultHttpClient' }
> stack: { 'org/apache/http/impl/client/SystemDefaultHttpClient' }
>   Bytecode:
> 0x000: bb00 0359 2ab7 0004 4cb2 0005 b900 0601
> 0x010: 0099 001e b200 05bb 0007 59b7 0008 1209
> 0x020: b600 0a2b b600 0bb6 000c b900 0d02 00b8
> 0x030: 000e 4d2c 2bb8 000f 2cb0
>   Stackmap Table:
> append_frame(@47,Object[#144])
> at 
> org.apache.ambari.logfeeder.output.OutputSolr.setupSecurity(OutputSolr.java:134)
> at 
> org.apache.ambari.logfeeder.output.OutputSolr.init(OutputSolr.java:94)
> at 
> org.apache.ambari.logfeeder.output.OutputManager.init(OutputManager.java:72)
> at org.apache.ambari.logfeeder.LogFeeder.init(LogFeeder.java:102)
> at org.apache.ambari.logfeeder.LogFeeder.run(LogFeeder.java:84)
> at org.apache.ambari.logfeeder.LogFeeder.main(LogFeeder.java:511)
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-21277) Fail to create solr clients in Log Search / Log Feeder with openjdk8

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty updated AMBARI-21277:
---
Fix Version/s: 2.5.2

> Fail to create solr clients in Log Search / Log Feeder with openjdk8
> 
>
> Key: AMBARI-21277
> URL: https://issues.apache.org/jira/browse/AMBARI-21277
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-logsearch
>Affects Versions: 3.0.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
> Fix For: 3.0.0, 2.5.2
>
>
> From Feeder log:
> {code}
> 2017-06-15 20:31:14,765 [main] FATAL org.apache.ambari.logfeeder.LogFeeder 
> (LogFeeder.java:88) - Caught exception in main.
> java.lang.VerifyError: Bad return type
> Exception Details:
>   Location:
> 
> org/apache/solr/client/solrj/impl/HttpClientUtil.createClient(Lorg/apache/solr/common/params/SolrParams;)Lorg/apache/http/impl/client/CloseableHttpClient;
>  @57: areturn
>   Reason:
> Type 'org/apache/http/impl/client/SystemDefaultHttpClient' (current 
> frame, stack[0]) is not assignable to 
> 'org/apache/http/impl/client/CloseableHttpClient' (from method signature)
>   Current Frame:
> bci: @57
> flags: { }
> locals: { 'org/apache/solr/common/params/SolrParams', 
> 'org/apache/solr/common/params/ModifiableSolrParams', 
> 'org/apache/http/impl/client/SystemDefaultHttpClient' }
> stack: { 'org/apache/http/impl/client/SystemDefaultHttpClient' }
>   Bytecode:
> 0x000: bb00 0359 2ab7 0004 4cb2 0005 b900 0601
> 0x010: 0099 001e b200 05bb 0007 59b7 0008 1209
> 0x020: b600 0a2b b600 0bb6 000c b900 0d02 00b8
> 0x030: 000e 4d2c 2bb8 000f 2cb0
>   Stackmap Table:
> append_frame(@47,Object[#144])
> at 
> org.apache.ambari.logfeeder.output.OutputSolr.setupSecurity(OutputSolr.java:134)
> at 
> org.apache.ambari.logfeeder.output.OutputSolr.init(OutputSolr.java:94)
> at 
> org.apache.ambari.logfeeder.output.OutputManager.init(OutputManager.java:72)
> at org.apache.ambari.logfeeder.LogFeeder.init(LogFeeder.java:102)
> at org.apache.ambari.logfeeder.LogFeeder.run(LogFeeder.java:84)
> at org.apache.ambari.logfeeder.LogFeeder.main(LogFeeder.java:511)
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (AMBARI-21273) Swagger resources generation for doc purpose should not be part of default maven profile

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty commented on AMBARI-21273:


Thanks [~jaimin], +1

> Swagger resources generation for doc purpose should not be part of default 
> maven profile
> 
>
> Key: AMBARI-21273
> URL: https://issues.apache.org/jira/browse/AMBARI-21273
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Jaimin Jetly
>Assignee: Jaimin Jetly
> Fix For: 3.0.0
>
> Attachments: AMBARI-21273.patch
>
>
> On executing mvn compile on ambari-server and then checking with git status, 
> following files are automatically added/edited even when no code changes are 
> made
> {code}
> modified:   ambari-server/docs/api/generated/index.html
> Untracked files:
>   (use "git add ..." to include in what will be committed)
> docs/api/
> {code}
> As a fix to this issue, swagger resources that are presently checked in to 
> ambari project at ambari-server/docs/api/generated/ will be updated only when 
> mvn command is executed with -Dgenerate.swagger.resources flag.
> This is expected to be done and resources should be checked in just before 
> every new ambari release. with this commit, ambari wiki page for release 
> guideline will also be updated 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (AMBARI-21226) Improve Spark thriftserver default configuration

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty resolved AMBARI-21226.

Resolution: Fixed

> Improve Spark thriftserver default configuration
> 
>
> Key: AMBARI-21226
> URL: https://issues.apache.org/jira/browse/AMBARI-21226
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Reporter: Saisai Shao
>Assignee: Saisai Shao
>
> Add two new default configurations to Ambari Spark stacks, this is mainly 
> used to improve the stability of long running of thriftserver.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)