[jira] [Updated] (AMBARI-17311) Modify HTTP headers to follow best security practices

[Sangeeta Ravindran (JIRA)]

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

Sangeeta Ravindran updated AMBARI-17311:

Attachment: AMBARI-17311.patch

> Modify HTTP headers to follow best security practices
> -
>
> Key: AMBARI-17311
> URL: https://issues.apache.org/jira/browse/AMBARI-17311
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Affects Versions: trunk
>Reporter: Sangeeta Ravindran
>Assignee: Sangeeta Ravindran
> Fix For: trunk
>
> Attachments: AMBARI-17311.patch
>
>
> Add the following HTTP headers to follow security best practices.
> X-Content-Type-Options: nosniff
> Cache-control: no-store
> Pragma: no-cache



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

[jira] [Updated] (AMBARI-17311) Modify HTTP headers to follow best security practices

[Sangeeta Ravindran (JIRA)]

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

Sangeeta Ravindran updated AMBARI-17311:

Status: Open  (was: Patch Available)

> Modify HTTP headers to follow best security practices
> -
>
> Key: AMBARI-17311
> URL: https://issues.apache.org/jira/browse/AMBARI-17311
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Affects Versions: trunk
>Reporter: Sangeeta Ravindran
>Assignee: Sangeeta Ravindran
> Fix For: trunk
>
>
> Add the following HTTP headers to follow security best practices.
> X-Content-Type-Options: nosniff
> Cache-control: no-store
> Pragma: no-cache



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

[jira] [Updated] (AMBARI-17311) Modify HTTP headers to follow best security practices

[Sangeeta Ravindran (JIRA)]

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

Sangeeta Ravindran updated AMBARI-17311:

Attachment: (was: AMBARI-17311.patch)

> Modify HTTP headers to follow best security practices
> -
>
> Key: AMBARI-17311
> URL: https://issues.apache.org/jira/browse/AMBARI-17311
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Affects Versions: trunk
>Reporter: Sangeeta Ravindran
>Assignee: Sangeeta Ravindran
> Fix For: trunk
>
>
> Add the following HTTP headers to follow security best practices.
> X-Content-Type-Options: nosniff
> Cache-control: no-store
> Pragma: no-cache



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

[jira] [Updated] (AMBARI-17165) Handle Java patches execution during Ranger upgrade

[Gautam Borad (JIRA)]

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

Gautam Borad updated AMBARI-17165:
--
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Handle Java patches execution during Ranger upgrade
> ---
>
> Key: AMBARI-17165
> URL: https://issues.apache.org/jira/browse/AMBARI-17165
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0, 2.2.2
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
> Fix For: 2.4.0
>
> Attachments: AMBARI-17165.1.patch, AMBARI-17165.2.patch, 
> AMBARI-17165.3.patch, AMBARI-17165.patch
>
>
> Revisiting implementation of java patches during upgrade for Ranger Service



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

[jira] [Commented] (AMBARI-17165) Handle Java patches execution during Ranger upgrade

[Gautam Borad (JIRA)]

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

Gautam Borad commented on AMBARI-17165:
---

Committed to trunk : 
https://github.com/apache/ambari/commit/13fc644c65dc224259d555698663e51f2c77d293
Committed to branch-2.4 : 
https://github.com/apache/ambari/commit/8d023a2017fcf76facf70d70121d34bd9fce7922

> Handle Java patches execution during Ranger upgrade
> ---
>
> Key: AMBARI-17165
> URL: https://issues.apache.org/jira/browse/AMBARI-17165
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0, 2.2.2
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
> Fix For: 2.4.0
>
> Attachments: AMBARI-17165.1.patch, AMBARI-17165.2.patch, 
> AMBARI-17165.3.patch, AMBARI-17165.patch
>
>
> Revisiting implementation of java patches during upgrade for Ranger Service



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

[jira] [Commented] (AMBARI-17344) Clear /security.json if kerberos is disabled

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-17344:


{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12812239/AMBARI-17344.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/7463//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/7463//console

This message is automatically generated.

> Clear /security.json if kerberos is disabled
> 
>
> Key: AMBARI-17344
> URL: https://issues.apache.org/jira/browse/AMBARI-17344
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-logsearch, ambari-server
>Affects Versions: 2.4.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
> Fix For: 2.4.0
>
> Attachments: AMBARI-17344.patch
>
>




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

[jira] [Commented] (AMBARI-17226) When requesting a Kerberos Descriptor via the REST API, 'when' clauses should optionally be processed

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-17226:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12812230/AMBARI-17226_branch-2.4_01.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 5 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:red}-1 core tests{color}.  The patch failed these unit tests in 
ambari-server:

  org.apache.ambari.server.state.ServicePropertiesTest
  org.apache.ambari.server.agent.TestHeartbeatHandler

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

This message is automatically generated.

> When requesting a Kerberos Descriptor via the REST API, 'when' clauses should 
> optionally be processed
> -
>
> Key: AMBARI-17226
> URL: https://issues.apache.org/jira/browse/AMBARI-17226
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Robert Levas
>Assignee: Robert Levas
> Fix For: 2.4.0
>
> Attachments: AMBARI-17226_branch-2.4_01.patch, 
> AMBARI-17226_trunk_01.patch
>
>
> When requesting a Kerberos Descriptor via the REST API, 'when' clauses should 
> optionally be processed.  If elected to be processed, identities that contain 
> {{when}} clauses will be included or excluded from the resulting descriptor 
> based on the result of the evaluation. 
> In the event of an _add service_ scenario, the services being added should be 
> able to be specified so that they can be included in the data used for 
> {{when}}-clause evaluation.  
> *Solution*
> Add _{{GET}} directives_ to specify whether {{when}} clauses are to be 
> evaluated (or not) while building the Kerberos Descriptor using the following 
> API call:
> {noformat}
> GET 
> /api/v1/clusters/CLUSTER_NAME/kerberos_descriptors/COMPOSITE?evaluate_when=true
> {noformat}
> If new services are being added, the {{additional_services}} directive should 
> be added to the request so the evaluation can be preformed on the _future_ 
> set of services, which may evaluate differently then the _current_ set of 
> services.
> {noformat}
> GET 
> /api/v1/clusters/CLUSTER_NAME/kerberos_descriptors/COMPOSITE?evaluate_when=true@additional_services=HIVE,TEZ,PIG
> {noformat}



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

[jira] [Updated] (AMBARI-17353) First class support for YARN hosted services

[Yusaku Sako (JIRA)]

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

Yusaku Sako updated AMBARI-17353:
-
Fix Version/s: (was: 3.0.0)

> First class support for YARN hosted services
> 
>
> Key: AMBARI-17353
> URL: https://issues.apache.org/jira/browse/AMBARI-17353
> Project: Ambari
>  Issue Type: Epic
>  Components: ambari-agent, ambari-server, ambari-web
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
>Priority: Critical
>
> YARN-896 and SLIDER-183 enabled running long running applications (services) 
> on YARN. Apache Ambari Slider View provides us a way to deploy and manage 
> long running services on YARN. 
> However, the Slider View provides a limited functionality and does not 
> provide a first class support for YARN hosted services similar to traditional 
> services deployed directly on the hosts by Ambari. 
> Besides while YARN-896 got the ball rolling for supporting services on YARN, 
> the YARN team is working on major improvements and a first class support for 
> YARN hosted services (YARN-4692). 
> This initiative is for providing a first class support for YARN-hosted 
> services and leverage all the YARN improvements planned and documented in 
> YARN-4692. 



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

[jira] [Updated] (AMBARI-17354) POC: FE changes for first class support for Yarn hosted services

[Yusaku Sako (JIRA)]

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

Yusaku Sako updated AMBARI-17354:
-
Fix Version/s: (was: 3.0.0)

> POC: FE changes for first class support for Yarn hosted services
> 
>
> Key: AMBARI-17354
> URL: https://issues.apache.org/jira/browse/AMBARI-17354
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Reporter: Jayush Luniya
>Assignee: Jaimin D Jetly
>Priority: Critical
>
> JIRA for front end proof of concept work to provide first class support for 
> Yarn hosted services.



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

[jira] [Updated] (AMBARI-17355) POC: BE changes for first class support for Yarn hosted services

[Yusaku Sako (JIRA)]

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

Yusaku Sako updated AMBARI-17355:
-
Fix Version/s: (was: 3.0.0)

> POC: BE changes for first class support for Yarn hosted services
> 
>
> Key: AMBARI-17355
> URL: https://issues.apache.org/jira/browse/AMBARI-17355
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
>Priority: Critical
>
> JIRA for backend proof of concept work to provide first class support for 
> Yarn hosted services.



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

[jira] [Updated] (AMBARI-17354) POC: FE changes for first class support for Yarn hosted services

[Yusaku Sako (JIRA)]

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

Yusaku Sako updated AMBARI-17354:
-
Affects Version/s: (was: 2.4.0)

> POC: FE changes for first class support for Yarn hosted services
> 
>
> Key: AMBARI-17354
> URL: https://issues.apache.org/jira/browse/AMBARI-17354
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Reporter: Jayush Luniya
>Assignee: Jaimin D Jetly
>Priority: Critical
>
> JIRA for front end proof of concept work to provide first class support for 
> Yarn hosted services.



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

[jira] [Updated] (AMBARI-17353) First class support for YARN hosted services

[Yusaku Sako (JIRA)]

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

Yusaku Sako updated AMBARI-17353:
-
Affects Version/s: (was: 2.4.0)

> First class support for YARN hosted services
> 
>
> Key: AMBARI-17353
> URL: https://issues.apache.org/jira/browse/AMBARI-17353
> Project: Ambari
>  Issue Type: Epic
>  Components: ambari-agent, ambari-server, ambari-web
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
>Priority: Critical
>
> YARN-896 and SLIDER-183 enabled running long running applications (services) 
> on YARN. Apache Ambari Slider View provides us a way to deploy and manage 
> long running services on YARN. 
> However, the Slider View provides a limited functionality and does not 
> provide a first class support for YARN hosted services similar to traditional 
> services deployed directly on the hosts by Ambari. 
> Besides while YARN-896 got the ball rolling for supporting services on YARN, 
> the YARN team is working on major improvements and a first class support for 
> YARN hosted services (YARN-4692). 
> This initiative is for providing a first class support for YARN-hosted 
> services and leverage all the YARN improvements planned and documented in 
> YARN-4692. 



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

[jira] [Updated] (AMBARI-17355) POC: BE changes for first class support for Yarn hosted services

[Yusaku Sako (JIRA)]

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

Yusaku Sako updated AMBARI-17355:
-
Affects Version/s: (was: 2.4.0)

> POC: BE changes for first class support for Yarn hosted services
> 
>
> Key: AMBARI-17355
> URL: https://issues.apache.org/jira/browse/AMBARI-17355
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
>Priority: Critical
>
> JIRA for backend proof of concept work to provide first class support for 
> Yarn hosted services.



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

[jira] [Commented] (AMBARI-17243) Change livy principal to service type

[Hudson (JIRA)]

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

Hudson commented on AMBARI-17243:
-

FAILURE: Integrated in Ambari-trunk-Commit #5127 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5127/])
AMBARI-17243. Change livy principal to service type (Jeff Zhang via (rlevas: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=97b14647cf02a252ff092652c298b23314df6ec5])
* 
ambari-server/src/main/resources/common-services/SPARK/1.2.1/package/scripts/service_check.py
* ambari-server/src/main/resources/stacks/HDP/2.5/services/SPARK/kerberos.json
* 
ambari-server/src/main/resources/common-services/SPARK/1.2.1/package/scripts/params.py
* 
ambari-server/src/main/resources/common-services/SPARK/1.2.1/package/scripts/setup_livy.py


> Change livy principal to service type
> -
>
> Key: AMBARI-17243
> URL: https://issues.apache.org/jira/browse/AMBARI-17243
> Project: Ambari
>  Issue Type: Improvement
>  Components: stacks
>Affects Versions: 2.4.0
>Reporter: Jeff Zhang
>Assignee: Jeff Zhang
> Fix For: 2.4.0
>
>
> To have unique principal names that is the convention followed by rest of the 
> principals. 
> Noticed in stack deploy this principal does not have cluster name.



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

[jira] [Commented] (AMBARI-17280) RU to write out client configs that are dependencies of Hive, ATS, and Oozie during upgrades that change configs

[Hudson (JIRA)]

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

Hudson commented on AMBARI-17280:
-

FAILURE: Integrated in Ambari-trunk-Commit #5127 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5127/])
AMBARI-17280. RU to write out client configs that are dependencies of 
(afernandez: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=58198f5339b221e6b3c6d8fb2d61523f2ac0e3bf])
* 
ambari-server/src/main/resources/common-services/SPARK/1.2.1/package/scripts/spark_client.py
* 
ambari-common/src/main/python/resource_management/libraries/functions/conf_select.py
* 
ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/scripts/yarn.py
* ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/upgrade-2.5.xml
* ambari-server/src/test/python/stacks/2.1/TEZ/test_tez_client.py
* 
ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/scripts/mapreduce2_client.py
* 
ambari-server/src/main/resources/common-services/TEZ/0.4.0.2.1/package/scripts/params_linux.py
* ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.4.xml
* 
ambari-server/src/main/resources/common-services/TEZ/0.4.0.2.1/package/scripts/tez_client.py
* ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.5.xml
* 
ambari-server/src/main/resources/common-services/SPARK/1.2.1/package/scripts/setup_spark.py
* 
ambari-common/src/main/python/resource_management/libraries/functions/stack_select.py
* 
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/UpgradeResourceProvider.java
* 
ambari-server/src/main/resources/common-services/TEZ/0.4.0.2.1/package/scripts/tez.py
* 
ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/scripts/params_linux.py
* ambari-common/src/main/python/resource_management/libraries/script/script.py


> RU to write out client configs that are dependencies of Hive, ATS, and Oozie 
> during upgrades that change configs
> 
>
> Key: AMBARI-17280
> URL: https://issues.apache.org/jira/browse/AMBARI-17280
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.2.0
>Reporter: Ana Gillan
>Assignee: Alejandro Fernandez
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17280.branch-2.4.patch, AMBARI-17280.trunk.patch
>
>
> During RU, HiveServer2 is restarted but the newer tez configs have not yet 
> been saved, which is incorrect because Hive has a dependency on Tez.
> This is important when configs change during a major stack upgrade, e.g., HDP 
> 2.4 -> 2.5. What happens today is,
> * Install packages generates /etc/tez/2.5.0.0-1/0 and copies the configs from 
> /etc/tez/2.4.0.0-1/0/ to the new folder
> * If configs change during RU, then Hive is restarted and the classpath means 
> that it will pick up the older tez configs from the new /etc/tez/2.5.0.0-1/0 
> folder
> This problem exists for all of these components:
> HiveServer: depends on Tez and MapReduce clients
> ATS: depends on Tez and Spark clients
> Oozie: depends on Tez, Spark, and MapReduce clients
> This problem only exists when configs change (so crossing major stack 
> version) and during RU (because it is allowed to change configs during the 
> middle of restarting services).



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

[jira] [Commented] (AMBARI-17348) Allow https protocol for Log Search

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-17348:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12812254/AMBARI-17348.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:red}-1 core tests{color}.  The test build failed in 
ambari-logsearch/ambari-logsearch-portal 

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

This message is automatically generated.

> Allow https protocol for Log Search
> ---
>
> Key: AMBARI-17348
> URL: https://issues.apache.org/jira/browse/AMBARI-17348
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-logsearch
>Affects Versions: 2.4.0
>Reporter: Miklos Gergely
>Assignee: Miklos Gergely
> Fix For: 2.4.0
>
> Attachments: AMBARI-17348.patch
>
>
> Add a property to choose whether or not the Log Search UI should run using 
> https.



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

[jira] [Commented] (AMBARI-17345) Hive metastore failed to start

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-17345:


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

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

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

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

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

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

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

This message is automatically generated.

> Hive metastore failed to start
> --
>
> Key: AMBARI-17345
> URL: https://issues.apache.org/jira/browse/AMBARI-17345
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-17345.patch
>
>
> STR:
> 1) Add Hive Metastore on hosts that do not have it
> 2) Restart services with stale configs
> It started fine on retrying
> {code}
> ERROR: Unable to connect to the DB. Please check DB connection 
> properties.\njava.lang.ClassNotFoundException: 
> oracle.jdbc.driver.OracleDriver\n2016-06-20 13:18:14,206 - Retrying after 10 
> seconds. Reason: Execution of '/usr/jdk64/jdk1.8.0_77/bin/java -cp 
> /usr/lib/ambari-agent/DBConnectionVerification.jar:/usr/hdp/current/hive-metastore/lib/ojdbc6.jar
>  org.apache.ambari.server.DBConnectionVerification 
> 'jdbc:oracle:thin:@//172.22.124.192:1521/XE' hiveuser [PROTECTED] 
> oracle.jdbc.driver.OracleDriver' returned 1. ERROR: Unable to connect to the 
> DB. Please check DB connection properties.\njava.lang.ClassNotFoundException:
> {code}



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

[jira] [Commented] (AMBARI-11999) Blueprint export incorrectly includes Kerberos host information

[Shi Wang (JIRA)]

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

Shi Wang commented on AMBARI-11999:
---

Hi,

I think this has been fixed in 2.2, in my generated blueprint there is no kdc 
server info anymore and need to add manually to blueprint a new cluster.

> Blueprint export incorrectly includes Kerberos host information
> ---
>
> Key: AMBARI-11999
> URL: https://issues.apache.org/jira/browse/AMBARI-11999
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.1.0
>Reporter: Robert Nettleton
>Assignee: Robert Nettleton
>Priority: Critical
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> The Blueprint processor incorrectly includes some Kerberos-related hostname 
> properties in an exported Blueprint.  Since there is no support yet for 
> starting a Kerberized cluster directly with a Blueprint, these properties are 
> confusing to users, and also include hostname information, which makes the 
> Blueprint less portable across different cluster types.  
> Steps to reproduce:
> 1. Setup a single-node cluster (HDFS/Yarn/Zookeeper/Metrics) with the Ambari 
> UI.
> 2. Enable Kerberos using the Kerberos Wizard in the Ambari UI.
> 3. Export a Blueprint from the running cluster using the following REST URL:
> http://host:port/api/v1/clusters/cluster_name?format=blueprint
> This Blueprint will include the following Kerberos hostname properties:
> "admin_server_host" in "kerberos-env"
> "kdc_host" in "kerberos-env"
> "hadoop.proxyuser.yarn.hosts" in "core-site"
> The Blueprints configuration processor needs to updated to filter out these 
> properties, or export them without the hostname information. 
> I'm working on a fix for this, and will submit a patch shortly. 



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

[jira] [Updated] (AMBARI-17356) Add the ability to perform interactive shell commands from Ambari server side actions

[Robert Levas (JIRA)]

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

Robert Levas updated AMBARI-17356:
--
Issue Type: Task  (was: Bug)

> Add the ability to perform interactive shell commands from Ambari server side 
> actions
> -
>
> Key: AMBARI-17356
> URL: https://issues.apache.org/jira/browse/AMBARI-17356
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Affects Versions: 2.0.0
>Reporter: Robert Levas
>Assignee: Robert Levas
> Fix For: 2.4.0
>
> Attachments: AMBARI-17356_branch-2.4_01.patch, 
> AMBARI-17356_trunk_01.patch
>
>
> Add the ability to perform interactive shell commands from Ambari server side 
> actions. This will allow sensitive data, like passwords, to be sent to shell 
> commands via STDIN rather than on the command line. 



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

[jira] [Commented] (AMBARI-17342) Ambari agent log contains failures for AMS status commands

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-17342:


{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12812221/AMBARI-17342.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/7458//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/7458//console

This message is automatically generated.

> Ambari agent log contains failures for AMS status commands
> --
>
> Key: AMBARI-17342
> URL: https://issues.apache.org/jira/browse/AMBARI-17342
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.4.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-17342.patch
>
>
> Ambari agent logs contain failures for status commands for AMS collector is 
> status command is executed before AMS collector is actually installed. 
> Reproduced on blueprint deployments
> {code}
> INFO 2016-06-15 08:48:17,190 PythonReflectiveExecutor.py:65 - Reflective 
> command failed with exception:
> Traceback (most recent call last):
>   File 
> "/usr/lib/python2.6/site-packages/ambari_agent/PythonReflectiveExecutor.py", 
> line 57, in run_file
> imp.load_source('__main__', script)
>   File 
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_collector.py",
>  line 143, in 
> AmsCollector().execute()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 257, in execute
> method(env)
>   File 
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_collector.py",
>  line 98, in security_status
> is_hbase_distributed = 
> security_params['hbase-site']['hbase.cluster.distributed']
> KeyError: 'hbase.cluster.distributed'
> {code}



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

[jira] [Updated] (AMBARI-17356) Add the ability to perform interactive shell commands from Ambari server side actions

[Robert Levas (JIRA)]

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

Robert Levas updated AMBARI-17356:
--
Attachment: AMBARI-17356_trunk_01.patch
AMBARI-17356_branch-2.4_01.patch

> Add the ability to perform interactive shell commands from Ambari server side 
> actions
> -
>
> Key: AMBARI-17356
> URL: https://issues.apache.org/jira/browse/AMBARI-17356
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.0.0
>Reporter: Robert Levas
>Assignee: Robert Levas
> Fix For: 2.4.0
>
> Attachments: AMBARI-17356_branch-2.4_01.patch, 
> AMBARI-17356_trunk_01.patch
>
>
> Add the ability to perform interactive shell commands from Ambari server side 
> actions. This will allow sensitive data, like passwords, to be sent to shell 
> commands via STDIN rather than on the command line. 



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

[jira] [Updated] (AMBARI-17356) Add the ability to perform interactive shell commands from Ambari server side actions

[Robert Levas (JIRA)]

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

Robert Levas updated AMBARI-17356:
--
Status: Patch Available  (was: In Progress)

> Add the ability to perform interactive shell commands from Ambari server side 
> actions
> -
>
> Key: AMBARI-17356
> URL: https://issues.apache.org/jira/browse/AMBARI-17356
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.0.0
>Reporter: Robert Levas
>Assignee: Robert Levas
> Fix For: 2.4.0
>
> Attachments: AMBARI-17356_branch-2.4_01.patch, 
> AMBARI-17356_trunk_01.patch
>
>
> Add the ability to perform interactive shell commands from Ambari server side 
> actions. This will allow sensitive data, like passwords, to be sent to shell 
> commands via STDIN rather than on the command line. 



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

[jira] [Commented] (AMBARI-17341) Hosts sorting works for Load avg only in some cases

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-17341:


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

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

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

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

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

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

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

This message is automatically generated.

> Hosts sorting works for Load avg only in some cases
> ---
>
> Key: AMBARI-17341
> URL: https://issues.apache.org/jira/browse/AMBARI-17341
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17341.patch
>
>
> STR:
> # Deploy cluster HDP 2.3 on ambari 2.1.2
> # Enable NN HA
> # Upgrade ambari to 2.4.0
> # Restart all services
> # Go to hosts page
> # Try to sort hosts by "Load avg"
> Result: sorting is not working
> But if you go to other page and then come back to hosts page all hosts will 
> be sorted by "Load avg" right.



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

[jira] [Created] (AMBARI-17357) Add wiki on management packs

[Jayush Luniya (JIRA)]

Jayush Luniya created AMBARI-17357:
--

 Summary: Add wiki on management packs
 Key: AMBARI-17357
 URL: https://issues.apache.org/jira/browse/AMBARI-17357
 Project: Ambari
  Issue Type: Task
  Components: ambari-server
Affects Versions: 2.4.0
Reporter: Jayush Luniya
Assignee: Jayush Luniya
 Fix For: 2.4.0






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

[jira] [Created] (AMBARI-17356) Add the ability to perform interactive shell commands from Ambari server side actions

[Robert Levas (JIRA)]

Robert Levas created AMBARI-17356:
-

 Summary: Add the ability to perform interactive shell commands 
from Ambari server side actions
 Key: AMBARI-17356
 URL: https://issues.apache.org/jira/browse/AMBARI-17356
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: 2.0.0
Reporter: Robert Levas
Assignee: Robert Levas
 Fix For: 2.4.0


Add the ability to perform interactive shell commands from Ambari server side 
actions. This will allow sensitive data, like passwords, to be sent to shell 
commands via STDIN rather than on the command line. 



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

[jira] [Created] (AMBARI-17355) POC: BE changes for first class support for Yarn hosted services

[Jayush Luniya (JIRA)]

Jayush Luniya created AMBARI-17355:
--

 Summary: POC: BE changes for first class support for Yarn hosted 
services
 Key: AMBARI-17355
 URL: https://issues.apache.org/jira/browse/AMBARI-17355
 Project: Ambari
  Issue Type: Task
  Components: ambari-server
Affects Versions: 2.4.0
Reporter: Jayush Luniya
Assignee: Jayush Luniya
Priority: Critical
 Fix For: 3.0.0


JIRA for backend proof of concept work to provide first class support for Yarn 
hosted services.



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

[jira] [Created] (AMBARI-17354) POC: FE changes for first class support for Yarn hosted services

[Jayush Luniya (JIRA)]

Jayush Luniya created AMBARI-17354:
--

 Summary: POC: FE changes for first class support for Yarn hosted 
services
 Key: AMBARI-17354
 URL: https://issues.apache.org/jira/browse/AMBARI-17354
 Project: Ambari
  Issue Type: Task
  Components: ambari-web
Affects Versions: 2.4.0
Reporter: Jayush Luniya
Assignee: Jaimin D Jetly
Priority: Critical
 Fix For: 3.0.0


JIRA for front end proof of concept work to provide first class support for 
Yarn hosted services.



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

[jira] [Updated] (AMBARI-17353) First class support for YARN hosted services

[Jayush Luniya (JIRA)]

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

Jayush Luniya updated AMBARI-17353:
---
Description: 
YARN-896 and SLIDER-183 enabled running long running applications (services) on 
YARN. Apache Ambari Slider View provides us a way to deploy and manage long 
running services on YARN. 

However, the Slider View provides a limited functionality and does not provide 
a first class support for YARN hosted services similar to traditional services 
deployed directly on the hosts by Ambari. 

Besides while YARN-896 got the ball rolling for supporting services on YARN, 
the YARN team is working on major improvements and a first class support for 
YARN hosted services (YARN-4692). 

This initiative is for providing a first class support for YARN-hosted services 
and leverage all the YARN improvements planned and documented in YARN-4692. 

> First class support for YARN hosted services
> 
>
> Key: AMBARI-17353
> URL: https://issues.apache.org/jira/browse/AMBARI-17353
> Project: Ambari
>  Issue Type: Epic
>  Components: ambari-agent, ambari-server, ambari-web
>Affects Versions: 2.4.0
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
>Priority: Critical
> Fix For: 3.0.0
>
>
> YARN-896 and SLIDER-183 enabled running long running applications (services) 
> on YARN. Apache Ambari Slider View provides us a way to deploy and manage 
> long running services on YARN. 
> However, the Slider View provides a limited functionality and does not 
> provide a first class support for YARN hosted services similar to traditional 
> services deployed directly on the hosts by Ambari. 
> Besides while YARN-896 got the ball rolling for supporting services on YARN, 
> the YARN team is working on major improvements and a first class support for 
> YARN hosted services (YARN-4692). 
> This initiative is for providing a first class support for YARN-hosted 
> services and leverage all the YARN improvements planned and documented in 
> YARN-4692. 



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

[jira] [Commented] (AMBARI-17340) Alert mapreduce_history_server_process fails after enabling SSL

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-17340:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12812213/AMBARI-17340.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:red}-1 core tests{color}.  The patch failed these unit tests in 
ambari-server:

  
org.apache.ambari.server.controller.internal.ConfigGroupResourceProviderTest
  org.apache.ambari.server.state.ServicePropertiesTest

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

This message is automatically generated.

> Alert mapreduce_history_server_process fails after enabling SSL
> ---
>
> Key: AMBARI-17340
> URL: https://issues.apache.org/jira/browse/AMBARI-17340
> Project: Ambari
>  Issue Type: Bug
>  Components: alerts, ambari-upgrade
>Affects Versions: 2.2.2
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17340.patch
>
>
> Remove mapreduce_history_server_process , it duplicates 
> mapreduce_history_server_webui



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

[jira] [Commented] (AMBARI-17326) Mark the role "(from group)" if there is no specific user level role set.

[Hudson (JIRA)]

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

Hudson commented on AMBARI-17326:
-

FAILURE: Integrated in Ambari-trunk-Commit #5126 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5126/])
AMBARI-17326 - Mark the role "(from group)" if there is no specific user 
(rzang: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=50d794c7dff38a3613ca61bd8f112e6cef50ef1b])
* ambari-admin/src/main/resources/ui/admin-web/app/scripts/i18n.config.js
* 
ambari-admin/src/main/resources/ui/admin-web/app/views/clusters/userAccessList.html


> Mark the role "(from group)" if there is no specific user level role set.
> -
>
> Key: AMBARI-17326
> URL: https://issues.apache.org/jira/browse/AMBARI-17326
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-admin
>Affects Versions: 2.4.0
>Reporter: Richard Zang
>Assignee: Richard Zang
> Fix For: 2.4.0
>
> Attachments: AMBARI-17326.patch
>
>
> For user role listing view, we will mark the role "(from group)" if there is 
> no specific user level role set.



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

[jira] [Commented] (AMBARI-17317) tez.tez-ui.history-url.base did not get updated after ambari upgrade

[Hudson (JIRA)]

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

Hudson commented on AMBARI-17317:
-

FAILURE: Integrated in Ambari-trunk-Commit #5126 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5126/])
AMBARI-17317. 'tez.tez-ui.history-url.base' did not get updated after 
(dipayan.bhowmick: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=fb9e407cab7294b73fed413108ac103b343d7610])
* 
ambari-server/src/main/java/org/apache/ambari/server/upgrade/AbstractUpgradeCatalog.java
* 
ambari-server/src/test/java/org/apache/ambari/server/upgrade/AbstractUpgradeCatalogTest.java


> tez.tez-ui.history-url.base did not get updated after ambari upgrade
> 
>
> Key: AMBARI-17317
> URL: https://issues.apache.org/jira/browse/AMBARI-17317
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.2.0
>Reporter: DIPAYAN BHOWMICK
>Assignee: DIPAYAN BHOWMICK
> Fix For: 2.4.0
>
> Attachments: AMBARI-17317.branch-2.4.patch
>
>
> After upgrading from Ambari 2.2.1.0 to ambari 2.2.2.0 my 
> tez.tez-ui.history-url.base still pointed to the old version of the tez view 
> URL.
> This caused an issue when user clicked on the AM link for a running tez app 
> and it took them to the wrong url.



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

[jira] [Commented] (AMBARI-17331) Determine Tez for Hive2 config 'tez.am.resource.memory.mb' based on cluster capacity.

[Hudson (JIRA)]

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

Hudson commented on AMBARI-17331:
-

FAILURE: Integrated in Ambari-trunk-Commit #5126 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5126/])
AMBARI-17331. Determine Tez for Hive2 config 'tez.am.resource.memory.mb' 
(sshridhar: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=ff0f5c008a190360c998ee2cca147dd6d0d51063])
* ambari-server/src/main/resources/stacks/HDP/2.5/services/stack_advisor.py
* ambari-server/src/test/python/stacks/2.5/common/test_stack_advisor.py
* 
ambari-server/src/main/resources/stacks/HDP/2.5/services/HIVE/configuration/tez-interactive-site.xml


> Determine Tez for Hive2 config 'tez.am.resource.memory.mb' based on cluster 
> capacity.
> -
>
> Key: AMBARI-17331
> URL: https://issues.apache.org/jira/browse/AMBARI-17331
> Project: Ambari
>  Issue Type: Bug
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Attachments: AMBARI-17331.patch
>
>
> The current computations done for tez ends up with a large AM size.
> For LLAP, we'd like stack-advisor to change these computations.
> - Total Cluster Memory <=4GB - Tez AM size = 256MB and then normalized based 
> on YARN minimum container size.
> - Total Cluster Memory >4GB && <= 72GB - Tez AM size = 512MB and then 
> normalized based on YARN minimum container size.
> - Total Cluster Memory >72GB - Tez AM size = 1536MB and then normalized based 
> on YARN minimum container size.



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

[jira] [Commented] (AMBARI-17074) Expose Spark daemon memory in Spark2

[Hudson (JIRA)]

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

Hudson commented on AMBARI-17074:
-

FAILURE: Integrated in Ambari-trunk-Commit #5126 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5126/])
AMBARI-17074. Expose Spark daemon memory in Spark2 (Weiqing Yang via (sgunturi: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=706946e84cf8c1b6e9121da3ed08516c9d1329c8])
* 
ambari-server/src/main/resources/common-services/SPARK2/2.0.0/configuration/spark2-env.xml
* 
ambari-server/src/main/resources/common-services/SPARK2/2.0.0/package/scripts/params.py


> Expose Spark daemon memory in Spark2
> 
>
> Key: AMBARI-17074
> URL: https://issues.apache.org/jira/browse/AMBARI-17074
> Project: Ambari
>  Issue Type: Improvement
>Reporter: Weiqing Yang
>Assignee: Weiqing Yang
> Fix For: trunk, 2.4.0
>
> Attachments: AMBARI-17074.v1.patch, AMBARI-17074_v2.patch, 
> AMBARI-17074_v3.patch
>
>
> Expose Spark daemon memory in Spark2, so that the user can modify its size on 
> ambari web UI easily.



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

[jira] [Resolved] (AMBARI-17243) Change livy principal to service type

[Robert Levas (JIRA)]

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

Robert Levas resolved AMBARI-17243.
---
Resolution: Fixed

Committed to trunk
{noformat}
commit 97b14647cf02a252ff092652c298b23314df6ec5
Author: Jeff Zhang 
Date:   Tue Jun 21 19:44:14 2016 -0400
{noformat}

Committed to branch-2.4
{noformat}
commit f814c5f3d6447ef4e035aacb0d8d4b49b1beb9c2
Author: Jeff Zhang 
Date:   Tue Jun 21 19:45:03 2016 -0400
{noformat}

> Change livy principal to service type
> -
>
> Key: AMBARI-17243
> URL: https://issues.apache.org/jira/browse/AMBARI-17243
> Project: Ambari
>  Issue Type: Improvement
>  Components: stacks
>Affects Versions: 2.4.0
>Reporter: Jeff Zhang
>Assignee: Jeff Zhang
> Fix For: 2.4.0
>
>
> To have unique principal names that is the convention followed by rest of the 
> principals. 
> Noticed in stack deploy this principal does not have cluster name.



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

[jira] [Updated] (AMBARI-17280) RU to write out client configs that are dependencies of Hive, ATS, and Oozie during upgrades that change configs

[Alejandro Fernandez (JIRA)]

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

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

Pushed to trunk, commit 58198f5339b221e6b3c6d8fb2d61523f2ac0e3bf
branch-2.4, commit ac096a0e59abea2ee524ed880bc48f7e1dab9f21

> RU to write out client configs that are dependencies of Hive, ATS, and Oozie 
> during upgrades that change configs
> 
>
> Key: AMBARI-17280
> URL: https://issues.apache.org/jira/browse/AMBARI-17280
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.2.0
>Reporter: Ana Gillan
>Assignee: Alejandro Fernandez
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17280.branch-2.4.patch, AMBARI-17280.trunk.patch
>
>
> During RU, HiveServer2 is restarted but the newer tez configs have not yet 
> been saved, which is incorrect because Hive has a dependency on Tez.
> This is important when configs change during a major stack upgrade, e.g., HDP 
> 2.4 -> 2.5. What happens today is,
> * Install packages generates /etc/tez/2.5.0.0-1/0 and copies the configs from 
> /etc/tez/2.4.0.0-1/0/ to the new folder
> * If configs change during RU, then Hive is restarted and the classpath means 
> that it will pick up the older tez configs from the new /etc/tez/2.5.0.0-1/0 
> folder
> This problem exists for all of these components:
> HiveServer: depends on Tez and MapReduce clients
> ATS: depends on Tez and Spark clients
> Oozie: depends on Tez, Spark, and MapReduce clients
> This problem only exists when configs change (so crossing major stack 
> version) and during RU (because it is allowed to change configs during the 
> middle of restarting services).



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

[jira] [Updated] (AMBARI-17349) spark.driver.extraJavaOptions and spark.yarn.am.extraJavaOptions property is set to empty

[Weiqing Yang (JIRA)]

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

Weiqing Yang updated AMBARI-17349:
--
Attachment: AMBARI-17349_v0.patch

> spark.driver.extraJavaOptions and spark.yarn.am.extraJavaOptions property is 
> set to empty
> -
>
> Key: AMBARI-17349
> URL: https://issues.apache.org/jira/browse/AMBARI-17349
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.4.0
>Reporter: Yesha Vora
>Assignee: Weiqing Yang
> Attachments: AMBARI-17349_v0.patch
>
>
> spark.driver.extraJavaOptions and spark.yarn.am.extraJavaOptions is set to 
> empty.
> Either spark.driver.extraJavaOptions / spark.yarn.am.extraJavaOptions should 
> be removed from spark-defaults.conf or it should set to a valid value.



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

[jira] [Created] (AMBARI-17353) First class support for YARN hosted services

[Jayush Luniya (JIRA)]

Jayush Luniya created AMBARI-17353:
--

 Summary: First class support for YARN hosted services
 Key: AMBARI-17353
 URL: https://issues.apache.org/jira/browse/AMBARI-17353
 Project: Ambari
  Issue Type: Epic
  Components: ambari-agent, ambari-server, ambari-web
Affects Versions: 2.4.0
Reporter: Jayush Luniya
Assignee: Jayush Luniya
Priority: Critical
 Fix For: 3.0.0






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

[jira] [Commented] (AMBARI-17165) Handle Java patches execution during Ranger upgrade

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-17165:


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

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

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

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

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

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

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

This message is automatically generated.

> Handle Java patches execution during Ranger upgrade
> ---
>
> Key: AMBARI-17165
> URL: https://issues.apache.org/jira/browse/AMBARI-17165
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0, 2.2.2
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
> Fix For: 2.4.0
>
> Attachments: AMBARI-17165.1.patch, AMBARI-17165.2.patch, 
> AMBARI-17165.3.patch, AMBARI-17165.patch
>
>
> Revisiting implementation of java patches during upgrade for Ranger Service



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

[jira] [Updated] (AMBARI-17280) RU to write out client configs that are dependencies of Hive, ATS, and Oozie during upgrades that change configs

[Alejandro Fernandez (JIRA)]

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

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

> RU to write out client configs that are dependencies of Hive, ATS, and Oozie 
> during upgrades that change configs
> 
>
> Key: AMBARI-17280
> URL: https://issues.apache.org/jira/browse/AMBARI-17280
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.2.0
>Reporter: Ana Gillan
>Assignee: Alejandro Fernandez
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17280.branch-2.4.patch, AMBARI-17280.trunk.patch
>
>
> During RU, HiveServer2 is restarted but the newer tez configs have not yet 
> been saved, which is incorrect because Hive has a dependency on Tez.
> This is important when configs change during a major stack upgrade, e.g., HDP 
> 2.4 -> 2.5. What happens today is,
> * Install packages generates /etc/tez/2.5.0.0-1/0 and copies the configs from 
> /etc/tez/2.4.0.0-1/0/ to the new folder
> * If configs change during RU, then Hive is restarted and the classpath means 
> that it will pick up the older tez configs from the new /etc/tez/2.5.0.0-1/0 
> folder
> This problem exists for all of these components:
> HiveServer: depends on Tez and MapReduce clients
> ATS: depends on Tez and Spark clients
> Oozie: depends on Tez, Spark, and MapReduce clients
> This problem only exists when configs change (so crossing major stack 
> version) and during RU (because it is allowed to change configs during the 
> middle of restarting services).



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

[jira] [Updated] (AMBARI-17280) RU to write out client configs that are dependencies of Hive, ATS, and Oozie during upgrades that change configs

[Alejandro Fernandez (JIRA)]

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

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

> RU to write out client configs that are dependencies of Hive, ATS, and Oozie 
> during upgrades that change configs
> 
>
> Key: AMBARI-17280
> URL: https://issues.apache.org/jira/browse/AMBARI-17280
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.2.0
>Reporter: Ana Gillan
>Assignee: Alejandro Fernandez
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17280.branch-2.4.patch, AMBARI-17280.trunk.patch
>
>
> During RU, HiveServer2 is restarted but the newer tez configs have not yet 
> been saved, which is incorrect because Hive has a dependency on Tez.
> This is important when configs change during a major stack upgrade, e.g., HDP 
> 2.4 -> 2.5. What happens today is,
> * Install packages generates /etc/tez/2.5.0.0-1/0 and copies the configs from 
> /etc/tez/2.4.0.0-1/0/ to the new folder
> * If configs change during RU, then Hive is restarted and the classpath means 
> that it will pick up the older tez configs from the new /etc/tez/2.5.0.0-1/0 
> folder
> This problem exists for all of these components:
> HiveServer: depends on Tez and MapReduce clients
> ATS: depends on Tez and Spark clients
> Oozie: depends on Tez, Spark, and MapReduce clients
> This problem only exists when configs change (so crossing major stack 
> version) and during RU (because it is allowed to change configs during the 
> middle of restarting services).



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

[jira] [Updated] (AMBARI-17280) RU to write out client configs that are dependencies of Hive, ATS, and Oozie during upgrades that change configs

[Alejandro Fernandez (JIRA)]

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

Alejandro Fernandez updated AMBARI-17280:
-
Attachment: (was: AMBARI-17280.branch-2.4.patch)

> RU to write out client configs that are dependencies of Hive, ATS, and Oozie 
> during upgrades that change configs
> 
>
> Key: AMBARI-17280
> URL: https://issues.apache.org/jira/browse/AMBARI-17280
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.2.0
>Reporter: Ana Gillan
>Assignee: Alejandro Fernandez
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17280.branch-2.4.patch, AMBARI-17280.trunk.patch
>
>
> During RU, HiveServer2 is restarted but the newer tez configs have not yet 
> been saved, which is incorrect because Hive has a dependency on Tez.
> This is important when configs change during a major stack upgrade, e.g., HDP 
> 2.4 -> 2.5. What happens today is,
> * Install packages generates /etc/tez/2.5.0.0-1/0 and copies the configs from 
> /etc/tez/2.4.0.0-1/0/ to the new folder
> * If configs change during RU, then Hive is restarted and the classpath means 
> that it will pick up the older tez configs from the new /etc/tez/2.5.0.0-1/0 
> folder
> This problem exists for all of these components:
> HiveServer: depends on Tez and MapReduce clients
> ATS: depends on Tez and Spark clients
> Oozie: depends on Tez, Spark, and MapReduce clients
> This problem only exists when configs change (so crossing major stack 
> version) and during RU (because it is allowed to change configs during the 
> middle of restarting services).



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

[jira] [Commented] (AMBARI-17312) Open Advanced logsearch-admin-json upon install

[Hudson (JIRA)]

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

Hudson commented on AMBARI-17312:
-

SUCCESS: Integrated in Ambari-trunk-Commit #5125 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5125/])
AMBARI-17312. Open Advanced logsearch-admin-json upon install (Miklos 
(oleewere: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=5e243959be3f8e221517dbccd2c6f986bbed9a70])
* ambari-web/app/models/stack_service.js
* ambari-web/app/data/HDP2/site_properties.js


> Open Advanced logsearch-admin-json upon install
> ---
>
> Key: AMBARI-17312
> URL: https://issues.apache.org/jira/browse/AMBARI-17312
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-logsearch
>Affects Versions: 2.4.0
>Reporter: Miklos Gergely
>Assignee: Miklos Gergely
>Priority: Minor
> Fix For: 2.4.0
>
> Attachments: AMBARI-17312.patch
>
>
> During the installation of the Log Search service via Ambari the user has to 
> specify the logsearch admin password. For convenience the 'Advanced 
> logsearch-admin-json' properties panel should be open by default.



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

[jira] [Commented] (AMBARI-17292) Operations during upgrade are permitted by all roles

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-17292:


{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12812195/AMBARI-17292.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/7453//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/7453//console

This message is automatically generated.

> Operations during upgrade are permitted by all roles
> 
>
> Key: AMBARI-17292
> URL: https://issues.apache.org/jira/browse/AMBARI-17292
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.4.0
>
> Attachments: AMBARI-17292.patch
>
>
> ambari-server --hash  
> 9a2943ba77371f1c20b4f3da900abb7c2e89d22b  
> Build# ambari-server-2.4.0.0-591.x86_64
> **Steps**
>   1. Create user with different roles like Cluster user, Service 
> Administrator etc.
>   2. Login as Ambari admin user and start Express Upgrade (register version, 
> install packages and start EU)
>   3. Pause the Upgrade at any step that requires manual intervention (like 
> stop YARN queue or backup DB or even at Finalize step)
>   4. Logout and login as cluster user
> **Result**:  
> The logged in user has complete access to Upgrade Wizard and can resume
> upgrade  
> Also do actions like Downgrade, 'Ignore and Proceed', 'Retry'
> The same is true for other roles like service administrator too, both during
> upgrade and downgrade
> **Expected Result:** Only Ambari Admin and Cluster Admin should be permitted 
> to perform actions during cluster upgrade
> Screenshots attached for reference while logged in as cluster user role
> (cluser)
> Another observation: While upgrade is in progress, login in a different
> session as cluster user - the cluster user can view the upgrade wizard in
> exact same way as admin



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

[jira] [Updated] (AMBARI-17326) Mark the role "(from group)" if there is no specific user level role set.

[Richard Zang (JIRA)]

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

Richard Zang updated AMBARI-17326:
--
Resolution: Fixed
Status: Resolved  (was: Patch Available)

Committed to trunk and 2.4 50d794c7dff38a3613ca61bd8f112e6cef50ef1b

> Mark the role "(from group)" if there is no specific user level role set.
> -
>
> Key: AMBARI-17326
> URL: https://issues.apache.org/jira/browse/AMBARI-17326
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-admin
>Affects Versions: 2.4.0
>Reporter: Richard Zang
>Assignee: Richard Zang
> Fix For: 2.4.0
>
> Attachments: AMBARI-17326.patch
>
>
> For user role listing view, we will mark the role "(from group)" if there is 
> no specific user level role set.



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

[jira] [Resolved] (AMBARI-17074) Expose Spark daemon memory in Spark2

[Srimanth Gunturi (JIRA)]

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

Srimanth Gunturi resolved AMBARI-17074.
---
Resolution: Fixed

Committed to trunk and branch-2.4

> Expose Spark daemon memory in Spark2
> 
>
> Key: AMBARI-17074
> URL: https://issues.apache.org/jira/browse/AMBARI-17074
> Project: Ambari
>  Issue Type: Improvement
>Reporter: Weiqing Yang
>Assignee: Weiqing Yang
> Fix For: trunk, 2.4.0
>
> Attachments: AMBARI-17074.v1.patch, AMBARI-17074_v2.patch, 
> AMBARI-17074_v3.patch
>
>
> Expose Spark daemon memory in Spark2, so that the user can modify its size on 
> ambari web UI easily.



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

[jira] [Commented] (AMBARI-17074) Expose Spark daemon memory in Spark2

[Weiqing Yang (JIRA)]

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

Weiqing Yang commented on AMBARI-17074:
---

[~srimanth.gunturi] The patch has been updated based on the review comments. 
Could you help to review it again? Thanks.


> Expose Spark daemon memory in Spark2
> 
>
> Key: AMBARI-17074
> URL: https://issues.apache.org/jira/browse/AMBARI-17074
> Project: Ambari
>  Issue Type: Improvement
>Reporter: Weiqing Yang
>Assignee: Weiqing Yang
> Fix For: trunk, 2.4.0
>
> Attachments: AMBARI-17074.v1.patch, AMBARI-17074_v2.patch, 
> AMBARI-17074_v3.patch
>
>
> Expose Spark daemon memory in Spark2, so that the user can modify its size on 
> ambari web UI easily.



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

[jira] [Updated] (AMBARI-17178) Tez View: Load public host names

[Sreenath Somarajapuram (JIRA)]

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

Sreenath Somarajapuram updated AMBARI-17178:

Status: Open  (was: Patch Available)

> Tez View: Load public host names
> 
>
> Key: AMBARI-17178
> URL: https://issues.apache.org/jira/browse/AMBARI-17178
> Project: Ambari
>  Issue Type: Bug
>Reporter: Sreenath Somarajapuram
>Assignee: Sreenath Somarajapuram
> Attachments: AMBARI-17178.1.patch
>
>
> Load public_host_name, parse and set the cnames configuration.



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

[jira] [Updated] (AMBARI-17331) Determine Tez for Hive2 config 'tez.am.resource.memory.mb' based on cluster capacity.

[Swapan Shridhar (JIRA)]

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

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

> Determine Tez for Hive2 config 'tez.am.resource.memory.mb' based on cluster 
> capacity.
> -
>
> Key: AMBARI-17331
> URL: https://issues.apache.org/jira/browse/AMBARI-17331
> Project: Ambari
>  Issue Type: Bug
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Attachments: AMBARI-17331.patch
>
>
> The current computations done for tez ends up with a large AM size.
> For LLAP, we'd like stack-advisor to change these computations.
> - Total Cluster Memory <=4GB - Tez AM size = 256MB and then normalized based 
> on YARN minimum container size.
> - Total Cluster Memory >4GB && <= 72GB - Tez AM size = 512MB and then 
> normalized based on YARN minimum container size.
> - Total Cluster Memory >72GB - Tez AM size = 1536MB and then normalized based 
> on YARN minimum container size.



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

[jira] [Updated] (AMBARI-17331) Determine Tez for Hive2 config 'tez.am.resource.memory.mb' based on cluster capacity.

[Swapan Shridhar (JIRA)]

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

Swapan Shridhar updated AMBARI-17331:
-
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Determine Tez for Hive2 config 'tez.am.resource.memory.mb' based on cluster 
> capacity.
> -
>
> Key: AMBARI-17331
> URL: https://issues.apache.org/jira/browse/AMBARI-17331
> Project: Ambari
>  Issue Type: Bug
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Attachments: AMBARI-17331.patch
>
>
> The current computations done for tez ends up with a large AM size.
> For LLAP, we'd like stack-advisor to change these computations.
> - Total Cluster Memory <=4GB - Tez AM size = 256MB and then normalized based 
> on YARN minimum container size.
> - Total Cluster Memory >4GB && <= 72GB - Tez AM size = 512MB and then 
> normalized based on YARN minimum container size.
> - Total Cluster Memory >72GB - Tez AM size = 1536MB and then normalized based 
> on YARN minimum container size.



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

[jira] [Updated] (AMBARI-17331) Determine Tez for Hive2 config 'tez.am.resource.memory.mb' based on cluster capacity.

[Swapan Shridhar (JIRA)]

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

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

> Determine Tez for Hive2 config 'tez.am.resource.memory.mb' based on cluster 
> capacity.
> -
>
> Key: AMBARI-17331
> URL: https://issues.apache.org/jira/browse/AMBARI-17331
> Project: Ambari
>  Issue Type: Bug
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Attachments: AMBARI-17331.patch
>
>
> The current computations done for tez ends up with a large AM size.
> For LLAP, we'd like stack-advisor to change these computations.
> - Total Cluster Memory <=4GB - Tez AM size = 256MB and then normalized based 
> on YARN minimum container size.
> - Total Cluster Memory >4GB && <= 72GB - Tez AM size = 512MB and then 
> normalized based on YARN minimum container size.
> - Total Cluster Memory >72GB - Tez AM size = 1536MB and then normalized based 
> on YARN minimum container size.



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

[jira] [Updated] (AMBARI-17331) Determine Tez for Hive2 config 'tez.am.resource.memory.mb' based on cluster capacity.

[Swapan Shridhar (JIRA)]

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

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

> Determine Tez for Hive2 config 'tez.am.resource.memory.mb' based on cluster 
> capacity.
> -
>
> Key: AMBARI-17331
> URL: https://issues.apache.org/jira/browse/AMBARI-17331
> Project: Ambari
>  Issue Type: Bug
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>
> The current computations done for tez ends up with a large AM size.
> For LLAP, we'd like stack-advisor to change these computations.
> - Total Cluster Memory <=4GB - Tez AM size = 256MB and then normalized based 
> on YARN minimum container size.
> - Total Cluster Memory >4GB && <= 72GB - Tez AM size = 512MB and then 
> normalized based on YARN minimum container size.
> - Total Cluster Memory >72GB - Tez AM size = 1536MB and then normalized based 
> on YARN minimum container size.



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

[jira] [Commented] (AMBARI-17331) Determine Tez for Hive2 config 'tez.am.resource.memory.mb' based on cluster capacity.

[Swapan Shridhar (JIRA)]

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

Swapan Shridhar commented on AMBARI-17331:
--

Commits :

trunk:

{code}
commit ff0f5c008a190360c998ee2cca147dd6d0d51063
Author: Swapan Shridhar 
Date:   Tue Jun 21 12:58:24 2016 -0700

AMBARI-17331. Determine Tez for Hive2 config 'tez.am.resource.memory.mb' 
based on cluster capacity.
{code}


branch-2.4:

{code}
commit dad2cf34bba5d653b7e4f800f586c1e541b68e0a
Author: Swapan Shridhar 
Date:   Tue Jun 21 13:00:16 2016 -0700

AMBARI-17331. Determine Tez for Hive2 config 'tez.am.resource.memory.mb' 
based on cluster capacity.
{code}

> Determine Tez for Hive2 config 'tez.am.resource.memory.mb' based on cluster 
> capacity.
> -
>
> Key: AMBARI-17331
> URL: https://issues.apache.org/jira/browse/AMBARI-17331
> Project: Ambari
>  Issue Type: Bug
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>
> The current computations done for tez ends up with a large AM size.
> For LLAP, we'd like stack-advisor to change these computations.
> - Total Cluster Memory <=4GB - Tez AM size = 256MB and then normalized based 
> on YARN minimum container size.
> - Total Cluster Memory >4GB && <= 72GB - Tez AM size = 512MB and then 
> normalized based on YARN minimum container size.
> - Total Cluster Memory >72GB - Tez AM size = 1536MB and then normalized based 
> on YARN minimum container size.



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

[jira] [Updated] (AMBARI-17331) Determine Tez for Hive2 config 'tez.am.resource.memory.mb' based on cluster capacity.

[Swapan Shridhar (JIRA)]

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

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

> Determine Tez for Hive2 config 'tez.am.resource.memory.mb' based on cluster 
> capacity.
> -
>
> Key: AMBARI-17331
> URL: https://issues.apache.org/jira/browse/AMBARI-17331
> Project: Ambari
>  Issue Type: Bug
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>
> The current computations done for tez ends up with a large AM size.
> For LLAP, we'd like stack-advisor to change these computations.
> - Total Cluster Memory <=4GB - Tez AM size = 256MB and then normalized based 
> on YARN minimum container size.
> - Total Cluster Memory >4GB && <= 72GB - Tez AM size = 512MB and then 
> normalized based on YARN minimum container size.
> - Total Cluster Memory >72GB - Tez AM size = 1536MB and then normalized based 
> on YARN minimum container size.



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

[jira] [Updated] (AMBARI-17280) RU to write out client configs that are dependencies of Hive, ATS, and Oozie during upgrades that change configs

[Alejandro Fernandez (JIRA)]

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

Alejandro Fernandez updated AMBARI-17280:
-
Attachment: AMBARI-17280.branch-2.4.patch
AMBARI-17280.trunk.patch

> RU to write out client configs that are dependencies of Hive, ATS, and Oozie 
> during upgrades that change configs
> 
>
> Key: AMBARI-17280
> URL: https://issues.apache.org/jira/browse/AMBARI-17280
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.2.0
>Reporter: Ana Gillan
>Assignee: Alejandro Fernandez
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17280.branch-2.4.patch, AMBARI-17280.trunk.patch
>
>
> During RU, HiveServer2 is restarted but the newer tez configs have not yet 
> been saved, which is incorrect because Hive has a dependency on Tez.
> This is important when configs change during a major stack upgrade, e.g., HDP 
> 2.4 -> 2.5. What happens today is,
> * Install packages generates /etc/tez/2.5.0.0-1/0 and copies the configs from 
> /etc/tez/2.4.0.0-1/0/ to the new folder
> * If configs change during RU, then Hive is restarted and the classpath means 
> that it will pick up the older tez configs from the new /etc/tez/2.5.0.0-1/0 
> folder
> This problem exists for all of these components:
> HiveServer: depends on Tez and MapReduce clients
> ATS: depends on Tez and Spark clients
> Oozie: depends on Tez, Spark, and MapReduce clients
> This problem only exists when configs change (so crossing major stack 
> version) and during RU (because it is allowed to change configs during the 
> middle of restarting services).



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

[jira] [Updated] (AMBARI-17280) RU to write out client configs that are dependencies of Hive, ATS, and Oozie during upgrades that change configs

[Alejandro Fernandez (JIRA)]

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

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

> RU to write out client configs that are dependencies of Hive, ATS, and Oozie 
> during upgrades that change configs
> 
>
> Key: AMBARI-17280
> URL: https://issues.apache.org/jira/browse/AMBARI-17280
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.2.0
>Reporter: Ana Gillan
>Assignee: Alejandro Fernandez
>Priority: Critical
> Fix For: 2.4.0
>
>
> During RU, HiveServer2 is restarted but the newer tez configs have not yet 
> been saved, which is incorrect because Hive has a dependency on Tez.
> This is important when configs change during a major stack upgrade, e.g., HDP 
> 2.4 -> 2.5. What happens today is,
> * Install packages generates /etc/tez/2.5.0.0-1/0 and copies the configs from 
> /etc/tez/2.4.0.0-1/0/ to the new folder
> * If configs change during RU, then Hive is restarted and the classpath means 
> that it will pick up the older tez configs from the new /etc/tez/2.5.0.0-1/0 
> folder
> This problem exists for all of these components:
> HiveServer: depends on Tez and MapReduce clients
> ATS: depends on Tez and Spark clients
> Oozie: depends on Tez, Spark, and MapReduce clients
> This problem only exists when configs change (so crossing major stack 
> version) and during RU (because it is allowed to change configs during the 
> middle of restarting services).



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

[jira] [Updated] (AMBARI-17280) RU to write out client configs that are dependencies of Hive, ATS, and Oozie during upgrades that change configs

[Alejandro Fernandez (JIRA)]

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

Alejandro Fernandez updated AMBARI-17280:
-
Attachment: (was: AMBARI-17280.branch-2.4.patch)

> RU to write out client configs that are dependencies of Hive, ATS, and Oozie 
> during upgrades that change configs
> 
>
> Key: AMBARI-17280
> URL: https://issues.apache.org/jira/browse/AMBARI-17280
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.2.0
>Reporter: Ana Gillan
>Assignee: Alejandro Fernandez
>Priority: Critical
> Fix For: 2.4.0
>
>
> During RU, HiveServer2 is restarted but the newer tez configs have not yet 
> been saved, which is incorrect because Hive has a dependency on Tez.
> This is important when configs change during a major stack upgrade, e.g., HDP 
> 2.4 -> 2.5. What happens today is,
> * Install packages generates /etc/tez/2.5.0.0-1/0 and copies the configs from 
> /etc/tez/2.4.0.0-1/0/ to the new folder
> * If configs change during RU, then Hive is restarted and the classpath means 
> that it will pick up the older tez configs from the new /etc/tez/2.5.0.0-1/0 
> folder
> This problem exists for all of these components:
> HiveServer: depends on Tez and MapReduce clients
> ATS: depends on Tez and Spark clients
> Oozie: depends on Tez, Spark, and MapReduce clients
> This problem only exists when configs change (so crossing major stack 
> version) and during RU (because it is allowed to change configs during the 
> middle of restarting services).



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

[jira] [Updated] (AMBARI-17280) RU to write out client configs that are dependencies of Hive, ATS, and Oozie during upgrades that change configs

[Alejandro Fernandez (JIRA)]

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

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

> RU to write out client configs that are dependencies of Hive, ATS, and Oozie 
> during upgrades that change configs
> 
>
> Key: AMBARI-17280
> URL: https://issues.apache.org/jira/browse/AMBARI-17280
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.2.0
>Reporter: Ana Gillan
>Assignee: Alejandro Fernandez
>Priority: Critical
> Fix For: 2.4.0
>
>
> During RU, HiveServer2 is restarted but the newer tez configs have not yet 
> been saved, which is incorrect because Hive has a dependency on Tez.
> This is important when configs change during a major stack upgrade, e.g., HDP 
> 2.4 -> 2.5. What happens today is,
> * Install packages generates /etc/tez/2.5.0.0-1/0 and copies the configs from 
> /etc/tez/2.4.0.0-1/0/ to the new folder
> * If configs change during RU, then Hive is restarted and the classpath means 
> that it will pick up the older tez configs from the new /etc/tez/2.5.0.0-1/0 
> folder
> This problem exists for all of these components:
> HiveServer: depends on Tez and MapReduce clients
> ATS: depends on Tez and Spark clients
> Oozie: depends on Tez, Spark, and MapReduce clients
> This problem only exists when configs change (so crossing major stack 
> version) and during RU (because it is allowed to change configs during the 
> middle of restarting services).



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

[jira] [Created] (AMBARI-17352) A command line script to run pre-install checks and summarize the results

[Di Li (JIRA)]

Di Li created AMBARI-17352:
--

 Summary: A command line script to run pre-install checks and 
summarize the results
 Key: AMBARI-17352
 URL: https://issues.apache.org/jira/browse/AMBARI-17352
 Project: Ambari
  Issue Type: New Feature
  Components: contrib
Affects Versions: trunk
Reporter: Di Li
 Fix For: trunk


Ambari web UI runs host checks during host (ambari agent) registration. For 
users that run blueprint install, it would be nice if Ambari ships with a 
command line script that runs host checks and summarize the results. 



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

[jira] [Updated] (AMBARI-17317) tez.tez-ui.history-url.base did not get updated after ambari upgrade

[DIPAYAN BHOWMICK (JIRA)]

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

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

Committed to branch-2.4, trunk.

> tez.tez-ui.history-url.base did not get updated after ambari upgrade
> 
>
> Key: AMBARI-17317
> URL: https://issues.apache.org/jira/browse/AMBARI-17317
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.2.0
>Reporter: DIPAYAN BHOWMICK
>Assignee: DIPAYAN BHOWMICK
> Fix For: 2.4.0
>
> Attachments: AMBARI-17317.branch-2.4.patch
>
>
> After upgrading from Ambari 2.2.1.0 to ambari 2.2.2.0 my 
> tez.tez-ui.history-url.base still pointed to the old version of the tez view 
> URL.
> This caused an issue when user clicked on the AM link for a running tez app 
> and it took them to the wrong url.



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

[jira] [Updated] (AMBARI-17344) Clear /security.json if kerberos is disabled

[JIRA]

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

Olivér Szabó updated AMBARI-17344:
--
Status: Patch Available  (was: Open)

> Clear /security.json if kerberos is disabled
> 
>
> Key: AMBARI-17344
> URL: https://issues.apache.org/jira/browse/AMBARI-17344
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-logsearch, ambari-server
>Affects Versions: 2.4.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
> Fix For: 2.4.0
>
> Attachments: AMBARI-17344.patch
>
>




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

[jira] [Commented] (AMBARI-17117) Fix misnamed Zookeeper connect strings in Log Search

[Hudson (JIRA)]

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

Hudson commented on AMBARI-17117:
-

SUCCESS: Integrated in Ambari-trunk-Commit #5124 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5124/])
AMBARI-17117. Fix misnamed Zookeeper connect strings in Log Search (oleewere: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=a2c23b213380cf7e8ccbf1db130a0925cc159516])
* 
ambari-logsearch/ambari-logsearch-solr-client/src/main/java/org/apache/ambari/logsearch/solr/commands/GetSolrHostsCommand.java
* 
ambari-logsearch/ambari-logsearch-solr-client/src/test/java/org/apache/ambari/logsearch/solr/AmbariSolrCloudClientTest.java
* 
ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/package/templates/logfeeder.properties.j2
* 
ambari-logsearch/ambari-logsearch-solr-client/src/main/java/org/apache/ambari/logsearch/solr/AmbariSolrCloudClient.java
* ambari-logsearch/ambari-logsearch-logfeeder/src/main/resources/config.json.j2
* ambari-server/src/test/python/stacks/2.4/configs/default.json
* 
ambari-logsearch/ambari-logsearch-solr-client/src/main/java/org/apache/ambari/logsearch/solr/AmbariSolrCloudClientBuilder.java
* 
ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/package/templates/logsearch.properties.j2
* 
ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/logconfig/FetchConfigFromSolr.java
* 
ambari-logsearch/ambari-logsearch-solr-client/src/main/java/org/apache/ambari/logsearch/solr/AmbariSolrCloudCLI.java
* 
ambari-logsearch/ambari-logsearch-logfeeder/src/main/resources/output.config.json.j2
* 
ambari-logsearch/ambari-logsearch-portal/src/main/java/org/apache/ambari/logsearch/dao/UserConfigSolrDao.java
* 
ambari-logsearch/ambari-logsearch-portal/src/main/resources/logsearch.properties.j2
* 
ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/output/OutputSolr.java
* 
ambari-logsearch/ambari-logsearch-portal/src/main/java/org/apache/ambari/logsearch/dao/SolrDaoBase.java
* 
ambari-logsearch/ambari-logsearch-logfeeder/src/main/resources/logfeeder.properties
* 
ambari-logsearch/ambari-logsearch-portal/src/main/java/org/apache/ambari/logsearch/solr/metrics/SolrMetricsLoader.java
* 
ambari-logsearch/ambari-logsearch-logfeeder/src/test/java/org/apache/ambari/logfeeder/output/OutputSolrTest.java
* 
ambari-logsearch/ambari-logsearch-portal/src/main/java/org/apache/ambari/logsearch/dao/ServiceLogsSolrDao.java
* 
ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/package/templates/output.config.json.j2
* 
ambari-logsearch/ambari-logsearch-portal/src/main/java/org/apache/ambari/logsearch/dao/AuditSolrDao.java
* 
ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/util/SolrUtil.java


> Fix misnamed Zookeeper connect strings in Log Search
> 
>
> Key: AMBARI-17117
> URL: https://issues.apache.org/jira/browse/AMBARI-17117
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-logsearch
>Affects Versions: 2.4.0
>Reporter: Miklos Gergely
>Assignee: Miklos Gergely
> Fix For: 2.4.0
>
> Attachments: AMBARI-17117.patch
>
>
> Variables/properties holding zookeeper connect strings are misnamed as 
> zk_host, or zk_hosts, which may be misleading. Variable / property names 
> fixed.



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

[jira] [Commented] (AMBARI-17322) No alerts on Select Version page when selected stack 2.2 with JDK 1.8

[Hudson (JIRA)]

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

Hudson commented on AMBARI-17322:
-

SUCCESS: Integrated in Ambari-trunk-Commit #5124 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5124/])
AMBARI-17322 No alerts on Select Version page when selected stack 2.2 (zhewang: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=78037086ee492e067380aba5113034f7312bdb5d])
* ambari-web/app/utils/ajax/ajax.js
* ambari-web/app/models/stack.js


> No alerts on Select Version page when selected stack 2.2 with JDK 1.8
> -
>
> Key: AMBARI-17322
> URL: https://issues.apache.org/jira/browse/AMBARI-17322
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Zhe (Joe) Wang
>Assignee: Zhe (Joe) Wang
> Fix For: 2.4.0
>
> Attachments: AMBARI-17322.v0.patch
>
>
> 1) Install Ambari with Oracle JDK 1.8
> 2) Go to Select Version page
> 3) Select HDP 2.2
> Expected: Alert concering jdk mismatch
> Actually: there is no alert



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

[jira] [Commented] (AMBARI-17323) Follow up NiFi log changes in the LogFeeder config

[Hudson (JIRA)]

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

Hudson commented on AMBARI-17323:
-

SUCCESS: Integrated in Ambari-trunk-Commit #5124 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5124/])
AMBARI-17323. Follow up NiFi log changes in the LogFeeder config (Miklos 
(oleewere: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=4f0c4a9ea865fb75918023bed1c497ed054753d2])
* 
ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/package/scripts/params.py
* 
ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/package/templates/input.config-nifi.json.j2
* 
ambari-logsearch/ambari-logsearch-portal/src/main/resources/HadoopServiceConfig.json


> Follow up NiFi log changes in the LogFeeder config
> --
>
> Key: AMBARI-17323
> URL: https://issues.apache.org/jira/browse/AMBARI-17323
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-logsearch
>Affects Versions: 2.4.0
>Reporter: Miklos Gergely
>Assignee: Miklos Gergely
> Fix For: 2.4.0
>
> Attachments: AMBARI-17323.patch
>
>
> The NiFi service log dir properties were recently changes. The LogFeeder 
> config needs to follow up this change to access the NiFi logs



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

[jira] [Updated] (AMBARI-17348) Allow https protocol for Log Search

[Alejandro Fernandez (JIRA)]

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

Alejandro Fernandez updated AMBARI-17348:
-
Summary: Allow https protocol for Log Search  (was: Allow https prtotocol 
for Log Search)

> Allow https protocol for Log Search
> ---
>
> Key: AMBARI-17348
> URL: https://issues.apache.org/jira/browse/AMBARI-17348
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-logsearch
>Affects Versions: 2.4.0
>Reporter: Miklos Gergely
>Assignee: Miklos Gergely
> Fix For: 2.4.0
>
> Attachments: AMBARI-17348.patch
>
>
> Add a property to choose whether or not the Log Search UI should run using 
> https.



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

[jira] [Updated] (AMBARI-17321) Zeppelin: Kerberos configurations and latest interpreter config missing

[DIPAYAN BHOWMICK (JIRA)]

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

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

Committed to branch-2.4, trunk.

> Zeppelin: Kerberos configurations and latest interpreter config missing
> ---
>
> Key: AMBARI-17321
> URL: https://issues.apache.org/jira/browse/AMBARI-17321
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Renjith Kamath
>Assignee: Renjith Kamath
> Fix For: 2.4.0
>
> Attachments: AMBARI-17321_trunk+branch-2.4_v1.patch
>
>




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

[jira] [Updated] (AMBARI-17350) If two users are created differing in case then no users are shown due to error

[Nahappan Somasundaram (JIRA)]

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

Nahappan Somasundaram updated AMBARI-17350:
---
Attachment: Screen Shot 2016-06-11 at 9.17.12 PM.png

> If two users are created differing in case then no users are shown due to 
> error
> ---
>
> Key: AMBARI-17350
> URL: https://issues.apache.org/jira/browse/AMBARI-17350
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: Screen Shot 2016-06-11 at 9.17.12 PM.png
>
>
> When usernames that differ only by case are created, no users are show in the 
> when clicking the Users link in Ambari Management page due to the following 
> error.
> The fix is to block creating usernames that differ only by case.
> {code}
> 12 Jun 2016 03:59:28,569  WARN [ambari-client-thread-559] ServletHandler:628 
> - /api/v1/users/
> javax.persistence.NonUniqueResultException: More than one result was returned 
> from Query.getSingleResult()
> at 
> org.eclipse.persistence.internal.jpa.QueryImpl.throwNonUniqueResultException(QueryImpl.java:980)
> at 
> org.eclipse.persistence.internal.jpa.QueryImpl.getSingleResult(QueryImpl.java:529)
> at 
> org.eclipse.persistence.internal.jpa.EJBQueryImpl.getSingleResult(EJBQueryImpl.java:400)
> at 
> org.apache.ambari.server.orm.dao.UserDAO.findUserByName(UserDAO.java:69)
> at 
> org.apache.ambari.server.orm.AmbariLocalSessionInterceptor.invoke(AmbariLocalSessionInterceptor.java:53)
> at 
> org.apache.ambari.server.controller.internal.ActiveWidgetLayoutResourceProvider.getResources(ActiveWidgetLayoutResourceProvider.java:161)
> at 
> org.apache.ambari.server.controller.internal.ClusterControllerImpl$ExtendedResourceProviderWrapper.queryForResources(ClusterControllerImpl.java:966)
> at 
> org.apache.ambari.server.controller.internal.ClusterControllerImpl.getResources(ClusterControllerImpl.java:141)
> at 
> org.apache.ambari.server.api.query.QueryImpl.doQuery(QueryImpl.java:512)
> at 
> org.apache.ambari.server.api.query.QueryImpl.queryForSubResources(QueryImpl.java:464)
> ...
> {code}
> {code}
> select * from users ;
> ***(press return to proceed or enter x and return to 
> cancel)
>  user_id | principal_id | ldap_user | user_name | user_type |
> create_time |  user_password  
>  | active | active
> _widget_layouts
> -+--+---+---+---++--++---
> 
>1 |1 | 0 | admin | LOCAL | 2016-06-11 
> 16:08:51.300678 | 
> 538916f8943ec225d97a9a86a2c6ec0818c1cd400e09e03b660fdaaec4af29ddbb6f2b1033b81b00
>  |  1 | [{"id"
> :"6"}]
>3 |   14 | 0 | Abcd  | LOCAL | 2016-06-12 
> 03:58:38.944| 
> ee677dc216a63092fd1e4dbb56c3661dcca0053feae5968bdf82e15cb95e9b83747f1b7d25c3badc
>  |  1 |
>4 |   15 | 0 | abcd  | LOCAL | 2016-06-12 
> 03:58:49.32 | 
> f941a9570f1b42f2f74b164e9e419fb7d63660681e3ccd9e9313f0369c6d5d03e3249fcfc1fd835e
>  |  1 |
> (3 rows)
> {code}



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

[jira] [Assigned] (AMBARI-17349) spark.driver.extraJavaOptions and spark.yarn.am.extraJavaOptions property is set to empty

[Weiqing Yang (JIRA)]

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

Weiqing Yang reassigned AMBARI-17349:
-

Assignee: Weiqing Yang

> spark.driver.extraJavaOptions and spark.yarn.am.extraJavaOptions property is 
> set to empty
> -
>
> Key: AMBARI-17349
> URL: https://issues.apache.org/jira/browse/AMBARI-17349
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.4.0
>Reporter: Yesha Vora
>Assignee: Weiqing Yang
>
> spark.driver.extraJavaOptions and spark.yarn.am.extraJavaOptions is set to 
> empty.
> Either spark.driver.extraJavaOptions / spark.yarn.am.extraJavaOptions should 
> be removed from spark-defaults.conf or it should set to a valid value.



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

[jira] [Resolved] (AMBARI-17351) spark.driver.extraJavaOptions and spark.yarn.am.extraJavaOptions property is set to empty

[Weiqing Yang (JIRA)]

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

Weiqing Yang resolved AMBARI-17351.
---
Resolution: Duplicate

This Jira is duplicated with 
AMBARI-17349. 

> spark.driver.extraJavaOptions and spark.yarn.am.extraJavaOptions property is 
> set to empty
> -
>
> Key: AMBARI-17351
> URL: https://issues.apache.org/jira/browse/AMBARI-17351
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Weiqing Yang
>Assignee: Weiqing Yang
>
> spark.driver.extraJavaOptions and spark.yarn.am.extraJavaOptions is set to 
> empty. Either spark.driver.extraJavaOptions / spark.yarn.am.extraJavaOptions 
> should be removed from spark-defaults.conf or it should set to a valid value.
> In past runs, ambari deploy was not setting spark.driver.extraJavaOptions and 
> spark.yarn.am.extraJavaOptions property.
> This issue is originally reported by [~yeshavora]



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

[jira] [Created] (AMBARI-17351) spark.driver.extraJavaOptions and spark.yarn.am.extraJavaOptions property is set to empty

[Weiqing Yang (JIRA)]

Weiqing Yang created AMBARI-17351:
-

 Summary: spark.driver.extraJavaOptions and 
spark.yarn.am.extraJavaOptions property is set to empty
 Key: AMBARI-17351
 URL: https://issues.apache.org/jira/browse/AMBARI-17351
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Reporter: Weiqing Yang
Assignee: Weiqing Yang


spark.driver.extraJavaOptions and spark.yarn.am.extraJavaOptions is set to 
empty. Either spark.driver.extraJavaOptions / spark.yarn.am.extraJavaOptions 
should be removed from spark-defaults.conf or it should set to a valid value.
In past runs, ambari deploy was not setting spark.driver.extraJavaOptions and 
spark.yarn.am.extraJavaOptions property.
This issue is originally reported by [~yeshavora]



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

[jira] [Updated] (AMBARI-17349) spark.driver.extraJavaOptions and spark.yarn.am.extraJavaOptions property is set to empty

[Yesha Vora (JIRA)]

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

Yesha Vora updated AMBARI-17349:

Description: 
spark.driver.extraJavaOptions and spark.yarn.am.extraJavaOptions is set to 
empty.

Either spark.driver.extraJavaOptions / spark.yarn.am.extraJavaOptions should be 
removed from spark-defaults.conf or it should set to a valid value.

  was:
spark.driver.extraJavaOptions is set to empty.

Either spark.driver.extraJavaOptions should be removed from spark-defaults.conf 
or it should set to a valid value.



> spark.driver.extraJavaOptions and spark.yarn.am.extraJavaOptions property is 
> set to empty
> -
>
> Key: AMBARI-17349
> URL: https://issues.apache.org/jira/browse/AMBARI-17349
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.4.0
>Reporter: Yesha Vora
>
> spark.driver.extraJavaOptions and spark.yarn.am.extraJavaOptions is set to 
> empty.
> Either spark.driver.extraJavaOptions / spark.yarn.am.extraJavaOptions should 
> be removed from spark-defaults.conf or it should set to a valid value.



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

[jira] [Updated] (AMBARI-17349) spark.driver.extraJavaOptions and spark.yarn.am.extraJavaOptions property is set to empty

[Yesha Vora (JIRA)]

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

Yesha Vora updated AMBARI-17349:

Summary: spark.driver.extraJavaOptions and spark.yarn.am.extraJavaOptions 
property is set to empty  (was: spark.driver.extraJavaOptions property is set 
to empty)

> spark.driver.extraJavaOptions and spark.yarn.am.extraJavaOptions property is 
> set to empty
> -
>
> Key: AMBARI-17349
> URL: https://issues.apache.org/jira/browse/AMBARI-17349
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.4.0
>Reporter: Yesha Vora
>
> spark.driver.extraJavaOptions is set to empty.
> Either spark.driver.extraJavaOptions should be removed from 
> spark-defaults.conf or it should set to a valid value.



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

[jira] [Created] (AMBARI-17350) If two users are created differing in case then no users are shown due to error

[Nahappan Somasundaram (JIRA)]

Nahappan Somasundaram created AMBARI-17350:
--

 Summary: If two users are created differing in case then no users 
are shown due to error
 Key: AMBARI-17350
 URL: https://issues.apache.org/jira/browse/AMBARI-17350
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: 2.4.0
Reporter: Nahappan Somasundaram
Assignee: Nahappan Somasundaram
Priority: Critical
 Fix For: 2.4.0


When usernames that differ only by case are created, no users are show in the 
when clicking the Users link in Ambari Management page due to the following 
error.

The fix is to block creating usernames that differ only by case.

{code}
12 Jun 2016 03:59:28,569  WARN [ambari-client-thread-559] ServletHandler:628 - 
/api/v1/users/
javax.persistence.NonUniqueResultException: More than one result was returned 
from Query.getSingleResult()
at 
org.eclipse.persistence.internal.jpa.QueryImpl.throwNonUniqueResultException(QueryImpl.java:980)
at 
org.eclipse.persistence.internal.jpa.QueryImpl.getSingleResult(QueryImpl.java:529)
at 
org.eclipse.persistence.internal.jpa.EJBQueryImpl.getSingleResult(EJBQueryImpl.java:400)
at 
org.apache.ambari.server.orm.dao.UserDAO.findUserByName(UserDAO.java:69)
at 
org.apache.ambari.server.orm.AmbariLocalSessionInterceptor.invoke(AmbariLocalSessionInterceptor.java:53)
at 
org.apache.ambari.server.controller.internal.ActiveWidgetLayoutResourceProvider.getResources(ActiveWidgetLayoutResourceProvider.java:161)
at 
org.apache.ambari.server.controller.internal.ClusterControllerImpl$ExtendedResourceProviderWrapper.queryForResources(ClusterControllerImpl.java:966)
at 
org.apache.ambari.server.controller.internal.ClusterControllerImpl.getResources(ClusterControllerImpl.java:141)
at 
org.apache.ambari.server.api.query.QueryImpl.doQuery(QueryImpl.java:512)
at 
org.apache.ambari.server.api.query.QueryImpl.queryForSubResources(QueryImpl.java:464)
...
{code}

{code}
select * from users ;
***(press return to proceed or enter x and return to cancel)

 user_id | principal_id | ldap_user | user_name | user_type |
create_time |  user_password
   | active | active
_widget_layouts
-+--+---+---+---++--++---

   1 |1 | 0 | admin | LOCAL | 2016-06-11 
16:08:51.300678 | 
538916f8943ec225d97a9a86a2c6ec0818c1cd400e09e03b660fdaaec4af29ddbb6f2b1033b81b00
 |  1 | [{"id"
:"6"}]
   3 |   14 | 0 | Abcd  | LOCAL | 2016-06-12 
03:58:38.944| 
ee677dc216a63092fd1e4dbb56c3661dcca0053feae5968bdf82e15cb95e9b83747f1b7d25c3badc
 |  1 |
   4 |   15 | 0 | abcd  | LOCAL | 2016-06-12 
03:58:49.32 | 
f941a9570f1b42f2f74b164e9e419fb7d63660681e3ccd9e9313f0369c6d5d03e3249fcfc1fd835e
 |  1 |
(3 rows)
{code}



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

[jira] [Created] (AMBARI-17349) spark.driver.extraJavaOptions property is set to empty

[Yesha Vora (JIRA)]

Yesha Vora created AMBARI-17349:
---

 Summary: spark.driver.extraJavaOptions property is set to empty
 Key: AMBARI-17349
 URL: https://issues.apache.org/jira/browse/AMBARI-17349
 Project: Ambari
  Issue Type: Bug
Reporter: Yesha Vora


spark.driver.extraJavaOptions is set to empty.

Either spark.driver.extraJavaOptions should be removed from spark-defaults.conf 
or it should set to a valid value.




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

[jira] [Updated] (AMBARI-17349) spark.driver.extraJavaOptions property is set to empty

[Yesha Vora (JIRA)]

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

Yesha Vora updated AMBARI-17349:

Affects Version/s: 2.4.0

> spark.driver.extraJavaOptions property is set to empty
> --
>
> Key: AMBARI-17349
> URL: https://issues.apache.org/jira/browse/AMBARI-17349
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.4.0
>Reporter: Yesha Vora
>
> spark.driver.extraJavaOptions is set to empty.
> Either spark.driver.extraJavaOptions should be removed from 
> spark-defaults.conf or it should set to a valid value.



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

[jira] [Updated] (AMBARI-17074) Expose Spark daemon memory in Spark2

[Weiqing Yang (JIRA)]

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

Weiqing Yang updated AMBARI-17074:
--
Attachment: AMBARI-17074_v3.patch

> Expose Spark daemon memory in Spark2
> 
>
> Key: AMBARI-17074
> URL: https://issues.apache.org/jira/browse/AMBARI-17074
> Project: Ambari
>  Issue Type: Improvement
>Reporter: Weiqing Yang
>Assignee: Weiqing Yang
> Fix For: trunk, 2.4.0
>
> Attachments: AMBARI-17074.v1.patch, AMBARI-17074_v2.patch, 
> AMBARI-17074_v3.patch
>
>
> Expose Spark daemon memory in Spark2, so that the user can modify its size on 
> ambari web UI easily.



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

[jira] [Updated] (AMBARI-17348) Allow https prtotocol for Log Search

[Miklos Gergely (JIRA)]

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

Miklos Gergely updated AMBARI-17348:

Status: Patch Available  (was: Open)

> Allow https prtotocol for Log Search
> 
>
> Key: AMBARI-17348
> URL: https://issues.apache.org/jira/browse/AMBARI-17348
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-logsearch
>Affects Versions: 2.4.0
>Reporter: Miklos Gergely
>Assignee: Miklos Gergely
> Fix For: 2.4.0
>
> Attachments: AMBARI-17348.patch
>
>
> Add a property to choose whether or not the Log Search UI should run using 
> https.



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

[jira] [Updated] (AMBARI-17348) Allow https prtotocol for Log Search

[Miklos Gergely (JIRA)]

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

Miklos Gergely updated AMBARI-17348:

Attachment: AMBARI-17348.patch

> Allow https prtotocol for Log Search
> 
>
> Key: AMBARI-17348
> URL: https://issues.apache.org/jira/browse/AMBARI-17348
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-logsearch
>Affects Versions: 2.4.0
>Reporter: Miklos Gergely
>Assignee: Miklos Gergely
> Fix For: 2.4.0
>
> Attachments: AMBARI-17348.patch
>
>
> Add a property to choose whether or not the Log Search UI should run using 
> https.



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

[jira] [Resolved] (AMBARI-17312) Open Advanced logsearch-admin-json upon install

[JIRA]

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

Olivér Szabó resolved AMBARI-17312.
---
Resolution: Fixed

committed to trunk:
{code:java}
commit 8f76a5fb12624556d5fdf05b695db1276bc08a15
Author: Miklos Gergely 
Date:   Tue Jun 21 19:47:33 2016 +0200

AMBARI-17312. Open Advanced logsearch-admin-json upon install (Miklos 
Gergely via oleewere)
{code}
comitted to branch-2.4:
{code:java}
commit 8f76a5fb12624556d5fdf05b695db1276bc08a15
Author: Miklos Gergely 
Date:   Tue Jun 21 19:47:33 2016 +0200

AMBARI-17312. Open Advanced logsearch-admin-json upon install (Miklos 
Gergely via oleewere)
{code}

> Open Advanced logsearch-admin-json upon install
> ---
>
> Key: AMBARI-17312
> URL: https://issues.apache.org/jira/browse/AMBARI-17312
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-logsearch
>Affects Versions: 2.4.0
>Reporter: Miklos Gergely
>Assignee: Miklos Gergely
>Priority: Minor
> Fix For: 2.4.0
>
> Attachments: AMBARI-17312.patch
>
>
> During the installation of the Log Search service via Ambari the user has to 
> specify the logsearch admin password. For convenience the 'Advanced 
> logsearch-admin-json' properties panel should be open by default.



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

[jira] [Updated] (AMBARI-17345) Hive metastore failed to start

[Vitaly Brodetskyi (JIRA)]

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

Vitaly Brodetskyi updated AMBARI-17345:
---
Priority: Blocker  (was: Critical)

> Hive metastore failed to start
> --
>
> Key: AMBARI-17345
> URL: https://issues.apache.org/jira/browse/AMBARI-17345
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-17345.patch
>
>
> STR:
> 1) Add Hive Metastore on hosts that do not have it
> 2) Restart services with stale configs
> It started fine on retrying
> {code}
> ERROR: Unable to connect to the DB. Please check DB connection 
> properties.\njava.lang.ClassNotFoundException: 
> oracle.jdbc.driver.OracleDriver\n2016-06-20 13:18:14,206 - Retrying after 10 
> seconds. Reason: Execution of '/usr/jdk64/jdk1.8.0_77/bin/java -cp 
> /usr/lib/ambari-agent/DBConnectionVerification.jar:/usr/hdp/current/hive-metastore/lib/ojdbc6.jar
>  org.apache.ambari.server.DBConnectionVerification 
> 'jdbc:oracle:thin:@//172.22.124.192:1521/XE' hiveuser [PROTECTED] 
> oracle.jdbc.driver.OracleDriver' returned 1. ERROR: Unable to connect to the 
> DB. Please check DB connection properties.\njava.lang.ClassNotFoundException:
> {code}



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

[jira] [Commented] (AMBARI-17336) UI : More than one validation for same config is not displayed on UI.

[Hudson (JIRA)]

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

Hudson commented on AMBARI-17336:
-

SUCCESS: Integrated in Ambari-trunk-Commit #5123 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5123/])
AMBARI-17336. UI : More than one validation for same config is not (hiveww: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=a6de04361600be152fda3629f27769a480f71073])
* ambari-web/app/models/configs/objects/service_config_property.js
* ambari-web/app/templates/common/modal_popups/config_recommendation_popup.hbs
* ambari-web/app/mixins/common/serverValidator.js
* ambari-web/test/mixins/common/serverValidator_test.js


> UI : More than one validation for same config is not displayed on UI.
> -
>
> Key: AMBARI-17336
> URL: https://issues.apache.org/jira/browse/AMBARI-17336
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 2.4.0
>
> Attachments: AMBARI-17336.patch
>
>
> - Screenshot :  !Screen Shot 2016-06-14 at 1.52.21 PM.png|thumbnail! 
> - For config, 'hive.llap.daemon.queue.name' has 2 validations suggested by 
> SA, but only 1 makes way on UI.



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

[jira] [Commented] (AMBARI-17337) Client installs failed on debian 7

[Hudson (JIRA)]

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

Hudson commented on AMBARI-17337:
-

SUCCESS: Integrated in Ambari-trunk-Commit #5123 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5123/])
AMBARI-17337. Client installs failed on debian 7 (aonishuk) (aonishuk: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=4f78290a627f642b41e7ee1d75984f06eca90723])
* 
ambari-common/src/main/python/resource_management/libraries/functions/packages_analyzer.py
* 
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/utils.py


> Client installs failed on debian 7
> --
>
> Key: AMBARI-17337
> URL: https://issues.apache.org/jira/browse/AMBARI-17337
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.4.0
>
> Attachments: AMBARI-17337.patch
>
>
> Type of install : UI  
> Install failures of : HBASE_CLIENT, HDFS_CLIENT, YARN_CLIENT, MR2 client,
> MAHOUT, SLIDER and other clients  
> OS : Debian7  
> Cause : Looks like a common cause :  
> Applying File['/usr/hdp/current/hadoop-client/conf/core-site.xml'](https://hor
> tonworks.jira.com/wiki/display/BUG/%27%2Fusr%2Fhdp%2Fcurrent%2Fhadoop-
> client%2Fconf%2Fcore-site.xml%27) failed, parent directory /usr/hdp/current
> /hadoop-client/conf doesn't exist
> Artifacts here :  
>  /ambari-hosts/artifacts/screenshots/com.hw.ambari.ui.tests.heavyweights.TestRe
> InstallHostComponents/testA_PrepareCluster/_18_14_49_36_Page_with_URL__https_1
> 72_22_107_798443_installer_step10__has_not_been_loaded_within_180/lastAvailabl
> eRequests.txt>
> Live cluster here :  
> 
> Checked the folder :
> 
> 
> 
> root@nat-os-d7-sbhat-ambari-hosts-6-5:~# ls -l /usr/hdp/current/
> total 12
> drwxr-x--- 4 cstm-falcon root 4096 Jun 19 07:37 falcon-client
> drwxr-x--- 3 rootroot 4096 Jun 19 07:37 hbase-client
> drwxr-xr-x 4 rootroot 4096 Jun 19 07:37 storm-client
> 



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

[jira] [Created] (AMBARI-17348) Allow https prtotocol for Log Search

[Miklos Gergely (JIRA)]

Miklos Gergely created AMBARI-17348:
---

 Summary: Allow https prtotocol for Log Search
 Key: AMBARI-17348
 URL: https://issues.apache.org/jira/browse/AMBARI-17348
 Project: Ambari
  Issue Type: Improvement
  Components: ambari-logsearch
Affects Versions: 2.4.0
Reporter: Miklos Gergely
Assignee: Miklos Gergely
 Fix For: 2.4.0


Add a property to choose whether or not the Log Search UI should run using 
https.



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

[jira] [Commented] (AMBARI-17277) Log Level filter not applied before Log Search Starts at first

[Hudson (JIRA)]

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

Hudson commented on AMBARI-17277:
-

SUCCESS: Integrated in Ambari-trunk-Commit #5123 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5123/])
AMBARI-17277. Log Level filter not applied before Log Search Starts at 
(oleewere: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=6a6bb7a87f01b125a0cba717f98e2c74af348d06])
* 
ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/util/SolrUtil.java
* 
ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/LogFeeder.java
* 
ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/output/OutputSolr.java
* 
ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/logconfig/FetchConfigFromSolr.java
* 
ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/logconfig/LogFeederConstants.java
* 
ambari-logsearch/ambari-logsearch-logfeeder/src/test/java/org/apache/ambari/logfeeder/output/OutputSolrTest.java
* 
ambari-logsearch/ambari-logsearch-logfeeder/src/main/resources/logfeeder.properties
* 
ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/package/templates/logfeeder.properties.j2


> Log Level filter not applied before Log Search Starts at first
> --
>
> Key: AMBARI-17277
> URL: https://issues.apache.org/jira/browse/AMBARI-17277
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-logsearch
>Affects Versions: 2.4.0
>Reporter: Miklos Gergely
>Assignee: Miklos Gergely
> Fix For: 2.4.0
>
> Attachments: AMBARI-17277.patch
>
>
> After Log Search is started it sends the filters to the Solr which describes 
> what log levels should be persisted. In the meantime Logfeeders start to push 
> their data, which is not filtered. The result is misleading, the user may 
> find it add that some specific level logs are loaded, others are not.



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

[jira] [Commented] (AMBARI-17200) Tez, Pig, Hive, MapReduce service checks will fail on non standard queue names

[Hudson (JIRA)]

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

Hudson commented on AMBARI-17200:
-

SUCCESS: Integrated in Ambari-trunk-Commit #5123 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5123/])
AMBARI-17200. Tez, Pig, Hive, MapReduce service checks will fail on non 
(dlysnichenko: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=5eadd6c1529c651a6d1d2a9dbac374028e8e3b1d])
* ambari-server/src/main/resources/stacks/HDP/2.0.6/services/stack_advisor.py
* 
ambari-server/src/main/resources/common-services/TEZ/0.4.0.2.1/configuration/tez-site.xml
* ambari-server/src/test/python/stacks/2.2/common/test_stack_advisor.py
* ambari-server/src/test/python/stacks/2.3/common/test_stack_advisor.py
* ambari-server/src/test/python/stacks/2.5/common/test_stack_advisor.py
* ambari-server/src/main/resources/stacks/HDP/2.1/services/stack_advisor.py
* 
ambari-server/src/main/java/org/apache/ambari/server/upgrade/AbstractUpgradeCatalog.java
* 
ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/configuration/yarn-env.xml
* 
ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/configuration-mapred/mapred-site.xml
* 
ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/configuration/webhcat-site.xml
* 
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog240.java
* 
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog240Test.java
* ambari-server/src/main/resources/stacks/HDP/2.2/services/stack_advisor.py
* ambari-server/src/test/python/stacks/2.0.6/common/test_stack_advisor.py


> Tez, Pig, Hive, MapReduce service checks will fail on non standard queue names
> --
>
> Key: AMBARI-17200
> URL: https://issues.apache.org/jira/browse/AMBARI-17200
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Dmytro Grinenko
>Assignee: Dmitry Lysnichenko
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17200.patch, AMBARI-17200.patch.1, 
> AMBARI-17200.patch.2, AMBARI-17200.patch.3
>
>
> If user will change queue names in a way when default queue will be missing - 
> Tez, Hive and Pig service checks will fail coz no default queue found



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

[jira] [Commented] (AMBARI-17338) Better xpath needed on Hosts Details Page for selecting clients with restart required

[Hudson (JIRA)]

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

Hudson commented on AMBARI-17338:
-

SUCCESS: Integrated in Ambari-trunk-Commit #5123 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5123/])
AMBARI-17338. Better xpath needed on Hosts Details Page for selecting (hiveww: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=6c2736acdd4e8aaf19fec6a87bddffa562da45ab])
* ambari-web/app/templates/main/host/summary.hbs


> Better xpath needed on Hosts Details Page for selecting clients with restart 
> required
> -
>
> Key: AMBARI-17338
> URL: https://issues.apache.org/jira/browse/AMBARI-17338
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 2.4.0
>
> Attachments: AMBARI-17338.patch
>
>
> On hosts details page, better xpath is required to select clients with 
> restart required.



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

[jira] [Updated] (AMBARI-17323) Follow up NiFi log changes in the LogFeeder config

[JIRA]

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

Olivér Szabó updated AMBARI-17323:
--
Resolution: Fixed
Status: Resolved  (was: Patch Available)

committed to trunk:
{code:java}
commit 4f0c4a9ea865fb75918023bed1c497ed054753d2
Author: Miklos Gergely 
Date:   Tue Jun 21 19:34:57 2016 +0200

AMBARI-17323. Follow up NiFi log changes in the LogFeeder config (Miklos 
Gergely via oleewere)
{code}
comitted to branch-2.4:
{code:java}
commit 66b9e256121264734959c3faadc32d1b56fd48b3
Author: Miklos Gergely 
Date:   Tue Jun 21 19:34:57 2016 +0200

AMBARI-17323. Follow up NiFi log changes in the LogFeeder config (Miklos 
Gergely via oleewere)
{code}

> Follow up NiFi log changes in the LogFeeder config
> --
>
> Key: AMBARI-17323
> URL: https://issues.apache.org/jira/browse/AMBARI-17323
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-logsearch
>Affects Versions: 2.4.0
>Reporter: Miklos Gergely
>Assignee: Miklos Gergely
> Fix For: 2.4.0
>
> Attachments: AMBARI-17323.patch
>
>
> The NiFi service log dir properties were recently changes. The LogFeeder 
> config needs to follow up this change to access the NiFi logs



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

[jira] [Commented] (AMBARI-17339) Ambari alert "NameNode Last Checkpoint" failing when NameNode is HA

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-17339:


{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12812206/AMBARI-17339.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/7451//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/7451//console

This message is automatically generated.

> Ambari alert "NameNode Last Checkpoint" failing when NameNode is HA
> ---
>
> Key: AMBARI-17339
> URL: https://issues.apache.org/jira/browse/AMBARI-17339
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.4.0
>
> Attachments: AMBARI-17339.patch
>
>
> The "NameNode Last Checkpoint" alert is implemented in
> _alert_checkpoint_time.py_. This script uses the value of **dfs.namenode.http-
> address** property for querying the last checkpoint timestamp.
> This works fine when the NN is not in HA mode. However when NN is in HA mode
> this property is either not defined or might not be pointing to the right NN
> instance.
> The script needs to be improved such as to figure out if the NN is in HA mode.
> If it's in HA mode do not use **dfs.namenode.http-address** property but
> rather determine the correct URL to connect to similarly as how it's done in
> the _alert_ha_namenode_health.py_



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

[jira] [Updated] (AMBARI-17117) Fix misnamed Zookeeper connect strings in Log Search

[JIRA]

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

Olivér Szabó updated AMBARI-17117:
--
Resolution: Fixed
Status: Resolved  (was: Patch Available)

committed to trunk:
{code:java}
commit a2c23b213380cf7e8ccbf1db130a0925cc159516
Author: Miklos Gergely 
Date:   Tue Jun 21 19:05:52 2016 +0200

AMBARI-17117. Fix misnamed Zookeeper connect strings in Log Search (Miklos 
Gergely via oleewere)
{code}
comitted to branch-2.4:
{code:java}
commit 9471646c71da8619364e0d8cbc20fc783d6492b8
Author: Miklos Gergely 
Date:   Tue Jun 21 19:05:52 2016 +0200

AMBARI-17117. Fix misnamed Zookeeper connect strings in Log Search (Miklos 
Gergely via oleewere)
{code}

> Fix misnamed Zookeeper connect strings in Log Search
> 
>
> Key: AMBARI-17117
> URL: https://issues.apache.org/jira/browse/AMBARI-17117
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-logsearch
>Affects Versions: 2.4.0
>Reporter: Miklos Gergely
>Assignee: Miklos Gergely
> Fix For: 2.4.0
>
> Attachments: AMBARI-17117.patch
>
>
> Variables/properties holding zookeeper connect strings are misnamed as 
> zk_host, or zk_hosts, which may be misleading. Variable / property names 
> fixed.



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

[jira] [Commented] (AMBARI-17292) Operations during upgrade are permitted by all roles

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-17292:


{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12812195/AMBARI-17292.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/7450//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/7450//console

This message is automatically generated.

> Operations during upgrade are permitted by all roles
> 
>
> Key: AMBARI-17292
> URL: https://issues.apache.org/jira/browse/AMBARI-17292
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.4.0
>
> Attachments: AMBARI-17292.patch
>
>
> ambari-server --hash  
> 9a2943ba77371f1c20b4f3da900abb7c2e89d22b  
> Build# ambari-server-2.4.0.0-591.x86_64
> **Steps**
>   1. Create user with different roles like Cluster user, Service 
> Administrator etc.
>   2. Login as Ambari admin user and start Express Upgrade (register version, 
> install packages and start EU)
>   3. Pause the Upgrade at any step that requires manual intervention (like 
> stop YARN queue or backup DB or even at Finalize step)
>   4. Logout and login as cluster user
> **Result**:  
> The logged in user has complete access to Upgrade Wizard and can resume
> upgrade  
> Also do actions like Downgrade, 'Ignore and Proceed', 'Retry'
> The same is true for other roles like service administrator too, both during
> upgrade and downgrade
> **Expected Result:** Only Ambari Admin and Cluster Admin should be permitted 
> to perform actions during cluster upgrade
> Screenshots attached for reference while logged in as cluster user role
> (cluser)
> Another observation: While upgrade is in progress, login in a different
> session as cluster user - the cluster user can view the upgrade wizard in
> exact same way as admin



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

[jira] [Updated] (AMBARI-17347) Different order HDP versions in admin_view stackVersionsi and admin/stack/versions

[Andrii Babiichuk (JIRA)]

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

Andrii Babiichuk updated AMBARI-17347:
--
Attachment: AMBARI-17347.patch

> Different order HDP versions in admin_view stackVersionsi and 
> admin/stack/versions
> --
>
> Key: AMBARI-17347
> URL: https://issues.apache.org/jira/browse/AMBARI-17347
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-admin
>Affects Versions: 2.4.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
> Fix For: 2.4.0
>
> Attachments: AMBARI-17347.patch
>
>
> STR:
> # Deploy HDP 2.3 on Ambari2.1.2
> # Enable HA 
> # Perform ambari upgrade to 2.4.0
> # Register HDP 2.4.3
> # Install new stack version
> # install HDP 2.4.3
> # Register HDP 2.5, 2.5.0.0 + some custom vd file with HDP version 
> 2.5.0.0-xxx.
> Result: Different order HDP versions in admin_view stackVersionsi and 
> admin/stack/versions
> For example version 2.5 is last in admin_view stackVersions page and not last 
> in admin/stack/versions page.



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

[jira] [Created] (AMBARI-17347) Different order HDP versions in admin_view stackVersionsi and admin/stack/versions

[Andrii Babiichuk (JIRA)]

Andrii Babiichuk created AMBARI-17347:
-

 Summary: Different order HDP versions in admin_view stackVersionsi 
and admin/stack/versions
 Key: AMBARI-17347
 URL: https://issues.apache.org/jira/browse/AMBARI-17347
 Project: Ambari
  Issue Type: Bug
  Components: ambari-admin
Affects Versions: 2.4.0
Reporter: Andrii Babiichuk
Assignee: Andrii Babiichuk
 Fix For: 2.4.0


STR:
# Deploy HDP 2.3 on Ambari2.1.2
# Enable HA 
# Perform ambari upgrade to 2.4.0
# Register HDP 2.4.3
# Install new stack version
# install HDP 2.4.3
# Register HDP 2.5, 2.5.0.0 + some custom vd file with HDP version 2.5.0.0-xxx.
Result: Different order HDP versions in admin_view stackVersionsi and 
admin/stack/versions
For example version 2.5 is last in admin_view stackVersions page and not last 
in admin/stack/versions page.



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

[jira] [Created] (AMBARI-17346) Dependent components should be shutdown before stopping hdfs

[Ted Yu (JIRA)]

Ted Yu created AMBARI-17346:
---

 Summary: Dependent components should be shutdown before stopping 
hdfs
 Key: AMBARI-17346
 URL: https://issues.apache.org/jira/browse/AMBARI-17346
 Project: Ambari
  Issue Type: Bug
Reporter: Ted Yu


Sometimes admin shuts down hdfs first, then hbase. 

By the time hbase is shutdown, no data can be persisted (including metadata). 
This results in large number of inconsistencies when hbase cluster is brought 
back up.

Before hdfs is shutdown, the components dependent on hdfs should be shutdown 
first.



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

[jira] [Updated] (AMBARI-17345) Hive metastore failed to start

[Vitaly Brodetskyi (JIRA)]

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

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

> Hive metastore failed to start
> --
>
> Key: AMBARI-17345
> URL: https://issues.apache.org/jira/browse/AMBARI-17345
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17345.patch
>
>
> STR:
> 1) Add Hive Metastore on hosts that do not have it
> 2) Restart services with stale configs
> It started fine on retrying
> {code}
> ERROR: Unable to connect to the DB. Please check DB connection 
> properties.\njava.lang.ClassNotFoundException: 
> oracle.jdbc.driver.OracleDriver\n2016-06-20 13:18:14,206 - Retrying after 10 
> seconds. Reason: Execution of '/usr/jdk64/jdk1.8.0_77/bin/java -cp 
> /usr/lib/ambari-agent/DBConnectionVerification.jar:/usr/hdp/current/hive-metastore/lib/ojdbc6.jar
>  org.apache.ambari.server.DBConnectionVerification 
> 'jdbc:oracle:thin:@//172.22.124.192:1521/XE' hiveuser [PROTECTED] 
> oracle.jdbc.driver.OracleDriver' returned 1. ERROR: Unable to connect to the 
> DB. Please check DB connection properties.\njava.lang.ClassNotFoundException:
> {code}



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

[jira] [Updated] (AMBARI-17345) Hive metastore failed to start

[Vitaly Brodetskyi (JIRA)]

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

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

> Hive metastore failed to start
> --
>
> Key: AMBARI-17345
> URL: https://issues.apache.org/jira/browse/AMBARI-17345
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17345.patch
>
>
> STR:
> 1) Add Hive Metastore on hosts that do not have it
> 2) Restart services with stale configs
> It started fine on retrying
> {code}
> ERROR: Unable to connect to the DB. Please check DB connection 
> properties.\njava.lang.ClassNotFoundException: 
> oracle.jdbc.driver.OracleDriver\n2016-06-20 13:18:14,206 - Retrying after 10 
> seconds. Reason: Execution of '/usr/jdk64/jdk1.8.0_77/bin/java -cp 
> /usr/lib/ambari-agent/DBConnectionVerification.jar:/usr/hdp/current/hive-metastore/lib/ojdbc6.jar
>  org.apache.ambari.server.DBConnectionVerification 
> 'jdbc:oracle:thin:@//172.22.124.192:1521/XE' hiveuser [PROTECTED] 
> oracle.jdbc.driver.OracleDriver' returned 1. ERROR: Unable to connect to the 
> DB. Please check DB connection properties.\njava.lang.ClassNotFoundException:
> {code}



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

[jira] [Created] (AMBARI-17345) Hive metastore failed to start

[Vitaly Brodetskyi (JIRA)]

Vitaly Brodetskyi created AMBARI-17345:
--

 Summary: Hive metastore failed to start
 Key: AMBARI-17345
 URL: https://issues.apache.org/jira/browse/AMBARI-17345
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: 2.4.0
Reporter: Vitaly Brodetskyi
Assignee: Vitaly Brodetskyi
Priority: Critical
 Fix For: 2.4.0
 Attachments: AMBARI-17345.patch

STR:
1) Add Hive Metastore on hosts that do not have it
2) Restart services with stale configs
It started fine on retrying

{code}
ERROR: Unable to connect to the DB. Please check DB connection 
properties.\njava.lang.ClassNotFoundException: 
oracle.jdbc.driver.OracleDriver\n2016-06-20 13:18:14,206 - Retrying after 10 
seconds. Reason: Execution of '/usr/jdk64/jdk1.8.0_77/bin/java -cp 
/usr/lib/ambari-agent/DBConnectionVerification.jar:/usr/hdp/current/hive-metastore/lib/ojdbc6.jar
 org.apache.ambari.server.DBConnectionVerification 
'jdbc:oracle:thin:@//172.22.124.192:1521/XE' hiveuser [PROTECTED] 
oracle.jdbc.driver.OracleDriver' returned 1. ERROR: Unable to connect to the 
DB. Please check DB connection properties.\njava.lang.ClassNotFoundException:
{code}



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

[jira] [Created] (AMBARI-17344) Clear /security.json if kerberos is disabled

[JIRA]

Olivér Szabó created AMBARI-17344:
-

 Summary: Clear /security.json if kerberos is disabled
 Key: AMBARI-17344
 URL: https://issues.apache.org/jira/browse/AMBARI-17344
 Project: Ambari
  Issue Type: Bug
  Components: ambari-logsearch, ambari-server
Affects Versions: 2.4.0
Reporter: Olivér Szabó
Assignee: Olivér Szabó
 Fix For: 2.4.0






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

[jira] [Resolved] (AMBARI-17294) Retry logic for creating /ambari-solr znode for logsearch Solr

[JIRA]

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

Olivér Szabó resolved AMBARI-17294.
---
Resolution: Fixed

> Retry logic for creating /ambari-solr znode for logsearch Solr
> --
>
> Key: AMBARI-17294
> URL: https://issues.apache.org/jira/browse/AMBARI-17294
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-logsearch, ambari-server
>Affects Versions: 2.4.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17294.patch
>
>
> Cluster deployed with blueprint. Log Search Server start failed due to error: 
> {code:java}
> Traceback (most recent call last):
>   File 
> "/var/lib/ambari-agent/cache/common-services/LOGSEARCH/0.5.0/package/scripts/logsearch.py",
>  line 64, in 
> LogSearch().execute()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 257, in execute
> method(env)
>   File 
> "/var/lib/ambari-agent/cache/common-services/LOGSEARCH/0.5.0/package/scripts/logsearch.py",
>  line 43, in start
> self.configure(env)
>   File 
> "/var/lib/ambari-agent/cache/common-services/LOGSEARCH/0.5.0/package/scripts/logsearch.py",
>  line 38, in configure
> setup_logsearch()
>   File 
> "/var/lib/ambari-agent/cache/common-services/LOGSEARCH/0.5.0/package/scripts/setup_logsearch.py",
>  line 92, in setup_logsearch
> upload_conf_set(format('{logsearch_solr_collection_service_logs}'), 
> random_num)
>   File 
> "/var/lib/ambari-agent/cache/common-services/LOGSEARCH/0.5.0/package/scripts/setup_logsearch.py",
>  line 114, in upload_conf_set
> user=params.logsearch_solr_user)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/solr_cloud_util.py",
>  line 49, in upload_configuration_to_zk
> user=user
>   File "/usr/lib/python2.6/site-packages/resource_management/core/base.py", 
> line 155, in __init__
> self.env.run()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
> line 160, in run
> self.run_action(resource, action)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
> line 124, in run_action
> provider_action()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
>  line 273, in action_run
> tries=self.resource.tries, try_sleep=self.resource.try_sleep)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 70, in inner
> result = function(command, **kwargs)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 92, in checked_call
> tries=tries, try_sleep=try_sleep)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 140, in _call_wrapper
> result = _call(command, **kwargs_copy)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 293, in _call
> raise Fail(err_msg)
> resource_management.core.exceptions.Fail: Execution of 'export 
> JAVA_HOME=/usr/jdk64/jdk1.7.0_67 ; 
> /usr/lib/ambari-logsearch-solr-client/solrCloudCli.sh -z 
> nat-os-r7-uepcxu-stackdeploy-1.openstacklocal:2181,nat-os-r7-uepcxu-stackdeploy-2.openstacklocal:2181,nat-os-r7-uepcxu-stackdeploy-4.openstacklocal:2181,nat-os-r7-uepcxu-stackdeploy-5.openstacklocal:2181/ambari-solr
>  --upload-config -d 
> /etc/ambari-logsearch-portal/conf/solr_configsets/hadoop_logs/conf -cs 
> hadoop_logs -rt 5 -i 10' returned 1. Using default ZkCredentialsProvider
> {code}
> This error occurs during Logsearch portal start, reason is znode was not 
> created during solr bootsrapping



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

[jira] [Updated] (AMBARI-17226) When requesting a Kerberos Descriptor via the REST API, 'when' clauses should optionally be processed

[Robert Levas (JIRA)]

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

Robert Levas updated AMBARI-17226:
--
Attachment: AMBARI-17226_branch-2.4_01.patch

> When requesting a Kerberos Descriptor via the REST API, 'when' clauses should 
> optionally be processed
> -
>
> Key: AMBARI-17226
> URL: https://issues.apache.org/jira/browse/AMBARI-17226
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Robert Levas
>Assignee: Robert Levas
> Fix For: 2.4.0
>
> Attachments: AMBARI-17226_branch-2.4_01.patch, 
> AMBARI-17226_trunk_01.patch
>
>
> When requesting a Kerberos Descriptor via the REST API, 'when' clauses should 
> optionally be processed.  If elected to be processed, identities that contain 
> {{when}} clauses will be included or excluded from the resulting descriptor 
> based on the result of the evaluation. 
> In the event of an _add service_ scenario, the services being added should be 
> able to be specified so that they can be included in the data used for 
> {{when}}-clause evaluation.  
> *Solution*
> Add _{{GET}} directives_ to specify whether {{when}} clauses are to be 
> evaluated (or not) while building the Kerberos Descriptor using the following 
> API call:
> {noformat}
> GET 
> /api/v1/clusters/CLUSTER_NAME/kerberos_descriptors/COMPOSITE?evaluate_when=true
> {noformat}
> If new services are being added, the {{additional_services}} directive should 
> be added to the request so the evaluation can be preformed on the _future_ 
> set of services, which may evaluate differently then the _current_ set of 
> services.
> {noformat}
> GET 
> /api/v1/clusters/CLUSTER_NAME/kerberos_descriptors/COMPOSITE?evaluate_when=true@additional_services=HIVE,TEZ,PIG
> {noformat}



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

[jira] [Created] (AMBARI-17343) Blueprint attribute provision_action=INSTALL_ONLY loses its value after server restart

[Sandor Magyari (JIRA)]

Sandor Magyari created AMBARI-17343:
---

 Summary: Blueprint attribute provision_action=INSTALL_ONLY loses 
its value after server restart
 Key: AMBARI-17343
 URL: https://issues.apache.org/jira/browse/AMBARI-17343
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: 2.4.0
Reporter: Sandor Magyari
Assignee: Sandor Magyari
Priority: Critical
 Fix For: 2.4.0


We created a cluster via blueprints where we did not want components to be 
started by Ambari (background - this was a takeover of existing cluster where 
services were already installed and started. We did not want STARTs to be done 
as they would overwrite existing configs). Towards this goal we set 
{{"provision_action" : "INSTALL_ONLY"}} so that when agents register with 
Ambari they will only do the install and not start.

{code}
{
  "blueprint" : "blueprint",
  "default_password" : "ambari",
  "provision_action" : "INSTALL_ONLY",
  "host_groups" : [
 ...
  ]
}
{code}

This flag did its job as long as ambari-server was not restarted. After restart 
however, new agents would install and start the host-components.



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

[jira] [Updated] (AMBARI-17117) Fix misnamed Zookeeper connect strings in Log Search

[Miklos Gergely (JIRA)]

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

Miklos Gergely updated AMBARI-17117:

Attachment: (was: AMBARI-17117.patch)

> Fix misnamed Zookeeper connect strings in Log Search
> 
>
> Key: AMBARI-17117
> URL: https://issues.apache.org/jira/browse/AMBARI-17117
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-logsearch
>Affects Versions: 2.4.0
>Reporter: Miklos Gergely
>Assignee: Miklos Gergely
> Fix For: 2.4.0
>
> Attachments: AMBARI-17117.patch
>
>
> Variables/properties holding zookeeper connect strings are misnamed as 
> zk_host, or zk_hosts, which may be misleading. Variable / property names 
> fixed.



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