[jira] [Updated] (AMBARI-19871) Config version switch/compare/revert doesn't work

[Richard Zang (JIRA)]

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

Richard Zang updated AMBARI-19871:
--
Status: Patch Available  (was: Open)

> Config version switch/compare/revert doesn't work
> -
>
> Key: AMBARI-19871
> URL: https://issues.apache.org/jira/browse/AMBARI-19871
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Richard Zang
>Assignee: Richard Zang
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19871.patch
>
>
> *Steps to reproduce:*
> 1. Go to any service with multiple config versions.
> 2. On the bottom left of the config history bar(the cross button), select an 
> older version and click View.
> *Actual result:*
> Now direct clicking on other config version block will not be able to switch 
> version. Only through the cross button can you switch to other version. 
> Compare configs also does not work, it always compare to the current version 
> and end up with empty diff.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-19871) Config version switch/compare/revert doesn't work

[Richard Zang (JIRA)]

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

Richard Zang updated AMBARI-19871:
--
Attachment: AMBARI-19871.patch

> Config version switch/compare/revert doesn't work
> -
>
> Key: AMBARI-19871
> URL: https://issues.apache.org/jira/browse/AMBARI-19871
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Richard Zang
>Assignee: Richard Zang
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19871.patch
>
>
> *Steps to reproduce:*
> 1. Go to any service with multiple config versions.
> 2. On the bottom left of the config history bar(the cross button), select an 
> older version and click View.
> *Actual result:*
> Now direct clicking on other config version block will not be able to switch 
> version. Only through the cross button can you switch to other version. 
> Compare configs also does not work, it always compare to the current version 
> and end up with empty diff.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (AMBARI-19871) Config version switch/compare/revert doesn't work

[Richard Zang (JIRA)]

Richard Zang created AMBARI-19871:
-

 Summary: Config version switch/compare/revert doesn't work
 Key: AMBARI-19871
 URL: https://issues.apache.org/jira/browse/AMBARI-19871
 Project: Ambari
  Issue Type: Bug
  Components: ambari-web
Affects Versions: 2.5.0
Reporter: Richard Zang
Assignee: Richard Zang
 Fix For: 2.5.0


*Steps to reproduce:*
1. Go to any service with multiple config versions.
2. On the bottom left of the config history bar(the cross button), select an 
older version and click View.

*Actual result:*
Now direct clicking on other config version block will not be able to switch 
version. Only through the cross button can you switch to other version. Compare 
configs also does not work, it always compare to the current version and end up 
with empty diff.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-19871) Config version switch/compare/revert doesn't work

[Richard Zang (JIRA)]

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

Richard Zang updated AMBARI-19871:
--
Priority: Critical  (was: Major)

> Config version switch/compare/revert doesn't work
> -
>
> Key: AMBARI-19871
> URL: https://issues.apache.org/jira/browse/AMBARI-19871
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Richard Zang
>Assignee: Richard Zang
>Priority: Critical
> Fix For: 2.5.0
>
>
> *Steps to reproduce:*
> 1. Go to any service with multiple config versions.
> 2. On the bottom left of the config history bar(the cross button), select an 
> older version and click View.
> *Actual result:*
> Now direct clicking on other config version block will not be able to switch 
> version. Only through the cross button can you switch to other version. 
> Compare configs also does not work, it always compare to the current version 
> and end up with empty diff.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-19319) Disable auto start before RU/EU and enable during finalization phase

[Yusaku Sako (JIRA)]

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

Yusaku Sako updated AMBARI-19319:
-
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Disable auto start before RU/EU and enable during finalization phase
> 
>
> Key: AMBARI-19319
> URL: https://issues.apache.org/jira/browse/AMBARI-19319
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19319.patch
>
>
> Add the API calls to disable/enable auto start and assign it to the UI team 
> to make the changes as part of RU/EU orchestration.
> Lets see if we can also design an alert that WARNs when autostart is disabled 
> - especially if it was disabled due to EU/RU.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-19827) HiveServer2 Interactive won't start in clusters with less memory

[Swapan Shridhar (JIRA)]

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

Swapan Shridhar updated AMBARI-19827:
-
Status: Patch Available  (was: Open)

> HiveServer2 Interactive won't start in clusters with less memory
> 
>
> Key: AMBARI-19827
> URL: https://issues.apache.org/jira/browse/AMBARI-19827
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-19827.patch
>
>
> HS2 Interactive in a 3 node local cluster with 3.5G memory in each node. The 
> task fails due to this exception:
> {code:java}
> WARN conf.HiveConf: HiveConf of name hive.llap.daemon.allow.permanent.fns 
> does not exist
> WARN conf.HiveConf: HiveConf hive.llap.daemon.vcpus.per.instance expects INT 
> type value
> Failed: null
> java.lang.IllegalArgumentException
>   at 
> java.util.concurrent.ThreadPoolExecutor.(ThreadPoolExecutor.java:1307)
>   at 
> java.util.concurrent.ThreadPoolExecutor.(ThreadPoolExecutor.java:1230)
>   at java.util.concurrent.Executors.newFixedThreadPool(Executors.java:151)
>   at 
> org.apache.hadoop.hive.llap.cli.LlapServiceDriver.run(LlapServiceDriver.java:197)
>   at 
> org.apache.hadoop.hive.llap.cli.LlapServiceDriver.main(LlapServiceDriver.java:112)
> INFO cli.LlapServiceDriver: LLAP service driver finished
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-19827) HiveServer2 Interactive won't start in clusters with less memory

[Swapan Shridhar (JIRA)]

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

Swapan Shridhar updated AMBARI-19827:
-
Status: Open  (was: Patch Available)

> HiveServer2 Interactive won't start in clusters with less memory
> 
>
> Key: AMBARI-19827
> URL: https://issues.apache.org/jira/browse/AMBARI-19827
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-19827.patch
>
>
> HS2 Interactive in a 3 node local cluster with 3.5G memory in each node. The 
> task fails due to this exception:
> {code:java}
> WARN conf.HiveConf: HiveConf of name hive.llap.daemon.allow.permanent.fns 
> does not exist
> WARN conf.HiveConf: HiveConf hive.llap.daemon.vcpus.per.instance expects INT 
> type value
> Failed: null
> java.lang.IllegalArgumentException
>   at 
> java.util.concurrent.ThreadPoolExecutor.(ThreadPoolExecutor.java:1307)
>   at 
> java.util.concurrent.ThreadPoolExecutor.(ThreadPoolExecutor.java:1230)
>   at java.util.concurrent.Executors.newFixedThreadPool(Executors.java:151)
>   at 
> org.apache.hadoop.hive.llap.cli.LlapServiceDriver.run(LlapServiceDriver.java:197)
>   at 
> org.apache.hadoop.hive.llap.cli.LlapServiceDriver.main(LlapServiceDriver.java:112)
> INFO cli.LlapServiceDriver: LLAP service driver finished
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-19827) HiveServer2 Interactive won't start in clusters with less memory

[Swapan Shridhar (JIRA)]

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

Swapan Shridhar updated AMBARI-19827:
-
Attachment: (was: AMBARI-19827.patch)

> HiveServer2 Interactive won't start in clusters with less memory
> 
>
> Key: AMBARI-19827
> URL: https://issues.apache.org/jira/browse/AMBARI-19827
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-19827.patch
>
>
> HS2 Interactive in a 3 node local cluster with 3.5G memory in each node. The 
> task fails due to this exception:
> {code:java}
> WARN conf.HiveConf: HiveConf of name hive.llap.daemon.allow.permanent.fns 
> does not exist
> WARN conf.HiveConf: HiveConf hive.llap.daemon.vcpus.per.instance expects INT 
> type value
> Failed: null
> java.lang.IllegalArgumentException
>   at 
> java.util.concurrent.ThreadPoolExecutor.(ThreadPoolExecutor.java:1307)
>   at 
> java.util.concurrent.ThreadPoolExecutor.(ThreadPoolExecutor.java:1230)
>   at java.util.concurrent.Executors.newFixedThreadPool(Executors.java:151)
>   at 
> org.apache.hadoop.hive.llap.cli.LlapServiceDriver.run(LlapServiceDriver.java:197)
>   at 
> org.apache.hadoop.hive.llap.cli.LlapServiceDriver.main(LlapServiceDriver.java:112)
> INFO cli.LlapServiceDriver: LLAP service driver finished
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-19827) HiveServer2 Interactive won't start in clusters with less memory

[Swapan Shridhar (JIRA)]

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

Swapan Shridhar updated AMBARI-19827:
-
Attachment: AMBARI-19827.patch

> HiveServer2 Interactive won't start in clusters with less memory
> 
>
> Key: AMBARI-19827
> URL: https://issues.apache.org/jira/browse/AMBARI-19827
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-19827.patch
>
>
> HS2 Interactive in a 3 node local cluster with 3.5G memory in each node. The 
> task fails due to this exception:
> {code:java}
> WARN conf.HiveConf: HiveConf of name hive.llap.daemon.allow.permanent.fns 
> does not exist
> WARN conf.HiveConf: HiveConf hive.llap.daemon.vcpus.per.instance expects INT 
> type value
> Failed: null
> java.lang.IllegalArgumentException
>   at 
> java.util.concurrent.ThreadPoolExecutor.(ThreadPoolExecutor.java:1307)
>   at 
> java.util.concurrent.ThreadPoolExecutor.(ThreadPoolExecutor.java:1230)
>   at java.util.concurrent.Executors.newFixedThreadPool(Executors.java:151)
>   at 
> org.apache.hadoop.hive.llap.cli.LlapServiceDriver.run(LlapServiceDriver.java:197)
>   at 
> org.apache.hadoop.hive.llap.cli.LlapServiceDriver.main(LlapServiceDriver.java:112)
> INFO cli.LlapServiceDriver: LLAP service driver finished
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-19859) The user must be clearly communicated about YARN pre-emption requirements when Hive LLAP is enabled

[Hudson (JIRA)]

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

Hudson commented on AMBARI-19859:
-

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6647 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6647/])
AMBARI-19859. The user must be clearly communicated about YARN (yusaku: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=eba63884beeb7096834a374b710ea6e7f0d7b7f8])
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.6/services/HIVE/configuration/hive-interactive-env.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.5/services/HIVE/configuration/hive-interactive-env.xml


> The user must be clearly communicated about YARN pre-emption requirements 
> when Hive LLAP is enabled
> ---
>
> Key: AMBARI-19859
> URL: https://issues.apache.org/jira/browse/AMBARI-19859
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Vivek Ratnavel Subramanian
>Assignee: Vivek Ratnavel Subramanian
> Fix For: 2.5.0
>
> Attachments: AMBARI-19859.v0.patch, AMBARI-19859.v1.patch, Ambari   
> c1.png, Screen Shot 2017-02-02 at 7.02.45 PM.png
>
>
> Capacity Scheduler preemption is not enabled by default in HDP. Enabling it 
> affects the entire cluster. But it is strongly recommended to enable YARN 
> pre-emption before enabling Hive LLAP. The user needs to be warned about this 
> before enabling Interactive Query in Hive configs page.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-19830) HDP 3.0 TP - Support changed configs and scripts for HDFS

[Hudson (JIRA)]

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

Hudson commented on AMBARI-19830:
-

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6647 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6647/])
AMBARI-19830. HDP 3.0 TP - Support changed configs and scripts for HDFS 
(afernandez: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=e4bac844b33539b06e4208e058e7d89c7761eb99])
* (edit) ambari-server/src/test/python/stacks/2.5/HIVE/test_hive_server_int.py
* (edit) ambari-server/src/test/python/unitTests.py
* (edit) 
ambari-server/src/main/resources/common-services/HDFS/3.0.0.3.0/package/scripts/utils.py
* (edit) 
ambari-server/src/main/resources/common-services/HDFS/3.0.0.3.0/configuration/hdfs-site.xml
* (edit) 
ambari-server/src/main/resources/common-services/HDFS/3.0.0.3.0/package/scripts/params_linux.py


> HDP 3.0 TP - Support changed configs and scripts for HDFS
> -
>
> Key: AMBARI-19830
> URL: https://issues.apache.org/jira/browse/AMBARI-19830
> Project: Ambari
>  Issue Type: Story
>  Components: stacks
>Affects Versions: 3.0.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 3.0.0
>
> Attachments: AMBARI-19830.patch
>
>
> In HDP 3.0, there are expected changes to configs and the startup scripts for 
> HDFS.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-19859) The user must be clearly communicated about YARN pre-emption requirements when Hive LLAP is enabled

[Hudson (JIRA)]

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

Hudson commented on AMBARI-19859:
-

FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #905 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/905/])
AMBARI-19859. The user must be clearly communicated about YARN (yusaku: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=e8cef81e46c87cdff3e156a4b3f038be4b8e3d58])
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.6/services/HIVE/configuration/hive-interactive-env.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.5/services/HIVE/configuration/hive-interactive-env.xml


> The user must be clearly communicated about YARN pre-emption requirements 
> when Hive LLAP is enabled
> ---
>
> Key: AMBARI-19859
> URL: https://issues.apache.org/jira/browse/AMBARI-19859
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Vivek Ratnavel Subramanian
>Assignee: Vivek Ratnavel Subramanian
> Fix For: 2.5.0
>
> Attachments: AMBARI-19859.v0.patch, AMBARI-19859.v1.patch, Ambari   
> c1.png, Screen Shot 2017-02-02 at 7.02.45 PM.png
>
>
> Capacity Scheduler preemption is not enabled by default in HDP. Enabling it 
> affects the entire cluster. But it is strongly recommended to enable YARN 
> pre-emption before enabling Hive LLAP. The user needs to be warned about this 
> before enabling Interactive Query in Hive configs page.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-19858) Add "live_hosts" metric in AMS for apps

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-19858:


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

{color:red}-1 patch{color}.  The patch command could not apply the patch.

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

This message is automatically generated.

> Add "live_hosts" metric in AMS for apps
> ---
>
> Key: AMBARI-19858
> URL: https://issues.apache.org/jira/browse/AMBARI-19858
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-metrics
>Affects Versions: 2.5.0
>Reporter: Siddharth Wagle
>Assignee: Aravindan Vijayan
> Fix For: 2.5.0
>
> Attachments: AMBARI-19858-2.patch, AMBARI-19858.patch
>
>
> {quote}
> live_hosts=> # count of total hosts reporting 
> metrics
> live_hosts & appId =  => # count of hosts hosting this appId
> {quote}
> Where appId = { namenode, datanode, hbase ... etc }



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-19830) HDP 3.0 TP - Support changed configs and scripts for HDFS

[Alejandro Fernandez (JIRA)]

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

Alejandro Fernandez updated AMBARI-19830:
-
Resolution: Fixed
Status: Resolved  (was: Patch Available)

Pushed to trunk, commit e4bac844b33539b06e4208e058e7d89c7761eb99

> HDP 3.0 TP - Support changed configs and scripts for HDFS
> -
>
> Key: AMBARI-19830
> URL: https://issues.apache.org/jira/browse/AMBARI-19830
> Project: Ambari
>  Issue Type: Story
>  Components: stacks
>Affects Versions: 3.0.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 3.0.0
>
> Attachments: AMBARI-19830.patch
>
>
> In HDP 3.0, there are expected changes to configs and the startup scripts for 
> HDFS.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-19594) configure kerberos authentication for Druid UIs

[Hudson (JIRA)]

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

Hudson commented on AMBARI-19594:
-

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6646 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6646/])
AMBARI-19594. configure kerberos authentication for Druid UIs (Nishant 
(smohanty: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=dca9135af7702ec21f91859095ef34332cc6cc30])
* (edit) 
ambari-server/src/main/resources/common-services/DRUID/0.9.2/package/scripts/params.py
* (edit) 
ambari-server/src/main/resources/common-services/DRUID/0.9.2/package/scripts/druid.py
* (edit) 
ambari-server/src/main/resources/common-services/DRUID/0.9.2/configuration/druid-common.xml
* (edit) ambari-server/src/test/python/stacks/2.6/DRUID/test_druid.py
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.6/services/DRUID/kerberos.json
* (edit) ambari-server/src/test/python/stacks/2.6/configs/default.json


> configure kerberos authentication for Druid UIs
> ---
>
> Key: AMBARI-19594
> URL: https://issues.apache.org/jira/browse/AMBARI-19594
> Project: Ambari
>  Issue Type: Task
>Reporter: Nishant Bangarwa
>Assignee: Nishant Bangarwa
> Fix For: trunk, 2.5.0
>
> Attachments: ambari-19594.patch
>
>
> Druid Now supports kerberos authentication for UIs using SPNego 
> (https://github.com/druid-io/druid/pull/3853). 
> This task is to make druid end points secure when kerberos is enabled - 
> 1) Add druid-kerberos extension to druid extensions
> 2) Set druid.authentication.type to kerberos 
> 3) configure spnego keytab and principal in druid configs



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-19859) The user must be clearly communicated about YARN pre-emption requirements when Hive LLAP is enabled

[Yusaku Sako (JIRA)]

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

Yusaku Sako commented on AMBARI-19859:
--

+1'd on ReviewBoard.
Committed to trunk and branch-2.5.

> The user must be clearly communicated about YARN pre-emption requirements 
> when Hive LLAP is enabled
> ---
>
> Key: AMBARI-19859
> URL: https://issues.apache.org/jira/browse/AMBARI-19859
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Vivek Ratnavel Subramanian
>Assignee: Vivek Ratnavel Subramanian
> Fix For: 2.5.0
>
> Attachments: AMBARI-19859.v0.patch, AMBARI-19859.v1.patch, Ambari   
> c1.png, Screen Shot 2017-02-02 at 7.02.45 PM.png
>
>
> Capacity Scheduler preemption is not enabled by default in HDP. Enabling it 
> affects the entire cluster. But it is strongly recommended to enable YARN 
> pre-emption before enabling Hive LLAP. The user needs to be warned about this 
> before enabling Interactive Query in Hive configs page.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-19870) Add Superset as a UI for Druid in HDP

[Nishant Bangarwa (JIRA)]

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

Nishant Bangarwa updated AMBARI-19870:
--
Attachment: ambari-19870.patch

> Add Superset as a UI for Druid in HDP
> -
>
> Key: AMBARI-19870
> URL: https://issues.apache.org/jira/browse/AMBARI-19870
> Project: Ambari
>  Issue Type: Task
>Reporter: Nishant Bangarwa
>Assignee: Nishant Bangarwa
> Attachments: ambari-19870.patch
>
>
> Add superset stack definitions to HDP 2.6



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-19859) The user must be clearly communicated about YARN pre-emption requirements when Hive LLAP is enabled

[Yusaku Sako (JIRA)]

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

Yusaku Sako updated AMBARI-19859:
-
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> The user must be clearly communicated about YARN pre-emption requirements 
> when Hive LLAP is enabled
> ---
>
> Key: AMBARI-19859
> URL: https://issues.apache.org/jira/browse/AMBARI-19859
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Vivek Ratnavel Subramanian
>Assignee: Vivek Ratnavel Subramanian
> Fix For: 2.5.0
>
> Attachments: AMBARI-19859.v0.patch, AMBARI-19859.v1.patch, Ambari   
> c1.png, Screen Shot 2017-02-02 at 7.02.45 PM.png
>
>
> Capacity Scheduler preemption is not enabled by default in HDP. Enabling it 
> affects the entire cluster. But it is strongly recommended to enable YARN 
> pre-emption before enabling Hive LLAP. The user needs to be warned about this 
> before enabling Interactive Query in Hive configs page.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (AMBARI-19870) Add Superset as a UI for Druid in HDP

[Nishant Bangarwa (JIRA)]

Nishant Bangarwa created AMBARI-19870:
-

 Summary: Add Superset as a UI for Druid in HDP
 Key: AMBARI-19870
 URL: https://issues.apache.org/jira/browse/AMBARI-19870
 Project: Ambari
  Issue Type: Task
Reporter: Nishant Bangarwa
Assignee: Nishant Bangarwa


Add superset stack definitions to HDP 2.6




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-19865) Ambari-server logon failure: Hadoop-common dependency on servlet-api 2.5

[Nahappan Somasundaram (JIRA)]

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

Nahappan Somasundaram commented on AMBARI-19865:


Committed to branch-2.5 and trunk

> Ambari-server logon failure: Hadoop-common dependency on servlet-api 2.5 
> -
>
> Key: AMBARI-19865
> URL: https://issues.apache.org/jira/browse/AMBARI-19865
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
> Fix For: 2.5.0
>
> Attachments: rb56281.patch
>
>
> CredentialUtil uses hadoop-common which depends on servlet-api 2.5. This 
> causes a failure during ambari-server logon:
> {code}
> 02 Feb 2017 13:15:57,992  WARN [ambari-client-thread-25] ServletHandler:592 - 
> Error for /api/v1/clusters
> java.lang.NoSuchMethodError: 
> javax.servlet.http.HttpServletResponse.getStatus()I
> at 
> org.apache.ambari.server.security.authorization.AmbariAuthorizationFilter.doFilter(AmbariAuthorizationFilter.java:277)
> at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
> at 
> org.springframework.security.web.access.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:113)
> at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
> at 
> org.springframework.security.web.session.SessionManagementFilter.doFilter(SessionManagementFilter.java:103)
> at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
> at 
> org.springframework.security.web.authentication.AnonymousAuthenticationFilter.doFilter(AnonymousAuthenticationFilter.java:113)
> at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
> {code}
> This happens because of classpath collision between multiple servlet api 
> versions. The org.apache.hadoop:hadoop-common depends on an old version of 
> servlet api (2.5).
> {code}
> [INFO] +- org.apache.hadoop:hadoop-common:jar:2.7.2:compile
> [INFO] |  +- xmlenc:xmlenc:jar:0.52:compile
> [INFO] |  +- commons-httpclient:commons-httpclient:jar:3.1:compile
> [INFO] |  +- javax.servlet:servlet-api:jar:2.5:compile
> [INFO] |  +- org.mortbay.jetty:jetty:jar:6.1.26:compile
> [INFO] |  +- org.mortbay.jetty:jetty-util:jar:6.1.26:compile
> [INFO] |  +- javax.servlet.jsp:jsp-api:jar:2.1:runtime
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-19865) Ambari-server logon failure: Hadoop-common dependency on servlet-api 2.5

[Nahappan Somasundaram (JIRA)]

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

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

> Ambari-server logon failure: Hadoop-common dependency on servlet-api 2.5 
> -
>
> Key: AMBARI-19865
> URL: https://issues.apache.org/jira/browse/AMBARI-19865
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
> Fix For: 2.5.0
>
> Attachments: rb56281.patch
>
>
> CredentialUtil uses hadoop-common which depends on servlet-api 2.5. This 
> causes a failure during ambari-server logon:
> {code}
> 02 Feb 2017 13:15:57,992  WARN [ambari-client-thread-25] ServletHandler:592 - 
> Error for /api/v1/clusters
> java.lang.NoSuchMethodError: 
> javax.servlet.http.HttpServletResponse.getStatus()I
> at 
> org.apache.ambari.server.security.authorization.AmbariAuthorizationFilter.doFilter(AmbariAuthorizationFilter.java:277)
> at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
> at 
> org.springframework.security.web.access.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:113)
> at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
> at 
> org.springframework.security.web.session.SessionManagementFilter.doFilter(SessionManagementFilter.java:103)
> at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
> at 
> org.springframework.security.web.authentication.AnonymousAuthenticationFilter.doFilter(AnonymousAuthenticationFilter.java:113)
> at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
> {code}
> This happens because of classpath collision between multiple servlet api 
> versions. The org.apache.hadoop:hadoop-common depends on an old version of 
> servlet api (2.5).
> {code}
> [INFO] +- org.apache.hadoop:hadoop-common:jar:2.7.2:compile
> [INFO] |  +- xmlenc:xmlenc:jar:0.52:compile
> [INFO] |  +- commons-httpclient:commons-httpclient:jar:3.1:compile
> [INFO] |  +- javax.servlet:servlet-api:jar:2.5:compile
> [INFO] |  +- org.mortbay.jetty:jetty:jar:6.1.26:compile
> [INFO] |  +- org.mortbay.jetty:jetty-util:jar:6.1.26:compile
> [INFO] |  +- javax.servlet.jsp:jsp-api:jar:2.1:runtime
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-19830) HDP 3.0 TP - Support changed configs and scripts for HDFS

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-19830:


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

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

{color:green}+1 tests included{color}.  The patch appears to include 2 new 
or modified test files.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in 
ambari-server.

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

This message is automatically generated.

> HDP 3.0 TP - Support changed configs and scripts for HDFS
> -
>
> Key: AMBARI-19830
> URL: https://issues.apache.org/jira/browse/AMBARI-19830
> Project: Ambari
>  Issue Type: Story
>  Components: stacks
>Affects Versions: 3.0.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 3.0.0
>
> Attachments: AMBARI-19830.patch
>
>
> In HDP 3.0, there are expected changes to configs and the startup scripts for 
> HDFS.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-19730) Namenodes fail to come up after removing some Journalnodes

[Vivek Rathod (JIRA)]

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

Vivek Rathod commented on AMBARI-19730:
---

Thanks [~stoader] for the analysis

> Namenodes fail to come up after removing some Journalnodes
> --
>
> Key: AMBARI-19730
> URL: https://issues.apache.org/jira/browse/AMBARI-19730
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Vivek Rathod
> Fix For: 2.5.0
>
>
> Namenodes fail to come up after removing some Journalnodes
> STR:
> Deploy a 6 node HA cluster using Blueprints, with 6 Journalnodes. 
> Remove 2 Journalnodes using Manage JN Wizard
> In the Start All Services in Manage JN Wizard, Both the Namenodes fail to 
> come up.
> {code}
> 17/01/26 03:39:56 INFO ipc.Client: Retrying connect to server: 
> /:8020. Already tried 0 time(s); 
> retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=1, 
> sleepTime=1000 MILLISECONDS)
> 17/01/26 03:39:56 WARN ipc.Client: Failed to connect to server: 
> /:8020: retries get failed due to 
> exceeded maximum allowed retries number: 1
> java.net.ConnectException: Connection refused
>   at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
>   at 
> sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717)
>   at 
> org.apache.hadoop.net.SocketIOWithTimeout.connect(SocketIOWithTimeout.java:206)
>   at org.apache.hadoop.net.NetUtils.connect(NetUtils.java:531)
>   at org.apache.hadoop.net.NetUtils.connect(NetUtils.java:495)
>   at 
> org.apache.hadoop.ipc.Client$Connection.setupConnection(Client.java:650)
>   at 
> org.apache.hadoop.ipc.Client$Connection.setupIOstreams(Client.java:745)
>   at org.apache.hadoop.ipc.Client$Connection.access$3200(Client.java:397)
>   at org.apache.hadoop.ipc.Client.getConnection(Client.java:1618)
>   at org.apache.hadoop.ipc.Client.call(Client.java:1449)
>   at org.apache.hadoop.ipc.Client.call(Client.java:1396)
>   at 
> org.apache.hadoop.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:233)
>   at com.sun.proxy.$Proxy8.getServiceStatus(Unknown Source)
>   at 
> org.apache.hadoop.ha.protocolPB.HAServiceProtocolClientSideTranslatorPB.getServiceStatus(HAServiceProtocolClientSideTranslatorPB.java:122)
>   at org.apache.hadoop.ha.HAAdmin.getServiceState(HAAdmin.java:359)
>   at org.apache.hadoop.ha.HAAdmin.runCmd(HAAdmin.java:457)
>   at org.apache.hadoop.hdfs.tools.DFSHAAdmin.runCmd(DFSHAAdmin.java:120)
>   at org.apache.hadoop.ha.HAAdmin.run(HAAdmin.java:384)
>   at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:76)
>   at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:90)
>   at org.apache.hadoop.hdfs.tools.DFSHAAdmin.main(DFSHAAdmin.java:132)
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (AMBARI-19730) Namenodes fail to come up after removing some Journalnodes

[Vivek Rathod (JIRA)]

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

Vivek Rathod resolved AMBARI-19730.
---
Resolution: Invalid

> Namenodes fail to come up after removing some Journalnodes
> --
>
> Key: AMBARI-19730
> URL: https://issues.apache.org/jira/browse/AMBARI-19730
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Vivek Rathod
> Fix For: 2.5.0
>
>
> Namenodes fail to come up after removing some Journalnodes
> STR:
> Deploy a 6 node HA cluster using Blueprints, with 6 Journalnodes. 
> Remove 2 Journalnodes using Manage JN Wizard
> In the Start All Services in Manage JN Wizard, Both the Namenodes fail to 
> come up.
> {code}
> 17/01/26 03:39:56 INFO ipc.Client: Retrying connect to server: 
> /:8020. Already tried 0 time(s); 
> retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=1, 
> sleepTime=1000 MILLISECONDS)
> 17/01/26 03:39:56 WARN ipc.Client: Failed to connect to server: 
> /:8020: retries get failed due to 
> exceeded maximum allowed retries number: 1
> java.net.ConnectException: Connection refused
>   at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
>   at 
> sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717)
>   at 
> org.apache.hadoop.net.SocketIOWithTimeout.connect(SocketIOWithTimeout.java:206)
>   at org.apache.hadoop.net.NetUtils.connect(NetUtils.java:531)
>   at org.apache.hadoop.net.NetUtils.connect(NetUtils.java:495)
>   at 
> org.apache.hadoop.ipc.Client$Connection.setupConnection(Client.java:650)
>   at 
> org.apache.hadoop.ipc.Client$Connection.setupIOstreams(Client.java:745)
>   at org.apache.hadoop.ipc.Client$Connection.access$3200(Client.java:397)
>   at org.apache.hadoop.ipc.Client.getConnection(Client.java:1618)
>   at org.apache.hadoop.ipc.Client.call(Client.java:1449)
>   at org.apache.hadoop.ipc.Client.call(Client.java:1396)
>   at 
> org.apache.hadoop.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:233)
>   at com.sun.proxy.$Proxy8.getServiceStatus(Unknown Source)
>   at 
> org.apache.hadoop.ha.protocolPB.HAServiceProtocolClientSideTranslatorPB.getServiceStatus(HAServiceProtocolClientSideTranslatorPB.java:122)
>   at org.apache.hadoop.ha.HAAdmin.getServiceState(HAAdmin.java:359)
>   at org.apache.hadoop.ha.HAAdmin.runCmd(HAAdmin.java:457)
>   at org.apache.hadoop.hdfs.tools.DFSHAAdmin.runCmd(DFSHAAdmin.java:120)
>   at org.apache.hadoop.ha.HAAdmin.run(HAAdmin.java:384)
>   at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:76)
>   at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:90)
>   at org.apache.hadoop.hdfs.tools.DFSHAAdmin.main(DFSHAAdmin.java:132)
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-19859) The user must be clearly communicated about YARN pre-emption requirements when Hive LLAP is enabled

[Vivek Ratnavel Subramanian (JIRA)]

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

Vivek Ratnavel Subramanian commented on AMBARI-19859:
-

The test failure is not related to this patch.

> The user must be clearly communicated about YARN pre-emption requirements 
> when Hive LLAP is enabled
> ---
>
> Key: AMBARI-19859
> URL: https://issues.apache.org/jira/browse/AMBARI-19859
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Vivek Ratnavel Subramanian
>Assignee: Vivek Ratnavel Subramanian
> Fix For: 2.5.0
>
> Attachments: AMBARI-19859.v0.patch, AMBARI-19859.v1.patch, Ambari   
> c1.png, Screen Shot 2017-02-02 at 7.02.45 PM.png
>
>
> Capacity Scheduler preemption is not enabled by default in HDP. Enabling it 
> affects the entire cluster. But it is strongly recommended to enable YARN 
> pre-emption before enabling Hive LLAP. The user needs to be warned about this 
> before enabling Interactive Query in Hive configs page.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-19730) Namenodes fail to come up after removing some Journalnodes

[Vivek Rathod (JIRA)]

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

Vivek Rathod commented on AMBARI-19730:
---

Closing this as invalid issue because format Journalnodes did not execute 
correctly as dfs.namenode.shared.edits.dir pointed to only 3 JournalNodes 
instead of all 6. 

Setting the value of dfs.namenode.shared.edits.dir to 
qjournal://localhost:8485/mycluster worked because by specifying localhost in 
the value, Blueprint processor recognises "localhost" and replaces with the 
necessary real host names

> Namenodes fail to come up after removing some Journalnodes
> --
>
> Key: AMBARI-19730
> URL: https://issues.apache.org/jira/browse/AMBARI-19730
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Vivek Rathod
> Fix For: 2.5.0
>
>
> Namenodes fail to come up after removing some Journalnodes
> STR:
> Deploy a 6 node HA cluster using Blueprints, with 6 Journalnodes. 
> Remove 2 Journalnodes using Manage JN Wizard
> In the Start All Services in Manage JN Wizard, Both the Namenodes fail to 
> come up.
> {code}
> 17/01/26 03:39:56 INFO ipc.Client: Retrying connect to server: 
> /:8020. Already tried 0 time(s); 
> retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=1, 
> sleepTime=1000 MILLISECONDS)
> 17/01/26 03:39:56 WARN ipc.Client: Failed to connect to server: 
> /:8020: retries get failed due to 
> exceeded maximum allowed retries number: 1
> java.net.ConnectException: Connection refused
>   at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
>   at 
> sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717)
>   at 
> org.apache.hadoop.net.SocketIOWithTimeout.connect(SocketIOWithTimeout.java:206)
>   at org.apache.hadoop.net.NetUtils.connect(NetUtils.java:531)
>   at org.apache.hadoop.net.NetUtils.connect(NetUtils.java:495)
>   at 
> org.apache.hadoop.ipc.Client$Connection.setupConnection(Client.java:650)
>   at 
> org.apache.hadoop.ipc.Client$Connection.setupIOstreams(Client.java:745)
>   at org.apache.hadoop.ipc.Client$Connection.access$3200(Client.java:397)
>   at org.apache.hadoop.ipc.Client.getConnection(Client.java:1618)
>   at org.apache.hadoop.ipc.Client.call(Client.java:1449)
>   at org.apache.hadoop.ipc.Client.call(Client.java:1396)
>   at 
> org.apache.hadoop.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:233)
>   at com.sun.proxy.$Proxy8.getServiceStatus(Unknown Source)
>   at 
> org.apache.hadoop.ha.protocolPB.HAServiceProtocolClientSideTranslatorPB.getServiceStatus(HAServiceProtocolClientSideTranslatorPB.java:122)
>   at org.apache.hadoop.ha.HAAdmin.getServiceState(HAAdmin.java:359)
>   at org.apache.hadoop.ha.HAAdmin.runCmd(HAAdmin.java:457)
>   at org.apache.hadoop.hdfs.tools.DFSHAAdmin.runCmd(DFSHAAdmin.java:120)
>   at org.apache.hadoop.ha.HAAdmin.run(HAAdmin.java:384)
>   at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:76)
>   at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:90)
>   at org.apache.hadoop.hdfs.tools.DFSHAAdmin.main(DFSHAAdmin.java:132)
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-19594) configure kerberos authentication for Druid UIs

[Hudson (JIRA)]

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

Hudson commented on AMBARI-19594:
-

SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #904 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/904/])
AMBARI-19594. configure kerberos authentication for Druid UIs (Nishant 
(smohanty: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=caa69171b163a547341da5f4341ba6d0df66ceb5])
* (edit) ambari-server/src/test/python/stacks/2.6/DRUID/test_druid.py
* (edit) 
ambari-server/src/main/resources/common-services/DRUID/0.9.2/package/scripts/params.py
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.6/services/DRUID/kerberos.json
* (edit) 
ambari-server/src/main/resources/common-services/DRUID/0.9.2/configuration/druid-common.xml
* (edit) ambari-server/src/test/python/stacks/2.6/configs/default.json
* (edit) 
ambari-server/src/main/resources/common-services/DRUID/0.9.2/package/scripts/druid.py


> configure kerberos authentication for Druid UIs
> ---
>
> Key: AMBARI-19594
> URL: https://issues.apache.org/jira/browse/AMBARI-19594
> Project: Ambari
>  Issue Type: Task
>Reporter: Nishant Bangarwa
>Assignee: Nishant Bangarwa
> Fix For: trunk, 2.5.0
>
> Attachments: ambari-19594.patch
>
>
> Druid Now supports kerberos authentication for UIs using SPNego 
> (https://github.com/druid-io/druid/pull/3853). 
> This task is to make druid end points secure when kerberos is enabled - 
> 1) Add druid-kerberos extension to druid extensions
> 2) Set druid.authentication.type to kerberos 
> 3) configure spnego keytab and principal in druid configs



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (AMBARI-19787) Service Checks not being executed after Wire Encryption

[Vivek Rathod (JIRA)]

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

Vivek Rathod resolved AMBARI-19787.
---
Resolution: Duplicate

> Service Checks not being executed after Wire Encryption
> ---
>
> Key: AMBARI-19787
> URL: https://issues.apache.org/jira/browse/AMBARI-19787
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Vivek Rathod
> Fix For: 2.5.0
>
> Attachments: screenshot-1.png
>
>
> Service Checks not being executed after Wire Encryption. Deploy failed 
> because some service checks were queued but were never executed after Wire 
> Encryption.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-19787) Service Checks not being executed after Wire Encryption

[Vivek Rathod (JIRA)]

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

Vivek Rathod commented on AMBARI-19787:
---

This was fixed as part of AMBARI-19775

> Service Checks not being executed after Wire Encryption
> ---
>
> Key: AMBARI-19787
> URL: https://issues.apache.org/jira/browse/AMBARI-19787
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Vivek Rathod
> Fix For: 2.5.0
>
> Attachments: screenshot-1.png
>
>
> Service Checks not being executed after Wire Encryption. Deploy failed 
> because some service checks were queued but were never executed after Wire 
> Encryption.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (AMBARI-19840) Atlas Metadata Server Fails to start

[Vivek Rathod (JIRA)]

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

Vivek Rathod resolved AMBARI-19840.
---
Resolution: Invalid

> Atlas Metadata Server Fails to start
> 
>
> Key: AMBARI-19840
> URL: https://issues.apache.org/jira/browse/AMBARI-19840
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Vivek Rathod
> Fix For: 2.5.0
>
>
> Atlas Metadata Server Fails to start after deleting and adding back atlas.
> STR:
> 1) Delete the following services from the cluster: Smartsense, Atlas, Hbase, 
> Sqoop, Storm, Knox, Flume and AMS
> 2) Add back the deleted services using Add service Wizard
> Atlas Metadata Server fails with
> {code}
> ERROR Java::OrgApacheHadoopHbaseIpc::RemoteWithExtrasException: 
> org.apache.hadoop.hbase.coprocessor.CoprocessorException: SSLContext must not 
> be null
>   at 
> org.apache.ranger.authorization.hbase.RangerAuthorizationCoprocessor.grant(RangerAuthorizationCoprocessor.java:1180)
>   at 
> org.apache.hadoop.hbase.protobuf.generated.AccessControlProtos$AccessControlService$1.grant(AccessControlProtos.java:9933)
>   at 
> org.apache.hadoop.hbase.protobuf.generated.AccessControlProtos$AccessControlService.callMethod(AccessControlProtos.java:10097)
>   at 
> org.apache.hadoop.hbase.regionserver.HRegion.execService(HRegion.java:7832)
>   at 
> org.apache.hadoop.hbase.regionserver.RSRpcServices.execServiceOnRegion(RSRpcServices.java:1961)
>   at 
> org.apache.hadoop.hbase.regionserver.RSRpcServices.execService(RSRpcServices.java:1943)
>   at 
> org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:32389)
>   at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2141)
>   at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:112)
>   at 
> org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:187)
>   at 
> org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:167)
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-19840) Atlas Metadata Server Fails to start

[Vivek Rathod (JIRA)]

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

Vivek Rathod commented on AMBARI-19840:
---

The issue was that the cluster was wire encrypted and on deleting some services 
and adding them back, those services were no longer configured to work with 
SSL. But Ranger still tried to communicate to them using SSL. 

The solution is either to un-wire encrypt ranger, or the enable wire encryption 
back for the newly added services. Resolving this as invalid buy

> Atlas Metadata Server Fails to start
> 
>
> Key: AMBARI-19840
> URL: https://issues.apache.org/jira/browse/AMBARI-19840
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Vivek Rathod
> Fix For: 2.5.0
>
>
> Atlas Metadata Server Fails to start after deleting and adding back atlas.
> STR:
> 1) Delete the following services from the cluster: Smartsense, Atlas, Hbase, 
> Sqoop, Storm, Knox, Flume and AMS
> 2) Add back the deleted services using Add service Wizard
> Atlas Metadata Server fails with
> {code}
> ERROR Java::OrgApacheHadoopHbaseIpc::RemoteWithExtrasException: 
> org.apache.hadoop.hbase.coprocessor.CoprocessorException: SSLContext must not 
> be null
>   at 
> org.apache.ranger.authorization.hbase.RangerAuthorizationCoprocessor.grant(RangerAuthorizationCoprocessor.java:1180)
>   at 
> org.apache.hadoop.hbase.protobuf.generated.AccessControlProtos$AccessControlService$1.grant(AccessControlProtos.java:9933)
>   at 
> org.apache.hadoop.hbase.protobuf.generated.AccessControlProtos$AccessControlService.callMethod(AccessControlProtos.java:10097)
>   at 
> org.apache.hadoop.hbase.regionserver.HRegion.execService(HRegion.java:7832)
>   at 
> org.apache.hadoop.hbase.regionserver.RSRpcServices.execServiceOnRegion(RSRpcServices.java:1961)
>   at 
> org.apache.hadoop.hbase.regionserver.RSRpcServices.execService(RSRpcServices.java:1943)
>   at 
> org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:32389)
>   at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2141)
>   at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:112)
>   at 
> org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:187)
>   at 
> org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:167)
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-19830) HDP 3.0 TP - Support changed configs and scripts for HDFS

[Alejandro Fernandez (JIRA)]

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

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

> HDP 3.0 TP - Support changed configs and scripts for HDFS
> -
>
> Key: AMBARI-19830
> URL: https://issues.apache.org/jira/browse/AMBARI-19830
> Project: Ambari
>  Issue Type: Story
>  Components: stacks
>Affects Versions: 3.0.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 3.0.0
>
> Attachments: AMBARI-19830.patch
>
>
> In HDP 3.0, there are expected changes to configs and the startup scripts for 
> HDFS.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-19830) HDP 3.0 TP - Support changed configs and scripts for HDFS

[Alejandro Fernandez (JIRA)]

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

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

> HDP 3.0 TP - Support changed configs and scripts for HDFS
> -
>
> Key: AMBARI-19830
> URL: https://issues.apache.org/jira/browse/AMBARI-19830
> Project: Ambari
>  Issue Type: Story
>  Components: stacks
>Affects Versions: 3.0.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 3.0.0
>
> Attachments: AMBARI-19830.patch
>
>
> In HDP 3.0, there are expected changes to configs and the startup scripts for 
> HDFS.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-19830) HDP 3.0 TP - Support changed configs and scripts for HDFS

[Alejandro Fernandez (JIRA)]

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

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

> HDP 3.0 TP - Support changed configs and scripts for HDFS
> -
>
> Key: AMBARI-19830
> URL: https://issues.apache.org/jira/browse/AMBARI-19830
> Project: Ambari
>  Issue Type: Story
>  Components: stacks
>Affects Versions: 3.0.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 3.0.0
>
> Attachments: AMBARI-19830.patch
>
>
> In HDP 3.0, there are expected changes to configs and the startup scripts for 
> HDFS.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-19594) configure kerberos authentication for Druid UIs

[Sumit Mohanty (JIRA)]

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

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

Committed to trunk and branch-2.5

> configure kerberos authentication for Druid UIs
> ---
>
> Key: AMBARI-19594
> URL: https://issues.apache.org/jira/browse/AMBARI-19594
> Project: Ambari
>  Issue Type: Task
>Reporter: Nishant Bangarwa
>Assignee: Nishant Bangarwa
> Fix For: trunk, 2.5.0
>
> Attachments: ambari-19594.patch
>
>
> Druid Now supports kerberos authentication for UIs using SPNego 
> (https://github.com/druid-io/druid/pull/3853). 
> This task is to make druid end points secure when kerberos is enabled - 
> 1) Add druid-kerberos extension to druid extensions
> 2) Set druid.authentication.type to kerberos 
> 3) configure spnego keytab and principal in druid configs



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-19830) HDP 3.0 TP - Support changed configs and scripts for HDFS

[Alejandro Fernandez (JIRA)]

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

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

> HDP 3.0 TP - Support changed configs and scripts for HDFS
> -
>
> Key: AMBARI-19830
> URL: https://issues.apache.org/jira/browse/AMBARI-19830
> Project: Ambari
>  Issue Type: Story
>  Components: stacks
>Affects Versions: 3.0.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 3.0.0
>
>
> In HDP 3.0, there are expected changes to configs and the startup scripts for 
> HDFS.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-19865) Ambari-server logon failure: Hadoop-common dependency on servlet-api 2.5

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-19865:


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

{color:red}-1 patch{color}.  The patch command could not apply the patch.

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

This message is automatically generated.

> Ambari-server logon failure: Hadoop-common dependency on servlet-api 2.5 
> -
>
> Key: AMBARI-19865
> URL: https://issues.apache.org/jira/browse/AMBARI-19865
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
> Fix For: 2.5.0
>
> Attachments: rb56281.patch
>
>
> CredentialUtil uses hadoop-common which depends on servlet-api 2.5. This 
> causes a failure during ambari-server logon:
> {code}
> 02 Feb 2017 13:15:57,992  WARN [ambari-client-thread-25] ServletHandler:592 - 
> Error for /api/v1/clusters
> java.lang.NoSuchMethodError: 
> javax.servlet.http.HttpServletResponse.getStatus()I
> at 
> org.apache.ambari.server.security.authorization.AmbariAuthorizationFilter.doFilter(AmbariAuthorizationFilter.java:277)
> at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
> at 
> org.springframework.security.web.access.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:113)
> at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
> at 
> org.springframework.security.web.session.SessionManagementFilter.doFilter(SessionManagementFilter.java:103)
> at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
> at 
> org.springframework.security.web.authentication.AnonymousAuthenticationFilter.doFilter(AnonymousAuthenticationFilter.java:113)
> at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
> {code}
> This happens because of classpath collision between multiple servlet api 
> versions. The org.apache.hadoop:hadoop-common depends on an old version of 
> servlet api (2.5).
> {code}
> [INFO] +- org.apache.hadoop:hadoop-common:jar:2.7.2:compile
> [INFO] |  +- xmlenc:xmlenc:jar:0.52:compile
> [INFO] |  +- commons-httpclient:commons-httpclient:jar:3.1:compile
> [INFO] |  +- javax.servlet:servlet-api:jar:2.5:compile
> [INFO] |  +- org.mortbay.jetty:jetty:jar:6.1.26:compile
> [INFO] |  +- org.mortbay.jetty:jetty-util:jar:6.1.26:compile
> [INFO] |  +- javax.servlet.jsp:jsp-api:jar:2.1:runtime
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-19868) Build fails on trunk because of import reordering as part of AMBARI-19810 check-in.

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty commented on AMBARI-19868:


LGTM, +1

> Build fails on trunk because of import reordering as part of AMBARI-19810 
> check-in.
> ---
>
> Key: AMBARI-19868
> URL: https://issues.apache.org/jira/browse/AMBARI-19868
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Blocker
> Fix For: trunk
>
> Attachments: AMBARI-19868.patch
>
>
> Error:
> {code}
> [INFO] --- maven-checkstyle-plugin:2.17:check (checkstyle) @ ambari-server ---
> [INFO] Starting audit...
> [ERROR] 
> ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog250.java:22:
>  Wrong order for 'org.apache.ambari.server.AmbariException' import. 
> [ImportOrder]
> [ERROR] 
> ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog250.java:37:
>  Wrong order for 'java.sql.ResultSet' import. [ImportOrder]
> [ERROR] 
> ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog250Test.java:29:
>  'junit.framework.AssertionFailedError' should be separated from previous 
> imports. [ImportOrder]
> [ERROR] 
> ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog250Test.java:30:
>  Wrong order for 'org.apache.ambari.server.AmbariException' import. 
> [ImportOrder]
> [ERROR] 
> ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog250Test.java:61:
>  Wrong order for 'javax.persistence.EntityManager' import. [ImportOrder]
> [ERROR] 
> ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog250Test.java:62:
>  Wrong order for 'java.lang.reflect.Method' import. [ImportOrder]
> [ERROR] 
> ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog250Test.java:75:
>  Wrong order for 'org.easymock.EasyMock.anyObject' import. [ImportOrder]
> Audit done.
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-19869) POST to api to regsiter a blueprint throws com.google.gson.JsonSyntaxException

[Barry (JIRA)]

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

Barry commented on AMBARI-19869:


[~jonathan.hurley], after fighting it for a while and trying various posts I 
found that text/plain is necessary and to not wrap the JSON in 
quotes{noformat}""{noformat}

> POST to api to regsiter a blueprint throws com.google.gson.JsonSyntaxException
> --
>
> Key: AMBARI-19869
> URL: https://issues.apache.org/jira/browse/AMBARI-19869
> Project: Ambari
>  Issue Type: Bug
>  Components: blueprints
>Affects Versions: 2.4.2
> Environment: Centos7 AWS (ami-6d1c2007)
> [root@dev-ambari-master /]# cat /etc/centos-release && uname -a
> CentOS Linux release 7.3.1611 (Core) 
> Linux xxx.xxx.com 3.10.0-514.6.1.el7.x86_64 #1 SMP Wed Jan 18 13:06:36 UTC 
> 2017 x86_64 x86_64 x86_64 GNU/Linux
>Reporter: Barry
>Priority: Trivial
>  Labels: api, blueprints
>
> Exporting blueprint json from a server, then attempting to post the json to 
> another server results in a 500 err. Occurrs regardless of specifying 
> ?validate_topology=false or not. JSON has also been validated. POST headers 
> are 
> {noformat}
> X-Requested-By: ambari
> Authorization: Basic Yxxx==
> Content-Type: application/json
> {noformat}
> Full stack trace below. 
> {noformat}03 Feb 2017 20:07:43,907 ERROR [ambari-client-thread-27] 
> ContainerResponse:419 - The RuntimeException could not be mapped to a 
> response, re-throwing to the HTTP container
> com.google.gson.JsonSyntaxException: java.lang.IllegalStateException: 
> Expected a string but was BEGIN_OBJECT at line 1 column 2
>   at com.google.gson.Gson.fromJson(Gson.java:806)
>   at com.google.gson.Gson.fromJson(Gson.java:761)
>   at 
> org.apache.ambari.server.api.GsonJsonProvider.readFrom(GsonJsonProvider.java:60)
>   at 
> com.sun.jersey.spi.container.ContainerRequest.getEntity(ContainerRequest.java:490)
>   at 
> com.sun.jersey.server.impl.model.method.dispatch.EntityParamDispatchProvider$EntityInjectable.getValue(EntityParamDispatchProvider.java:123)
>   at 
> com.sun.jersey.server.impl.inject.InjectableValuesProvider.getInjectableValues(InjectableValuesProvider.java:86)
>   at 
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$EntityParamInInvoker.getParams(AbstractResourceMethodDispatchProvider.java:153)
>   at 
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:203)
>   at 
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
>   at 
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
>   at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
>   at 
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
>   at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
>   at 
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
>   at 
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
>   at 
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
>   at 
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
>   at 
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)
>   at 
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)
>   at 
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)
>   at 
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)
>   at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
>   at 
> org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:684)
>   at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1507)
>   at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:330)
>   at 
> org.springframework.security.web.access.intercept.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:118)
>   at 
> org.springframework.security.web.access.intercept.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:84)
>   at 
> 

[jira] [Resolved] (AMBARI-19869) POST to api to regsiter a blueprint throws com.google.gson.JsonSyntaxException

[Barry (JIRA)]

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

Barry resolved AMBARI-19869.

Resolution: Not A Problem

> POST to api to regsiter a blueprint throws com.google.gson.JsonSyntaxException
> --
>
> Key: AMBARI-19869
> URL: https://issues.apache.org/jira/browse/AMBARI-19869
> Project: Ambari
>  Issue Type: Bug
>  Components: blueprints
>Affects Versions: 2.4.2
> Environment: Centos7 AWS (ami-6d1c2007)
> [root@dev-ambari-master /]# cat /etc/centos-release && uname -a
> CentOS Linux release 7.3.1611 (Core) 
> Linux xxx.xxx.com 3.10.0-514.6.1.el7.x86_64 #1 SMP Wed Jan 18 13:06:36 UTC 
> 2017 x86_64 x86_64 x86_64 GNU/Linux
>Reporter: Barry
>Priority: Trivial
>  Labels: api, blueprints
>
> Exporting blueprint json from a server, then attempting to post the json to 
> another server results in a 500 err. Occurrs regardless of specifying 
> ?validate_topology=false or not. JSON has also been validated. POST headers 
> are 
> {noformat}
> X-Requested-By: ambari
> Authorization: Basic Yxxx==
> Content-Type: application/json
> {noformat}
> Full stack trace below. 
> {noformat}03 Feb 2017 20:07:43,907 ERROR [ambari-client-thread-27] 
> ContainerResponse:419 - The RuntimeException could not be mapped to a 
> response, re-throwing to the HTTP container
> com.google.gson.JsonSyntaxException: java.lang.IllegalStateException: 
> Expected a string but was BEGIN_OBJECT at line 1 column 2
>   at com.google.gson.Gson.fromJson(Gson.java:806)
>   at com.google.gson.Gson.fromJson(Gson.java:761)
>   at 
> org.apache.ambari.server.api.GsonJsonProvider.readFrom(GsonJsonProvider.java:60)
>   at 
> com.sun.jersey.spi.container.ContainerRequest.getEntity(ContainerRequest.java:490)
>   at 
> com.sun.jersey.server.impl.model.method.dispatch.EntityParamDispatchProvider$EntityInjectable.getValue(EntityParamDispatchProvider.java:123)
>   at 
> com.sun.jersey.server.impl.inject.InjectableValuesProvider.getInjectableValues(InjectableValuesProvider.java:86)
>   at 
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$EntityParamInInvoker.getParams(AbstractResourceMethodDispatchProvider.java:153)
>   at 
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:203)
>   at 
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
>   at 
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
>   at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
>   at 
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
>   at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
>   at 
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
>   at 
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
>   at 
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
>   at 
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
>   at 
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)
>   at 
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)
>   at 
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)
>   at 
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)
>   at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
>   at 
> org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:684)
>   at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1507)
>   at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:330)
>   at 
> org.springframework.security.web.access.intercept.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:118)
>   at 
> org.springframework.security.web.access.intercept.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:84)
>   at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
>   at 
> org.apache.ambari.server.security.authorization.AmbariAuthorizationFilter.doFilter(AmbariAuthorizationFilter.java:257)
>   at 
> 

[jira] [Commented] (AMBARI-19869) POST to api to regsiter a blueprint throws com.google.gson.JsonSyntaxException

[Jonathan Hurley (JIRA)]

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

Jonathan Hurley commented on AMBARI-19869:
--

[~bmac] - Can you provide the blueprint which is causing this problem and 
attach it to this Jira? Also - you are attempting to take a blueprint from one 
Ambari and use it on another Ambari instance - are they both the same version 
of Ambari?

> POST to api to regsiter a blueprint throws com.google.gson.JsonSyntaxException
> --
>
> Key: AMBARI-19869
> URL: https://issues.apache.org/jira/browse/AMBARI-19869
> Project: Ambari
>  Issue Type: Bug
>  Components: blueprints
>Affects Versions: 2.4.2
> Environment: Centos7 AWS (ami-6d1c2007)
> [root@dev-ambari-master /]# cat /etc/centos-release && uname -a
> CentOS Linux release 7.3.1611 (Core) 
> Linux xxx.xxx.com 3.10.0-514.6.1.el7.x86_64 #1 SMP Wed Jan 18 13:06:36 UTC 
> 2017 x86_64 x86_64 x86_64 GNU/Linux
>Reporter: Barry
>Priority: Critical
>  Labels: api, blueprints
>
> Exporting blueprint json from a server, then attempting to post the json to 
> another server results in a 500 err. Occurrs regardless of specifying 
> ?validate_topology=false or not. JSON has also been validated. POST headers 
> are 
> {noformat}
> X-Requested-By: ambari
> Authorization: Basic Yxxx==
> Content-Type: application/json
> {noformat}
> Full stack trace below. 
> {noformat}03 Feb 2017 20:07:43,907 ERROR [ambari-client-thread-27] 
> ContainerResponse:419 - The RuntimeException could not be mapped to a 
> response, re-throwing to the HTTP container
> com.google.gson.JsonSyntaxException: java.lang.IllegalStateException: 
> Expected a string but was BEGIN_OBJECT at line 1 column 2
>   at com.google.gson.Gson.fromJson(Gson.java:806)
>   at com.google.gson.Gson.fromJson(Gson.java:761)
>   at 
> org.apache.ambari.server.api.GsonJsonProvider.readFrom(GsonJsonProvider.java:60)
>   at 
> com.sun.jersey.spi.container.ContainerRequest.getEntity(ContainerRequest.java:490)
>   at 
> com.sun.jersey.server.impl.model.method.dispatch.EntityParamDispatchProvider$EntityInjectable.getValue(EntityParamDispatchProvider.java:123)
>   at 
> com.sun.jersey.server.impl.inject.InjectableValuesProvider.getInjectableValues(InjectableValuesProvider.java:86)
>   at 
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$EntityParamInInvoker.getParams(AbstractResourceMethodDispatchProvider.java:153)
>   at 
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:203)
>   at 
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
>   at 
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
>   at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
>   at 
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
>   at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
>   at 
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
>   at 
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
>   at 
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
>   at 
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
>   at 
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)
>   at 
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)
>   at 
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)
>   at 
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)
>   at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
>   at 
> org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:684)
>   at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1507)
>   at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:330)
>   at 
> org.springframework.security.web.access.intercept.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:118)
>   at 
> 

[jira] [Updated] (AMBARI-19869) POST to api to regsiter a blueprint throws com.google.gson.JsonSyntaxException

[Barry (JIRA)]

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

Barry updated AMBARI-19869:
---
Priority: Trivial  (was: Critical)

> POST to api to regsiter a blueprint throws com.google.gson.JsonSyntaxException
> --
>
> Key: AMBARI-19869
> URL: https://issues.apache.org/jira/browse/AMBARI-19869
> Project: Ambari
>  Issue Type: Bug
>  Components: blueprints
>Affects Versions: 2.4.2
> Environment: Centos7 AWS (ami-6d1c2007)
> [root@dev-ambari-master /]# cat /etc/centos-release && uname -a
> CentOS Linux release 7.3.1611 (Core) 
> Linux xxx.xxx.com 3.10.0-514.6.1.el7.x86_64 #1 SMP Wed Jan 18 13:06:36 UTC 
> 2017 x86_64 x86_64 x86_64 GNU/Linux
>Reporter: Barry
>Priority: Trivial
>  Labels: api, blueprints
>
> Exporting blueprint json from a server, then attempting to post the json to 
> another server results in a 500 err. Occurrs regardless of specifying 
> ?validate_topology=false or not. JSON has also been validated. POST headers 
> are 
> {noformat}
> X-Requested-By: ambari
> Authorization: Basic Yxxx==
> Content-Type: application/json
> {noformat}
> Full stack trace below. 
> {noformat}03 Feb 2017 20:07:43,907 ERROR [ambari-client-thread-27] 
> ContainerResponse:419 - The RuntimeException could not be mapped to a 
> response, re-throwing to the HTTP container
> com.google.gson.JsonSyntaxException: java.lang.IllegalStateException: 
> Expected a string but was BEGIN_OBJECT at line 1 column 2
>   at com.google.gson.Gson.fromJson(Gson.java:806)
>   at com.google.gson.Gson.fromJson(Gson.java:761)
>   at 
> org.apache.ambari.server.api.GsonJsonProvider.readFrom(GsonJsonProvider.java:60)
>   at 
> com.sun.jersey.spi.container.ContainerRequest.getEntity(ContainerRequest.java:490)
>   at 
> com.sun.jersey.server.impl.model.method.dispatch.EntityParamDispatchProvider$EntityInjectable.getValue(EntityParamDispatchProvider.java:123)
>   at 
> com.sun.jersey.server.impl.inject.InjectableValuesProvider.getInjectableValues(InjectableValuesProvider.java:86)
>   at 
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$EntityParamInInvoker.getParams(AbstractResourceMethodDispatchProvider.java:153)
>   at 
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:203)
>   at 
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
>   at 
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
>   at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
>   at 
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
>   at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
>   at 
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
>   at 
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
>   at 
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
>   at 
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
>   at 
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)
>   at 
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)
>   at 
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)
>   at 
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)
>   at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
>   at 
> org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:684)
>   at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1507)
>   at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:330)
>   at 
> org.springframework.security.web.access.intercept.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:118)
>   at 
> org.springframework.security.web.access.intercept.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:84)
>   at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
>   at 
> org.apache.ambari.server.security.authorization.AmbariAuthorizationFilter.doFilter(AmbariAuthorizationFilter.java:257)
>   at 

[jira] [Commented] (AMBARI-19869) POST to api to regsiter a blueprint throws com.google.gson.JsonSyntaxException

[Barry (JIRA)]

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

Barry commented on AMBARI-19869:


Do not use header {noformat}Content-Type: application/json{noformat}
Do not wrap json in quotes. 

> POST to api to regsiter a blueprint throws com.google.gson.JsonSyntaxException
> --
>
> Key: AMBARI-19869
> URL: https://issues.apache.org/jira/browse/AMBARI-19869
> Project: Ambari
>  Issue Type: Bug
>  Components: blueprints
>Affects Versions: 2.4.2
> Environment: Centos7 AWS (ami-6d1c2007)
> [root@dev-ambari-master /]# cat /etc/centos-release && uname -a
> CentOS Linux release 7.3.1611 (Core) 
> Linux xxx.xxx.com 3.10.0-514.6.1.el7.x86_64 #1 SMP Wed Jan 18 13:06:36 UTC 
> 2017 x86_64 x86_64 x86_64 GNU/Linux
>Reporter: Barry
>Priority: Critical
>  Labels: api, blueprints
>
> Exporting blueprint json from a server, then attempting to post the json to 
> another server results in a 500 err. Occurrs regardless of specifying 
> ?validate_topology=false or not. JSON has also been validated. POST headers 
> are 
> {noformat}
> X-Requested-By: ambari
> Authorization: Basic Yxxx==
> Content-Type: application/json
> {noformat}
> Full stack trace below. 
> {noformat}03 Feb 2017 20:07:43,907 ERROR [ambari-client-thread-27] 
> ContainerResponse:419 - The RuntimeException could not be mapped to a 
> response, re-throwing to the HTTP container
> com.google.gson.JsonSyntaxException: java.lang.IllegalStateException: 
> Expected a string but was BEGIN_OBJECT at line 1 column 2
>   at com.google.gson.Gson.fromJson(Gson.java:806)
>   at com.google.gson.Gson.fromJson(Gson.java:761)
>   at 
> org.apache.ambari.server.api.GsonJsonProvider.readFrom(GsonJsonProvider.java:60)
>   at 
> com.sun.jersey.spi.container.ContainerRequest.getEntity(ContainerRequest.java:490)
>   at 
> com.sun.jersey.server.impl.model.method.dispatch.EntityParamDispatchProvider$EntityInjectable.getValue(EntityParamDispatchProvider.java:123)
>   at 
> com.sun.jersey.server.impl.inject.InjectableValuesProvider.getInjectableValues(InjectableValuesProvider.java:86)
>   at 
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$EntityParamInInvoker.getParams(AbstractResourceMethodDispatchProvider.java:153)
>   at 
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:203)
>   at 
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
>   at 
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
>   at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
>   at 
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
>   at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
>   at 
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
>   at 
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
>   at 
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
>   at 
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
>   at 
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)
>   at 
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)
>   at 
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)
>   at 
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)
>   at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
>   at 
> org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:684)
>   at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1507)
>   at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:330)
>   at 
> org.springframework.security.web.access.intercept.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:118)
>   at 
> org.springframework.security.web.access.intercept.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:84)
>   at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
>   at 
> 

[jira] [Commented] (AMBARI-19810) Remove upgrade logic in UpdateCatalog250 for tez-interactive-site's 'tez.runtime.io.sort.mb' and 'tez.runtime.unordered.output.buffer.size-mb'.

[Swapan Shridhar (JIRA)]

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

Swapan Shridhar commented on AMBARI-19810:
--

Build issue reported on trunk -> Fixed it as part of AMBARI-19868.

> Remove upgrade logic in UpdateCatalog250 for tez-interactive-site's 
> 'tez.runtime.io.sort.mb' and 'tez.runtime.unordered.output.buffer.size-mb'.
> ---
>
> Key: AMBARI-19810
> URL: https://issues.apache.org/jira/browse/AMBARI-19810
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-19810.01.patch, AMBARI-19810.trunk.01.patch
>
>
> Remove the following code and its references:
> {code}
> +  protected void updateTEZInteractiveConfigs() throws AmbariException {
> +AmbariManagementController ambariManagementController = 
> injector.getInstance(AmbariManagementController.class);
> +Clusters clusters = ambariManagementController.getClusters();
> +if (clusters != null) {
> +  Map clusterMap = clusters.getClusters();
> +
> +  if (clusterMap != null && !clusterMap.isEmpty()) {
> +for (final Cluster cluster : clusterMap.values()) {
> +  Config tezInteractiveSite = 
> cluster.getDesiredConfigByType("tez-interactive-site");
> +  if (tezInteractiveSite != null) {
> +
> +updateConfigurationProperties("tez-interactive-site", 
> Collections.singletonMap("tez.runtime.io.sort.mb", "512"), true, true);
> +
> +updateConfigurationProperties("tez-interactive-site", 
> Collections.singletonMap("tez.runtime.unordered.output.buffer.size-mb",
> +"100"), true, true);
> +  }
> +}
> +  }
> +}
> +  }
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-19858) Add "live_hosts" metric in AMS for apps

[Siddharth Wagle (JIRA)]

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

Siddharth Wagle commented on AMBARI-19858:
--

Changes look good. +1 

> Add "live_hosts" metric in AMS for apps
> ---
>
> Key: AMBARI-19858
> URL: https://issues.apache.org/jira/browse/AMBARI-19858
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-metrics
>Affects Versions: 2.5.0
>Reporter: Siddharth Wagle
>Assignee: Aravindan Vijayan
> Fix For: 2.5.0
>
> Attachments: AMBARI-19858-2.patch, AMBARI-19858.patch
>
>
> {quote}
> live_hosts=> # count of total hosts reporting 
> metrics
> live_hosts & appId =  => # count of hosts hosting this appId
> {quote}
> Where appId = { namenode, datanode, hbase ... etc }



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-19868) Build fails on trunk because of import reordering as part of AMBARI-19810 check-in.

[Swapan Shridhar (JIRA)]

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

Swapan Shridhar updated AMBARI-19868:
-
Description: 
Error:

{code}
[INFO] --- maven-checkstyle-plugin:2.17:check (checkstyle) @ ambari-server ---
[INFO] Starting audit...
[ERROR] 
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog250.java:22:
 Wrong order for 'org.apache.ambari.server.AmbariException' import. 
[ImportOrder]
[ERROR] 
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog250.java:37:
 Wrong order for 'java.sql.ResultSet' import. [ImportOrder]
[ERROR] 
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog250Test.java:29:
 'junit.framework.AssertionFailedError' should be separated from previous 
imports. [ImportOrder]
[ERROR] 
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog250Test.java:30:
 Wrong order for 'org.apache.ambari.server.AmbariException' import. 
[ImportOrder]
[ERROR] 
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog250Test.java:61:
 Wrong order for 'javax.persistence.EntityManager' import. [ImportOrder]
[ERROR] 
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog250Test.java:62:
 Wrong order for 'java.lang.reflect.Method' import. [ImportOrder]
[ERROR] 
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog250Test.java:75:
 Wrong order for 'org.easymock.EasyMock.anyObject' import. [ImportOrder]
Audit done.
{code}

> Build fails on trunk because of import reordering as part of AMBARI-19810 
> check-in.
> ---
>
> Key: AMBARI-19868
> URL: https://issues.apache.org/jira/browse/AMBARI-19868
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Blocker
> Fix For: trunk
>
> Attachments: AMBARI-19868.patch
>
>
> Error:
> {code}
> [INFO] --- maven-checkstyle-plugin:2.17:check (checkstyle) @ ambari-server ---
> [INFO] Starting audit...
> [ERROR] 
> ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog250.java:22:
>  Wrong order for 'org.apache.ambari.server.AmbariException' import. 
> [ImportOrder]
> [ERROR] 
> ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog250.java:37:
>  Wrong order for 'java.sql.ResultSet' import. [ImportOrder]
> [ERROR] 
> ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog250Test.java:29:
>  'junit.framework.AssertionFailedError' should be separated from previous 
> imports. [ImportOrder]
> [ERROR] 
> ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog250Test.java:30:
>  Wrong order for 'org.apache.ambari.server.AmbariException' import. 
> [ImportOrder]
> [ERROR] 
> ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog250Test.java:61:
>  Wrong order for 'javax.persistence.EntityManager' import. [ImportOrder]
> [ERROR] 
> ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog250Test.java:62:
>  Wrong order for 'java.lang.reflect.Method' import. [ImportOrder]
> [ERROR] 
> ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog250Test.java:75:
>  Wrong order for 'org.easymock.EasyMock.anyObject' import. [ImportOrder]
> Audit done.
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (AMBARI-19869) POST to api to regsiter a blueprint throws com.google.gson.JsonSyntaxException

[Barry (JIRA)]

Barry created AMBARI-19869:
--

 Summary: POST to api to regsiter a blueprint throws 
com.google.gson.JsonSyntaxException
 Key: AMBARI-19869
 URL: https://issues.apache.org/jira/browse/AMBARI-19869
 Project: Ambari
  Issue Type: Bug
  Components: blueprints
Affects Versions: 2.4.2
 Environment: Centos7 AWS (ami-6d1c2007)
[root@dev-ambari-master /]# cat /etc/centos-release && uname -a
CentOS Linux release 7.3.1611 (Core) 
Linux xxx.xxx.com 3.10.0-514.6.1.el7.x86_64 #1 SMP Wed Jan 18 13:06:36 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux

Reporter: Barry
Priority: Critical


Exporting blueprint json from a server, then attempting to post the json to 
another server results in a 500 err. Occurrs regardless of specifying 
?validate_topology=false or not. JSON has also been validated. POST headers are 
{noformat}
X-Requested-By: ambari
Authorization: Basic Yxxx==
Content-Type: application/json
{noformat}

Full stack trace below. 
{noformat}03 Feb 2017 20:07:43,907 ERROR [ambari-client-thread-27] 
ContainerResponse:419 - The RuntimeException could not be mapped to a response, 
re-throwing to the HTTP container
com.google.gson.JsonSyntaxException: java.lang.IllegalStateException: Expected 
a string but was BEGIN_OBJECT at line 1 column 2
at com.google.gson.Gson.fromJson(Gson.java:806)
at com.google.gson.Gson.fromJson(Gson.java:761)
at 
org.apache.ambari.server.api.GsonJsonProvider.readFrom(GsonJsonProvider.java:60)
at 
com.sun.jersey.spi.container.ContainerRequest.getEntity(ContainerRequest.java:490)
at 
com.sun.jersey.server.impl.model.method.dispatch.EntityParamDispatchProvider$EntityInjectable.getValue(EntityParamDispatchProvider.java:123)
at 
com.sun.jersey.server.impl.inject.InjectableValuesProvider.getInjectableValues(InjectableValuesProvider.java:86)
at 
com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$EntityParamInInvoker.getParams(AbstractResourceMethodDispatchProvider.java:153)
at 
com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:203)
at 
com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
at 
com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
at 
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at 
com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
at 
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at 
com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
at 
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
at 
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
at 
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
at 
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)
at 
com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)
at 
com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)
at 
com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
at 
org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:684)
at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1507)
at 
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:330)
at 
org.springframework.security.web.access.intercept.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:118)
at 
org.springframework.security.web.access.intercept.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:84)
at 
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
at 
org.apache.ambari.server.security.authorization.AmbariAuthorizationFilter.doFilter(AmbariAuthorizationFilter.java:257)
at 
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
at 
org.springframework.security.web.access.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:113)
at 
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
at 

[jira] [Commented] (AMBARI-19868) Build fails on trunk because of import reordering as part of AMBARI-19810 check-in.

[Swapan Shridhar (JIRA)]

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

Swapan Shridhar commented on AMBARI-19868:
--

Patch for review : [~afernandez] | [~sumitmohanty]

> Build fails on trunk because of import reordering as part of AMBARI-19810 
> check-in.
> ---
>
> Key: AMBARI-19868
> URL: https://issues.apache.org/jira/browse/AMBARI-19868
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Blocker
> Fix For: trunk
>
> Attachments: AMBARI-19868.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-19858) Add "live_hosts" metric in AMS for apps

[Aravindan Vijayan (JIRA)]

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

Aravindan Vijayan updated AMBARI-19858:
---
Attachment: AMBARI-19858-2.patch

> Add "live_hosts" metric in AMS for apps
> ---
>
> Key: AMBARI-19858
> URL: https://issues.apache.org/jira/browse/AMBARI-19858
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-metrics
>Affects Versions: 2.5.0
>Reporter: Siddharth Wagle
>Assignee: Aravindan Vijayan
> Fix For: 2.5.0
>
> Attachments: AMBARI-19858-2.patch, AMBARI-19858.patch
>
>
> {quote}
> live_hosts=> # count of total hosts reporting 
> metrics
> live_hosts & appId =  => # count of hosts hosting this appId
> {quote}
> Where appId = { namenode, datanode, hbase ... etc }



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-19813) findLatestServiceConfigsByStack query returns deleted config group

[Hudson (JIRA)]

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

Hudson commented on AMBARI-19813:
-

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6644 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6644/])
AMBARI-19813: findLatestServiceConfigsByStack query returns deleted (dili: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=ecfc951b5c8589b9225684c3ad2660cdb4ef4445])
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/orm/dao/ServiceConfigDAOTest.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/orm/entities/ServiceConfigEntity.java


> findLatestServiceConfigsByStack query returns deleted config group
> --
>
> Key: AMBARI-19813
> URL: https://issues.apache.org/jira/browse/AMBARI-19813
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Amruta Borkar
>Assignee: Amruta Borkar
> Fix For: trunk
>
> Attachments: AMBARI-19813.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-19868) Build fails on trunk because of import reordering as part of AMBARI-19810 check-in.

[Swapan Shridhar (JIRA)]

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

Swapan Shridhar updated AMBARI-19868:
-
Affects Version/s: (was: 2.5.0)
   trunk

> Build fails on trunk because of import reordering as part of AMBARI-19810 
> check-in.
> ---
>
> Key: AMBARI-19868
> URL: https://issues.apache.org/jira/browse/AMBARI-19868
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Blocker
> Fix For: trunk
>
> Attachments: AMBARI-19868.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-19868) Build fails on trunk because of import reordering as part of AMBARI-19810 check-in.

[Swapan Shridhar (JIRA)]

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

Swapan Shridhar updated AMBARI-19868:
-
Status: Patch Available  (was: Open)

> Build fails on trunk because of import reordering as part of AMBARI-19810 
> check-in.
> ---
>
> Key: AMBARI-19868
> URL: https://issues.apache.org/jira/browse/AMBARI-19868
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Blocker
> Fix For: trunk
>
> Attachments: AMBARI-19868.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-19868) Build fails on trunk because of import reordering as part of AMBARI-19810 check-in.

[Swapan Shridhar (JIRA)]

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

Swapan Shridhar updated AMBARI-19868:
-
Attachment: AMBARI-19868.patch

> Build fails on trunk because of import reordering as part of AMBARI-19810 
> check-in.
> ---
>
> Key: AMBARI-19868
> URL: https://issues.apache.org/jira/browse/AMBARI-19868
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Blocker
> Fix For: trunk
>
> Attachments: AMBARI-19868.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-19813) findLatestServiceConfigsByStack query returns deleted config group

[Amruta Borkar (JIRA)]

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

Amruta Borkar updated AMBARI-19813:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> findLatestServiceConfigsByStack query returns deleted config group
> --
>
> Key: AMBARI-19813
> URL: https://issues.apache.org/jira/browse/AMBARI-19813
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Amruta Borkar
>Assignee: Amruta Borkar
> Fix For: trunk
>
> Attachments: AMBARI-19813.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-19867) Grafana install fails if custom directory's parent does not exist

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-19867:


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

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

{color:green}+1 tests included{color}.  The patch appears to include 1 new 
or modified test files.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in 
ambari-server.

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

This message is automatically generated.

> Grafana install fails if custom directory's parent does not exist
> -
>
> Key: AMBARI-19867
> URL: https://issues.apache.org/jira/browse/AMBARI-19867
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Minor
> Fix For: 3.0.0, 2.5.0
>
> Attachments: AMBARI-19867.patch
>
>
> Creating cluster via blueprint with custom {{metrics_grafana_log_dir}} and/or 
> {{metrics_grafana_data_dir}} whose parent directory does not exist fails.
> {noformat:title=sample config}
> "ams-grafana-env": {
>   "properties": {
> "metrics_grafana_log_dir": "/var/log/ambari/metrics/grafana",
> "metrics_grafana_data_dir": "/var/lib/ambari/metrics/grafana"
>   }
> }
> {noformat}
> {noformat:title=error}
> Traceback (most recent call last):
>   File 
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py",
>  line 81, in 
> AmsGrafana().execute()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 314, in execute
> method(env)
>   File 
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py",
>  line 34, in install
> self.configure(env) # for security
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 117, in locking_configure
> original_configure(obj, *args, **kw)
>   File 
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py",
>  line 39, in configure
> ams(name='grafana', action=action)
>   File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py", 
> line 89, in thunk
> return fn(*args, **kwargs)
>   File 
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/ams.py",
>  line 426, in ams
> recursive_ownership = True
>   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 189, in action_create
> raise Fail("Applying %s failed, parent directory %s doesn't exist" % 
> (self.resource, dirname))
> resource_management.core.exceptions.Fail: Applying 
> Directory['/var/log/ambari/metrics/grafana'] failed, parent directory 
> /var/log/ambari/metrics doesn't exist
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (AMBARI-19868) Build fails on trunk because of import reordering as part of AMBARI-19810 check-in.

[Swapan Shridhar (JIRA)]

Swapan Shridhar created AMBARI-19868:


 Summary: Build fails on trunk because of import reordering as part 
of AMBARI-19810 check-in.
 Key: AMBARI-19868
 URL: https://issues.apache.org/jira/browse/AMBARI-19868
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: 2.5.0
Reporter: Swapan Shridhar
Assignee: Swapan Shridhar
Priority: Blocker
 Fix For: trunk






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-19799) Optimize DB initialization for Ambari Server Unit Tests

[Hudson (JIRA)]

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

Hudson commented on AMBARI-19799:
-

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6643 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6643/])
AMBARI-19799. Optimize DB initialization for Ambari Server Unit Tests. 
(mpapyrkovskyy: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=e86dddad7da519558210ddf41621aad60af55c55])
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog250Test.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog250.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/H2DatabaseCleaner.java


> Optimize DB initialization for Ambari Server Unit Tests
> ---
>
> Key: AMBARI-19799
> URL: https://issues.apache.org/jira/browse/AMBARI-19799
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Myroslav Papirkovskyi
>Assignee: Myroslav Papirkovskyi
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19799.patch
>
>
> Optimize DB initialization so DB so DB is not recreated before each UT.
> Also replaces Derby with H2 for more control over DB and increased 
> performance.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-19594) configure kerberos authentication for Druid UIs

[Nishant Bangarwa (JIRA)]

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

Nishant Bangarwa updated AMBARI-19594:
--
Fix Version/s: 2.5.0
   trunk
   Status: Patch Available  (was: Open)

> configure kerberos authentication for Druid UIs
> ---
>
> Key: AMBARI-19594
> URL: https://issues.apache.org/jira/browse/AMBARI-19594
> Project: Ambari
>  Issue Type: Task
>Reporter: Nishant Bangarwa
>Assignee: Nishant Bangarwa
> Fix For: trunk, 2.5.0
>
> Attachments: ambari-19594.patch
>
>
> Druid Now supports kerberos authentication for UIs using SPNego 
> (https://github.com/druid-io/druid/pull/3853). 
> This task is to make druid end points secure when kerberos is enabled - 
> 1) Add druid-kerberos extension to druid extensions
> 2) Set druid.authentication.type to kerberos 
> 3) configure spnego keytab and principal in druid configs



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-19594) configure kerberos authentication for Druid UIs

[Nishant Bangarwa (JIRA)]

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

Nishant Bangarwa updated AMBARI-19594:
--
Attachment: ambari-19594.patch

> configure kerberos authentication for Druid UIs
> ---
>
> Key: AMBARI-19594
> URL: https://issues.apache.org/jira/browse/AMBARI-19594
> Project: Ambari
>  Issue Type: Task
>Reporter: Nishant Bangarwa
>Assignee: Nishant Bangarwa
> Fix For: trunk, 2.5.0
>
> Attachments: ambari-19594.patch
>
>
> Druid Now supports kerberos authentication for UIs using SPNego 
> (https://github.com/druid-io/druid/pull/3853). 
> This task is to make druid end points secure when kerberos is enabled - 
> 1) Add druid-kerberos extension to druid extensions
> 2) Set druid.authentication.type to kerberos 
> 3) configure spnego keytab and principal in druid configs



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-15024) Ability for Ambari to determine java_vendor and pass it as hostLevelParam

[Robert Nettleton (JIRA)]

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

Robert Nettleton commented on AMBARI-15024:
---

Hi [~gss2002], As [~avijayan] mentioned it would probably be best to post this 
to the Apache ReviewBoard, and have this patch reviewed there.  

In general, the idea of the patch is fine with me, but I would recommend 
changing the following:

In AmbariManagementControllerImplTest, the following assertion was introduced 
by this patch:

{code}assertTrue(defaultHostParams.get(JAVA_VENDOR).equals("ibm") || 
defaultHostParams.get(JAVA_VENDOR).equals("oracle"));{code}

I would recommend either removing this assertion, or making it more flexible.  
My concern here would be if a developer attempts to run the ambari-server unit 
tests on a JDK install that is provided by a different vendor, which would case 
the test to fail.  

Thanks. 

CC [~u39kun], [~swagle]


> Ability for Ambari to determine java_vendor and pass it as hostLevelParam
> -
>
> Key: AMBARI-15024
> URL: https://issues.apache.org/jira/browse/AMBARI-15024
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Reporter: Greg Senia
>  Labels: ibm-jdk
> Fix For: 2.5.0
>
> Attachments: AMBARI-15024.patch
>
>
> Adding the ability to pass java_vendor down to ambari-agent as a 
> hostLevelParam will allow other JDKs to be put into place such as the IBM JDK 
> which has different tuning params when it comes to hadoop-env.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (AMBARI-19858) Add "live_hosts" metric in AMS for apps

[Siddharth Wagle (JIRA)]

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

Siddharth Wagle reassigned AMBARI-19858:


Assignee: Aravindan Vijayan  (was: Siddharth Wagle)

> Add "live_hosts" metric in AMS for apps
> ---
>
> Key: AMBARI-19858
> URL: https://issues.apache.org/jira/browse/AMBARI-19858
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-metrics
>Affects Versions: 2.5.0
>Reporter: Siddharth Wagle
>Assignee: Aravindan Vijayan
> Fix For: 2.5.0
>
> Attachments: AMBARI-19858.patch
>
>
> {quote}
> live_hosts=> # count of total hosts reporting 
> metrics
> live_hosts & appId =  => # count of hosts hosting this appId
> {quote}
> Where appId = { namenode, datanode, hbase ... etc }



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-19799) Optimize DB initialization for Ambari Server Unit Tests

[Hudson (JIRA)]

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

Hudson commented on AMBARI-19799:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6642 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6642/])
AMBARI-19799. Optimize DB initialization for Ambari Server Unit Tests. 
(mpapyrkovskyy: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=20103709a2b2145323cf3bccb530da0a52db72e6])
* (edit) pom.xml
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/state/cluster/AlertDataManagerTest.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/H2DatabaseCleaner.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/serveraction/upgrades/ComponentVersionCheckActionTest.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/orm/dao/CrudDAOTest.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/state/ConfigHelperTest.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/orm/dao/UpgradeDAOTest.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/serveraction/upgrades/UpgradeActionTest.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/ControllerModule.java


> Optimize DB initialization for Ambari Server Unit Tests
> ---
>
> Key: AMBARI-19799
> URL: https://issues.apache.org/jira/browse/AMBARI-19799
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Myroslav Papirkovskyi
>Assignee: Myroslav Papirkovskyi
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19799.patch
>
>
> Optimize DB initialization so DB so DB is not recreated before each UT.
> Also replaces Derby with H2 for more control over DB and increased 
> performance.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-19799) Optimize DB initialization for Ambari Server Unit Tests

[Hudson (JIRA)]

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

Hudson commented on AMBARI-19799:
-

FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #902 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/902/])
AMBARI-19799. Optimize DB initialization for Ambari Server Unit Tests. 
(mpapyrkovskyy: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=4dea63774aae481b36376cce65a11bfa28cfefa3])
* (edit) pom.xml
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/ControllerModule.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/orm/dao/UpgradeDAOTest.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/state/cluster/AlertDataManagerTest.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/orm/dao/CrudDAOTest.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/H2DatabaseCleaner.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/state/ConfigHelperTest.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/serveraction/upgrades/ComponentVersionCheckActionTest.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/serveraction/upgrades/UpgradeActionTest.java


> Optimize DB initialization for Ambari Server Unit Tests
> ---
>
> Key: AMBARI-19799
> URL: https://issues.apache.org/jira/browse/AMBARI-19799
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Myroslav Papirkovskyi
>Assignee: Myroslav Papirkovskyi
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19799.patch
>
>
> Optimize DB initialization so DB so DB is not recreated before each UT.
> Also replaces Derby with H2 for more control over DB and increased 
> performance.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-19829) Several HDFS/YARN widgets on Heatmaps show N/A

[Qin Liu (JIRA)]

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

Qin Liu commented on AMBARI-19829:
--

@atkach & @dsen Hi Andrii and Dmytro, I sent you the review request for 
AMBARI-19829. Please review it. Thanks!

> Several HDFS/YARN widgets on Heatmaps show N/A
> --
>
> Key: AMBARI-19829
> URL: https://issues.apache.org/jira/browse/AMBARI-19829
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics
>Affects Versions: 2.2.2
>Reporter: Qin Liu
>Assignee: Qin Liu
> Fix For: trunk
>
> Attachments: AMBARI-19829.patch
>
>
> The following HDFS/YARN widgets on Heatmaps show N/A:
> 1. HDFS - HDFS Bytes Written, HDFS Bytes Read, DataNode Process Disk I/O 
> Utilization, and DataNode Process Network I/O Utilization
> 2. YARN - Container Failures
> The issue was introduced by AMBARI-15835 "Rate metrics requesting widgets do 
> not show up on Ambari" which introduced rate metrics and applied rate metrics 
> to several HBASE/HDFS/YARN widgets on Summary pages  as well as Heatmap 
> pages. Rate metrics work fine on Summary pages but they don't work on Heatmap 
> pages because current Heatmap design can only show point-in-time metrics and 
> rate metrics need a time range.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-19867) Grafana install fails if custom directory's parent does not exist

[Doroszlai, Attila (JIRA)]

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

Doroszlai, Attila updated AMBARI-19867:
---
Status: Patch Available  (was: Open)

> Grafana install fails if custom directory's parent does not exist
> -
>
> Key: AMBARI-19867
> URL: https://issues.apache.org/jira/browse/AMBARI-19867
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Minor
> Fix For: 3.0.0, 2.5.0
>
> Attachments: AMBARI-19867.patch
>
>
> Creating cluster via blueprint with custom {{metrics_grafana_log_dir}} and/or 
> {{metrics_grafana_data_dir}} whose parent directory does not exist fails.
> {noformat:title=sample config}
> "ams-grafana-env": {
>   "properties": {
> "metrics_grafana_log_dir": "/var/log/ambari/metrics/grafana",
> "metrics_grafana_data_dir": "/var/lib/ambari/metrics/grafana"
>   }
> }
> {noformat}
> {noformat:title=error}
> Traceback (most recent call last):
>   File 
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py",
>  line 81, in 
> AmsGrafana().execute()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 314, in execute
> method(env)
>   File 
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py",
>  line 34, in install
> self.configure(env) # for security
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 117, in locking_configure
> original_configure(obj, *args, **kw)
>   File 
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py",
>  line 39, in configure
> ams(name='grafana', action=action)
>   File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py", 
> line 89, in thunk
> return fn(*args, **kwargs)
>   File 
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/ams.py",
>  line 426, in ams
> recursive_ownership = True
>   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 189, in action_create
> raise Fail("Applying %s failed, parent directory %s doesn't exist" % 
> (self.resource, dirname))
> resource_management.core.exceptions.Fail: Applying 
> Directory['/var/log/ambari/metrics/grafana'] failed, parent directory 
> /var/log/ambari/metrics doesn't exist
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-19867) Grafana install fails if custom directory's parent does not exist

[Doroszlai, Attila (JIRA)]

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

Doroszlai, Attila updated AMBARI-19867:
---
Attachment: AMBARI-19867.patch

> Grafana install fails if custom directory's parent does not exist
> -
>
> Key: AMBARI-19867
> URL: https://issues.apache.org/jira/browse/AMBARI-19867
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Minor
> Fix For: 3.0.0, 2.5.0
>
> Attachments: AMBARI-19867.patch
>
>
> Creating cluster via blueprint with custom {{metrics_grafana_log_dir}} and/or 
> {{metrics_grafana_data_dir}} whose parent directory does not exist fails.
> {noformat:title=sample config}
> "ams-grafana-env": {
>   "properties": {
> "metrics_grafana_log_dir": "/var/log/ambari/metrics/grafana",
> "metrics_grafana_data_dir": "/var/lib/ambari/metrics/grafana"
>   }
> }
> {noformat}
> {noformat:title=error}
> Traceback (most recent call last):
>   File 
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py",
>  line 81, in 
> AmsGrafana().execute()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 314, in execute
> method(env)
>   File 
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py",
>  line 34, in install
> self.configure(env) # for security
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 117, in locking_configure
> original_configure(obj, *args, **kw)
>   File 
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py",
>  line 39, in configure
> ams(name='grafana', action=action)
>   File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py", 
> line 89, in thunk
> return fn(*args, **kwargs)
>   File 
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/ams.py",
>  line 426, in ams
> recursive_ownership = True
>   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 189, in action_create
> raise Fail("Applying %s failed, parent directory %s doesn't exist" % 
> (self.resource, dirname))
> resource_management.core.exceptions.Fail: Applying 
> Directory['/var/log/ambari/metrics/grafana'] failed, parent directory 
> /var/log/ambari/metrics doesn't exist
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (AMBARI-19867) Grafana install fails if custom directory's parent does not exist

[Doroszlai, Attila (JIRA)]

Doroszlai, Attila created AMBARI-19867:
--

 Summary: Grafana install fails if custom directory's parent does 
not exist
 Key: AMBARI-19867
 URL: https://issues.apache.org/jira/browse/AMBARI-19867
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: 2.4.0
Reporter: Doroszlai, Attila
Assignee: Doroszlai, Attila
Priority: Minor
 Fix For: 3.0.0, 2.5.0


Creating cluster via blueprint with custom {{metrics_grafana_log_dir}} and/or 
{{metrics_grafana_data_dir}} whose parent directory does not exist fails.

{noformat:title=sample config}
"ams-grafana-env": {
  "properties": {
"metrics_grafana_log_dir": "/var/log/ambari/metrics/grafana",
"metrics_grafana_data_dir": "/var/lib/ambari/metrics/grafana"
  }
}
{noformat}

{noformat:title=error}
Traceback (most recent call last):
  File 
"/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py",
 line 81, in 
AmsGrafana().execute()
  File 
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
 line 314, in execute
method(env)
  File 
"/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py",
 line 34, in install
self.configure(env) # for security
  File 
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
 line 117, in locking_configure
original_configure(obj, *args, **kw)
  File 
"/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py",
 line 39, in configure
ams(name='grafana', action=action)
  File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py", 
line 89, in thunk
return fn(*args, **kwargs)
  File 
"/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/ams.py",
 line 426, in ams
recursive_ownership = True
  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 189, in action_create
raise Fail("Applying %s failed, parent directory %s doesn't exist" % 
(self.resource, dirname))
resource_management.core.exceptions.Fail: Applying 
Directory['/var/log/ambari/metrics/grafana'] failed, parent directory 
/var/log/ambari/metrics doesn't exist
{noformat}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (AMBARI-19866) Scale requests are failing after removing services from original components of a hostgroup

[Sandor Magyari (JIRA)]

Sandor Magyari created AMBARI-19866:
---

 Summary: Scale requests are failing after removing services from 
original components of a hostgroup
 Key: AMBARI-19866
 URL: https://issues.apache.org/jira/browse/AMBARI-19866
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Reporter: Sandor Magyari
Assignee: Sandor Magyari
Priority: Critical
 Fix For: 2.5.0


In case of BP based deployments, if after successful deployment some services 
are removed from cluster, a new Scale / Auto Scale request will fail to create 
resources, since hostgroup will contain components of a service already removed:

{code}
org.apache.ambari.server.AmbariException: The service[AMBARI_INFRA] associated 
with the component[INFRA_SOLR] doesn't exist for the cluster[adl-prod]
at 
org.apache.ambari.server.topology.AmbariContext.createAmbariHostResources(AmbariContext.java:292)
at 
org.apache.ambari.server.topology.HostRequest$PersistHostResourcesTask.run(HostRequest.java:463)
at 
{code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-19824) Add consistency checker for blueprint tables

[Sandor Magyari (JIRA)]

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

Sandor Magyari commented on AMBARI-19824:
-

Committed to trunk, branch-2.5. UT failures not related to this patch.

> Add consistency checker for blueprint tables
> 
>
> Key: AMBARI-19824
> URL: https://issues.apache.org/jira/browse/AMBARI-19824
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Sandor Magyari
>Assignee: Sandor Magyari
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19824.patch
>
>
> Additional check for topolgy tables: check that for each row in 
> topology_request there is at least one row in topology_logical_request,
> topology_host_request, topology_host_task, topology_logical_task.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-19824) Add consistency checker for blueprint tables

[Sandor Magyari (JIRA)]

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

Sandor Magyari updated AMBARI-19824:

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

> Add consistency checker for blueprint tables
> 
>
> Key: AMBARI-19824
> URL: https://issues.apache.org/jira/browse/AMBARI-19824
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Sandor Magyari
>Assignee: Sandor Magyari
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19824.patch
>
>
> Additional check for topolgy tables: check that for each row in 
> topology_request there is at least one row in topology_logical_request,
> topology_host_request, topology_host_task, topology_logical_task.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-19865) Ambari-server logon failure: Hadoop-common dependency on servlet-api 2.5

[Nahappan Somasundaram (JIRA)]

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

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

> Ambari-server logon failure: Hadoop-common dependency on servlet-api 2.5 
> -
>
> Key: AMBARI-19865
> URL: https://issues.apache.org/jira/browse/AMBARI-19865
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
> Attachments: rb56281.patch
>
>
> CredentialUtil uses hadoop-common which depends on servlet-api 2.5. This 
> causes a failure during ambari-server logon:
> {code}
> 02 Feb 2017 13:15:57,992  WARN [ambari-client-thread-25] ServletHandler:592 - 
> Error for /api/v1/clusters
> java.lang.NoSuchMethodError: 
> javax.servlet.http.HttpServletResponse.getStatus()I
> at 
> org.apache.ambari.server.security.authorization.AmbariAuthorizationFilter.doFilter(AmbariAuthorizationFilter.java:277)
> at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
> at 
> org.springframework.security.web.access.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:113)
> at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
> at 
> org.springframework.security.web.session.SessionManagementFilter.doFilter(SessionManagementFilter.java:103)
> at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
> at 
> org.springframework.security.web.authentication.AnonymousAuthenticationFilter.doFilter(AnonymousAuthenticationFilter.java:113)
> at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
> {code}
> This happens because of classpath collision between multiple servlet api 
> versions. The org.apache.hadoop:hadoop-common depends on an old version of 
> servlet api (2.5).
> {code}
> [INFO] +- org.apache.hadoop:hadoop-common:jar:2.7.2:compile
> [INFO] |  +- xmlenc:xmlenc:jar:0.52:compile
> [INFO] |  +- commons-httpclient:commons-httpclient:jar:3.1:compile
> [INFO] |  +- javax.servlet:servlet-api:jar:2.5:compile
> [INFO] |  +- org.mortbay.jetty:jetty:jar:6.1.26:compile
> [INFO] |  +- org.mortbay.jetty:jetty-util:jar:6.1.26:compile
> [INFO] |  +- javax.servlet.jsp:jsp-api:jar:2.1:runtime
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-19865) Ambari-server logon failure: Hadoop-common dependency on servlet-api 2.5

[Nahappan Somasundaram (JIRA)]

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

Nahappan Somasundaram updated AMBARI-19865:
---
Affects Version/s: 2.5.0
Fix Version/s: 2.5.0
  Component/s: ambari-server

> Ambari-server logon failure: Hadoop-common dependency on servlet-api 2.5 
> -
>
> Key: AMBARI-19865
> URL: https://issues.apache.org/jira/browse/AMBARI-19865
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
> Fix For: 2.5.0
>
> Attachments: rb56281.patch
>
>
> CredentialUtil uses hadoop-common which depends on servlet-api 2.5. This 
> causes a failure during ambari-server logon:
> {code}
> 02 Feb 2017 13:15:57,992  WARN [ambari-client-thread-25] ServletHandler:592 - 
> Error for /api/v1/clusters
> java.lang.NoSuchMethodError: 
> javax.servlet.http.HttpServletResponse.getStatus()I
> at 
> org.apache.ambari.server.security.authorization.AmbariAuthorizationFilter.doFilter(AmbariAuthorizationFilter.java:277)
> at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
> at 
> org.springframework.security.web.access.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:113)
> at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
> at 
> org.springframework.security.web.session.SessionManagementFilter.doFilter(SessionManagementFilter.java:103)
> at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
> at 
> org.springframework.security.web.authentication.AnonymousAuthenticationFilter.doFilter(AnonymousAuthenticationFilter.java:113)
> at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
> {code}
> This happens because of classpath collision between multiple servlet api 
> versions. The org.apache.hadoop:hadoop-common depends on an old version of 
> servlet api (2.5).
> {code}
> [INFO] +- org.apache.hadoop:hadoop-common:jar:2.7.2:compile
> [INFO] |  +- xmlenc:xmlenc:jar:0.52:compile
> [INFO] |  +- commons-httpclient:commons-httpclient:jar:3.1:compile
> [INFO] |  +- javax.servlet:servlet-api:jar:2.5:compile
> [INFO] |  +- org.mortbay.jetty:jetty:jar:6.1.26:compile
> [INFO] |  +- org.mortbay.jetty:jetty-util:jar:6.1.26:compile
> [INFO] |  +- javax.servlet.jsp:jsp-api:jar:2.1:runtime
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-19865) Ambari-server logon failure: Hadoop-common dependency on servlet-api 2.5

[Nahappan Somasundaram (JIRA)]

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

Nahappan Somasundaram updated AMBARI-19865:
---
Attachment: rb56281.patch

> Ambari-server logon failure: Hadoop-common dependency on servlet-api 2.5 
> -
>
> Key: AMBARI-19865
> URL: https://issues.apache.org/jira/browse/AMBARI-19865
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
> Fix For: 2.5.0
>
> Attachments: rb56281.patch
>
>
> CredentialUtil uses hadoop-common which depends on servlet-api 2.5. This 
> causes a failure during ambari-server logon:
> {code}
> 02 Feb 2017 13:15:57,992  WARN [ambari-client-thread-25] ServletHandler:592 - 
> Error for /api/v1/clusters
> java.lang.NoSuchMethodError: 
> javax.servlet.http.HttpServletResponse.getStatus()I
> at 
> org.apache.ambari.server.security.authorization.AmbariAuthorizationFilter.doFilter(AmbariAuthorizationFilter.java:277)
> at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
> at 
> org.springframework.security.web.access.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:113)
> at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
> at 
> org.springframework.security.web.session.SessionManagementFilter.doFilter(SessionManagementFilter.java:103)
> at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
> at 
> org.springframework.security.web.authentication.AnonymousAuthenticationFilter.doFilter(AnonymousAuthenticationFilter.java:113)
> at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
> {code}
> This happens because of classpath collision between multiple servlet api 
> versions. The org.apache.hadoop:hadoop-common depends on an old version of 
> servlet api (2.5).
> {code}
> [INFO] +- org.apache.hadoop:hadoop-common:jar:2.7.2:compile
> [INFO] |  +- xmlenc:xmlenc:jar:0.52:compile
> [INFO] |  +- commons-httpclient:commons-httpclient:jar:3.1:compile
> [INFO] |  +- javax.servlet:servlet-api:jar:2.5:compile
> [INFO] |  +- org.mortbay.jetty:jetty:jar:6.1.26:compile
> [INFO] |  +- org.mortbay.jetty:jetty-util:jar:6.1.26:compile
> [INFO] |  +- javax.servlet.jsp:jsp-api:jar:2.1:runtime
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-19855) Stack advisor issues encountered

[Hudson (JIRA)]

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

Hudson commented on AMBARI-19855:
-

FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #901 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/901/])
AMBARI-19855 Stack advisor issues encountered (dsen) (dsen: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=98e37b008c8a64703a5464d4dd3e5f8ccae4792b])
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.2/services/stack_advisor.py
* (edit) ambari-server/src/test/python/stacks/2.2/common/test_stack_advisor.py
* (edit) 
ambari-server/src/main/resources/stacks/HDPWIN/2.2/services/stack_advisor.py


> Stack advisor issues encountered
> 
>
> Key: AMBARI-19855
> URL: https://issues.apache.org/jira/browse/AMBARI-19855
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.5.0
> Environment: 1. A default setting that did not hold so many cores in 
> reserve. 20% seems very high.
> 2. This setting should be validated to flag when an impossible setting has 
> been configured, specifically when the number of configured virtual cores is 
> greater than actual number of cores it should be flagged.
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
> Fix For: 2.5.0
>
> Attachments: AMBARI-19855.patch
>
>
> 1. A default setting that did not hold so many cores in reserve. 20% seems 
> very high.
> 2. This setting should be validated to flag when an impossible setting has 
> been configured, specifically when the number of configured virtual cores is 
> greater than actual number of cores it should be flagged.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-19865) Ambari-server logon failure: Hadoop-common dependency on servlet-api 2.5

[Nahappan Somasundaram (JIRA)]

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

Nahappan Somasundaram updated AMBARI-19865:
---
Description: 
CredentialUtil uses hadoop-common which depends on servlet-api 2.5. This causes 
a failure during ambari-server logon:

{code}
02 Feb 2017 13:15:57,992  WARN [ambari-client-thread-25] ServletHandler:592 - 
Error for /api/v1/clusters
java.lang.NoSuchMethodError: javax.servlet.http.HttpServletResponse.getStatus()I
at 
org.apache.ambari.server.security.authorization.AmbariAuthorizationFilter.doFilter(AmbariAuthorizationFilter.java:277)
at 
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
at 
org.springframework.security.web.access.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:113)
at 
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
at 
org.springframework.security.web.session.SessionManagementFilter.doFilter(SessionManagementFilter.java:103)
at 
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
at 
org.springframework.security.web.authentication.AnonymousAuthenticationFilter.doFilter(AnonymousAuthenticationFilter.java:113)
at 
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
{code}

This happens because of classpath collision between multiple servlet api 
versions. The org.apache.hadoop:hadoop-common depends on an old version of 
servlet api (2.5).

{code}
[INFO] +- org.apache.hadoop:hadoop-common:jar:2.7.2:compile
[INFO] |  +- xmlenc:xmlenc:jar:0.52:compile
[INFO] |  +- commons-httpclient:commons-httpclient:jar:3.1:compile
[INFO] |  +- javax.servlet:servlet-api:jar:2.5:compile
[INFO] |  +- org.mortbay.jetty:jetty:jar:6.1.26:compile
[INFO] |  +- org.mortbay.jetty:jetty-util:jar:6.1.26:compile
[INFO] |  +- javax.servlet.jsp:jsp-api:jar:2.1:runtime
{code}

  was:

{code}
02 Feb 2017 13:15:57,992  WARN [ambari-client-thread-25] ServletHandler:592 - 
Error for /api/v1/clusters
java.lang.NoSuchMethodError: javax.servlet.http.HttpServletResponse.getStatus()I
at 
org.apache.ambari.server.security.authorization.AmbariAuthorizationFilter.doFilter(AmbariAuthorizationFilter.java:277)
at 
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
at 
org.springframework.security.web.access.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:113)
at 
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
at 
org.springframework.security.web.session.SessionManagementFilter.doFilter(SessionManagementFilter.java:103)
at 
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
at 
org.springframework.security.web.authentication.AnonymousAuthenticationFilter.doFilter(AnonymousAuthenticationFilter.java:113)
at 
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
{code}

This happens because of classpath collision between multiple servlet api 
versions. The org.apache.hadoop:hadoop-common depends on an old version of 
servlet api (2.5).

{code}
[INFO] +- org.apache.hadoop:hadoop-common:jar:2.7.2:compile
[INFO] |  +- xmlenc:xmlenc:jar:0.52:compile
[INFO] |  +- commons-httpclient:commons-httpclient:jar:3.1:compile
[INFO] |  +- javax.servlet:servlet-api:jar:2.5:compile
[INFO] |  +- org.mortbay.jetty:jetty:jar:6.1.26:compile
[INFO] |  +- org.mortbay.jetty:jetty-util:jar:6.1.26:compile
[INFO] |  +- javax.servlet.jsp:jsp-api:jar:2.1:runtime
{code}


> Ambari-server logon failure: Hadoop-common dependency on servlet-api 2.5 
> -
>
> Key: AMBARI-19865
> URL: https://issues.apache.org/jira/browse/AMBARI-19865
> Project: Ambari
>  Issue Type: Bug
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
>
> CredentialUtil uses hadoop-common which depends on servlet-api 2.5. This 
> causes a failure during ambari-server logon:
> {code}
> 02 Feb 2017 13:15:57,992  WARN [ambari-client-thread-25] ServletHandler:592 - 
> Error for /api/v1/clusters
> java.lang.NoSuchMethodError: 
> javax.servlet.http.HttpServletResponse.getStatus()I
> at 
> org.apache.ambari.server.security.authorization.AmbariAuthorizationFilter.doFilter(AmbariAuthorizationFilter.java:277)
> at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
> at 
> 

[jira] [Updated] (AMBARI-18896) Suse11 deployment failures due to package issues

[Dmytro Sen (JIRA)]

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

Dmytro Sen updated AMBARI-18896:

Resolution: Cannot Reproduce
Status: Resolved  (was: Patch Available)

the patch for AMBARI-17898 causing this issue was reverted.

> Suse11 deployment failures due to package issues
> 
>
> Key: AMBARI-18896
> URL: https://issues.apache.org/jira/browse/AMBARI-18896
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics
>Affects Versions: 2.5.0
> Environment: Suse
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-18896_2.patch, AMBARI-18896.patch
>
>
> Suse 11 deployment failed due to
> {code}
>   File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 303, in _call
> raise ExecutionFailed(err_msg, code, out, err)
> resource_management.core.exceptions.ExecutionFailed: Execution of 
> '/usr/bin/zypper --quiet install --auto-agree-with-licenses --no-confirm 
> ambari-metrics-monitor' returned 4. Problem: nothing provides python-kerberos 
> needed by ambari-metrics-monitor-2.5.0.0-283.x86_64
>  Solution 1: do not install ambari-metrics-monitor-2.5.0.0-283.x86_64
>  Solution 2: break ambari-metrics-monitor-2.5.0.0-283.x86_64 by ignoring some 
> of its dependencies
> Choose from above solutions by number or cancel [1/2/c] (c): c
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-19855) Stack advisor issues encountered

[Hudson (JIRA)]

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

Hudson commented on AMBARI-19855:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6641 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6641/])
AMBARI-19855 Stack advisor issues encountered (dsen) (dsen: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=b51691b17db954d64e4dd52226aefb7d860428c2])
* (edit) ambari-server/src/test/python/stacks/2.2/common/test_stack_advisor.py
* (edit) 
ambari-server/src/main/resources/common-services/YARN/3.0.0.3.0/service_advisor.py
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.2/services/stack_advisor.py
* (edit) 
ambari-server/src/main/resources/stacks/HDPWIN/2.2/services/stack_advisor.py


> Stack advisor issues encountered
> 
>
> Key: AMBARI-19855
> URL: https://issues.apache.org/jira/browse/AMBARI-19855
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.5.0
> Environment: 1. A default setting that did not hold so many cores in 
> reserve. 20% seems very high.
> 2. This setting should be validated to flag when an impossible setting has 
> been configured, specifically when the number of configured virtual cores is 
> greater than actual number of cores it should be flagged.
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
> Fix For: 2.5.0
>
> Attachments: AMBARI-19855.patch
>
>
> 1. A default setting that did not hold so many cores in reserve. 20% seems 
> very high.
> 2. This setting should be validated to flag when an impossible setting has 
> been configured, specifically when the number of configured virtual cores is 
> greater than actual number of cores it should be flagged.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (AMBARI-19865) Ambari-server logon failure: Hadoop-common dependency on servlet-api 2.5

[Nahappan Somasundaram (JIRA)]

Nahappan Somasundaram created AMBARI-19865:
--

 Summary: Ambari-server logon failure: Hadoop-common dependency on 
servlet-api 2.5 
 Key: AMBARI-19865
 URL: https://issues.apache.org/jira/browse/AMBARI-19865
 Project: Ambari
  Issue Type: Bug
Reporter: Nahappan Somasundaram
Assignee: Nahappan Somasundaram



{code}
02 Feb 2017 13:15:57,992  WARN [ambari-client-thread-25] ServletHandler:592 - 
Error for /api/v1/clusters
java.lang.NoSuchMethodError: javax.servlet.http.HttpServletResponse.getStatus()I
at 
org.apache.ambari.server.security.authorization.AmbariAuthorizationFilter.doFilter(AmbariAuthorizationFilter.java:277)
at 
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
at 
org.springframework.security.web.access.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:113)
at 
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
at 
org.springframework.security.web.session.SessionManagementFilter.doFilter(SessionManagementFilter.java:103)
at 
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
at 
org.springframework.security.web.authentication.AnonymousAuthenticationFilter.doFilter(AnonymousAuthenticationFilter.java:113)
at 
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
{code}

This happens because of classpath collision between multiple servlet api 
versions. The org.apache.hadoop:hadoop-common depends on an old version of 
servlet api (2.5).

{code}
[INFO] +- org.apache.hadoop:hadoop-common:jar:2.7.2:compile
[INFO] |  +- xmlenc:xmlenc:jar:0.52:compile
[INFO] |  +- commons-httpclient:commons-httpclient:jar:3.1:compile
[INFO] |  +- javax.servlet:servlet-api:jar:2.5:compile
[INFO] |  +- org.mortbay.jetty:jetty:jar:6.1.26:compile
[INFO] |  +- org.mortbay.jetty:jetty-util:jar:6.1.26:compile
[INFO] |  +- javax.servlet.jsp:jsp-api:jar:2.1:runtime
{code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-19855) Stack advisor issues encountered

[Dmytro Sen (JIRA)]

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

Dmytro Sen updated AMBARI-19855:

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

Committed to trunk and branch-2.5

> Stack advisor issues encountered
> 
>
> Key: AMBARI-19855
> URL: https://issues.apache.org/jira/browse/AMBARI-19855
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.5.0
> Environment: 1. A default setting that did not hold so many cores in 
> reserve. 20% seems very high.
> 2. This setting should be validated to flag when an impossible setting has 
> been configured, specifically when the number of configured virtual cores is 
> greater than actual number of cores it should be flagged.
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
> Fix For: 2.5.0
>
> Attachments: AMBARI-19855.patch
>
>
> 1. A default setting that did not hold so many cores in reserve. 20% seems 
> very high.
> 2. This setting should be validated to flag when an impossible setting has 
> been configured, specifically when the number of configured virtual cores is 
> greater than actual number of cores it should be flagged.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-19856) Perf: start/stop all actions works much slower after few days of testing

[Hudson (JIRA)]

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

Hudson commented on AMBARI-19856:
-

SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #900 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/900/])
AMBARI-19856. Perf: start/stop all actions works much slower after few 
(vbrodetskyi: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=0615883bd740999b410e604f3f4cd0128747e581])
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/state/ServiceComponentHost.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/state/svccomphost/ServiceComponentHostImpl.java
* (edit) contrib/utils/perf/deploy-gce-perf-cluster.py
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariManagementControllerImpl.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/state/ConfigHelper.java


> Perf: start/stop all actions works much slower after few days of testing
> 
>
> Key: AMBARI-19856
> URL: https://issues.apache.org/jira/browse/AMBARI-19856
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19856.patch
>
>
> Add changes to gce script, to deploy perf cluster with all options needed. 
> Try to find more code to optimize.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-19856) Perf: start/stop all actions works much slower after few days of testing

[Hudson (JIRA)]

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

Hudson commented on AMBARI-19856:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6640 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6640/])
AMBARI-19856. Perf: start/stop all actions works much slower after few 
(vbrodetskyi: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=132e266521642d90908d3dd69446a701ca94c3db])
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/state/svccomphost/ServiceComponentHostImpl.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/state/ServiceComponentHost.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/state/ConfigHelper.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariManagementControllerImpl.java
* (edit) contrib/utils/perf/deploy-gce-perf-cluster.py


> Perf: start/stop all actions works much slower after few days of testing
> 
>
> Key: AMBARI-19856
> URL: https://issues.apache.org/jira/browse/AMBARI-19856
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19856.patch
>
>
> Add changes to gce script, to deploy perf cluster with all options needed. 
> Try to find more code to optimize.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-19864) Zookeeper namespace for Hive service should be taken from hive-interactive-site, when only Hive-server Interactive is installed.

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-19864:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12850829/AMBARI-19864.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/10406//console

This message is automatically generated.

> Zookeeper namespace for Hive service should be taken from 
> hive-interactive-site, when only Hive-server Interactive is installed.
> 
>
> Key: AMBARI-19864
> URL: https://issues.apache.org/jira/browse/AMBARI-19864
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Vishal Suvagia
>Assignee: Vishal Suvagia
> Fix For: 2.5.0
>
> Attachments: AMBARI-19864.patch
>
>
> If Hive-Server Interactive is installed independently, then zoo-keeper name 
> space for hive service configured for Ranger should be taken from 
> hive-interactive-site.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-19864) Zookeeper namespace for Hive service should be taken from hive-interactive-site, when only Hive-server Interactive is installed.

[Vishal Suvagia (JIRA)]

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

Vishal Suvagia updated AMBARI-19864:

Status: Patch Available  (was: In Progress)

adding fix for the issue

> Zookeeper namespace for Hive service should be taken from 
> hive-interactive-site, when only Hive-server Interactive is installed.
> 
>
> Key: AMBARI-19864
> URL: https://issues.apache.org/jira/browse/AMBARI-19864
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Vishal Suvagia
>Assignee: Vishal Suvagia
> Fix For: 2.5.0
>
> Attachments: AMBARI-19864.patch
>
>
> If Hive-Server Interactive is installed independently, then zoo-keeper name 
> space for hive service configured for Ranger should be taken from 
> hive-interactive-site.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-19856) Perf: start/stop all actions works much slower after few days of testing

[Vitaly Brodetskyi (JIRA)]

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

Vitaly Brodetskyi updated AMBARI-19856:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

Committed to trunk and branch-2.5

> Perf: start/stop all actions works much slower after few days of testing
> 
>
> Key: AMBARI-19856
> URL: https://issues.apache.org/jira/browse/AMBARI-19856
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19856.patch
>
>
> Add changes to gce script, to deploy perf cluster with all options needed. 
> Try to find more code to optimize.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-19864) Zookeeper namespace for Hive service should be taken from hive-interactive-site, when only Hive-server Interactive is installed.

[Vishal Suvagia (JIRA)]

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

Vishal Suvagia updated AMBARI-19864:

Attachment: AMBARI-19864.patch

> Zookeeper namespace for Hive service should be taken from 
> hive-interactive-site, when only Hive-server Interactive is installed.
> 
>
> Key: AMBARI-19864
> URL: https://issues.apache.org/jira/browse/AMBARI-19864
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Vishal Suvagia
>Assignee: Vishal Suvagia
> Fix For: 2.5.0
>
> Attachments: AMBARI-19864.patch
>
>
> If Hive-Server Interactive is installed independently, then zoo-keeper name 
> space for hive service configured for Ranger should be taken from 
> hive-interactive-site.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-19845) Secure Ranger passwords in Ambari Stacks

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-19845:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12850820/AMBARI-19845.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/10405//console

This message is automatically generated.

> Secure Ranger passwords in Ambari Stacks
> 
>
> Key: AMBARI-19845
> URL: https://issues.apache.org/jira/browse/AMBARI-19845
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.1.0, 2.2.2, 2.4.2
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19845.patch
>
>
> Make sure plain-text password is not persisted in XML and always stored in 
> jceks



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-19860) Ambari upgrade to HDP 2.5 from earlier versions does not update storm worker log directory

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-19860:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12850819/AMBARI-19860.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/10404//console

This message is automatically generated.

> Ambari upgrade to HDP 2.5 from earlier versions does not update storm worker 
> log directory
> --
>
> Key: AMBARI-19860
> URL: https://issues.apache.org/jira/browse/AMBARI-19860
> Project: Ambari
>  Issue Type: Bug
>Reporter: Arun Mahadevan
> Attachments: AMBARI-19860.patch
>
>
> During upgrade the storm worker.xml and cluster.xml files should have updated 
> path.
> {noformat}
> 
> fileName="${sys:workers.artifacts}/${sys:storm.id}/${sys:worker.port}/${sys:logfile.name}"
>   
> filePattern="${sys:workers.artifacts}/${sys:storm.id}/${sys:worker.port}/${sys:logfile.name}.%i.gz">
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-19851) ambari-server start failed with exit code 1.

[Hudson (JIRA)]

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

Hudson commented on AMBARI-19851:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6639 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6639/])
AMBARI-19851. ambari-server start failed with exit code 1. (aonishuk) 
(aonishuk: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=f2561c48f71614d56fd747239cdd16bf5a6ef9ea])
* (edit) ambari-server/src/main/python/ambari_server/serverConfiguration.py
* (edit) ambari-server/src/main/python/ambari_server/serverSetup.py


> ambari-server start failed with exit code 1.
> 
>
> Key: AMBARI-19851
> URL: https://issues.apache.org/jira/browse/AMBARI-19851
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.5.0
>
> Attachments: AMBARI-19851.patch
>
>
> Found this issue in ST.  
> Trying to provide setup ambari-server and
> 
> 
> [root@ctr-e126-1485243696039-17812-01-04 ~]# ambari-server setup -s
> Using python  /usr/bin/python
> Setup ambari-server
> Nothing was done. Ambari Setup already performed and cannot re-run setup 
> in silent mode. Use "ambari-server setup" command without -s option to change 
> Ambari setup.
> 
> Trying to start ambari-server
> 
> 
> [root@ctr-e126-1485243696039-17812-01-04 ~]# ambari-server start
> Using python  /usr/bin/python
> Starting ambari-server
> ERROR: Exiting with exit code 1. 
> REASON: Unable to detect a system user for Ambari Server.
> - If this is a new setup, then run the "ambari-server setup" command to 
> create the user
> - If this is an upgrade of an existing setup, run the "ambari-server 
> upgrade" command.
> Refer to the Ambari documentation for more information on setup and 
> upgrade.
> 
> Ambari-server restart in debug log
> 
> 
> 2017-02-01 04:36:34,630 DEBUG 
> com.hw.ambari.ui.util.cluster_managers.CommandExecutor.executeCommandSequence():
>  Sending command [ambari-server restart --debug]
> 2017-02-01 04:36:35,331 DEBUG 
> com.hw.ambari.ui.util.cluster_managers.CommandExecutor.executeCommandSequence():
>  [OUTPUT STREAM]
> Using python  /usr/bin/python
> Restarting ambari-server
> Ambari Server is not running
> ERROR: Exiting with exit code 1. 
> REASON: Unable to detect a system user for Ambari Server.
> - If this is a new setup, then run the "ambari-server setup" command to 
> create the user
> - If this is an upgrade of an existing setup, run the "ambari-server 
> upgrade" command.
> Refer to the Ambari documentation for more information on setup and 
> upgrade.
> **ambari-server setup** without -s setup ambari successful and ambari-server 
> start passed.
> artifacts:  /test-logs/ambari-setup-hw/artifacts/screenshots/com.hw.ambari.ui.tests.consol
> e.TestInstallSeparateSSLCertificate/testA_InstallSeparateSSLCertificate/_1_4_4
> 0_52_Element_has_not_been_found_within_60_seconds__/>  
> cluster: 172.27.30.144



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-19851) ambari-server start failed with exit code 1.

[Hudson (JIRA)]

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

Hudson commented on AMBARI-19851:
-

FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #898 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/898/])
AMBARI-19851. ambari-server start failed with exit code 1. (aonishuk) 
(aonishuk: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=679248abef5c2669d586d205d58886e4c219b795])
* (edit) ambari-server/src/main/python/ambari_server/serverSetup.py
* (edit) ambari-server/src/main/python/ambari_server/serverConfiguration.py


> ambari-server start failed with exit code 1.
> 
>
> Key: AMBARI-19851
> URL: https://issues.apache.org/jira/browse/AMBARI-19851
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.5.0
>
> Attachments: AMBARI-19851.patch
>
>
> Found this issue in ST.  
> Trying to provide setup ambari-server and
> 
> 
> [root@ctr-e126-1485243696039-17812-01-04 ~]# ambari-server setup -s
> Using python  /usr/bin/python
> Setup ambari-server
> Nothing was done. Ambari Setup already performed and cannot re-run setup 
> in silent mode. Use "ambari-server setup" command without -s option to change 
> Ambari setup.
> 
> Trying to start ambari-server
> 
> 
> [root@ctr-e126-1485243696039-17812-01-04 ~]# ambari-server start
> Using python  /usr/bin/python
> Starting ambari-server
> ERROR: Exiting with exit code 1. 
> REASON: Unable to detect a system user for Ambari Server.
> - If this is a new setup, then run the "ambari-server setup" command to 
> create the user
> - If this is an upgrade of an existing setup, run the "ambari-server 
> upgrade" command.
> Refer to the Ambari documentation for more information on setup and 
> upgrade.
> 
> Ambari-server restart in debug log
> 
> 
> 2017-02-01 04:36:34,630 DEBUG 
> com.hw.ambari.ui.util.cluster_managers.CommandExecutor.executeCommandSequence():
>  Sending command [ambari-server restart --debug]
> 2017-02-01 04:36:35,331 DEBUG 
> com.hw.ambari.ui.util.cluster_managers.CommandExecutor.executeCommandSequence():
>  [OUTPUT STREAM]
> Using python  /usr/bin/python
> Restarting ambari-server
> Ambari Server is not running
> ERROR: Exiting with exit code 1. 
> REASON: Unable to detect a system user for Ambari Server.
> - If this is a new setup, then run the "ambari-server setup" command to 
> create the user
> - If this is an upgrade of an existing setup, run the "ambari-server 
> upgrade" command.
> Refer to the Ambari documentation for more information on setup and 
> upgrade.
> **ambari-server setup** without -s setup ambari successful and ambari-server 
> start passed.
> artifacts:  /test-logs/ambari-setup-hw/artifacts/screenshots/com.hw.ambari.ui.tests.consol
> e.TestInstallSeparateSSLCertificate/testA_InstallSeparateSSLCertificate/_1_4_4
> 0_52_Element_has_not_been_found_within_60_seconds__/>  
> cluster: 172.27.30.144



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-19856) Perf: start/stop all actions works much slower after few days of testing

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-19856:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12850815/AMBARI-19856.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/10403//console

This message is automatically generated.

> Perf: start/stop all actions works much slower after few days of testing
> 
>
> Key: AMBARI-19856
> URL: https://issues.apache.org/jira/browse/AMBARI-19856
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19856.patch
>
>
> Add changes to gce script, to deploy perf cluster with all options needed. 
> Try to find more code to optimize.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-19851) ambari-server start failed with exit code 1.

[Andrew Onischuk (JIRA)]

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

Andrew Onischuk updated AMBARI-19851:
-
Resolution: Fixed
Status: Resolved  (was: Patch Available)

Committed to trunk and branch-2.5

> ambari-server start failed with exit code 1.
> 
>
> Key: AMBARI-19851
> URL: https://issues.apache.org/jira/browse/AMBARI-19851
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.5.0
>
> Attachments: AMBARI-19851.patch
>
>
> Found this issue in ST.  
> Trying to provide setup ambari-server and
> 
> 
> [root@ctr-e126-1485243696039-17812-01-04 ~]# ambari-server setup -s
> Using python  /usr/bin/python
> Setup ambari-server
> Nothing was done. Ambari Setup already performed and cannot re-run setup 
> in silent mode. Use "ambari-server setup" command without -s option to change 
> Ambari setup.
> 
> Trying to start ambari-server
> 
> 
> [root@ctr-e126-1485243696039-17812-01-04 ~]# ambari-server start
> Using python  /usr/bin/python
> Starting ambari-server
> ERROR: Exiting with exit code 1. 
> REASON: Unable to detect a system user for Ambari Server.
> - If this is a new setup, then run the "ambari-server setup" command to 
> create the user
> - If this is an upgrade of an existing setup, run the "ambari-server 
> upgrade" command.
> Refer to the Ambari documentation for more information on setup and 
> upgrade.
> 
> Ambari-server restart in debug log
> 
> 
> 2017-02-01 04:36:34,630 DEBUG 
> com.hw.ambari.ui.util.cluster_managers.CommandExecutor.executeCommandSequence():
>  Sending command [ambari-server restart --debug]
> 2017-02-01 04:36:35,331 DEBUG 
> com.hw.ambari.ui.util.cluster_managers.CommandExecutor.executeCommandSequence():
>  [OUTPUT STREAM]
> Using python  /usr/bin/python
> Restarting ambari-server
> Ambari Server is not running
> ERROR: Exiting with exit code 1. 
> REASON: Unable to detect a system user for Ambari Server.
> - If this is a new setup, then run the "ambari-server setup" command to 
> create the user
> - If this is an upgrade of an existing setup, run the "ambari-server 
> upgrade" command.
> Refer to the Ambari documentation for more information on setup and 
> upgrade.
> **ambari-server setup** without -s setup ambari successful and ambari-server 
> start passed.
> artifacts:  /test-logs/ambari-setup-hw/artifacts/screenshots/com.hw.ambari.ui.tests.consol
> e.TestInstallSeparateSSLCertificate/testA_InstallSeparateSSLCertificate/_1_4_4
> 0_52_Element_has_not_been_found_within_60_seconds__/>  
> cluster: 172.27.30.144



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (AMBARI-19864) Zookeeper namespace for Hive service should be taken from hive-interactive-site, when only Hive-server Interactive is installed.

[Vishal Suvagia (JIRA)]

Vishal Suvagia created AMBARI-19864:
---

 Summary: Zookeeper namespace for Hive service should be taken from 
hive-interactive-site, when only Hive-server Interactive is installed.
 Key: AMBARI-19864
 URL: https://issues.apache.org/jira/browse/AMBARI-19864
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: 2.5.0
Reporter: Vishal Suvagia
Assignee: Vishal Suvagia
 Fix For: 2.5.0


If Hive-Server Interactive is installed independently, then zoo-keeper name 
space for hive service configured for Ranger should be taken from 
hive-interactive-site.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-19859) The user must be clearly communicated about YARN pre-emption requirements when Hive LLAP is enabled

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-19859:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12850759/AMBARI-19859.v1.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/10399//console

This message is automatically generated.

> The user must be clearly communicated about YARN pre-emption requirements 
> when Hive LLAP is enabled
> ---
>
> Key: AMBARI-19859
> URL: https://issues.apache.org/jira/browse/AMBARI-19859
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Vivek Ratnavel Subramanian
>Assignee: Vivek Ratnavel Subramanian
> Fix For: 2.5.0
>
> Attachments: AMBARI-19859.v0.patch, AMBARI-19859.v1.patch, Ambari   
> c1.png, Screen Shot 2017-02-02 at 7.02.45 PM.png
>
>
> Capacity Scheduler preemption is not enabled by default in HDP. Enabling it 
> affects the entire cluster. But it is strongly recommended to enable YARN 
> pre-emption before enabling Hive LLAP. The user needs to be warned about this 
> before enabling Interactive Query in Hive configs page.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-19860) Ambari upgrade to HDP 2.5 from earlier versions does not update storm worker log directory

[Arun Mahadevan (JIRA)]

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

Arun Mahadevan commented on AMBARI-19860:
-

[~sriharsha] Please review.

> Ambari upgrade to HDP 2.5 from earlier versions does not update storm worker 
> log directory
> --
>
> Key: AMBARI-19860
> URL: https://issues.apache.org/jira/browse/AMBARI-19860
> Project: Ambari
>  Issue Type: Bug
>Reporter: Arun Mahadevan
> Attachments: AMBARI-19860.patch
>
>
> During upgrade the storm worker.xml and cluster.xml files should have updated 
> path.
> {noformat}
> 
> fileName="${sys:workers.artifacts}/${sys:storm.id}/${sys:worker.port}/${sys:logfile.name}"
>   
> filePattern="${sys:workers.artifacts}/${sys:storm.id}/${sys:worker.port}/${sys:logfile.name}.%i.gz">
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-19806) After setting up hadoop credential, cannot start Hive Metastore

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-19806:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12850790/AMBARI-19806_servlet_api.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/10398//console

This message is automatically generated.

> After setting up hadoop credential, cannot start Hive Metastore
> ---
>
> Key: AMBARI-19806
> URL: https://issues.apache.org/jira/browse/AMBARI-19806
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19806_servlet_api.patch, rb56142.patch
>
>
> In HIVE, after javax.jdo.option.ConnectionPassword property and value is 
> moved  into a JCEKS file using hadoop credential store, hive-site.xml looks 
> like this:
> {quote} 
> hadoop.security.credential.provider.path
> jceks://file/usr/lib/hive/conf/hive.jceks
>   {quote}
> instead of:
> {quote} 
> javax.jdo.option.ConnectionPassword
> MyHiveConnectionPassword
>   {quote}
> However, after the above change, HIVE fails to start. This is an Ambari 
> deployed cluster.
> {quote}Traceback (most recent call last):
>   File 
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_metastore.py",
>  line 259, in 
> HiveMetastore().execute()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 287, in execute
> method(env)
>   File 
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_metastore.py",
>  line 59, in start
> self.configure(env)
>   File 
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_metastore.py",
>  line 73, in configure
> hive(name = 'metastore')
>   File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py", 
> line 89, in thunk
> return fn(*args, **kwargs)
>   File 
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive.py",
>  line 326, in hive
> create_schema_cmd = format("export HIVE_CONF_DIR={hive_server_conf_dir} ; 
> "
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/format.py",
>  line 95, in format
> return ConfigurationFormatter().format(format_string, args, **result)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/format.py",
>  line 62, in format
> result_unprotected = self.vformat(format_string, args, all_params)
>   File "/usr/lib64/python2.6/string.py", line 549, in vformat
> result = self._vformat(format_string, args, kwargs, used_args, 2)
>   File "/usr/lib64/python2.6/string.py", line 575, in _vformat
> obj = self.convert_field(obj, conversion)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/format.py",
>  line 70, in convert_field_unprotected
> return self._convert_field(value, conversion, False)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/format.py",
>  line 85, in _convert_field
> return utils.PASSWORDS_HIDE_STRING if is_protected else 
> self._convert_field(value, 'e', is_protected)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/format.py",
>  line 81, in _convert_field
> return quote_bash_args(unicode(value))
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/config_dictionary.py",
>  line 73, in __getattr__
> raise Fail("Configuration parameter '" + self.name + "' was not found in 
> configurations dictionary!")
> resource_management.core.exceptions.Fail: Configuration parameter 
> 'javax.jdo.option.ConnectionPassword' was not found in configurations 
> dictionary!{quote}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-19824) Add consistency checker for blueprint tables

[Hudson (JIRA)]

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

Hudson commented on AMBARI-19824:
-

FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #897 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/897/])
AMBARI-19824. Add consistency checker for blueprint tables (smagyari: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=7eac12f20dd46c0a4b6d705b045998d49840a575])
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/checks/DatabaseConsistencyCheckHelper.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/checks/DatabaseConsistencyCheckHelperTest.java


> Add consistency checker for blueprint tables
> 
>
> Key: AMBARI-19824
> URL: https://issues.apache.org/jira/browse/AMBARI-19824
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Sandor Magyari
>Assignee: Sandor Magyari
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19824.patch
>
>
> Additional check for topolgy tables: check that for each row in 
> topology_request there is at least one row in topology_logical_request,
> topology_host_request, topology_host_task, topology_logical_task.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-19863) Fix Log Search User Config bugs

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-19863:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12850801/AMBARI-19863.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/10397//console

This message is automatically generated.

> Fix Log Search User Config bugs
> ---
>
> Key: AMBARI-19863
> URL: https://issues.apache.org/jira/browse/AMBARI-19863
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-logsearch
>Affects Versions: 2.4.0
>Reporter: Miklos Gergely
>Assignee: Miklos Gergely
> Fix For: 2.5.0
>
> Attachments: AMBARI-19863.patch
>
>
> There are several bugs relating to the user configs:
> - due to a bug saving filters do not work
> - saving / viewing / deleting filters uses the user name received, instead of 
> the logged in user
> - deleting filter button is not visible



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-19860) Ambari upgrade to HDP 2.5 from earlier versions does not update storm worker log directory

[Arun Mahadevan (JIRA)]

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

Arun Mahadevan updated AMBARI-19860:

Summary: Ambari upgrade to HDP 2.5 from earlier versions does not update 
storm worker log directory  (was: Ambari upgrade to HDP 2.5 from earlier 
versions does not update storm worker/cluster log directory)

> Ambari upgrade to HDP 2.5 from earlier versions does not update storm worker 
> log directory
> --
>
> Key: AMBARI-19860
> URL: https://issues.apache.org/jira/browse/AMBARI-19860
> Project: Ambari
>  Issue Type: Bug
>Reporter: Arun Mahadevan
> Attachments: AMBARI-19860.patch
>
>
> During upgrade the storm worker.xml and cluster.xml files should have updated 
> path.
> {noformat}
> 
> fileName="${sys:workers.artifacts}/${sys:storm.id}/${sys:worker.port}/${sys:logfile.name}"
>   
> filePattern="${sys:workers.artifacts}/${sys:storm.id}/${sys:worker.port}/${sys:logfile.name}.%i.gz">
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-19845) Secure Ranger passwords in Ambari Stacks

[Mugdha Varadkar (JIRA)]

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

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

> Secure Ranger passwords in Ambari Stacks
> 
>
> Key: AMBARI-19845
> URL: https://issues.apache.org/jira/browse/AMBARI-19845
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.1.0, 2.2.2, 2.4.2
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19845.patch
>
>
> Make sure plain-text password is not persisted in XML and always stored in 
> jceks



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-19845) Secure Ranger passwords in Ambari Stacks

[Mugdha Varadkar (JIRA)]

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

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

> Secure Ranger passwords in Ambari Stacks
> 
>
> Key: AMBARI-19845
> URL: https://issues.apache.org/jira/browse/AMBARI-19845
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.1.0, 2.2.2, 2.4.2
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19845.patch
>
>
> Make sure plain-text password is not persisted in XML and always stored in 
> jceks



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)