[jira] [Updated] (AMBARI-18173) HSI is not started even when "Enable Interactive Query" is set to Yes in installer wizard

[Jayush Luniya (JIRA)]

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

Jayush Luniya updated AMBARI-18173:
---
Labels: 240RMApproved  (was: )

> HSI is not started even when "Enable Interactive Query" is set to Yes in 
> installer wizard
> -
>
> Key: AMBARI-18173
> URL: https://issues.apache.org/jira/browse/AMBARI-18173
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Jaimin D Jetly
>Assignee: Jaimin D Jetly
>Priority: Blocker
>  Labels: 240RMApproved
> Fix For: 2.4.0
>
> Attachments: AMBARI-18173.patch
>
>




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

[jira] [Updated] (AMBARI-18173) HSI is not started even when "Enable Interactive Query" is set to Yes in installer wizard

[Jaimin D Jetly (JIRA)]

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

Jaimin D Jetly updated AMBARI-18173:

Summary: HSI is not started even when "Enable Interactive Query" is set to 
Yes in installer wizard  (was: HSI is not started even when "Enable Interactive 
Query" is set to Yes)

> HSI is not started even when "Enable Interactive Query" is set to Yes in 
> installer wizard
> -
>
> Key: AMBARI-18173
> URL: https://issues.apache.org/jira/browse/AMBARI-18173
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Jaimin D Jetly
>Assignee: Jaimin D Jetly
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-18173.patch
>
>




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

[jira] [Updated] (AMBARI-18173) HSI is not started even when "Enable Interactive Query" is set to Yes in installer wizard

[Jaimin D Jetly (JIRA)]

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

Jaimin D Jetly updated AMBARI-18173:

Resolution: Fixed
Status: Resolved  (was: Patch Available)

Received +1 on review board.
Patch committed to trunk and branch-2.4

> HSI is not started even when "Enable Interactive Query" is set to Yes in 
> installer wizard
> -
>
> Key: AMBARI-18173
> URL: https://issues.apache.org/jira/browse/AMBARI-18173
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Jaimin D Jetly
>Assignee: Jaimin D Jetly
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-18173.patch
>
>




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

[jira] [Updated] (AMBARI-18173) HSI is not started even when "Enable Interactive Query" is set to Yes

[Jaimin D Jetly (JIRA)]

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

Jaimin D Jetly updated AMBARI-18173:

Status: Patch Available  (was: Open)

> HSI is not started even when "Enable Interactive Query" is set to Yes
> -
>
> Key: AMBARI-18173
> URL: https://issues.apache.org/jira/browse/AMBARI-18173
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Jaimin D Jetly
>Assignee: Jaimin D Jetly
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-18173.patch
>
>




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

[jira] [Created] (AMBARI-18176) Support removing Hive Metastore password from Hive configuration

[Bing Li (JIRA)]

Bing Li created AMBARI-18176:


 Summary: Support removing Hive Metastore password from Hive 
configuration
 Key: AMBARI-18176
 URL: https://issues.apache.org/jira/browse/AMBARI-18176
 Project: Ambari
  Issue Type: Improvement
  Components: ambari-server
Affects Versions: 2.2.0
Reporter: Bing Li


Based on Hive wiki:
https://cwiki.apache.org/confluence/display/Hive/AdminManual+Configuration#AdminManualConfiguration-RemovingHiveMetastorePasswordfromHiveConfiguration

Hive supports to use a CredentialProvider to handle storing/retrieval of 
passwords from 0.14.0 (Hadoop version should be 2.6.0+).

Current Ambari doesn't support it, because we can't delete a default property 
or set an empty value to a property on UI.

In order to improve this, 
1. Ambari could have the user to specify whether to use a Hadoop credential 
store for the password 
2. If the user selects yes, then Ambari should show an input field for 
providing the credential file location
3. The password field can stay, but depending on whether the credential store 
is selected or not, the password should be written to either the credential 
store or the hive-site.xml directly (this takes care of the user changing the 
password).




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

[jira] [Commented] (AMBARI-18074) umask value should less than 18 when check hosts in the step 3 of install ambari

[wuhui (JIRA)]

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

wuhui commented on AMBARI-18074:


Dear Jayush Luniya：
  Thanks for your attention！should I upload a new patch according trunk？ 

> umask value should less than 18 when check hosts in the step 3 of install 
> ambari
> 
>
> Key: AMBARI-18074
> URL: https://issues.apache.org/jira/browse/AMBARI-18074
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: trunk
>Reporter: wuhui
> Fix For: trunk
>
> Attachments: AMBARI-18074.patch
>
>
> if umask value big than 18 ,some hdfs user may not have the privilege to 
> operate the hdfs system.
> so i suggest to notice people to revise the umask value when the umask value 
> it not narmal in the step 3 of host check.



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

[jira] [Commented] (AMBARI-17805) the history versions of config can't be showed in the screen fully

[wuhui (JIRA)]

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

wuhui commented on AMBARI-17805:


Dear Jayush Luniya：
  Thanks for your attention！should I upload a new patch according trunk？

> the history versions of config can't be showed in the screen fully
> --
>
> Key: AMBARI-17805
> URL: https://issues.apache.org/jira/browse/AMBARI-17805
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.2.2
>Reporter: wuhui
> Fix For: trunk
>
> Attachments: AMBARI-17805.patch, A_WQ6V3PP70}SPDU09QZG8P.jpg, 
> [Q{M}H{{3JVL%U(A8${UMWF.png, page_turn_1.png, page_turn_2.png
>
>
> when the number of config version is more than twenty-one，type the button 
> ‘show more config history’，the configs can't be show in the screen fully。
> if you want to show the detail of the bug，please see the picture of below！



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

[jira] [Created] (AMBARI-18174) Add configuration and monitoring for XeonPhi

[Ben Markham (JIRA)]

Ben Markham created AMBARI-18174:


 Summary: Add configuration and monitoring for XeonPhi
 Key: AMBARI-18174
 URL: https://issues.apache.org/jira/browse/AMBARI-18174
 Project: Ambari
  Issue Type: Epic
Reporter: Ben Markham






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

[jira] [Created] (AMBARI-18175) Add configuration and monitoring for GPU

[Ben Markham (JIRA)]

Ben Markham created AMBARI-18175:


 Summary: Add configuration and monitoring for GPU
 Key: AMBARI-18175
 URL: https://issues.apache.org/jira/browse/AMBARI-18175
 Project: Ambari
  Issue Type: Epic
Reporter: Ben Markham






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

[jira] [Updated] (AMBARI-17875) Add configuration to monitoring to LustreFS

[Ben Markham (JIRA)]

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

Ben Markham updated AMBARI-17875:
-
Summary: Add configuration to monitoring to LustreFS  (was: Add monitoring 
to LustreFS, InfiniBand, GPU, Xeon Phi)

> Add configuration to monitoring to LustreFS
> ---
>
> Key: AMBARI-17875
> URL: https://issues.apache.org/jira/browse/AMBARI-17875
> Project: Ambari
>  Issue Type: Epic
>  Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Ben Markham
>Assignee: Ben Markham
>




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

[jira] [Commented] (AMBARI-18173) HSI is not started even when "Enable Interactive Query" is set to Yes

[Jaimin D Jetly (JIRA)]

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

Jaimin D Jetly commented on AMBARI-18173:
-

This is a regression and blocks one of the flow of enabling "Enable Interactive 
Qeuery" (LLAP) feature. So needs to be addressed in 2.4.0
cc [~jluniya]

> HSI is not started even when "Enable Interactive Query" is set to Yes
> -
>
> Key: AMBARI-18173
> URL: https://issues.apache.org/jira/browse/AMBARI-18173
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Jaimin D Jetly
>Assignee: Jaimin D Jetly
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-18173.patch
>
>




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

[jira] [Updated] (AMBARI-18173) HSI is not started even when "Enable Interactive Query" is set to Yes

[Jaimin D Jetly (JIRA)]

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

Jaimin D Jetly updated AMBARI-18173:

Attachment: AMBARI-18173.patch

> HSI is not started even when "Enable Interactive Query" is set to Yes
> -
>
> Key: AMBARI-18173
> URL: https://issues.apache.org/jira/browse/AMBARI-18173
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Jaimin D Jetly
>Assignee: Jaimin D Jetly
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-18173.patch
>
>




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

[jira] [Updated] (AMBARI-18173) HSI is not started even when "Enable Interactive Query" is set to Yes

[Jaimin D Jetly (JIRA)]

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

Jaimin D Jetly updated AMBARI-18173:

Summary: HSI is not started even when "Enable Interactive Query" is set to 
Yes  (was: HSI is not started even when enable_hive_interactive is set to Yes)

> HSI is not started even when "Enable Interactive Query" is set to Yes
> -
>
> Key: AMBARI-18173
> URL: https://issues.apache.org/jira/browse/AMBARI-18173
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Jaimin D Jetly
>Assignee: Jaimin D Jetly
>Priority: Blocker
> Fix For: 2.4.0
>
>




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

[jira] [Created] (AMBARI-18173) HSI is not started even when enable_hive_interactive is set to Yes

[Jaimin D Jetly (JIRA)]

Jaimin D Jetly created AMBARI-18173:
---

 Summary: HSI is not started even when enable_hive_interactive is 
set to Yes
 Key: AMBARI-18173
 URL: https://issues.apache.org/jira/browse/AMBARI-18173
 Project: Ambari
  Issue Type: Bug
  Components: ambari-web
Affects Versions: 2.4.0
Reporter: Jaimin D Jetly
Assignee: Jaimin D Jetly
Priority: Blocker
 Fix For: 2.4.0






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

[jira] [Updated] (AMBARI-18151) Oozie Hive actions fail when Atlas is installed since Atlas Hive Hooks need to be copied to Oozie Share Lib in HDFS

[Alejandro Fernandez (JIRA)]

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

Alejandro Fernandez updated AMBARI-18151:
-
Attachment: AMBARI-18151.patch

> Oozie Hive actions fail when Atlas is installed since Atlas Hive Hooks need 
> to be copied to Oozie Share Lib in HDFS
> ---
>
> Key: AMBARI-18151
> URL: https://issues.apache.org/jira/browse/AMBARI-18151
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.4.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Blocker
>  Labels: 240RMApproved
> Fix For: 2.4.0
>
> Attachments: AMBARI-18151.patch
>
>
> After the Falcon-Atlas hook has been enabled, the following properties are 
> added.
> startup.properties
> {noformat}
> *.application.services=org.apache.falcon.security.AuthenticationInitializationService,\
>   org.apache.falcon.workflow.WorkflowJobEndNotificationService, \
>   org.apache.falcon.service.ProcessSubscriberService,\
>   org.apache.falcon.extensions.ExtensionService,\
>   org.apache.falcon.service.LifecyclePolicyMap,\
>   org.apache.falcon.entity.store.ConfigurationStore,\
>   org.apache.falcon.rerun.service.RetryService,\
>   org.apache.falcon.rerun.service.LateRunService,\
>   org.apache.falcon.service.LogCleanupService,\
>   org.apache.falcon.metadata.MetadataMappingService,\
> org.apache.atlas.falcon.service.AtlasService
> {noformat}
> falcon-env.sh
> {noformat}
> # Add the Atlas Falcon hook to the Falcon classpath
> export 
> FALCON_EXTRA_CLASS_PATH=/usr/hdp/current/atlas-client/hook/falcon/*:${FALCON_EXTRA_CLASS_PATH}
> {noformat} 
> Whenever Oozie submits Hive actions, they fail and the application logs show
> {noformat}
> hive.exec.post.hooks Class not found:org.apache.atlas.hive.hook.HiveHook
> FAILED: Hive Internal Error: 
> java.lang.ClassNotFoundException(org.apache.atlas.hive.hook.HiveHook)
> java.lang.ClassNotFoundException: org.apache.atlas.hive.hook.HiveHook
>   at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
>   at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
>   at java.lang.Class.forName0(Native Method)
>   at java.lang.Class.forName(Class.java:348)
>   at org.apache.hadoop.hive.ql.hooks.HookUtils.getHooks(HookUtils.java:60)
>   at org.apache.hadoop.hive.ql.Driver.getHooks(Driver.java:1384)
>   at org.apache.hadoop.hive.ql.Driver.getHooks(Driver.java:1368)
>   at org.apache.hadoop.hive.ql.Driver.execute(Driver.java:1595)
>   at org.apache.hadoop.hive.ql.Driver.runInternal(Driver.java:1289)
>   at org.apache.hadoop.hive.ql.Driver.run(Driver.java:1156)
>   at org.apache.hadoop.hive.ql.Driver.run(Driver.java:1146)
>   at 
> org.apache.hadoop.hive.cli.CliDriver.processLocalCmd(CliDriver.java:216)
>   at org.apache.hadoop.hive.cli.CliDriver.processCmd(CliDriver.java:168)
>   at org.apache.hadoop.hive.cli.CliDriver.processLine(CliDriver.java:379)
>   at org.apache.hadoop.hive.cli.CliDriver.processLine(CliDriver.java:314)
>   at 
> org.apache.hadoop.hive.cli.CliDriver.processReader(CliDriver.java:412)
>   at org.apache.hadoop.hive.cli.CliDriver.processFile(CliDriver.java:428)
>   at 
> org.apache.hadoop.hive.cli.CliDriver.executeDriver(CliDriver.java:717)
>   at org.apache.hadoop.hive.cli.CliDriver.run(CliDriver.java:684)
>   at org.apache.hadoop.hive.cli.CliDriver.main(CliDriver.java:624)
>   at org.apache.oozie.action.hadoop.HiveMain.runHive(HiveMain.java:335)
>   at org.apache.oozie.action.hadoop.HiveMain.run(HiveMain.java:312)
>   at org.apache.oozie.action.hadoop.LauncherMain.run(LauncherMain.java:51)
>   at org.apache.oozie.action.hadoop.HiveMain.main(HiveMain.java:69)
>   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.oozie.action.hadoop.LauncherMapper.map(LauncherMapper.java:242)
>   at org.apache.hadoop.mapred.MapRunner.run(MapRunner.java:54)
>   at org.apache.hadoop.mapred.MapTask.runOldMapper(MapTask.java:453)
>   at org.apache.hadoop.mapred.MapTask.run(MapTask.java:343)
>   at org.apache.hadoop.mapred.YarnChild$2.run(YarnChild.java:168)
>   at java.security.AccessController.doPrivileged(Native Method)
>   at 

[jira] [Updated] (AMBARI-18151) Oozie Hive actions fail when Atlas is installed since Atlas Hive Hooks need to be copied to Oozie Share Lib in HDFS

[Alejandro Fernandez (JIRA)]

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

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

> Oozie Hive actions fail when Atlas is installed since Atlas Hive Hooks need 
> to be copied to Oozie Share Lib in HDFS
> ---
>
> Key: AMBARI-18151
> URL: https://issues.apache.org/jira/browse/AMBARI-18151
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.4.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Blocker
>  Labels: 240RMApproved
> Fix For: 2.4.0
>
> Attachments: AMBARI-18151.patch
>
>
> After the Falcon-Atlas hook has been enabled, the following properties are 
> added.
> startup.properties
> {noformat}
> *.application.services=org.apache.falcon.security.AuthenticationInitializationService,\
>   org.apache.falcon.workflow.WorkflowJobEndNotificationService, \
>   org.apache.falcon.service.ProcessSubscriberService,\
>   org.apache.falcon.extensions.ExtensionService,\
>   org.apache.falcon.service.LifecyclePolicyMap,\
>   org.apache.falcon.entity.store.ConfigurationStore,\
>   org.apache.falcon.rerun.service.RetryService,\
>   org.apache.falcon.rerun.service.LateRunService,\
>   org.apache.falcon.service.LogCleanupService,\
>   org.apache.falcon.metadata.MetadataMappingService,\
> org.apache.atlas.falcon.service.AtlasService
> {noformat}
> falcon-env.sh
> {noformat}
> # Add the Atlas Falcon hook to the Falcon classpath
> export 
> FALCON_EXTRA_CLASS_PATH=/usr/hdp/current/atlas-client/hook/falcon/*:${FALCON_EXTRA_CLASS_PATH}
> {noformat} 
> Whenever Oozie submits Hive actions, they fail and the application logs show
> {noformat}
> hive.exec.post.hooks Class not found:org.apache.atlas.hive.hook.HiveHook
> FAILED: Hive Internal Error: 
> java.lang.ClassNotFoundException(org.apache.atlas.hive.hook.HiveHook)
> java.lang.ClassNotFoundException: org.apache.atlas.hive.hook.HiveHook
>   at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
>   at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
>   at java.lang.Class.forName0(Native Method)
>   at java.lang.Class.forName(Class.java:348)
>   at org.apache.hadoop.hive.ql.hooks.HookUtils.getHooks(HookUtils.java:60)
>   at org.apache.hadoop.hive.ql.Driver.getHooks(Driver.java:1384)
>   at org.apache.hadoop.hive.ql.Driver.getHooks(Driver.java:1368)
>   at org.apache.hadoop.hive.ql.Driver.execute(Driver.java:1595)
>   at org.apache.hadoop.hive.ql.Driver.runInternal(Driver.java:1289)
>   at org.apache.hadoop.hive.ql.Driver.run(Driver.java:1156)
>   at org.apache.hadoop.hive.ql.Driver.run(Driver.java:1146)
>   at 
> org.apache.hadoop.hive.cli.CliDriver.processLocalCmd(CliDriver.java:216)
>   at org.apache.hadoop.hive.cli.CliDriver.processCmd(CliDriver.java:168)
>   at org.apache.hadoop.hive.cli.CliDriver.processLine(CliDriver.java:379)
>   at org.apache.hadoop.hive.cli.CliDriver.processLine(CliDriver.java:314)
>   at 
> org.apache.hadoop.hive.cli.CliDriver.processReader(CliDriver.java:412)
>   at org.apache.hadoop.hive.cli.CliDriver.processFile(CliDriver.java:428)
>   at 
> org.apache.hadoop.hive.cli.CliDriver.executeDriver(CliDriver.java:717)
>   at org.apache.hadoop.hive.cli.CliDriver.run(CliDriver.java:684)
>   at org.apache.hadoop.hive.cli.CliDriver.main(CliDriver.java:624)
>   at org.apache.oozie.action.hadoop.HiveMain.runHive(HiveMain.java:335)
>   at org.apache.oozie.action.hadoop.HiveMain.run(HiveMain.java:312)
>   at org.apache.oozie.action.hadoop.LauncherMain.run(LauncherMain.java:51)
>   at org.apache.oozie.action.hadoop.HiveMain.main(HiveMain.java:69)
>   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.oozie.action.hadoop.LauncherMapper.map(LauncherMapper.java:242)
>   at org.apache.hadoop.mapred.MapRunner.run(MapRunner.java:54)
>   at org.apache.hadoop.mapred.MapTask.runOldMapper(MapTask.java:453)
>   at org.apache.hadoop.mapred.MapTask.run(MapTask.java:343)
>   at org.apache.hadoop.mapred.YarnChild$2.run(YarnChild.java:168)
>   at java.security.AccessController.doPrivileged(Native Method)
>   at 

[jira] [Updated] (AMBARI-18151) Oozie Hive actions fail when Atlas is installed since Atlas Hive Hooks need to be copied to Oozie Share Lib in HDFS

[Alejandro Fernandez (JIRA)]

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

Alejandro Fernandez updated AMBARI-18151:
-
Attachment: (was: AMBARI-18151.patch)

> Oozie Hive actions fail when Atlas is installed since Atlas Hive Hooks need 
> to be copied to Oozie Share Lib in HDFS
> ---
>
> Key: AMBARI-18151
> URL: https://issues.apache.org/jira/browse/AMBARI-18151
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.4.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Blocker
>  Labels: 240RMApproved
> Fix For: 2.4.0
>
> Attachments: AMBARI-18151.patch
>
>
> After the Falcon-Atlas hook has been enabled, the following properties are 
> added.
> startup.properties
> {noformat}
> *.application.services=org.apache.falcon.security.AuthenticationInitializationService,\
>   org.apache.falcon.workflow.WorkflowJobEndNotificationService, \
>   org.apache.falcon.service.ProcessSubscriberService,\
>   org.apache.falcon.extensions.ExtensionService,\
>   org.apache.falcon.service.LifecyclePolicyMap,\
>   org.apache.falcon.entity.store.ConfigurationStore,\
>   org.apache.falcon.rerun.service.RetryService,\
>   org.apache.falcon.rerun.service.LateRunService,\
>   org.apache.falcon.service.LogCleanupService,\
>   org.apache.falcon.metadata.MetadataMappingService,\
> org.apache.atlas.falcon.service.AtlasService
> {noformat}
> falcon-env.sh
> {noformat}
> # Add the Atlas Falcon hook to the Falcon classpath
> export 
> FALCON_EXTRA_CLASS_PATH=/usr/hdp/current/atlas-client/hook/falcon/*:${FALCON_EXTRA_CLASS_PATH}
> {noformat} 
> Whenever Oozie submits Hive actions, they fail and the application logs show
> {noformat}
> hive.exec.post.hooks Class not found:org.apache.atlas.hive.hook.HiveHook
> FAILED: Hive Internal Error: 
> java.lang.ClassNotFoundException(org.apache.atlas.hive.hook.HiveHook)
> java.lang.ClassNotFoundException: org.apache.atlas.hive.hook.HiveHook
>   at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
>   at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
>   at java.lang.Class.forName0(Native Method)
>   at java.lang.Class.forName(Class.java:348)
>   at org.apache.hadoop.hive.ql.hooks.HookUtils.getHooks(HookUtils.java:60)
>   at org.apache.hadoop.hive.ql.Driver.getHooks(Driver.java:1384)
>   at org.apache.hadoop.hive.ql.Driver.getHooks(Driver.java:1368)
>   at org.apache.hadoop.hive.ql.Driver.execute(Driver.java:1595)
>   at org.apache.hadoop.hive.ql.Driver.runInternal(Driver.java:1289)
>   at org.apache.hadoop.hive.ql.Driver.run(Driver.java:1156)
>   at org.apache.hadoop.hive.ql.Driver.run(Driver.java:1146)
>   at 
> org.apache.hadoop.hive.cli.CliDriver.processLocalCmd(CliDriver.java:216)
>   at org.apache.hadoop.hive.cli.CliDriver.processCmd(CliDriver.java:168)
>   at org.apache.hadoop.hive.cli.CliDriver.processLine(CliDriver.java:379)
>   at org.apache.hadoop.hive.cli.CliDriver.processLine(CliDriver.java:314)
>   at 
> org.apache.hadoop.hive.cli.CliDriver.processReader(CliDriver.java:412)
>   at org.apache.hadoop.hive.cli.CliDriver.processFile(CliDriver.java:428)
>   at 
> org.apache.hadoop.hive.cli.CliDriver.executeDriver(CliDriver.java:717)
>   at org.apache.hadoop.hive.cli.CliDriver.run(CliDriver.java:684)
>   at org.apache.hadoop.hive.cli.CliDriver.main(CliDriver.java:624)
>   at org.apache.oozie.action.hadoop.HiveMain.runHive(HiveMain.java:335)
>   at org.apache.oozie.action.hadoop.HiveMain.run(HiveMain.java:312)
>   at org.apache.oozie.action.hadoop.LauncherMain.run(LauncherMain.java:51)
>   at org.apache.oozie.action.hadoop.HiveMain.main(HiveMain.java:69)
>   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.oozie.action.hadoop.LauncherMapper.map(LauncherMapper.java:242)
>   at org.apache.hadoop.mapred.MapRunner.run(MapRunner.java:54)
>   at org.apache.hadoop.mapred.MapTask.runOldMapper(MapTask.java:453)
>   at org.apache.hadoop.mapred.MapTask.run(MapTask.java:343)
>   at org.apache.hadoop.mapred.YarnChild$2.run(YarnChild.java:168)
>   at java.security.AccessController.doPrivileged(Native Method)
>   at 

[jira] [Updated] (AMBARI-18172) Hive Service check is failing after moving webhcat server

[Zhe (Joe) Wang (JIRA)]

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

Zhe (Joe) Wang updated AMBARI-18172:

Status: Patch Available  (was: Open)

> Hive Service check is failing after moving webhcat server
> -
>
> Key: AMBARI-18172
> URL: https://issues.apache.org/jira/browse/AMBARI-18172
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Zhe (Joe) Wang
>Assignee: Zhe (Joe) Wang
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-18172.v0.patch
>
>
> Moving of webhcat server should change proxyuser configs for hosts in 
> core-site for webhcat user in non-kerberozed environment. Not doing so is 
> causing this issue.



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

[jira] [Updated] (AMBARI-18172) Hive Service check is failing after moving webhcat server

[Zhe (Joe) Wang (JIRA)]

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

Zhe (Joe) Wang updated AMBARI-18172:

Attachment: AMBARI-18172.v0.patch

Modified unit test.
Local ambari-web test passed.
29932 tests complete (27 seconds)
  154 tests pending
Manual testing done.

> Hive Service check is failing after moving webhcat server
> -
>
> Key: AMBARI-18172
> URL: https://issues.apache.org/jira/browse/AMBARI-18172
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Zhe (Joe) Wang
>Assignee: Zhe (Joe) Wang
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-18172.v0.patch
>
>
> Moving of webhcat server should change proxyuser configs for hosts in 
> core-site for webhcat user in non-kerberozed environment. Not doing so is 
> causing this issue.



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

[jira] [Commented] (AMBARI-18126) Refactor Configuration To Allow For Generation Of Documentation

[Masahiro Tanaka (JIRA)]

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

Masahiro Tanaka commented on AMBARI-18126:
--

Thanks!

> Refactor Configuration To Allow For Generation Of Documentation
> ---
>
> Key: AMBARI-18126
> URL: https://issues.apache.org/jira/browse/AMBARI-18126
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: trunk
>
> Attachments: AMBARI-18126.patch
>
>
> As part of the work for AMBARI-18089, all of the potential properties from 
> {{ambari.properties}} need a way to be organized and queried in order to 
> generate documentation. 
> This Jira proposes to change our disorganized String/String (key/default) 
> structure found in {{Configuration}}, and instead, have a strongly-coupled 
> relationship between key/default/type. 
> Additionally, expose a way to provide extra information in the markdown 
> (similar to JavaDoc, but geared more for users and not developers).



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

[jira] [Commented] (AMBARI-17213) Create ambari workflow designer contrib view

[Christine (JIRA)]

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

Christine commented on AMBARI-17213:


Description of Workflow Designer objectives

> Create ambari workflow designer contrib view
> 
>
> Key: AMBARI-17213
> URL: https://issues.apache.org/jira/browse/AMBARI-17213
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.4.0
>Reporter: Venkat Ranganathan
>Assignee: Venkat Ranganathan
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17213.patch
>
>
> Need to provide workflow designer as a contributed view in ambari



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

[jira] [Commented] (AMBARI-18166) configs.sh script updates

[Aravindan Vijayan (JIRA)]

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

Aravindan Vijayan commented on AMBARI-18166:


+1

> configs.sh script updates
> -
>
> Key: AMBARI-18166
> URL: https://issues.apache.org/jira/browse/AMBARI-18166
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Affects Versions: 2.0.0
>Reporter: Siddharth Wagle
> Fix For: 2.5.0
>
> Attachments: AMBARI-18166.patch
>
>
> This utility script is widely used by for change configs.
> Improvements:
> - Support importing of xml files along with json formatted config content
> - Infer property attributes like final from the xml file
> - Allow accepting password as hidden field



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

[jira] [Commented] (AMBARI-18167) RU: Kafka brokers restart was stopped during downgrade cluster

[Hudson (JIRA)]

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

Hudson commented on AMBARI-18167:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5536 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5536/])
AMBARI-18167: RU: Kafka brokers restart was stopped during downgrade (jluniya: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=43457696137486daa338f39cef5e899554f025b3])
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.5.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/upgrade-2.5.xml


> RU: Kafka brokers restart was stopped during downgrade cluster
> --
>
> Key: AMBARI-18167
> URL: https://issues.apache.org/jira/browse/AMBARI-18167
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
>Priority: Blocker
>  Labels: 240RMApproved
> Fix For: 2.4.0
>
> Attachments: AMBARI-18167.patch
>
>
> Kafka broker restart failed due to below error:
> {noformat}
> raise Fail("Configuration parameter '" + self.name + "' was not found in 
> configurations dictionary!")
> resource_management.core.exceptions.Fail: Configuration parameter 
> 'xasecure.audit.destination.db' was not found in configurations dictionary!
> {noformat}
> Solution:
> During RU downgrade,  runs on downgrade as well, which deleted 
> {{xasecure.audit.destination.db}} config property. 
> {noformat}
> 
>id="hdp_2_5_0_0_remove_ranger_kafka_audit_db" />
> 
> {noformat}
> Need to override it with a blank  element.



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

[jira] [Updated] (AMBARI-17591) Collect JVM Heap, GC and thread pool metrics from Ambari Server and push to AMS

[Li-Wei Tseng (JIRA)]

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

Li-Wei Tseng updated AMBARI-17591:
--
Attachment: AMBARI-17591.patch

> Collect JVM Heap, GC and thread pool metrics from Ambari Server and push to 
> AMS
> ---
>
> Key: AMBARI-17591
> URL: https://issues.apache.org/jira/browse/AMBARI-17591
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-metrics, ambari-server
>Affects Versions: 3.0.0
>Reporter: Aravindan Vijayan
>Assignee: Li-Wei Tseng
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: AMBARI-17591.patch
>
>
> 1. Collect JVM Heap, GC and thread pool metrics from Ambari Server
> 2. Implement/Refine an AmbariServer Metrics Sink to push metrics to AMS.
> 3. Visualize using Grafana



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

[jira] [Updated] (AMBARI-17591) Collect JVM Heap, GC and thread pool metrics from Ambari Server and push to AMS

[Li-Wei Tseng (JIRA)]

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

Li-Wei Tseng updated AMBARI-17591:
--
Status: Patch Available  (was: Open)

> Collect JVM Heap, GC and thread pool metrics from Ambari Server and push to 
> AMS
> ---
>
> Key: AMBARI-17591
> URL: https://issues.apache.org/jira/browse/AMBARI-17591
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-metrics, ambari-server
>Affects Versions: 3.0.0
>Reporter: Aravindan Vijayan
>Assignee: Li-Wei Tseng
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: AMBARI-17591.patch
>
>
> 1. Collect JVM Heap, GC and thread pool metrics from Ambari Server
> 2. Implement/Refine an AmbariServer Metrics Sink to push metrics to AMS.
> 3. Visualize using Grafana



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

[jira] [Updated] (AMBARI-18170) Kafka Metrics do not show up in AMS HA enabled cluster

[Aravindan Vijayan (JIRA)]

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

Aravindan Vijayan updated AMBARI-18170:
---
Status: In Progress  (was: Patch Available)

> Kafka Metrics do not show up in AMS HA enabled cluster
> --
>
> Key: AMBARI-18170
> URL: https://issues.apache.org/jira/browse/AMBARI-18170
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics
>Affects Versions: trunk
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Critical
> Fix For: trunk
>
> Attachments: AMBARI-18170.patch
>
>
> No kafka metrics are seen in trunk deployments.



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

[jira] [Commented] (AMBARI-18171) AMS, Accumulo, Hive metrics do not show up in AMS HA clusters.

[Siddharth Wagle (JIRA)]

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

Siddharth Wagle commented on AMBARI-18171:
--

+1 LGTM

> AMS, Accumulo, Hive metrics do not show up in AMS HA clusters.
> --
>
> Key: AMBARI-18171
> URL: https://issues.apache.org/jira/browse/AMBARI-18171
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics
>Affects Versions: trunk
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Critical
> Fix For: trunk
>
> Attachments: AMBARI-18171.patch
>
>
> There is an issue in the jinja template that causes the the metrics collector 
> protocol to be duplicated.



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

[jira] [Updated] (AMBARI-18171) AMS, Accumulo, Hive metrics do not show up in AMS HA clusters.

[Aravindan Vijayan (JIRA)]

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

Aravindan Vijayan updated AMBARI-18171:
---
Status: Patch Available  (was: Open)

> AMS, Accumulo, Hive metrics do not show up in AMS HA clusters.
> --
>
> Key: AMBARI-18171
> URL: https://issues.apache.org/jira/browse/AMBARI-18171
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics
>Affects Versions: trunk
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Critical
> Fix For: trunk
>
> Attachments: AMBARI-18171.patch
>
>
> There is an issue in the jinja template that causes the the metrics collector 
> protocol to be duplicated.



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

[jira] [Updated] (AMBARI-18170) Kafka Metrics do not show up in AMS HA enabled cluster

[Aravindan Vijayan (JIRA)]

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

Aravindan Vijayan updated AMBARI-18170:
---
Status: Patch Available  (was: Open)

> Kafka Metrics do not show up in AMS HA enabled cluster
> --
>
> Key: AMBARI-18170
> URL: https://issues.apache.org/jira/browse/AMBARI-18170
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics
>Affects Versions: trunk
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Critical
> Fix For: trunk
>
> Attachments: AMBARI-18170.patch
>
>
> No kafka metrics are seen in trunk deployments.



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

[jira] [Commented] (AMBARI-17591) Collect JVM Heap, GC and thread pool metrics from Ambari Server and push to AMS

[Aravindan Vijayan (JIRA)]

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

Aravindan Vijayan commented on AMBARI-17591:


Please attach the patch to the jira [~ltseng]

> Collect JVM Heap, GC and thread pool metrics from Ambari Server and push to 
> AMS
> ---
>
> Key: AMBARI-17591
> URL: https://issues.apache.org/jira/browse/AMBARI-17591
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-metrics, ambari-server
>Affects Versions: 3.0.0
>Reporter: Aravindan Vijayan
>Assignee: Li-Wei Tseng
>Priority: Critical
> Fix For: 3.0.0
>
>
> 1. Collect JVM Heap, GC and thread pool metrics from Ambari Server
> 2. Implement/Refine an AmbariServer Metrics Sink to push metrics to AMS.
> 3. Visualize using Grafana



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

[jira] [Updated] (AMBARI-18169) Falcon log4j configuration should be configurable via Ambari

[Venkat Ranganathan (JIRA)]

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

Venkat Ranganathan updated AMBARI-18169:

Attachment: AMBARI-18169-2.patch

> Falcon log4j configuration should be  configurable via Ambari
> -
>
> Key: AMBARI-18169
> URL: https://issues.apache.org/jira/browse/AMBARI-18169
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Venkat Ranganathan
>Assignee: Venkat Ranganathan
> Attachments: AMBARI-18169-2.patch, AMBARI-18169.patch
>
>
> The falcon log4j configuration needs to be managed by Ambari



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

[jira] [Updated] (AMBARI-18170) Kafka Metrics do not show up in AMS HA enabled cluster

[Aravindan Vijayan (JIRA)]

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

Aravindan Vijayan updated AMBARI-18170:
---
Attachment: AMBARI-18170.patch

> Kafka Metrics do not show up in AMS HA enabled cluster
> --
>
> Key: AMBARI-18170
> URL: https://issues.apache.org/jira/browse/AMBARI-18170
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics
>Affects Versions: trunk
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Critical
> Fix For: trunk
>
> Attachments: AMBARI-18170.patch
>
>
> No kafka metrics are seen in trunk deployments.



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

[jira] [Updated] (AMBARI-18171) AMS, Accumulo, Hive metrics do not show up in AMS HA clusters.

[Aravindan Vijayan (JIRA)]

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

Aravindan Vijayan updated AMBARI-18171:
---
Attachment: AMBARI-18171.patch

> AMS, Accumulo, Hive metrics do not show up in AMS HA clusters.
> --
>
> Key: AMBARI-18171
> URL: https://issues.apache.org/jira/browse/AMBARI-18171
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics
>Affects Versions: trunk
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Critical
> Fix For: trunk
>
> Attachments: AMBARI-18171.patch
>
>
> There is an issue in the jinja template that causes the the metrics collector 
> protocol to be duplicated.



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

[jira] [Updated] (AMBARI-18166) configs.sh script updates

[Siddharth Wagle (JIRA)]

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

Siddharth Wagle updated AMBARI-18166:
-
Attachment: AMBARI-18166.patch

> configs.sh script updates
> -
>
> Key: AMBARI-18166
> URL: https://issues.apache.org/jira/browse/AMBARI-18166
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Affects Versions: 2.0.0
>Reporter: Siddharth Wagle
> Fix For: 2.5.0
>
> Attachments: AMBARI-18166.patch
>
>
> This utility script is widely used by for change configs.
> Improvements:
> - Support importing of xml files along with json formatted config content
> - Infer property attributes like final from the xml file
> - Allow accepting password as hidden field



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

[jira] [Created] (AMBARI-18171) AMS, Accumulo, Hive metrics do not show up in AMS HA clusters.

[Aravindan Vijayan (JIRA)]

Aravindan Vijayan created AMBARI-18171:
--

 Summary: AMS, Accumulo, Hive metrics do not show up in AMS HA 
clusters.
 Key: AMBARI-18171
 URL: https://issues.apache.org/jira/browse/AMBARI-18171
 Project: Ambari
  Issue Type: Bug
  Components: ambari-metrics
Affects Versions: trunk
Reporter: Aravindan Vijayan
Assignee: Aravindan Vijayan
Priority: Critical
 Fix For: trunk


There is an issue in the jinja template that causes the the metrics collector 
protocol to be duplicated.



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

[jira] [Created] (AMBARI-18170) Kafka Metrics do not show up in AMS HA enabled cluster

[Aravindan Vijayan (JIRA)]

Aravindan Vijayan created AMBARI-18170:
--

 Summary: Kafka Metrics do not show up in AMS HA enabled cluster
 Key: AMBARI-18170
 URL: https://issues.apache.org/jira/browse/AMBARI-18170
 Project: Ambari
  Issue Type: Bug
  Components: ambari-metrics
Affects Versions: trunk
Reporter: Aravindan Vijayan
Assignee: Aravindan Vijayan
Priority: Critical
 Fix For: trunk


No kafka metrics are seen in trunk deployments.




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

[jira] [Updated] (AMBARI-18151) Oozie Hive actions fail when Atlas is installed since Atlas Hive Hooks need to be copied to Oozie Share Lib in HDFS

[Alejandro Fernandez (JIRA)]

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

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

> Oozie Hive actions fail when Atlas is installed since Atlas Hive Hooks need 
> to be copied to Oozie Share Lib in HDFS
> ---
>
> Key: AMBARI-18151
> URL: https://issues.apache.org/jira/browse/AMBARI-18151
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.4.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Blocker
>  Labels: 240RMApproved
> Fix For: 2.4.0
>
> Attachments: AMBARI-18151.patch
>
>
> After the Falcon-Atlas hook has been enabled, the following properties are 
> added.
> startup.properties
> {noformat}
> *.application.services=org.apache.falcon.security.AuthenticationInitializationService,\
>   org.apache.falcon.workflow.WorkflowJobEndNotificationService, \
>   org.apache.falcon.service.ProcessSubscriberService,\
>   org.apache.falcon.extensions.ExtensionService,\
>   org.apache.falcon.service.LifecyclePolicyMap,\
>   org.apache.falcon.entity.store.ConfigurationStore,\
>   org.apache.falcon.rerun.service.RetryService,\
>   org.apache.falcon.rerun.service.LateRunService,\
>   org.apache.falcon.service.LogCleanupService,\
>   org.apache.falcon.metadata.MetadataMappingService,\
> org.apache.atlas.falcon.service.AtlasService
> {noformat}
> falcon-env.sh
> {noformat}
> # Add the Atlas Falcon hook to the Falcon classpath
> export 
> FALCON_EXTRA_CLASS_PATH=/usr/hdp/current/atlas-client/hook/falcon/*:${FALCON_EXTRA_CLASS_PATH}
> {noformat} 
> Whenever Oozie submits Hive actions, they fail and the application logs show
> {noformat}
> hive.exec.post.hooks Class not found:org.apache.atlas.hive.hook.HiveHook
> FAILED: Hive Internal Error: 
> java.lang.ClassNotFoundException(org.apache.atlas.hive.hook.HiveHook)
> java.lang.ClassNotFoundException: org.apache.atlas.hive.hook.HiveHook
>   at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
>   at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
>   at java.lang.Class.forName0(Native Method)
>   at java.lang.Class.forName(Class.java:348)
>   at org.apache.hadoop.hive.ql.hooks.HookUtils.getHooks(HookUtils.java:60)
>   at org.apache.hadoop.hive.ql.Driver.getHooks(Driver.java:1384)
>   at org.apache.hadoop.hive.ql.Driver.getHooks(Driver.java:1368)
>   at org.apache.hadoop.hive.ql.Driver.execute(Driver.java:1595)
>   at org.apache.hadoop.hive.ql.Driver.runInternal(Driver.java:1289)
>   at org.apache.hadoop.hive.ql.Driver.run(Driver.java:1156)
>   at org.apache.hadoop.hive.ql.Driver.run(Driver.java:1146)
>   at 
> org.apache.hadoop.hive.cli.CliDriver.processLocalCmd(CliDriver.java:216)
>   at org.apache.hadoop.hive.cli.CliDriver.processCmd(CliDriver.java:168)
>   at org.apache.hadoop.hive.cli.CliDriver.processLine(CliDriver.java:379)
>   at org.apache.hadoop.hive.cli.CliDriver.processLine(CliDriver.java:314)
>   at 
> org.apache.hadoop.hive.cli.CliDriver.processReader(CliDriver.java:412)
>   at org.apache.hadoop.hive.cli.CliDriver.processFile(CliDriver.java:428)
>   at 
> org.apache.hadoop.hive.cli.CliDriver.executeDriver(CliDriver.java:717)
>   at org.apache.hadoop.hive.cli.CliDriver.run(CliDriver.java:684)
>   at org.apache.hadoop.hive.cli.CliDriver.main(CliDriver.java:624)
>   at org.apache.oozie.action.hadoop.HiveMain.runHive(HiveMain.java:335)
>   at org.apache.oozie.action.hadoop.HiveMain.run(HiveMain.java:312)
>   at org.apache.oozie.action.hadoop.LauncherMain.run(LauncherMain.java:51)
>   at org.apache.oozie.action.hadoop.HiveMain.main(HiveMain.java:69)
>   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.oozie.action.hadoop.LauncherMapper.map(LauncherMapper.java:242)
>   at org.apache.hadoop.mapred.MapRunner.run(MapRunner.java:54)
>   at org.apache.hadoop.mapred.MapTask.runOldMapper(MapTask.java:453)
>   at org.apache.hadoop.mapred.MapTask.run(MapTask.java:343)
>   at org.apache.hadoop.mapred.YarnChild$2.run(YarnChild.java:168)
>   at java.security.AccessController.doPrivileged(Native Method)
>   at 

[jira] [Updated] (AMBARI-18151) Oozie Hive actions fail when Atlas is installed since Atlas Hive Hooks need to be copied to Oozie Share Lib in HDFS

[Alejandro Fernandez (JIRA)]

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

Alejandro Fernandez updated AMBARI-18151:
-
Attachment: AMBARI-18151.patch

> Oozie Hive actions fail when Atlas is installed since Atlas Hive Hooks need 
> to be copied to Oozie Share Lib in HDFS
> ---
>
> Key: AMBARI-18151
> URL: https://issues.apache.org/jira/browse/AMBARI-18151
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.4.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Blocker
>  Labels: 240RMApproved
> Fix For: 2.4.0
>
> Attachments: AMBARI-18151.patch
>
>
> After the Falcon-Atlas hook has been enabled, the following properties are 
> added.
> startup.properties
> {noformat}
> *.application.services=org.apache.falcon.security.AuthenticationInitializationService,\
>   org.apache.falcon.workflow.WorkflowJobEndNotificationService, \
>   org.apache.falcon.service.ProcessSubscriberService,\
>   org.apache.falcon.extensions.ExtensionService,\
>   org.apache.falcon.service.LifecyclePolicyMap,\
>   org.apache.falcon.entity.store.ConfigurationStore,\
>   org.apache.falcon.rerun.service.RetryService,\
>   org.apache.falcon.rerun.service.LateRunService,\
>   org.apache.falcon.service.LogCleanupService,\
>   org.apache.falcon.metadata.MetadataMappingService,\
> org.apache.atlas.falcon.service.AtlasService
> {noformat}
> falcon-env.sh
> {noformat}
> # Add the Atlas Falcon hook to the Falcon classpath
> export 
> FALCON_EXTRA_CLASS_PATH=/usr/hdp/current/atlas-client/hook/falcon/*:${FALCON_EXTRA_CLASS_PATH}
> {noformat} 
> Whenever Oozie submits Hive actions, they fail and the application logs show
> {noformat}
> hive.exec.post.hooks Class not found:org.apache.atlas.hive.hook.HiveHook
> FAILED: Hive Internal Error: 
> java.lang.ClassNotFoundException(org.apache.atlas.hive.hook.HiveHook)
> java.lang.ClassNotFoundException: org.apache.atlas.hive.hook.HiveHook
>   at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
>   at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
>   at java.lang.Class.forName0(Native Method)
>   at java.lang.Class.forName(Class.java:348)
>   at org.apache.hadoop.hive.ql.hooks.HookUtils.getHooks(HookUtils.java:60)
>   at org.apache.hadoop.hive.ql.Driver.getHooks(Driver.java:1384)
>   at org.apache.hadoop.hive.ql.Driver.getHooks(Driver.java:1368)
>   at org.apache.hadoop.hive.ql.Driver.execute(Driver.java:1595)
>   at org.apache.hadoop.hive.ql.Driver.runInternal(Driver.java:1289)
>   at org.apache.hadoop.hive.ql.Driver.run(Driver.java:1156)
>   at org.apache.hadoop.hive.ql.Driver.run(Driver.java:1146)
>   at 
> org.apache.hadoop.hive.cli.CliDriver.processLocalCmd(CliDriver.java:216)
>   at org.apache.hadoop.hive.cli.CliDriver.processCmd(CliDriver.java:168)
>   at org.apache.hadoop.hive.cli.CliDriver.processLine(CliDriver.java:379)
>   at org.apache.hadoop.hive.cli.CliDriver.processLine(CliDriver.java:314)
>   at 
> org.apache.hadoop.hive.cli.CliDriver.processReader(CliDriver.java:412)
>   at org.apache.hadoop.hive.cli.CliDriver.processFile(CliDriver.java:428)
>   at 
> org.apache.hadoop.hive.cli.CliDriver.executeDriver(CliDriver.java:717)
>   at org.apache.hadoop.hive.cli.CliDriver.run(CliDriver.java:684)
>   at org.apache.hadoop.hive.cli.CliDriver.main(CliDriver.java:624)
>   at org.apache.oozie.action.hadoop.HiveMain.runHive(HiveMain.java:335)
>   at org.apache.oozie.action.hadoop.HiveMain.run(HiveMain.java:312)
>   at org.apache.oozie.action.hadoop.LauncherMain.run(LauncherMain.java:51)
>   at org.apache.oozie.action.hadoop.HiveMain.main(HiveMain.java:69)
>   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.oozie.action.hadoop.LauncherMapper.map(LauncherMapper.java:242)
>   at org.apache.hadoop.mapred.MapRunner.run(MapRunner.java:54)
>   at org.apache.hadoop.mapred.MapTask.runOldMapper(MapTask.java:453)
>   at org.apache.hadoop.mapred.MapTask.run(MapTask.java:343)
>   at org.apache.hadoop.mapred.YarnChild$2.run(YarnChild.java:168)
>   at java.security.AccessController.doPrivileged(Native Method)
>   at 

[jira] [Updated] (AMBARI-18151) Oozie Hive actions fail when Atlas is installed since Atlas Hive Hooks need to be copied to Oozie Share Lib in HDFS

[Alejandro Fernandez (JIRA)]

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

Alejandro Fernandez updated AMBARI-18151:
-
Attachment: (was: AMBARI-18151.patch)

> Oozie Hive actions fail when Atlas is installed since Atlas Hive Hooks need 
> to be copied to Oozie Share Lib in HDFS
> ---
>
> Key: AMBARI-18151
> URL: https://issues.apache.org/jira/browse/AMBARI-18151
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.4.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Blocker
>  Labels: 240RMApproved
> Fix For: 2.4.0
>
>
> After the Falcon-Atlas hook has been enabled, the following properties are 
> added.
> startup.properties
> {noformat}
> *.application.services=org.apache.falcon.security.AuthenticationInitializationService,\
>   org.apache.falcon.workflow.WorkflowJobEndNotificationService, \
>   org.apache.falcon.service.ProcessSubscriberService,\
>   org.apache.falcon.extensions.ExtensionService,\
>   org.apache.falcon.service.LifecyclePolicyMap,\
>   org.apache.falcon.entity.store.ConfigurationStore,\
>   org.apache.falcon.rerun.service.RetryService,\
>   org.apache.falcon.rerun.service.LateRunService,\
>   org.apache.falcon.service.LogCleanupService,\
>   org.apache.falcon.metadata.MetadataMappingService,\
> org.apache.atlas.falcon.service.AtlasService
> {noformat}
> falcon-env.sh
> {noformat}
> # Add the Atlas Falcon hook to the Falcon classpath
> export 
> FALCON_EXTRA_CLASS_PATH=/usr/hdp/current/atlas-client/hook/falcon/*:${FALCON_EXTRA_CLASS_PATH}
> {noformat} 
> Whenever Oozie submits Hive actions, they fail and the application logs show
> {noformat}
> hive.exec.post.hooks Class not found:org.apache.atlas.hive.hook.HiveHook
> FAILED: Hive Internal Error: 
> java.lang.ClassNotFoundException(org.apache.atlas.hive.hook.HiveHook)
> java.lang.ClassNotFoundException: org.apache.atlas.hive.hook.HiveHook
>   at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
>   at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
>   at java.lang.Class.forName0(Native Method)
>   at java.lang.Class.forName(Class.java:348)
>   at org.apache.hadoop.hive.ql.hooks.HookUtils.getHooks(HookUtils.java:60)
>   at org.apache.hadoop.hive.ql.Driver.getHooks(Driver.java:1384)
>   at org.apache.hadoop.hive.ql.Driver.getHooks(Driver.java:1368)
>   at org.apache.hadoop.hive.ql.Driver.execute(Driver.java:1595)
>   at org.apache.hadoop.hive.ql.Driver.runInternal(Driver.java:1289)
>   at org.apache.hadoop.hive.ql.Driver.run(Driver.java:1156)
>   at org.apache.hadoop.hive.ql.Driver.run(Driver.java:1146)
>   at 
> org.apache.hadoop.hive.cli.CliDriver.processLocalCmd(CliDriver.java:216)
>   at org.apache.hadoop.hive.cli.CliDriver.processCmd(CliDriver.java:168)
>   at org.apache.hadoop.hive.cli.CliDriver.processLine(CliDriver.java:379)
>   at org.apache.hadoop.hive.cli.CliDriver.processLine(CliDriver.java:314)
>   at 
> org.apache.hadoop.hive.cli.CliDriver.processReader(CliDriver.java:412)
>   at org.apache.hadoop.hive.cli.CliDriver.processFile(CliDriver.java:428)
>   at 
> org.apache.hadoop.hive.cli.CliDriver.executeDriver(CliDriver.java:717)
>   at org.apache.hadoop.hive.cli.CliDriver.run(CliDriver.java:684)
>   at org.apache.hadoop.hive.cli.CliDriver.main(CliDriver.java:624)
>   at org.apache.oozie.action.hadoop.HiveMain.runHive(HiveMain.java:335)
>   at org.apache.oozie.action.hadoop.HiveMain.run(HiveMain.java:312)
>   at org.apache.oozie.action.hadoop.LauncherMain.run(LauncherMain.java:51)
>   at org.apache.oozie.action.hadoop.HiveMain.main(HiveMain.java:69)
>   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.oozie.action.hadoop.LauncherMapper.map(LauncherMapper.java:242)
>   at org.apache.hadoop.mapred.MapRunner.run(MapRunner.java:54)
>   at org.apache.hadoop.mapred.MapTask.runOldMapper(MapTask.java:453)
>   at org.apache.hadoop.mapred.MapTask.run(MapTask.java:343)
>   at org.apache.hadoop.mapred.YarnChild$2.run(YarnChild.java:168)
>   at java.security.AccessController.doPrivileged(Native Method)
>   at javax.security.auth.Subject.doAs(Subject.java:422)
>   

[jira] [Updated] (AMBARI-18151) Oozie Hive actions fail when Atlas is installed since Atlas Hive Hooks need to be copied to Oozie Share Lib in HDFS

[Alejandro Fernandez (JIRA)]

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

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

> Oozie Hive actions fail when Atlas is installed since Atlas Hive Hooks need 
> to be copied to Oozie Share Lib in HDFS
> ---
>
> Key: AMBARI-18151
> URL: https://issues.apache.org/jira/browse/AMBARI-18151
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.4.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Blocker
>  Labels: 240RMApproved
> Fix For: 2.4.0
>
>
> After the Falcon-Atlas hook has been enabled, the following properties are 
> added.
> startup.properties
> {noformat}
> *.application.services=org.apache.falcon.security.AuthenticationInitializationService,\
>   org.apache.falcon.workflow.WorkflowJobEndNotificationService, \
>   org.apache.falcon.service.ProcessSubscriberService,\
>   org.apache.falcon.extensions.ExtensionService,\
>   org.apache.falcon.service.LifecyclePolicyMap,\
>   org.apache.falcon.entity.store.ConfigurationStore,\
>   org.apache.falcon.rerun.service.RetryService,\
>   org.apache.falcon.rerun.service.LateRunService,\
>   org.apache.falcon.service.LogCleanupService,\
>   org.apache.falcon.metadata.MetadataMappingService,\
> org.apache.atlas.falcon.service.AtlasService
> {noformat}
> falcon-env.sh
> {noformat}
> # Add the Atlas Falcon hook to the Falcon classpath
> export 
> FALCON_EXTRA_CLASS_PATH=/usr/hdp/current/atlas-client/hook/falcon/*:${FALCON_EXTRA_CLASS_PATH}
> {noformat} 
> Whenever Oozie submits Hive actions, they fail and the application logs show
> {noformat}
> hive.exec.post.hooks Class not found:org.apache.atlas.hive.hook.HiveHook
> FAILED: Hive Internal Error: 
> java.lang.ClassNotFoundException(org.apache.atlas.hive.hook.HiveHook)
> java.lang.ClassNotFoundException: org.apache.atlas.hive.hook.HiveHook
>   at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
>   at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
>   at java.lang.Class.forName0(Native Method)
>   at java.lang.Class.forName(Class.java:348)
>   at org.apache.hadoop.hive.ql.hooks.HookUtils.getHooks(HookUtils.java:60)
>   at org.apache.hadoop.hive.ql.Driver.getHooks(Driver.java:1384)
>   at org.apache.hadoop.hive.ql.Driver.getHooks(Driver.java:1368)
>   at org.apache.hadoop.hive.ql.Driver.execute(Driver.java:1595)
>   at org.apache.hadoop.hive.ql.Driver.runInternal(Driver.java:1289)
>   at org.apache.hadoop.hive.ql.Driver.run(Driver.java:1156)
>   at org.apache.hadoop.hive.ql.Driver.run(Driver.java:1146)
>   at 
> org.apache.hadoop.hive.cli.CliDriver.processLocalCmd(CliDriver.java:216)
>   at org.apache.hadoop.hive.cli.CliDriver.processCmd(CliDriver.java:168)
>   at org.apache.hadoop.hive.cli.CliDriver.processLine(CliDriver.java:379)
>   at org.apache.hadoop.hive.cli.CliDriver.processLine(CliDriver.java:314)
>   at 
> org.apache.hadoop.hive.cli.CliDriver.processReader(CliDriver.java:412)
>   at org.apache.hadoop.hive.cli.CliDriver.processFile(CliDriver.java:428)
>   at 
> org.apache.hadoop.hive.cli.CliDriver.executeDriver(CliDriver.java:717)
>   at org.apache.hadoop.hive.cli.CliDriver.run(CliDriver.java:684)
>   at org.apache.hadoop.hive.cli.CliDriver.main(CliDriver.java:624)
>   at org.apache.oozie.action.hadoop.HiveMain.runHive(HiveMain.java:335)
>   at org.apache.oozie.action.hadoop.HiveMain.run(HiveMain.java:312)
>   at org.apache.oozie.action.hadoop.LauncherMain.run(LauncherMain.java:51)
>   at org.apache.oozie.action.hadoop.HiveMain.main(HiveMain.java:69)
>   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.oozie.action.hadoop.LauncherMapper.map(LauncherMapper.java:242)
>   at org.apache.hadoop.mapred.MapRunner.run(MapRunner.java:54)
>   at org.apache.hadoop.mapred.MapTask.runOldMapper(MapTask.java:453)
>   at org.apache.hadoop.mapred.MapTask.run(MapTask.java:343)
>   at org.apache.hadoop.mapred.YarnChild$2.run(YarnChild.java:168)
>   at java.security.AccessController.doPrivileged(Native Method)
>   at javax.security.auth.Subject.doAs(Subject.java:422)
>   at 

[jira] [Updated] (AMBARI-18012) Metrics Sink unable to connect to zookeeper to locate collector host.

[Aravindan Vijayan (JIRA)]

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

Aravindan Vijayan updated AMBARI-18012:
---
Fix Version/s: (was: 2.5.0)
   trunk

> Metrics Sink unable to connect to zookeeper to locate collector host.
> -
>
> Key: AMBARI-18012
> URL: https://issues.apache.org/jira/browse/AMBARI-18012
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: trunk
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Critical
> Fix For: trunk
>
> Attachments: AMBARI-18012.patch
>
>
> Test and validate sink fallback connect to ZK for finding collector
> {code}
> 2016-07-14 20:37:01,212 INFO  timeline.HadoopTimelineMetricsSink 
> (AbstractTimelineMetricsSink.java:findPreferredCollectHost(353)) - Collector 
> ambari-sid-5.c.pramod-thangali.internal is not longer live. Removing it from 
> list of know live collector hosts : []
> 2016-07-14 20:37:03,213 WARN  availability.MetricCollectorHAHelper 
> (MetricCollectorHAHelper.java:findLiveCollectorHostsFromZNode(83)) - Unable 
> to connect to zookeeper.
> java.lang.IllegalStateException: Client is not started
> at 
> org.apache.hadoop.metrics2.sink.relocated.google.common.base.Preconditions.checkState(Preconditions.java:149)
> at 
> org.apache.hadoop.metrics2.sink.relocated.curator.CuratorZookeeperClient.getZooKeeper(CuratorZookeeperClient.java:113)
> at 
> org.apache.hadoop.metrics2.sink.timeline.availability.MetricCollectorHAHelper$1.call(MetricCollectorHAHelper.java:77)
> at 
> org.apache.hadoop.metrics2.sink.timeline.availability.MetricCollectorHAHelper$1.call(MetricCollectorHAHelper.java:74)
> at 
> org.apache.hadoop.metrics2.sink.relocated.curator.RetryLoop.callWithRetry(RetryLoop.java:107)
> at 
> org.apache.hadoop.metrics2.sink.timeline.availability.MetricCollectorHAHelper.findLiveCollectorHostsFromZNode(MetricCollectorHAHelper.java:74)
> at 
> org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink.findPreferredCollectHost(AbstractTimelineMetricsSink.java:363)
> at 
> org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink.emitMetrics(AbstractTimelineMetricsSink.java:209)
> at 
> org.apache.hadoop.metrics2.sink.timeline.HadoopTimelineMetricsSink.putMetrics(HadoopTimelineMetricsSink.java:315)
> at 
> org.apache.hadoop.metrics2.impl.MetricsSinkAdapter.consume(MetricsSinkAdapter.java:186)
> at 
> org.apache.hadoop.metrics2.impl.MetricsSinkAdapter.consume(MetricsSinkAdapter.java:43)
> at 
> org.apache.hadoop.metrics2.impl.SinkQueue.consumeAll(SinkQueue.java:87)
> at 
> org.apache.hadoop.metrics2.impl.MetricsSinkAdapter.publishMetricsFromQueue(MetricsSinkAdapter.java:134)
> at 
> org.apache.hadoop.metrics2.impl.MetricsSinkAdapter$1.run(MetricsSinkAdapter.java:88)
> 2016-07-14 20:37:03,245 WARN  timeline.HadoopTimelineMetricsSink 
> (AbstractTimelineMetricsSink.java:findLiveCollectorHostsFromKnownCollector(433))
>  - Unable to conne
> {code}



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

[jira] [Updated] (AMBARI-18012) Metrics Sink unable to connect to zookeeper to locate collector host.

[Aravindan Vijayan (JIRA)]

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

Aravindan Vijayan updated AMBARI-18012:
---
Affects Version/s: (was: 2.5.0)
   trunk

> Metrics Sink unable to connect to zookeeper to locate collector host.
> -
>
> Key: AMBARI-18012
> URL: https://issues.apache.org/jira/browse/AMBARI-18012
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: trunk
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Critical
> Fix For: trunk
>
> Attachments: AMBARI-18012.patch
>
>
> Test and validate sink fallback connect to ZK for finding collector
> {code}
> 2016-07-14 20:37:01,212 INFO  timeline.HadoopTimelineMetricsSink 
> (AbstractTimelineMetricsSink.java:findPreferredCollectHost(353)) - Collector 
> ambari-sid-5.c.pramod-thangali.internal is not longer live. Removing it from 
> list of know live collector hosts : []
> 2016-07-14 20:37:03,213 WARN  availability.MetricCollectorHAHelper 
> (MetricCollectorHAHelper.java:findLiveCollectorHostsFromZNode(83)) - Unable 
> to connect to zookeeper.
> java.lang.IllegalStateException: Client is not started
> at 
> org.apache.hadoop.metrics2.sink.relocated.google.common.base.Preconditions.checkState(Preconditions.java:149)
> at 
> org.apache.hadoop.metrics2.sink.relocated.curator.CuratorZookeeperClient.getZooKeeper(CuratorZookeeperClient.java:113)
> at 
> org.apache.hadoop.metrics2.sink.timeline.availability.MetricCollectorHAHelper$1.call(MetricCollectorHAHelper.java:77)
> at 
> org.apache.hadoop.metrics2.sink.timeline.availability.MetricCollectorHAHelper$1.call(MetricCollectorHAHelper.java:74)
> at 
> org.apache.hadoop.metrics2.sink.relocated.curator.RetryLoop.callWithRetry(RetryLoop.java:107)
> at 
> org.apache.hadoop.metrics2.sink.timeline.availability.MetricCollectorHAHelper.findLiveCollectorHostsFromZNode(MetricCollectorHAHelper.java:74)
> at 
> org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink.findPreferredCollectHost(AbstractTimelineMetricsSink.java:363)
> at 
> org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink.emitMetrics(AbstractTimelineMetricsSink.java:209)
> at 
> org.apache.hadoop.metrics2.sink.timeline.HadoopTimelineMetricsSink.putMetrics(HadoopTimelineMetricsSink.java:315)
> at 
> org.apache.hadoop.metrics2.impl.MetricsSinkAdapter.consume(MetricsSinkAdapter.java:186)
> at 
> org.apache.hadoop.metrics2.impl.MetricsSinkAdapter.consume(MetricsSinkAdapter.java:43)
> at 
> org.apache.hadoop.metrics2.impl.SinkQueue.consumeAll(SinkQueue.java:87)
> at 
> org.apache.hadoop.metrics2.impl.MetricsSinkAdapter.publishMetricsFromQueue(MetricsSinkAdapter.java:134)
> at 
> org.apache.hadoop.metrics2.impl.MetricsSinkAdapter$1.run(MetricsSinkAdapter.java:88)
> 2016-07-14 20:37:03,245 WARN  timeline.HadoopTimelineMetricsSink 
> (AbstractTimelineMetricsSink.java:findLiveCollectorHostsFromKnownCollector(433))
>  - Unable to conne
> {code}



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

[jira] [Commented] (AMBARI-18168) Create Atlas log4j changes for failed notifications

[Hudson (JIRA)]

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

Hudson commented on AMBARI-18168:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5535 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5535/])
AMBARI-18168: Create Atlas log4j changes for failed notifications 
(nsomasundaram: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=49cb0d1ac2ec9348d8c99d72500a0486e0c98614])
* (add) 
ambari-server/src/main/resources/common-services/ATLAS/0.7.0.2.5/configuration/atlas-log4j.xml


> Create Atlas log4j changes for failed notifications
> ---
>
> Key: AMBARI-18168
> URL: https://issues.apache.org/jira/browse/AMBARI-18168
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
>Priority: Blocker
>  Labels: 240RMApproved
> Fix For: 2.4.0
>
> Attachments: rb51144.patch
>
>
> Create Atlas log4j in 
> ambari-server/src/main/resources/common-services/ATLAS/0.7.0.2.5/configuration/atlas-log4j.xml
>  which is based on the earlier version, but makes the changes specified in
> https://issues.apache.org/jira/browse/ATLAS-
> No need to change EU/RU config packs since HDP 2.3/2.4 -> HDP 2.5 requires 
> removing Atlas service and all of its configs.



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

[jira] [Updated] (AMBARI-18169) Falcon log4j configuration should be configurable via Ambari

[Venkat Ranganathan (JIRA)]

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

Venkat Ranganathan updated AMBARI-18169:

Summary: Falcon log4j configuration should be  configurable via Ambari  
(was: Falcon log4j configuration is not configurable)

> Falcon log4j configuration should be  configurable via Ambari
> -
>
> Key: AMBARI-18169
> URL: https://issues.apache.org/jira/browse/AMBARI-18169
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Venkat Ranganathan
>Assignee: Venkat Ranganathan
> Attachments: AMBARI-18169.patch
>
>
> The falcon log4j configuration needs to be managed by Ambari



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

[jira] [Updated] (AMBARI-18169) Falcon log4j configuration is not configurable

[Venkat Ranganathan (JIRA)]

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

Venkat Ranganathan updated AMBARI-18169:

Status: Patch Available  (was: In Progress)

> Falcon log4j configuration is not configurable
> --
>
> Key: AMBARI-18169
> URL: https://issues.apache.org/jira/browse/AMBARI-18169
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Venkat Ranganathan
>Assignee: Venkat Ranganathan
> Attachments: AMBARI-18169.patch
>
>
> The falcon log4j configuration needs to be managed by Ambari



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

[jira] [Updated] (AMBARI-18169) Falcon log4j configuration is not configurable

[Venkat Ranganathan (JIRA)]

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

Venkat Ranganathan updated AMBARI-18169:

Attachment: AMBARI-18169.patch

> Falcon log4j configuration is not configurable
> --
>
> Key: AMBARI-18169
> URL: https://issues.apache.org/jira/browse/AMBARI-18169
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Venkat Ranganathan
>Assignee: Venkat Ranganathan
> Attachments: AMBARI-18169.patch
>
>
> The falcon log4j configuration needs to be managed by Ambari



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

[jira] [Created] (AMBARI-18169) Falcon log4j configuration is not configurable

[Venkat Ranganathan (JIRA)]

Venkat Ranganathan created AMBARI-18169:
---

 Summary: Falcon log4j configuration is not configurable
 Key: AMBARI-18169
 URL: https://issues.apache.org/jira/browse/AMBARI-18169
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: 2.4.0
Reporter: Venkat Ranganathan
Assignee: Venkat Ranganathan


The falcon log4j configuration needs to be managed by Ambari



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

[jira] [Commented] (AMBARI-18167) RU: Kafka brokers restart was stopped during downgrade cluster

[Jayush Luniya (JIRA)]

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

Jayush Luniya commented on AMBARI-18167:


+1 for the patch. The Hadoop QA failure is not related.

> RU: Kafka brokers restart was stopped during downgrade cluster
> --
>
> Key: AMBARI-18167
> URL: https://issues.apache.org/jira/browse/AMBARI-18167
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
>Priority: Blocker
>  Labels: 240RMApproved
> Fix For: 2.4.0
>
> Attachments: AMBARI-18167.patch
>
>
> Kafka broker restart failed due to below error:
> {noformat}
> raise Fail("Configuration parameter '" + self.name + "' was not found in 
> configurations dictionary!")
> resource_management.core.exceptions.Fail: Configuration parameter 
> 'xasecure.audit.destination.db' was not found in configurations dictionary!
> {noformat}
> Solution:
> During RU downgrade,  runs on downgrade as well, which deleted 
> {{xasecure.audit.destination.db}} config property. 
> {noformat}
> 
>id="hdp_2_5_0_0_remove_ranger_kafka_audit_db" />
> 
> {noformat}
> Need to override it with a blank  element.



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

[jira] [Updated] (AMBARI-18167) RU: Kafka brokers restart was stopped during downgrade cluster

[Jayush Luniya (JIRA)]

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

Jayush Luniya updated AMBARI-18167:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> RU: Kafka brokers restart was stopped during downgrade cluster
> --
>
> Key: AMBARI-18167
> URL: https://issues.apache.org/jira/browse/AMBARI-18167
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
>Priority: Blocker
>  Labels: 240RMApproved
> Fix For: 2.4.0
>
> Attachments: AMBARI-18167.patch
>
>
> Kafka broker restart failed due to below error:
> {noformat}
> raise Fail("Configuration parameter '" + self.name + "' was not found in 
> configurations dictionary!")
> resource_management.core.exceptions.Fail: Configuration parameter 
> 'xasecure.audit.destination.db' was not found in configurations dictionary!
> {noformat}
> Solution:
> During RU downgrade,  runs on downgrade as well, which deleted 
> {{xasecure.audit.destination.db}} config property. 
> {noformat}
> 
>id="hdp_2_5_0_0_remove_ranger_kafka_audit_db" />
> 
> {noformat}
> Need to override it with a blank  element.



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

[jira] [Commented] (AMBARI-18167) RU: Kafka brokers restart was stopped during downgrade cluster

[Jayush Luniya (JIRA)]

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

Jayush Luniya commented on AMBARI-18167:


Trunk
commit 43457696137486daa338f39cef5e899554f025b3
Author: Jayush Luniya 
Date:   Tue Aug 16 14:18:13 2016 -0700

AMBARI-18167: RU: Kafka brokers restart was stopped during downgrade 
cluster (Mugdha Varadkar via jluniya)

Branch-2.4
commit 473733c4e73a5328f75798936e8bdf89096d03db
Author: Jayush Luniya 
Date:   Tue Aug 16 14:18:13 2016 -0700

AMBARI-18167: RU: Kafka brokers restart was stopped during downgrade 
cluster (Mugdha Varadkar via jluniya)

> RU: Kafka brokers restart was stopped during downgrade cluster
> --
>
> Key: AMBARI-18167
> URL: https://issues.apache.org/jira/browse/AMBARI-18167
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
>Priority: Blocker
>  Labels: 240RMApproved
> Fix For: 2.4.0
>
> Attachments: AMBARI-18167.patch
>
>
> Kafka broker restart failed due to below error:
> {noformat}
> raise Fail("Configuration parameter '" + self.name + "' was not found in 
> configurations dictionary!")
> resource_management.core.exceptions.Fail: Configuration parameter 
> 'xasecure.audit.destination.db' was not found in configurations dictionary!
> {noformat}
> Solution:
> During RU downgrade,  runs on downgrade as well, which deleted 
> {{xasecure.audit.destination.db}} config property. 
> {noformat}
> 
>id="hdp_2_5_0_0_remove_ranger_kafka_audit_db" />
> 
> {noformat}
> Need to override it with a blank  element.



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

[jira] [Commented] (AMBARI-18167) RU: Kafka brokers restart was stopped during downgrade cluster

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-18167:


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

{color:red}-1 patch{color}.  Top-level trunk compilation may be broken.

Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/8432//console

This message is automatically generated.

> RU: Kafka brokers restart was stopped during downgrade cluster
> --
>
> Key: AMBARI-18167
> URL: https://issues.apache.org/jira/browse/AMBARI-18167
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
>Priority: Blocker
>  Labels: 240RMApproved
> Fix For: 2.4.0
>
> Attachments: AMBARI-18167.patch
>
>
> Kafka broker restart failed due to below error:
> {noformat}
> raise Fail("Configuration parameter '" + self.name + "' was not found in 
> configurations dictionary!")
> resource_management.core.exceptions.Fail: Configuration parameter 
> 'xasecure.audit.destination.db' was not found in configurations dictionary!
> {noformat}
> Solution:
> During RU downgrade,  runs on downgrade as well, which deleted 
> {{xasecure.audit.destination.db}} config property. 
> {noformat}
> 
>id="hdp_2_5_0_0_remove_ranger_kafka_audit_db" />
> 
> {noformat}
> Need to override it with a blank  element.



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

[jira] [Commented] (AMBARI-18042) Query execution takes a long time in hive view version1.5.0

[Hudson (JIRA)]

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

Hudson commented on AMBARI-18042:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5534 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5534/])
AMBARI-18042. Part 2. Query execution takes a long time in hive view 
(dipayan.bhowmick: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=28367d62b4d080d93b4941803612ea79cadf0f84])
* (add) 
contrib/views/hive-next/src/main/java/org/apache/ambari/view/hive2/actor/message/job/SaveDagInformation.java
* (edit) 
contrib/views/hive-next/src/main/java/org/apache/ambari/view/hive2/actor/message/job/UpdateYarnAtsGuid.java
* (edit) 
contrib/views/hive-next/src/main/java/org/apache/ambari/view/hive2/resources/jobs/Aggregator.java
* (edit) 
contrib/views/hive-next/src/main/java/org/apache/ambari/view/hive2/actor/YarnAtsGUIDFetcher.java
* (edit) 
contrib/views/hive-next/src/main/java/org/apache/ambari/view/hive2/actor/StatementExecutor.java
* (edit) 
contrib/views/hive-next/src/main/java/org/apache/ambari/view/hive2/resources/jobs/JobService.java
* (add) 
contrib/views/hive-next/src/main/java/org/apache/ambari/view/hive2/actor/message/job/SaveGuidToDB.java
* (edit) 
contrib/views/hive-next/src/main/java/org/apache/ambari/view/hive2/actor/OperationController.java
* (edit) 
contrib/views/hive-next/src/main/java/org/apache/ambari/view/hive2/actor/JdbcConnector.java


> Query execution takes a long time in hive view version1.5.0
> ---
>
> Key: AMBARI-18042
> URL: https://issues.apache.org/jira/browse/AMBARI-18042
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.4.0
>Reporter: Anusha Bilgi
>Assignee: DIPAYAN BHOWMICK
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-18042.branch-2.4.patch, 
> AMBARI-18042.part.2.branch-2.4.patch
>
>




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

[jira] [Commented] (AMBARI-18152) 'ambari-server --help' not working

[Hudson (JIRA)]

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

Hudson commented on AMBARI-18152:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5534 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5534/])
AMBARI-18152: 'ambari-server --help' not working (nsomasundaram: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=ff4b2c4bed5582b455f78055aec4f9e2a0284704])
* (edit) ambari-server/src/main/python/ambari_server/serverConfiguration.py
* (edit) ambari-server/sbin/ambari-server


> 'ambari-server --help' not working
> --
>
> Key: AMBARI-18152
> URL: https://issues.apache.org/jira/browse/AMBARI-18152
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: rb51123.patch
>
>
> The {{--help}} command is not working in ambari-server-2.4.0.0-1139 
> {noformat}
> [root@revo1 tmp]# ambari-server --hash
> 4512811263e2b168d03ad56430a73e418ce8a7a7
> [root@revo1 tmp]# ambari-server --help
> Using python  /usr/bin/python
> Usage: /usr/sbin/ambari-server.py
> 
> {start|stop|restart|setup|setup-jce|upgrade|status|upgradestack|setup-ldap|sync-ldap|set-current|setup-security|setup-sso|refresh-stack-hash|backup|restore|update-host-names|enable-stack|check-database|db-cleanup}
>  [options]
> Use /usr/sbin/ambari-server.py  --help to get details on 
> options available.
> Or, simply invoke ambari-server.py --help to print the options.
> [root@revo1 tmp]# /usr/sbin/ambari-server.py --help
> Could not read "/etc/ambari-server/conf/ambari.properties": 'ROOT'
> ERROR: Error getting ambari properties
> Traceback (most recent call last):
>   File "/usr/sbin/ambari-server.py", line 33, in 
> from ambari_server.dbConfiguration import DATABASE_NAMES, 
> LINUX_DBMS_KEYS_LIST
>   File "/usr/lib/python2.6/site-packages/ambari_server/dbConfiguration.py", 
> line 28, in 
> from ambari_server.serverConfiguration import decrypt_password_for_alias, 
> get_ambari_properties, get_is_secure, \
>   File 
> "/usr/lib/python2.6/site-packages/ambari_server/serverConfiguration.py", line 
> 552, in 
> configDefaults = ServerConfigDefaults()
>   File 
> "/usr/lib/python2.6/site-packages/ambari_server/serverConfiguration.py", line 
> 469, in __init__
> super(ServerConfigDefaultsLinux, self).__init__()
>   File 
> "/usr/lib/python2.6/site-packages/ambari_server/serverConfiguration.py", line 
> 349, in __init__
> self.PID_DIR = properties.get_property(PID_DIR_PROPERTY)
> AttributeError: 'int' object has no attribute 'get_property'
> {noformat}



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

[jira] [Updated] (AMBARI-18168) Create Atlas log4j changes for failed notifications

[Nahappan Somasundaram (JIRA)]

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

Nahappan Somasundaram updated AMBARI-18168:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Create Atlas log4j changes for failed notifications
> ---
>
> Key: AMBARI-18168
> URL: https://issues.apache.org/jira/browse/AMBARI-18168
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
>Priority: Blocker
>  Labels: 240RMApproved
> Fix For: 2.4.0
>
> Attachments: rb51144.patch
>
>
> Create Atlas log4j in 
> ambari-server/src/main/resources/common-services/ATLAS/0.7.0.2.5/configuration/atlas-log4j.xml
>  which is based on the earlier version, but makes the changes specified in
> https://issues.apache.org/jira/browse/ATLAS-
> No need to change EU/RU config packs since HDP 2.3/2.4 -> HDP 2.5 requires 
> removing Atlas service and all of its configs.



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

[jira] [Updated] (AMBARI-17717) Ambari should have a script to add new repository and service to existing stack

[Lav Jain (JIRA)]

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

Lav Jain updated AMBARI-17717:
--
Status: Open  (was: Patch Available)

The patch was not favored by Ambari community. Will explore management packs as 
Jayush requested.

> Ambari should have a script to add new repository and service to existing 
> stack
> ---
>
> Key: AMBARI-17717
> URL: https://issues.apache.org/jira/browse/AMBARI-17717
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Affects Versions: trunk
>Reporter: Matt
>Assignee: Lav Jain
> Fix For: trunk
>
> Attachments: AMBARI-17717.patch
>
>
> Ambari should have a script that users can run to add a custom service and 
> repository to the stack or an existing cluster.
> {code}
> Lavs-MacBook-Pro:scripts ljain$ ./add_common_service.py -h
> Usage: add_common_service.py [options]
> Options:
>   -h, --helpshow this help message and exit
>   -u USER, --user=USER  Ambari login username (Required)
>   -p PASSWORD, --password=PASSWORD
> Ambari login password. Providing password through
> command line is not recommended. The script prompts
> for the password.
>   -t STACK, --stack=STACK
> Stack Name and Version to be added (Required).(Eg:
> HDP-2.4 or HDP-2.5)
>   -s SERVICE, --service=SERVICE
> Service Name and Version to be added.(Eg: HAWQ/2.0.0
> or PXF/3.0.0)
>   -r REPOURL, --repourl=REPOURL
> Repository URL which points to the rpm packages
>   -i REPOID, --repoid=REPOID
> Repository ID of the new repository
>   -o OSTYPE, --ostype=OSTYPE
> OS for the new repository (Eg: redhat6)
> {code}



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

[jira] [Updated] (AMBARI-18151) Oozie Hive actions fail when Atlas is installed since Atlas Hive Hooks need to be copied to Oozie Share Lib in HDFS

[Jayush Luniya (JIRA)]

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

Jayush Luniya updated AMBARI-18151:
---
Labels: 240RMApproved  (was: )

> Oozie Hive actions fail when Atlas is installed since Atlas Hive Hooks need 
> to be copied to Oozie Share Lib in HDFS
> ---
>
> Key: AMBARI-18151
> URL: https://issues.apache.org/jira/browse/AMBARI-18151
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.4.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Blocker
>  Labels: 240RMApproved
> Fix For: 2.4.0
>
> Attachments: AMBARI-18151.patch
>
>
> After the Falcon-Atlas hook has been enabled, the following properties are 
> added.
> startup.properties
> {noformat}
> *.application.services=org.apache.falcon.security.AuthenticationInitializationService,\
>   org.apache.falcon.workflow.WorkflowJobEndNotificationService, \
>   org.apache.falcon.service.ProcessSubscriberService,\
>   org.apache.falcon.extensions.ExtensionService,\
>   org.apache.falcon.service.LifecyclePolicyMap,\
>   org.apache.falcon.entity.store.ConfigurationStore,\
>   org.apache.falcon.rerun.service.RetryService,\
>   org.apache.falcon.rerun.service.LateRunService,\
>   org.apache.falcon.service.LogCleanupService,\
>   org.apache.falcon.metadata.MetadataMappingService,\
> org.apache.atlas.falcon.service.AtlasService
> {noformat}
> falcon-env.sh
> {noformat}
> # Add the Atlas Falcon hook to the Falcon classpath
> export 
> FALCON_EXTRA_CLASS_PATH=/usr/hdp/current/atlas-client/hook/falcon/*:${FALCON_EXTRA_CLASS_PATH}
> {noformat} 
> Whenever Oozie submits Hive actions, they fail and the application logs show
> {noformat}
> hive.exec.post.hooks Class not found:org.apache.atlas.hive.hook.HiveHook
> FAILED: Hive Internal Error: 
> java.lang.ClassNotFoundException(org.apache.atlas.hive.hook.HiveHook)
> java.lang.ClassNotFoundException: org.apache.atlas.hive.hook.HiveHook
>   at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
>   at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
>   at java.lang.Class.forName0(Native Method)
>   at java.lang.Class.forName(Class.java:348)
>   at org.apache.hadoop.hive.ql.hooks.HookUtils.getHooks(HookUtils.java:60)
>   at org.apache.hadoop.hive.ql.Driver.getHooks(Driver.java:1384)
>   at org.apache.hadoop.hive.ql.Driver.getHooks(Driver.java:1368)
>   at org.apache.hadoop.hive.ql.Driver.execute(Driver.java:1595)
>   at org.apache.hadoop.hive.ql.Driver.runInternal(Driver.java:1289)
>   at org.apache.hadoop.hive.ql.Driver.run(Driver.java:1156)
>   at org.apache.hadoop.hive.ql.Driver.run(Driver.java:1146)
>   at 
> org.apache.hadoop.hive.cli.CliDriver.processLocalCmd(CliDriver.java:216)
>   at org.apache.hadoop.hive.cli.CliDriver.processCmd(CliDriver.java:168)
>   at org.apache.hadoop.hive.cli.CliDriver.processLine(CliDriver.java:379)
>   at org.apache.hadoop.hive.cli.CliDriver.processLine(CliDriver.java:314)
>   at 
> org.apache.hadoop.hive.cli.CliDriver.processReader(CliDriver.java:412)
>   at org.apache.hadoop.hive.cli.CliDriver.processFile(CliDriver.java:428)
>   at 
> org.apache.hadoop.hive.cli.CliDriver.executeDriver(CliDriver.java:717)
>   at org.apache.hadoop.hive.cli.CliDriver.run(CliDriver.java:684)
>   at org.apache.hadoop.hive.cli.CliDriver.main(CliDriver.java:624)
>   at org.apache.oozie.action.hadoop.HiveMain.runHive(HiveMain.java:335)
>   at org.apache.oozie.action.hadoop.HiveMain.run(HiveMain.java:312)
>   at org.apache.oozie.action.hadoop.LauncherMain.run(LauncherMain.java:51)
>   at org.apache.oozie.action.hadoop.HiveMain.main(HiveMain.java:69)
>   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.oozie.action.hadoop.LauncherMapper.map(LauncherMapper.java:242)
>   at org.apache.hadoop.mapred.MapRunner.run(MapRunner.java:54)
>   at org.apache.hadoop.mapred.MapTask.runOldMapper(MapTask.java:453)
>   at org.apache.hadoop.mapred.MapTask.run(MapTask.java:343)
>   at org.apache.hadoop.mapred.YarnChild$2.run(YarnChild.java:168)
>   at java.security.AccessController.doPrivileged(Native Method)
>   at 

[jira] [Updated] (AMBARI-18165) Hbase RegionServer start fails

[Jayush Luniya (JIRA)]

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

Jayush Luniya updated AMBARI-18165:
---
Labels: 240RMApproved  (was: )

> Hbase RegionServer start fails
> --
>
> Key: AMBARI-18165
> URL: https://issues.apache.org/jira/browse/AMBARI-18165
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Blocker
>  Labels: 240RMApproved
> Fix For: 2.4.0
>
> Attachments: AMBARI-18165.patch
>
>
> {code}
> Traceback (most recent call last):
>   File 
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_regionserver.py",
>  line 198, in 
> HbaseRegionServer().execute()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 280, in execute
> method(env)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 720, in restart
> self.start(env, upgrade_type=upgrade_type)
>   File 
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_regionserver.py",
>  line 124, in start
> self.post_start(env, upgrade_type=upgrade_type)
>   File 
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_regionserver.py",
>  line 89, in post_start
> self.apply_atlas_acl(params.hbase_user)
>   File 
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_regionserver.py",
>  line 114, in apply_atlas_acl
> shell.checked_call(format("{kinit_cmd}; {perm_cmd}"), 
> user=params.hbase_user, tries=10, try_sleep=10)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 71, in inner
> result = function(command, **kwargs)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 93, in checked_call
> tries=tries, try_sleep=try_sleep)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 141, in _call_wrapper
> result = _call(command, **kwargs_copy)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 294, in _call
> raise Fail(err_msg)
> resource_management.core.exceptions.Fail: Execution of '/usr/bin/kinit -kt 
> /etc/security/keytabs/hbase.service.keytab 
> hbase/nat-r6-gjss-ambari-blueprints-4re-1-1.openstacklo...@example.com; echo 
> "grant 'atlas', 'RWXCA', 'atlas_titan'" | hbase shell -n' returned 1. 
>  Hortonworks #
> This is MOTD message, added for testing in qe infra
> ERROR ArgumentError: Can't find a table: atlas_titan
> {code}



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

[jira] [Commented] (AMBARI-17717) Ambari should have a script to add new repository and service to existing stack

[Lav Jain (JIRA)]

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

Lav Jain commented on AMBARI-17717:
---

[~Tim Thorpe]

Please feel free to update/close this Jira when your script has been finalized.

> Ambari should have a script to add new repository and service to existing 
> stack
> ---
>
> Key: AMBARI-17717
> URL: https://issues.apache.org/jira/browse/AMBARI-17717
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Affects Versions: trunk
>Reporter: Matt
>Assignee: Lav Jain
> Fix For: trunk
>
> Attachments: AMBARI-17717.patch
>
>
> Ambari should have a script that users can run to add a custom service and 
> repository to the stack or an existing cluster.
> {code}
> Lavs-MacBook-Pro:scripts ljain$ ./add_common_service.py -h
> Usage: add_common_service.py [options]
> Options:
>   -h, --helpshow this help message and exit
>   -u USER, --user=USER  Ambari login username (Required)
>   -p PASSWORD, --password=PASSWORD
> Ambari login password. Providing password through
> command line is not recommended. The script prompts
> for the password.
>   -t STACK, --stack=STACK
> Stack Name and Version to be added (Required).(Eg:
> HDP-2.4 or HDP-2.5)
>   -s SERVICE, --service=SERVICE
> Service Name and Version to be added.(Eg: HAWQ/2.0.0
> or PXF/3.0.0)
>   -r REPOURL, --repourl=REPOURL
> Repository URL which points to the rpm packages
>   -i REPOID, --repoid=REPOID
> Repository ID of the new repository
>   -o OSTYPE, --ostype=OSTYPE
> OS for the new repository (Eg: redhat6)
> {code}



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

[jira] [Updated] (AMBARI-18135) Enable Namenode HA failing at install journal nodes with cluster operator user

[Jayush Luniya (JIRA)]

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

Jayush Luniya updated AMBARI-18135:
---
Labels: 240RMApproved rbac  (was: rbac)

> Enable Namenode HA failing at install journal nodes with cluster operator user
> --
>
> Key: AMBARI-18135
> URL: https://issues.apache.org/jira/browse/AMBARI-18135
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Shreya Bhat
>Assignee: Myroslav Papirkovskyi
>Priority: Blocker
>  Labels: 240RMApproved, rbac
> Fix For: 2.4.0
>
> Attachments: AMBARI-18135.patch
>
>
> Enabling name node HA is failing at journal node install for cluster operator 
> user. Looking at network from the chrome browser, looks like there is a 403.



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

[jira] [Issue Comment Deleted] (AMBARI-18135) Enable Namenode HA failing at install journal nodes with cluster operator user

[Jayush Luniya (JIRA)]

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

Jayush Luniya updated AMBARI-18135:
---
Comment: was deleted

(was: Pushing out non-blocker JIRAs from 2.4.0 to 2.5.0
)

> Enable Namenode HA failing at install journal nodes with cluster operator user
> --
>
> Key: AMBARI-18135
> URL: https://issues.apache.org/jira/browse/AMBARI-18135
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Shreya Bhat
>Assignee: Myroslav Papirkovskyi
>Priority: Blocker
>  Labels: 240RMApproved, rbac
> Fix For: 2.4.0
>
> Attachments: AMBARI-18135.patch
>
>
> Enabling name node HA is failing at journal node install for cluster operator 
> user. Looking at network from the chrome browser, looks like there is a 403.



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

[jira] [Updated] (AMBARI-18167) RU: Kafka brokers restart was stopped during downgrade cluster

[Jayush Luniya (JIRA)]

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

Jayush Luniya updated AMBARI-18167:
---
Labels: 240RMApproved  (was: )

> RU: Kafka brokers restart was stopped during downgrade cluster
> --
>
> Key: AMBARI-18167
> URL: https://issues.apache.org/jira/browse/AMBARI-18167
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
>Priority: Blocker
>  Labels: 240RMApproved
> Fix For: 2.4.0
>
> Attachments: AMBARI-18167.patch
>
>
> Kafka broker restart failed due to below error:
> {noformat}
> raise Fail("Configuration parameter '" + self.name + "' was not found in 
> configurations dictionary!")
> resource_management.core.exceptions.Fail: Configuration parameter 
> 'xasecure.audit.destination.db' was not found in configurations dictionary!
> {noformat}
> Solution:
> During RU downgrade,  runs on downgrade as well, which deleted 
> {{xasecure.audit.destination.db}} config property. 
> {noformat}
> 
>id="hdp_2_5_0_0_remove_ranger_kafka_audit_db" />
> 
> {noformat}
> Need to override it with a blank  element.



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

[jira] [Updated] (AMBARI-18168) Create Atlas log4j changes for failed notifications

[Jayush Luniya (JIRA)]

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

Jayush Luniya updated AMBARI-18168:
---
Labels: 240RMApproved  (was: )

> Create Atlas log4j changes for failed notifications
> ---
>
> Key: AMBARI-18168
> URL: https://issues.apache.org/jira/browse/AMBARI-18168
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
>Priority: Blocker
>  Labels: 240RMApproved
> Fix For: 2.4.0
>
> Attachments: rb51144.patch
>
>
> Create Atlas log4j in 
> ambari-server/src/main/resources/common-services/ATLAS/0.7.0.2.5/configuration/atlas-log4j.xml
>  which is based on the earlier version, but makes the changes specified in
> https://issues.apache.org/jira/browse/ATLAS-
> No need to change EU/RU config packs since HDP 2.3/2.4 -> HDP 2.5 requires 
> removing Atlas service and all of its configs.



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

[jira] [Commented] (AMBARI-17938) Ambari should not recursively chown for HAWQ hdfs upon every start

[Lav Jain (JIRA)]

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

Lav Jain commented on AMBARI-17938:
---

Confirmed. Thanks [~jluniya] for taking care of this.

> Ambari should not recursively chown for HAWQ hdfs upon every start
> --
>
> Key: AMBARI-17938
> URL: https://issues.apache.org/jira/browse/AMBARI-17938
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk, 2.4.0
>Reporter: Lav Jain
>Assignee: Lav Jain
>  Labels: performance
> Fix For: 2.4.0
>
> Attachments: AMBARI-17938.patch, AMBARI-17938.v2.patch, 
> AMBARI-17938.v3.patch
>
>
> This results in changing of owner even if the owner value is same. The 
> operation is very costly if there are a lot of subdirectories.
> The owner value only changes when you switch from regular mode to secure mode 
> and vice-versa.



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

[jira] [Updated] (AMBARI-18168) Create Atlas log4j changes for failed notifications

[Nahappan Somasundaram (JIRA)]

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

Nahappan Somasundaram updated AMBARI-18168:
---
Attachment: rb51144.patch

> Create Atlas log4j changes for failed notifications
> ---
>
> Key: AMBARI-18168
> URL: https://issues.apache.org/jira/browse/AMBARI-18168
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: rb51144.patch
>
>
> Create Atlas log4j in 
> ambari-server/src/main/resources/common-services/ATLAS/0.7.0.2.5/configuration/atlas-log4j.xml
>  which is based on the earlier version, but makes the changes specified in
> https://issues.apache.org/jira/browse/ATLAS-
> No need to change EU/RU config packs since HDP 2.3/2.4 -> HDP 2.5 requires 
> removing Atlas service and all of its configs.



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

[jira] [Updated] (AMBARI-18168) Create Atlas log4j changes for failed notifications

[Nahappan Somasundaram (JIRA)]

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

Nahappan Somasundaram updated AMBARI-18168:
---
Status: Patch Available  (was: Open)

> Create Atlas log4j changes for failed notifications
> ---
>
> Key: AMBARI-18168
> URL: https://issues.apache.org/jira/browse/AMBARI-18168
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: rb51144.patch
>
>
> Create Atlas log4j in 
> ambari-server/src/main/resources/common-services/ATLAS/0.7.0.2.5/configuration/atlas-log4j.xml
>  which is based on the earlier version, but makes the changes specified in
> https://issues.apache.org/jira/browse/ATLAS-
> No need to change EU/RU config packs since HDP 2.3/2.4 -> HDP 2.5 requires 
> removing Atlas service and all of its configs.



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

[jira] [Updated] (AMBARI-18168) Create Atlas log4j changes for failed notifications

[Nahappan Somasundaram (JIRA)]

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

Nahappan Somasundaram updated AMBARI-18168:
---
Description: 
Create Atlas log4j in 
ambari-server/src/main/resources/common-services/ATLAS/0.7.0.2.5/configuration/atlas-log4j.xml
 which is based on the earlier version, but makes the changes specified in
https://issues.apache.org/jira/browse/ATLAS-
No need to change EU/RU config packs since HDP 2.3/2.4 -> HDP 2.5 requires 
removing Atlas service and all of its configs.

  was:
Create Atlas log4j in 
ambari-server/src/main/resources/common-services/ATLAS/0.7.0.2.5/configuration/atlas-log4j.xml
 which is based on the earlier version, but makes the changes specified in
https://github.com/hortonworks/atlas/commit/09c7f1f078efd47eb4635da60a2d6147ff4b21e0#diff-7e17ad8d420848bb7caa6e23b3b7ee74
No need to change EU/RU config packs since HDP 2.3/2.4 -> HDP 2.5 requires 
removing Atlas service and all of its configs.


> Create Atlas log4j changes for failed notifications
> ---
>
> Key: AMBARI-18168
> URL: https://issues.apache.org/jira/browse/AMBARI-18168
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
>Priority: Blocker
> Fix For: 2.4.0
>
>
> Create Atlas log4j in 
> ambari-server/src/main/resources/common-services/ATLAS/0.7.0.2.5/configuration/atlas-log4j.xml
>  which is based on the earlier version, but makes the changes specified in
> https://issues.apache.org/jira/browse/ATLAS-
> No need to change EU/RU config packs since HDP 2.3/2.4 -> HDP 2.5 requires 
> removing Atlas service and all of its configs.



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

[jira] [Created] (AMBARI-18168) Create Atlas log4j changes for failed notifications

[Nahappan Somasundaram (JIRA)]

Nahappan Somasundaram created AMBARI-18168:
--

 Summary: Create Atlas log4j changes for failed notifications
 Key: AMBARI-18168
 URL: https://issues.apache.org/jira/browse/AMBARI-18168
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: 2.4.0
Reporter: Nahappan Somasundaram
Assignee: Nahappan Somasundaram
Priority: Blocker
 Fix For: 2.4.0


Create Atlas log4j in 
ambari-server/src/main/resources/common-services/ATLAS/0.7.0.2.5/configuration/atlas-log4j.xml
 which is based on the earlier version, but makes the changes specified in
https://github.com/hortonworks/atlas/commit/09c7f1f078efd47eb4635da60a2d6147ff4b21e0#diff-7e17ad8d420848bb7caa6e23b3b7ee74
No need to change EU/RU config packs since HDP 2.3/2.4 -> HDP 2.5 requires 
removing Atlas service and all of its configs.



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

[jira] [Commented] (AMBARI-18164) Enable Interactive Query should not be available in Add Service Wizard

[Hudson (JIRA)]

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

Hudson commented on AMBARI-18164:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5533 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5533/])
AMBARI-18164. Enable Interactive Query should not be available in Add 
(akovalenko: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=ba2aa091b166c77df02b37c4476cfa258f855178])
* (edit) ambari-web/app/controllers/wizard/step7_controller.js
* (edit) ambari-web/app/models/configs/objects/service_config_property.js


> Enable Interactive Query should not be available in Add Service Wizard
> --
>
> Key: AMBARI-18164
> URL: https://issues.apache.org/jira/browse/AMBARI-18164
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-18164.patch
>
>




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

[jira] [Updated] (AMBARI-18167) RU: Kafka brokers restart was stopped during downgrade cluster

[Mugdha Varadkar (JIRA)]

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

Mugdha Varadkar updated AMBARI-18167:
-
Status: Patch Available  (was: In Progress)

> RU: Kafka brokers restart was stopped during downgrade cluster
> --
>
> Key: AMBARI-18167
> URL: https://issues.apache.org/jira/browse/AMBARI-18167
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-18167.patch
>
>
> Kafka broker restart failed due to below error:
> {noformat}
> raise Fail("Configuration parameter '" + self.name + "' was not found in 
> configurations dictionary!")
> resource_management.core.exceptions.Fail: Configuration parameter 
> 'xasecure.audit.destination.db' was not found in configurations dictionary!
> {noformat}
> Solution:
> During RU downgrade,  runs on downgrade as well, which deleted 
> {{xasecure.audit.destination.db}} config property. 
> {noformat}
> 
>id="hdp_2_5_0_0_remove_ranger_kafka_audit_db" />
> 
> {noformat}
> Need to override it with a blank  element.



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

[jira] [Commented] (AMBARI-18140) Avoid hardcoded values in blueprint for hive and oozie

[Hudson (JIRA)]

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

Hudson commented on AMBARI-18140:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5533 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5533/])
AMBARI-18140: Avoid hardcoded values in blueprint for hive and oozie (dili: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=aa58a54b54adfed8893cf7cffe3286e9c2d1fec3])
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/BlueprintConfigurationProcessorTest.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/BlueprintConfigurationProcessor.java


> Avoid hardcoded values in blueprint for hive and oozie
> --
>
> Key: AMBARI-18140
> URL: https://issues.apache.org/jira/browse/AMBARI-18140
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server, blueprints
>Affects Versions: 2.2.0
>Reporter: Amruta Borkar
>Assignee: Amruta Borkar
> Fix For: trunk
>
> Attachments: AMBARI-18140.patch
>
>
> There are a lot of hardcoded values in blueprint for hive.
> {
>   "hive-env" : {
> "properties_attributes" : { },
> "properties" : {
>   "hive_security_authorization" : "None",
>   "hive_log_dir" : "/var/log/hive",
>   "hive_existing_oracle_host" : "hardcodedhostname
> com",
>   "hive_user" : "hive",
>   "hive_existing_mssql_server_2_host" : "hardcodedhostname.com",
>   "hive.heapsize" : "1024",
>   "hcat_log_dir" : "/var/log/webhcat",
>   "hive_hostname" : "%HOSTGROUP::host_group_1%",
>   "hive_database" : "New MySQL Database",
>   "hive_exec_orc_storage_strategy" : "SPEED",
>   "hive_database_name" : "hive",
>   "webhcat_user" : "hcat",
>   "hive_txn_acid" : "off",
>   "hcat_pid_dir" : "/var/run/webhcat",
>   "hive.metastore.heapsize" : "1024",
>   "hive.client.heapsize" : "512",
>   "hive_existing_mssql_server_host" : "hardcodedhostname.com",
>   "hcat_user" : "hcat",
>   "hive_ambari_database" : "MySQL",
>   "content" : "\n if [ \"$SERVICE\" = \"cli\" ]; then\n   {%...}
>   "hive_pid_dir" : "/var/run/hive",
>   "hive_existing_postgresql_host" : "hardcodedhostname.com",
>   "hive_database_type" : "mysql",
>   "hive_existing_mysql_host" : "hardcodedhostname.
> com"
> }



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

[jira] [Updated] (AMBARI-18167) RU: Kafka brokers restart was stopped during downgrade cluster

[Mugdha Varadkar (JIRA)]

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

Mugdha Varadkar updated AMBARI-18167:
-
Attachment: AMBARI-18167.patch

> RU: Kafka brokers restart was stopped during downgrade cluster
> --
>
> Key: AMBARI-18167
> URL: https://issues.apache.org/jira/browse/AMBARI-18167
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-18167.patch
>
>
> Kafka broker restart failed due to below error:
> {noformat}
> raise Fail("Configuration parameter '" + self.name + "' was not found in 
> configurations dictionary!")
> resource_management.core.exceptions.Fail: Configuration parameter 
> 'xasecure.audit.destination.db' was not found in configurations dictionary!
> {noformat}
> Solution:
> During RU downgrade,  runs on downgrade as well, which deleted 
> {{xasecure.audit.destination.db}} config property. 
> {noformat}
> 
>id="hdp_2_5_0_0_remove_ranger_kafka_audit_db" />
> 
> {noformat}
> Need to override it with a blank  element.



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

[jira] [Created] (AMBARI-18167) RU: Kafka brokers restart was stopped during downgrade cluster

[Mugdha Varadkar (JIRA)]

Mugdha Varadkar created AMBARI-18167:


 Summary: RU: Kafka brokers restart was stopped during downgrade 
cluster
 Key: AMBARI-18167
 URL: https://issues.apache.org/jira/browse/AMBARI-18167
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: 2.4.0
Reporter: Mugdha Varadkar
Assignee: Mugdha Varadkar
Priority: Blocker
 Fix For: 2.4.0


Kafka broker restart failed due to below error:
{noformat}
raise Fail("Configuration parameter '" + self.name + "' was not found in 
configurations dictionary!")
resource_management.core.exceptions.Fail: Configuration parameter 
'xasecure.audit.destination.db' was not found in configurations dictionary!
{noformat}


Solution:
During RU downgrade,  runs on downgrade as well, which deleted 
{{xasecure.audit.destination.db}} config property. 

{noformat}

  

{noformat}

Need to override it with a blank  element.



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

[jira] [Updated] (AMBARI-18042) Query execution takes a long time in hive view version1.5.0

[DIPAYAN BHOWMICK (JIRA)]

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

DIPAYAN BHOWMICK updated AMBARI-18042:
--
Resolution: Fixed
Status: Resolved  (was: Patch Available)

Committed to branch-2.4, trunk.

> Query execution takes a long time in hive view version1.5.0
> ---
>
> Key: AMBARI-18042
> URL: https://issues.apache.org/jira/browse/AMBARI-18042
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.4.0
>Reporter: Anusha Bilgi
>Assignee: DIPAYAN BHOWMICK
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-18042.branch-2.4.patch, 
> AMBARI-18042.part.2.branch-2.4.patch
>
>




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

[jira] [Commented] (AMBARI-16764) When "Use Local Repository" option is selected, the stack cannot be changed

[Jayush Luniya (JIRA)]

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

Jayush Luniya commented on AMBARI-16764:


[~onechiporenko]
Moving this out of 2.4.0 to 2.5.0. Please retriage if required. 

> When "Use Local Repository" option is selected, the stack cannot be changed
> ---
>
> Key: AMBARI-16764
> URL: https://issues.apache.org/jira/browse/AMBARI-16764
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
>Priority: Critical
> Fix For: 2.5.0
>
>
> Clicking on the stack version tab in "Select Stack" page does nothing when 
> "Use Local Repository" option is selected.



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

[jira] [Updated] (AMBARI-16764) When "Use Local Repository" option is selected, the stack cannot be changed

[Jayush Luniya (JIRA)]

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

Jayush Luniya updated AMBARI-16764:
---
Fix Version/s: (was: 2.4.0)
   2.5.0

> When "Use Local Repository" option is selected, the stack cannot be changed
> ---
>
> Key: AMBARI-16764
> URL: https://issues.apache.org/jira/browse/AMBARI-16764
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
>Priority: Critical
> Fix For: 2.5.0
>
>
> Clicking on the stack version tab in "Select Stack" page does nothing when 
> "Use Local Repository" option is selected.



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

[jira] [Created] (AMBARI-18166) configs.sh script updates

[Siddharth Wagle (JIRA)]

Siddharth Wagle created AMBARI-18166:


 Summary: configs.sh script updates
 Key: AMBARI-18166
 URL: https://issues.apache.org/jira/browse/AMBARI-18166
 Project: Ambari
  Issue Type: Improvement
  Components: ambari-server
Reporter: Siddharth Wagle
 Fix For: 2.5.0


This utility script is widely used by for change configs.

Improvements:
- Support importing of xml files along with json formatted config content
- Infer property attributes like final from the xml file
- Allow accepting password as hidden field




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

[jira] [Updated] (AMBARI-18166) configs.sh script updates

[Siddharth Wagle (JIRA)]

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

Siddharth Wagle updated AMBARI-18166:
-
Affects Version/s: 2.0.0

> configs.sh script updates
> -
>
> Key: AMBARI-18166
> URL: https://issues.apache.org/jira/browse/AMBARI-18166
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Affects Versions: 2.0.0
>Reporter: Siddharth Wagle
> Fix For: 2.5.0
>
>
> This utility script is widely used by for change configs.
> Improvements:
> - Support importing of xml files along with json formatted config content
> - Infer property attributes like final from the xml file
> - Allow accepting password as hidden field



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

[jira] [Commented] (AMBARI-17888) Create configuration flag to prevent changing of directory permissions

[Siddharth Wagle (JIRA)]

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

Siddharth Wagle commented on AMBARI-17888:
--

Yes this went into 2.4 branch. cc:[~jluniya]

> Create configuration flag to prevent changing of directory permissions
> --
>
> Key: AMBARI-17888
> URL: https://issues.apache.org/jira/browse/AMBARI-17888
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-agent
>Affects Versions: 2.2.2
>Reporter: Siddharth Wagle
>Assignee: Siddharth Wagle
> Fix For: 2.4.0
>
> Attachments: AMBARI-17888-1.patch
>
>
> A common method of addressing failed disks, which is to set unwritable 
> permissions on a directory such as /hadoop10 within the root filesystem.
> Once mounted, the mounted filesystem will overlay the correct permissions 
> structure, allowing hdfs to write to the mounted disk.
> In the case of a failed mount operation, the associated /hadoop10 directory 
> will be unwritable by hdfs.
> However, Ambari will see the visible directory with incorrect permissions, 
> and "fix" the permissions back to a writable directory-- resulting in the 
> datanode filling the root partition of a machine.
> We need to prevent ambari from changing permissions on YARN local and HDFS 
> data dirs.



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

[jira] [Updated] (AMBARI-18152) 'ambari-server --help' not working

[Nahappan Somasundaram (JIRA)]

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

Nahappan Somasundaram updated AMBARI-18152:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> 'ambari-server --help' not working
> --
>
> Key: AMBARI-18152
> URL: https://issues.apache.org/jira/browse/AMBARI-18152
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: rb51123.patch
>
>
> The {{--help}} command is not working in ambari-server-2.4.0.0-1139 
> {noformat}
> [root@revo1 tmp]# ambari-server --hash
> 4512811263e2b168d03ad56430a73e418ce8a7a7
> [root@revo1 tmp]# ambari-server --help
> Using python  /usr/bin/python
> Usage: /usr/sbin/ambari-server.py
> 
> {start|stop|restart|setup|setup-jce|upgrade|status|upgradestack|setup-ldap|sync-ldap|set-current|setup-security|setup-sso|refresh-stack-hash|backup|restore|update-host-names|enable-stack|check-database|db-cleanup}
>  [options]
> Use /usr/sbin/ambari-server.py  --help to get details on 
> options available.
> Or, simply invoke ambari-server.py --help to print the options.
> [root@revo1 tmp]# /usr/sbin/ambari-server.py --help
> Could not read "/etc/ambari-server/conf/ambari.properties": 'ROOT'
> ERROR: Error getting ambari properties
> Traceback (most recent call last):
>   File "/usr/sbin/ambari-server.py", line 33, in 
> from ambari_server.dbConfiguration import DATABASE_NAMES, 
> LINUX_DBMS_KEYS_LIST
>   File "/usr/lib/python2.6/site-packages/ambari_server/dbConfiguration.py", 
> line 28, in 
> from ambari_server.serverConfiguration import decrypt_password_for_alias, 
> get_ambari_properties, get_is_secure, \
>   File 
> "/usr/lib/python2.6/site-packages/ambari_server/serverConfiguration.py", line 
> 552, in 
> configDefaults = ServerConfigDefaults()
>   File 
> "/usr/lib/python2.6/site-packages/ambari_server/serverConfiguration.py", line 
> 469, in __init__
> super(ServerConfigDefaultsLinux, self).__init__()
>   File 
> "/usr/lib/python2.6/site-packages/ambari_server/serverConfiguration.py", line 
> 349, in __init__
> self.PID_DIR = properties.get_property(PID_DIR_PROPERTY)
> AttributeError: 'int' object has no attribute 'get_property'
> {noformat}



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

[jira] [Commented] (AMBARI-18165) Hbase RegionServer start fails

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-18165:


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

{color:red}-1 patch{color}.  Top-level trunk compilation may be broken.

Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/8431//console

This message is automatically generated.

> Hbase RegionServer start fails
> --
>
> Key: AMBARI-18165
> URL: https://issues.apache.org/jira/browse/AMBARI-18165
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-18165.patch
>
>
> {code}
> Traceback (most recent call last):
>   File 
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_regionserver.py",
>  line 198, in 
> HbaseRegionServer().execute()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 280, in execute
> method(env)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 720, in restart
> self.start(env, upgrade_type=upgrade_type)
>   File 
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_regionserver.py",
>  line 124, in start
> self.post_start(env, upgrade_type=upgrade_type)
>   File 
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_regionserver.py",
>  line 89, in post_start
> self.apply_atlas_acl(params.hbase_user)
>   File 
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_regionserver.py",
>  line 114, in apply_atlas_acl
> shell.checked_call(format("{kinit_cmd}; {perm_cmd}"), 
> user=params.hbase_user, tries=10, try_sleep=10)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 71, in inner
> result = function(command, **kwargs)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 93, in checked_call
> tries=tries, try_sleep=try_sleep)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 141, in _call_wrapper
> result = _call(command, **kwargs_copy)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 294, in _call
> raise Fail(err_msg)
> resource_management.core.exceptions.Fail: Execution of '/usr/bin/kinit -kt 
> /etc/security/keytabs/hbase.service.keytab 
> hbase/nat-r6-gjss-ambari-blueprints-4re-1-1.openstacklo...@example.com; echo 
> "grant 'atlas', 'RWXCA', 'atlas_titan'" | hbase shell -n' returned 1. 
>  Hortonworks #
> This is MOTD message, added for testing in qe infra
> ERROR ArgumentError: Can't find a table: atlas_titan
> {code}



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

[jira] [Updated] (AMBARI-18165) Hbase RegionServer start fails

[Vitaly Brodetskyi (JIRA)]

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

Vitaly Brodetskyi updated AMBARI-18165:
---
Status: Patch Available  (was: Open)

> Hbase RegionServer start fails
> --
>
> Key: AMBARI-18165
> URL: https://issues.apache.org/jira/browse/AMBARI-18165
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-18165.patch
>
>
> {code}
> Traceback (most recent call last):
>   File 
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_regionserver.py",
>  line 198, in 
> HbaseRegionServer().execute()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 280, in execute
> method(env)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 720, in restart
> self.start(env, upgrade_type=upgrade_type)
>   File 
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_regionserver.py",
>  line 124, in start
> self.post_start(env, upgrade_type=upgrade_type)
>   File 
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_regionserver.py",
>  line 89, in post_start
> self.apply_atlas_acl(params.hbase_user)
>   File 
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_regionserver.py",
>  line 114, in apply_atlas_acl
> shell.checked_call(format("{kinit_cmd}; {perm_cmd}"), 
> user=params.hbase_user, tries=10, try_sleep=10)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 71, in inner
> result = function(command, **kwargs)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 93, in checked_call
> tries=tries, try_sleep=try_sleep)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 141, in _call_wrapper
> result = _call(command, **kwargs_copy)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 294, in _call
> raise Fail(err_msg)
> resource_management.core.exceptions.Fail: Execution of '/usr/bin/kinit -kt 
> /etc/security/keytabs/hbase.service.keytab 
> hbase/nat-r6-gjss-ambari-blueprints-4re-1-1.openstacklo...@example.com; echo 
> "grant 'atlas', 'RWXCA', 'atlas_titan'" | hbase shell -n' returned 1. 
>  Hortonworks #
> This is MOTD message, added for testing in qe infra
> ERROR ArgumentError: Can't find a table: atlas_titan
> {code}



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

[jira] [Updated] (AMBARI-18165) Hbase RegionServer start fails

[Vitaly Brodetskyi (JIRA)]

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

Vitaly Brodetskyi updated AMBARI-18165:
---
Attachment: AMBARI-18165.patch

> Hbase RegionServer start fails
> --
>
> Key: AMBARI-18165
> URL: https://issues.apache.org/jira/browse/AMBARI-18165
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-18165.patch
>
>
> {code}
> Traceback (most recent call last):
>   File 
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_regionserver.py",
>  line 198, in 
> HbaseRegionServer().execute()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 280, in execute
> method(env)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 720, in restart
> self.start(env, upgrade_type=upgrade_type)
>   File 
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_regionserver.py",
>  line 124, in start
> self.post_start(env, upgrade_type=upgrade_type)
>   File 
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_regionserver.py",
>  line 89, in post_start
> self.apply_atlas_acl(params.hbase_user)
>   File 
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_regionserver.py",
>  line 114, in apply_atlas_acl
> shell.checked_call(format("{kinit_cmd}; {perm_cmd}"), 
> user=params.hbase_user, tries=10, try_sleep=10)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 71, in inner
> result = function(command, **kwargs)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 93, in checked_call
> tries=tries, try_sleep=try_sleep)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 141, in _call_wrapper
> result = _call(command, **kwargs_copy)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 294, in _call
> raise Fail(err_msg)
> resource_management.core.exceptions.Fail: Execution of '/usr/bin/kinit -kt 
> /etc/security/keytabs/hbase.service.keytab 
> hbase/nat-r6-gjss-ambari-blueprints-4re-1-1.openstacklo...@example.com; echo 
> "grant 'atlas', 'RWXCA', 'atlas_titan'" | hbase shell -n' returned 1. 
>  Hortonworks #
> This is MOTD message, added for testing in qe infra
> ERROR ArgumentError: Can't find a table: atlas_titan
> {code}



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

[jira] [Created] (AMBARI-18165) Hbase RegionServer start fails

[Vitaly Brodetskyi (JIRA)]

Vitaly Brodetskyi created AMBARI-18165:
--

 Summary: Hbase RegionServer start fails
 Key: AMBARI-18165
 URL: https://issues.apache.org/jira/browse/AMBARI-18165
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: 2.4.0
Reporter: Vitaly Brodetskyi
Assignee: Vitaly Brodetskyi
Priority: Blocker
 Fix For: 2.4.0


{code}
Traceback (most recent call last):
  File 
"/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_regionserver.py",
 line 198, in 
HbaseRegionServer().execute()
  File 
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
 line 280, in execute
method(env)
  File 
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
 line 720, in restart
self.start(env, upgrade_type=upgrade_type)
  File 
"/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_regionserver.py",
 line 124, in start
self.post_start(env, upgrade_type=upgrade_type)
  File 
"/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_regionserver.py",
 line 89, in post_start
self.apply_atlas_acl(params.hbase_user)
  File 
"/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_regionserver.py",
 line 114, in apply_atlas_acl
shell.checked_call(format("{kinit_cmd}; {perm_cmd}"), 
user=params.hbase_user, tries=10, try_sleep=10)
  File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
line 71, in inner
result = function(command, **kwargs)
  File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
line 93, in checked_call
tries=tries, try_sleep=try_sleep)
  File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
line 141, in _call_wrapper
result = _call(command, **kwargs_copy)
  File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
line 294, in _call
raise Fail(err_msg)
resource_management.core.exceptions.Fail: Execution of '/usr/bin/kinit -kt 
/etc/security/keytabs/hbase.service.keytab 
hbase/nat-r6-gjss-ambari-blueprints-4re-1-1.openstacklo...@example.com; echo 
"grant 'atlas', 'RWXCA', 'atlas_titan'" | hbase shell -n' returned 1.  
Hortonworks #
This is MOTD message, added for testing in qe infra
ERROR ArgumentError: Can't find a table: atlas_titan
{code}



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

[jira] [Commented] (AMBARI-18159) Cover widget views with unit tests

[Hudson (JIRA)]

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

Hudson commented on AMBARI-18159:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5532 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5532/])
AMBARI-18159 Cover widget views with unit tests. (atkach) (atkach: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=797752341c83b38cedfbad3b89c61736eac69772])
* (edit) ambari-web/app/assets/test/tests.js
* (add) ambari-web/test/views/common/widget/template_widget_view_test.js
* (add) ambari-web/test/views/common/widget/heatmap_widget_view_test.js
* (edit) ambari-web/test/views/common/widget/graph_widget_view_test.js
* (edit) ambari-web/app/views/common/widget/gauge_widget_view.js
* (edit) ambari-web/app/views/common/widget/graph_widget_view.js
* (edit) ambari-web/test/views/common/widget/gauge_widget_view_test.js
* (edit) ambari-web/test/views/common/widget/number_widget_view_test.js
* (edit) ambari-web/app/views/common/widget/heatmap_widget_view.js


> Cover widget views with unit tests
> --
>
> Key: AMBARI-18159
> URL: https://issues.apache.org/jira/browse/AMBARI-18159
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
> Fix For: trunk
>
> Attachments: AMBARI-18159.patch
>
>
> Cover following files:
> * /ambari-web/app/views/common/widget/gauge_widget_view.js
> * /ambari-web/app/views/common/widget/graph_widget_view.js
> * /ambari-web/app/views/common/widget/heatmap_widget_view.js
> * /ambari-web/app/views/common/widget/number_widget_view.js
> * /ambari-web/app/views/common/widget/template_widget_view.js



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

[jira] [Commented] (AMBARI-18162) Tracebacks of exceptions should always be available

[Hudson (JIRA)]

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

Hudson commented on AMBARI-18162:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5532 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5532/])
AMBARI-18162. Tracebacks of exceptions should always be available (aonishuk: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=4a2ee5009c3246a89a37fcf837eafad289fb7892])
* (edit) ambari-common/src/main/python/resource_management/core/exceptions.py
* (edit) 
ambari-common/src/main/python/resource_management/libraries/script/script.py


> Tracebacks of exceptions should always be available
> ---
>
> Key: AMBARI-18162
> URL: https://issues.apache.org/jira/browse/AMBARI-18162
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 3.0.0
>
> Attachments: AMBARI-18162.patch
>
>
> We have a bunch of places similar to this (especially in python RU code):
> 
> 
> 
>   try:
> dfsadmin_base_command = get_dfsadmin_base_command(hdfs_binary)
> command = dfsadmin_base_command + ' -report -live'
> return_code, hdfs_output = shell.call(command, user=params.hdfs_user)
>   except:
> raise Fail('Unable to determine if the DataNode has started after 
> upgrade.')
> 
> Where the actual valuable information is just masked by re-raising exception
> and saying "something went wrong sorry". This makes issues very problematic to
> debug, especially on other users side, where it's often hard to receive any
> information.
> The solution would be to make Fail exception class to print the causing
> exception. Similar to what is done by default in Python3.
> Example:
> 
> 
> Traceback (most recent call last):
>   File 
> "/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/service_check.py",
>  line 150, in service_check
> Execute("hive mkdir /a")
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/base.py", line 
> 155, 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 273, in action_run
> tries=self.resource.tries, try_sleep=self.resource.try_sleep)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 
> 71, in inner
> result = function(command, **kwargs)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 
> 93, in checked_call
> tries=tries, try_sleep=try_sleep)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 
> 141, in _call_wrapper
> result = _call(command, **kwargs_copy)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 
> 294, in _call
> raise Fail(err_msg)
> Fail: Execution of 'hive mkdir /a' returned 127. /bin/bash: hive: command 
> not found
> 
> The above exception was the direct cause of the following exception:
> 
> Traceback (most recent call last):
>   File 
> "/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/service_check.py",
>  line 164, in 
> ServiceCheck().execute()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 280, in execute
> method(env)
>   File 
> "/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/service_check.py",
>  line 152, in service_check
> raise Fail(format("Something went wrong"))
> resource_management.core.exceptions.Fail: Something went wrong
> 



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

[jira] [Resolved] (AMBARI-18164) Enable Interactive Query should not be available in Add Service Wizard

[Aleksandr Kovalenko (JIRA)]

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

Aleksandr Kovalenko resolved AMBARI-18164.
--
Resolution: Fixed

> Enable Interactive Query should not be available in Add Service Wizard
> --
>
> Key: AMBARI-18164
> URL: https://issues.apache.org/jira/browse/AMBARI-18164
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-18164.patch
>
>




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

[jira] [Commented] (AMBARI-18037) Supervisor service check and restart is failing

[Jayush Luniya (JIRA)]

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

Jayush Luniya commented on AMBARI-18037:


[~shreyabh...@gmail.com]
Can you assign the JIRA to the developer who is working on this?

> Supervisor service check and restart is failing
> ---
>
> Key: AMBARI-18037
> URL: https://issues.apache.org/jira/browse/AMBARI-18037
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Shreya Bhat
>Priority: Blocker
>  Labels: system_test
> Fix For: 2.4.0
>
>
> Storm service checks (and restart) fails with :
> "Configuration parameter '\" + self.name + \"' was not found in 
> configurations dictionary!\")\nresource_management.core.exceptions.Fail: 
> Configuration parameter 'storm_principal_name' was not found in 
> configurations dictionary!",
> Looks related to : https://issues.apache.org/jira/browse/AMBARI-17772



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

[jira] [Commented] (AMBARI-18134) Hive metastore stop failed

[Jayush Luniya (JIRA)]

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

Jayush Luniya commented on AMBARI-18134:


[~shreyabh...@gmail.com]
Can you assign the JIRA to the developer who is working on this?


> Hive metastore stop failed
> --
>
> Key: AMBARI-18134
> URL: https://issues.apache.org/jira/browse/AMBARI-18134
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Shreya Bhat
>Priority: Blocker
>  Labels: system_test
> Fix For: 2.4.0
>
>
> Hive metastore start is failing after install with :
> {code}
>  "Traceback (most recent call last):\n  File 
> \"/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_metastore.py\",
>  line 254, in \nHiveMetastore().execute()\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\",
>  line 280, in execute\nmethod(env)\n  File 
> \"/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_metastore.py\",
>  line 59, in start\nself.configure(env)\n  File 
> \"/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_metastore.py\",
>  line 73, in configure\nhive(name = 'metastore')\n  File 
> \"/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py\", line 
> 89, in thunk\nreturn fn(*args, **kwargs)\n  File 
> \"/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive.py\",
>  line 320, in hive\nuser = params.hive_user\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/base.py\", line 
> 155, in __init__\nself.env.run()\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\", 
> line 160, in run\nself.run_action(resource, action)\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\", 
> line 124, in run_action\nprovider_action()\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py\",
>  line 273, in action_run\ntries=self.resource.tries, 
> try_sleep=self.resource.try_sleep)\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line 
> 71, in inner\nresult = function(command, **kwargs)\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line 
> 93, in checked_call\ntries=tries, try_sleep=try_sleep)\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line 
> 141, in _call_wrapper\nresult = _call(command, **kwargs_copy)\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line 
> 294, in _call\nraise 
> Fail(err_msg)\nresource_management.core.exceptions.Fail: Execution of 'export 
> HIVE_CONF_DIR=/usr/hdp/current/hive-metastore/conf/conf.server ; 
> /usr/hdp/current/hive-server2-hive2/bin/schematool -initSchema -dbType mysql 
> -userName hive -passWord [PROTECTED] -verbose' returned 1. SLF4J: Class path 
> contains multiple SLF4J bindings.\nSLF4J: Found binding in 
> [jar:file:/grid/0/hdp/2.5.0.0-1189/hive2/lib/log4j-slf4j-impl-2.6.2.jar!/org/slf4j/impl/StaticLoggerBinder.class]\nSLF4J:
>  Found binding in 
> [jar:file:/grid/0/hdp/2.5.0.0-1189/hadoop/lib/slf4j-log4j12-1.7.10.jar!/org/slf4j/impl/StaticLoggerBinder.class]\nSLF4J:
>  See http://www.slf4j.org/codes.html#multiple_bindings for an 
> explanation.\nSLF4J: Actual binding is of type 
> [org.apache.logging.slf4j.Log4jLoggerFactory]\nMetastore connection URL:\t 
> jdbc:mysql://nat-s11-4-sies-ambari-hosts-6-3.openstacklocal/hive\nMetastore 
> Connection Driver :\t com.mysql.jdbc.Driver\nMetastore connection User:\t 
> hive\norg.apache.hadoop.hive.metastore.HiveMetaException: Failed to load 
> driver\nUnderlying cause: java.lang.ClassNotFoundException : 
> com.mysql.jdbc.Driver\norg.apache.hadoop.hive.metastore.HiveMetaException: 
> Failed to load driver\n\tat 
> org.apache.hive.beeline.HiveSchemaHelper.getConnectionToMetastore(HiveSchemaHelper.java:82)\n\tat
>  
> org.apache.hive.beeline.HiveSchemaTool.getConnectionToMetastore(HiveSchemaTool.java:133)\n\tat
>  
> org.apache.hive.beeline.HiveSchemaTool.testConnectionToMetastore(HiveSchemaTool.java:187)\n\tat
>  org.apache.hive.beeline.HiveSchemaTool.doInit(HiveSchemaTool.java:291)\n\tat 
> org.apache.hive.beeline.HiveSchemaTool.doInit(HiveSchemaTool.java:277)\n\tat 
> org.apache.hive.beeline.HiveSchemaTool.main(HiveSchemaTool.java:526)\n\tat 
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)\n\tat 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)\n\tat
>  
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)\n\tat
>  

[jira] [Commented] (AMBARI-18157) Hive service check is failing after RU

[Jayush Luniya (JIRA)]

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

Jayush Luniya commented on AMBARI-18157:


[~shreyabh...@gmail.com]
Can you assign the JIRA to the developer who is working on this?

> Hive service check is failing after RU
> --
>
> Key: AMBARI-18157
> URL: https://issues.apache.org/jira/browse/AMBARI-18157
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Shreya Bhat
>Priority: Blocker
>  Labels: system_test
> Fix For: 2.4.0
>
>
> {code}
> resource_management.core.exceptions.Fail: Execution of 
> '/var/lib/ambari-agent/tmp/templetonSmoke.sh $HOSTNAME 50111 
> idtest.ambari-qa.1471340206.23.pig 
> /etc/security/keytabs/smokeuser.headless.keytab true /usr/bin/kinit 
> ambari-qa@REALM_NAME /var/lib/ambari-agent/tmp' returned 1. Templeton Smoke 
> Test (ddl cmd): Failed. : {"error":"Unauthorized connection for super-user: 
> HTTP/HOST_NAME@REALM_NAME from IP HOST_IP"}http_code <500>
> {code}



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

[jira] [Updated] (AMBARI-18164) Enable Interactive Query should not be available in Add Service Wizard

[Aleksandr Kovalenko (JIRA)]

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

Aleksandr Kovalenko updated AMBARI-18164:
-
Status: In Progress  (was: Patch Available)

committed to trunk and branch-2.4

> Enable Interactive Query should not be available in Add Service Wizard
> --
>
> Key: AMBARI-18164
> URL: https://issues.apache.org/jira/browse/AMBARI-18164
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-18164.patch
>
>




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

[jira] [Updated] (AMBARI-17661) Support YARN timeline plugin classpath config

[Jayush Luniya (JIRA)]

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

Jayush Luniya updated AMBARI-17661:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

Resolving this as fixed as the patch is already committed to 2.4. Please 
confirm!

> Support YARN timeline plugin classpath config
> -
>
> Key: AMBARI-17661
> URL: https://issues.apache.org/jira/browse/AMBARI-17661
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Reporter: Bikas Saha
>Assignee: Bikas Saha
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17661.1.patch, AMBARI-17661.2.patch, 
> AMBARI-17661.3.patch
>
>
> YARN-5233 added a config to specify the plugin classpath. Adding support for 
> that config.



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

[jira] [Updated] (AMBARI-18151) Oozie Hive actions fail when Atlas is installed since Atlas Hive Hooks need to be copied to Oozie Share Lib in HDFS

[Jayush Luniya (JIRA)]

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

Jayush Luniya updated AMBARI-18151:
---
Priority: Blocker  (was: Major)

> Oozie Hive actions fail when Atlas is installed since Atlas Hive Hooks need 
> to be copied to Oozie Share Lib in HDFS
> ---
>
> Key: AMBARI-18151
> URL: https://issues.apache.org/jira/browse/AMBARI-18151
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.4.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-18151.patch
>
>
> After the Falcon-Atlas hook has been enabled, the following properties are 
> added.
> startup.properties
> {noformat}
> *.application.services=org.apache.falcon.security.AuthenticationInitializationService,\
>   org.apache.falcon.workflow.WorkflowJobEndNotificationService, \
>   org.apache.falcon.service.ProcessSubscriberService,\
>   org.apache.falcon.extensions.ExtensionService,\
>   org.apache.falcon.service.LifecyclePolicyMap,\
>   org.apache.falcon.entity.store.ConfigurationStore,\
>   org.apache.falcon.rerun.service.RetryService,\
>   org.apache.falcon.rerun.service.LateRunService,\
>   org.apache.falcon.service.LogCleanupService,\
>   org.apache.falcon.metadata.MetadataMappingService,\
> org.apache.atlas.falcon.service.AtlasService
> {noformat}
> falcon-env.sh
> {noformat}
> # Add the Atlas Falcon hook to the Falcon classpath
> export 
> FALCON_EXTRA_CLASS_PATH=/usr/hdp/current/atlas-client/hook/falcon/*:${FALCON_EXTRA_CLASS_PATH}
> {noformat} 
> Whenever Oozie submits Hive actions, they fail and the application logs show
> {noformat}
> hive.exec.post.hooks Class not found:org.apache.atlas.hive.hook.HiveHook
> FAILED: Hive Internal Error: 
> java.lang.ClassNotFoundException(org.apache.atlas.hive.hook.HiveHook)
> java.lang.ClassNotFoundException: org.apache.atlas.hive.hook.HiveHook
>   at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
>   at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
>   at java.lang.Class.forName0(Native Method)
>   at java.lang.Class.forName(Class.java:348)
>   at org.apache.hadoop.hive.ql.hooks.HookUtils.getHooks(HookUtils.java:60)
>   at org.apache.hadoop.hive.ql.Driver.getHooks(Driver.java:1384)
>   at org.apache.hadoop.hive.ql.Driver.getHooks(Driver.java:1368)
>   at org.apache.hadoop.hive.ql.Driver.execute(Driver.java:1595)
>   at org.apache.hadoop.hive.ql.Driver.runInternal(Driver.java:1289)
>   at org.apache.hadoop.hive.ql.Driver.run(Driver.java:1156)
>   at org.apache.hadoop.hive.ql.Driver.run(Driver.java:1146)
>   at 
> org.apache.hadoop.hive.cli.CliDriver.processLocalCmd(CliDriver.java:216)
>   at org.apache.hadoop.hive.cli.CliDriver.processCmd(CliDriver.java:168)
>   at org.apache.hadoop.hive.cli.CliDriver.processLine(CliDriver.java:379)
>   at org.apache.hadoop.hive.cli.CliDriver.processLine(CliDriver.java:314)
>   at 
> org.apache.hadoop.hive.cli.CliDriver.processReader(CliDriver.java:412)
>   at org.apache.hadoop.hive.cli.CliDriver.processFile(CliDriver.java:428)
>   at 
> org.apache.hadoop.hive.cli.CliDriver.executeDriver(CliDriver.java:717)
>   at org.apache.hadoop.hive.cli.CliDriver.run(CliDriver.java:684)
>   at org.apache.hadoop.hive.cli.CliDriver.main(CliDriver.java:624)
>   at org.apache.oozie.action.hadoop.HiveMain.runHive(HiveMain.java:335)
>   at org.apache.oozie.action.hadoop.HiveMain.run(HiveMain.java:312)
>   at org.apache.oozie.action.hadoop.LauncherMain.run(LauncherMain.java:51)
>   at org.apache.oozie.action.hadoop.HiveMain.main(HiveMain.java:69)
>   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.oozie.action.hadoop.LauncherMapper.map(LauncherMapper.java:242)
>   at org.apache.hadoop.mapred.MapRunner.run(MapRunner.java:54)
>   at org.apache.hadoop.mapred.MapTask.runOldMapper(MapTask.java:453)
>   at org.apache.hadoop.mapred.MapTask.run(MapTask.java:343)
>   at org.apache.hadoop.mapred.YarnChild$2.run(YarnChild.java:168)
>   at java.security.AccessController.doPrivileged(Native Method)
>   at javax.security.auth.Subject.doAs(Subject.java:422)
>   at 
> 

[jira] [Commented] (AMBARI-18164) Enable Interactive Query should not be available in Add Service Wizard

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-18164:


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

{color:red}-1 patch{color}.  Top-level trunk compilation may be broken.

Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/8430//console

This message is automatically generated.

> Enable Interactive Query should not be available in Add Service Wizard
> --
>
> Key: AMBARI-18164
> URL: https://issues.apache.org/jira/browse/AMBARI-18164
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-18164.patch
>
>




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

[jira] [Updated] (AMBARI-18164) Enable Interactive Query should not be available in Add Service Wizard

[Aleksandr Kovalenko (JIRA)]

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

Aleksandr Kovalenko updated AMBARI-18164:
-
Attachment: AMBARI-18164.patch

> Enable Interactive Query should not be available in Add Service Wizard
> --
>
> Key: AMBARI-18164
> URL: https://issues.apache.org/jira/browse/AMBARI-18164
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-18164.patch
>
>




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

[jira] [Updated] (AMBARI-18164) Enable Interactive Query should not be available in Add Service Wizard

[Aleksandr Kovalenko (JIRA)]

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

Aleksandr Kovalenko updated AMBARI-18164:
-
Status: Patch Available  (was: Open)

> Enable Interactive Query should not be available in Add Service Wizard
> --
>
> Key: AMBARI-18164
> URL: https://issues.apache.org/jira/browse/AMBARI-18164
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-18164.patch
>
>




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

[jira] [Created] (AMBARI-18164) Enable Interactive Query should not be available in Add Service Wizard

[Aleksandr Kovalenko (JIRA)]

Aleksandr Kovalenko created AMBARI-18164:


 Summary: Enable Interactive Query should not be available in Add 
Service Wizard
 Key: AMBARI-18164
 URL: https://issues.apache.org/jira/browse/AMBARI-18164
 Project: Ambari
  Issue Type: Bug
  Components: ambari-web
Affects Versions: 2.4.0
Reporter: Aleksandr Kovalenko
Assignee: Aleksandr Kovalenko
Priority: Blocker
 Fix For: 2.4.0






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

[jira] [Updated] (AMBARI-18144) Fix Hive JDBC unit tests

[Jayush Luniya (JIRA)]

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

Jayush Luniya updated AMBARI-18144:
---
Fix Version/s: (was: trunk)
   2.4.0

> Fix Hive JDBC unit tests
> 
>
> Key: AMBARI-18144
> URL: https://issues.apache.org/jira/browse/AMBARI-18144
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-views
>Affects Versions: trunk
>Reporter: Ashwin Rajeev
>Assignee: Ashwin Rajeev
> Fix For: 2.4.0
>
> Attachments: AMBARI-18144.trunk.patch
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>




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

[jira] [Commented] (AMBARI-18144) Fix Hive JDBC unit tests

[Jayush Luniya (JIRA)]

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

Jayush Luniya commented on AMBARI-18144:


[~dbhowmick]
Since this is purely unit test changes we should be ok. No need to back out.

> Fix Hive JDBC unit tests
> 
>
> Key: AMBARI-18144
> URL: https://issues.apache.org/jira/browse/AMBARI-18144
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-views
>Affects Versions: trunk
>Reporter: Ashwin Rajeev
>Assignee: Ashwin Rajeev
> Fix For: 2.4.0
>
> Attachments: AMBARI-18144.trunk.patch
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>




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

[jira] [Updated] (AMBARI-17065) Memory leak on ambari-agent

[Jayush Luniya (JIRA)]

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

Jayush Luniya updated AMBARI-17065:
---
Fix Version/s: (was: 2.5.0)
   2.4.0

> Memory leak on ambari-agent
> ---
>
> Key: AMBARI-17065
> URL: https://issues.apache.org/jira/browse/AMBARI-17065
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.2.2
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
>Priority: Critical
> Fix For: 2.4.0
>
>
> Ambari-agent is leaking memory (3-7GB every few days), requiring the agent to 
> be restarted every 2 days.
> 17718 root 20 0 7343m 5.5g 4348 S 1.3 35.2 650:31.70 python2 --> 
> /usr/bin/python2 /usr/lib/python2.6/site-packages/ambari_agent/main.py start
> [root@gf0vsxbd022t ~]# ambari-agent --version 
> 2.2.1.0 
> [root@gf0vsxbd022t ~]# rpm -qa|grep ambari-agent 
> ambari-agent-2.2.1.0-161.x86_64 
> This issue had been resolved in Ambari 2.2.x branch. After Ambari upgrade, we 
> continue to see memory leaks on Ambari 2.2.1.
> Attaching pmap, lsof, configs and logs from the ambari agent process.



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

[jira] [Updated] (AMBARI-18140) Avoid hardcoded values in blueprint for hive and oozie

[Di Li (JIRA)]

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

Di Li updated AMBARI-18140:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Avoid hardcoded values in blueprint for hive and oozie
> --
>
> Key: AMBARI-18140
> URL: https://issues.apache.org/jira/browse/AMBARI-18140
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server, blueprints
>Affects Versions: 2.2.0
>Reporter: Amruta Borkar
>Assignee: Amruta Borkar
> Fix For: trunk
>
> Attachments: AMBARI-18140.patch
>
>
> There are a lot of hardcoded values in blueprint for hive.
> {
>   "hive-env" : {
> "properties_attributes" : { },
> "properties" : {
>   "hive_security_authorization" : "None",
>   "hive_log_dir" : "/var/log/hive",
>   "hive_existing_oracle_host" : "hardcodedhostname
> com",
>   "hive_user" : "hive",
>   "hive_existing_mssql_server_2_host" : "hardcodedhostname.com",
>   "hive.heapsize" : "1024",
>   "hcat_log_dir" : "/var/log/webhcat",
>   "hive_hostname" : "%HOSTGROUP::host_group_1%",
>   "hive_database" : "New MySQL Database",
>   "hive_exec_orc_storage_strategy" : "SPEED",
>   "hive_database_name" : "hive",
>   "webhcat_user" : "hcat",
>   "hive_txn_acid" : "off",
>   "hcat_pid_dir" : "/var/run/webhcat",
>   "hive.metastore.heapsize" : "1024",
>   "hive.client.heapsize" : "512",
>   "hive_existing_mssql_server_host" : "hardcodedhostname.com",
>   "hcat_user" : "hcat",
>   "hive_ambari_database" : "MySQL",
>   "content" : "\n if [ \"$SERVICE\" = \"cli\" ]; then\n   {%...}
>   "hive_pid_dir" : "/var/run/hive",
>   "hive_existing_postgresql_host" : "hardcodedhostname.com",
>   "hive_database_type" : "mysql",
>   "hive_existing_mysql_host" : "hardcodedhostname.
> com"
> }



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