[jira] [Commented] (AMBARI-13442) stack advisor layout and validations for HAWQ service master components

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-13442:


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

This message is automatically generated.

> stack advisor layout and validations for HAWQ service master components
> ---
>
> Key: AMBARI-13442
> URL: https://issues.apache.org/jira/browse/AMBARI-13442
> Project: Ambari
>  Issue Type: Story
>Affects Versions: 2.1.2
>Reporter: Alexander Denissov
>Assignee: Alexander Denissov
> Fix For: 2.1.3
>
> Attachments: AMBARI-13442.patch, AMBARI-13442.patch.1
>
>
> Apache HAWQ will be a common service. When installing the service via UI 
> wizard, HAWQ Master and HAWQ Standby Master need to be placed on master 
> nodes. They should not be collocated with each other (causing an ERROR 
> message) and with Ambari Server (causing a WARN message).



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

Re: Review Request 39519: Create a script to change host names for a stopped cluster

[Sumit Mohanty]

> On Oct. 22, 2015, 6:14 a.m., Sumit Mohanty wrote:
> > ambari-server/src/main/java/org/apache/ambari/server/configuration/Configuration.java,
> >  line 859
> > 
> >
> > type - configuration

I meant typo.


- Sumit


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/39519/#review103530
---


On Oct. 21, 2015, 6:04 p.m., Vitalyi Brodetskyi wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/39519/
> ---
> 
> (Updated Oct. 21, 2015, 6:04 p.m.)
> 
> 
> Review request for Ambari, Dmitro Lisnichenko, Jonathan Hurley, Myroslav 
> Papirkovskyy, and Sumit Mohanty.
> 
> 
> Bugs: AMBARI-13507
> https://issues.apache.org/jira/browse/AMBARI-13507
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> At a high-level we may follow this approach:
> Ensure cluster is not kerberized
> Assume all services to be stopped (add a check to ensure that services are 
> stopped)
> We may also need to check and confirm that there are no commands pending 
> execution - or just mark them as aborted
> Update all host names in the database based on the mapping provided (e.g. 
> host1 --> master01.dev.com)
> As SQLClient cannot be assumed consider using jdbc - similar to the Upgrade 
> code
> Modify all configs to replace the hostnames as needed (not sure if plain 
> search and replace will suffice)
> Agents need to be re-configured if ambari-server hostname changes
> 
> 
> Diffs
> -
> 
>   ambari-server/sbin/ambari-server 1843cd6 
>   
> ambari-server/src/main/java/org/apache/ambari/server/configuration/Configuration.java
>  702e12d 
>   
> ambari-server/src/main/java/org/apache/ambari/server/state/ConfigHelper.java 
> 62c3b61 
>   
> ambari-server/src/main/java/org/apache/ambari/server/update/HostUpdateHelper.java
>  PRE-CREATION 
>   
> ambari-server/src/main/java/org/apache/ambari/server/upgrade/AbstractUpgradeCatalog.java
>  ed68313 
>   ambari-server/src/main/python/ambari-server.py 88df81a 
>   ambari-server/src/main/python/ambari_server/hostUpdate.py PRE-CREATION 
>   ambari-server/src/main/python/ambari_server/setupActions.py 6c6e7ea 
> 
> Diff: https://reviews.apache.org/r/39519/diff/
> 
> 
> Testing
> ---
> 
> mvn clean test
> 
> 
> Thanks,
> 
> Vitalyi Brodetskyi
> 
>

Re: Review Request 39519: Create a script to change host names for a stopped cluster

[Sumit Mohanty]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/39519/#review103530
---



ambari-server/sbin/ambari-server (line 148)


Updating hostnames



ambari-server/src/main/java/org/apache/ambari/server/configuration/Configuration.java
 (line 854)


type - configuration



ambari-server/src/main/java/org/apache/ambari/server/update/HostUpdateHelper.java
 (line 355)


How about topology_host_request table?



ambari-server/src/main/python/ambari_server/hostUpdate.py (line 39)


Lets modify the texts in this function to say "update host name" instead of 
"update host".



ambari-server/src/main/python/ambari_server/hostUpdate.py (line 45)


Lets ask if DB has been backed up and if the answer is N exit


- Sumit Mohanty


On Oct. 21, 2015, 6:04 p.m., Vitalyi Brodetskyi wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/39519/
> ---
> 
> (Updated Oct. 21, 2015, 6:04 p.m.)
> 
> 
> Review request for Ambari, Dmitro Lisnichenko, Jonathan Hurley, Myroslav 
> Papirkovskyy, and Sumit Mohanty.
> 
> 
> Bugs: AMBARI-13507
> https://issues.apache.org/jira/browse/AMBARI-13507
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> At a high-level we may follow this approach:
> Ensure cluster is not kerberized
> Assume all services to be stopped (add a check to ensure that services are 
> stopped)
> We may also need to check and confirm that there are no commands pending 
> execution - or just mark them as aborted
> Update all host names in the database based on the mapping provided (e.g. 
> host1 --> master01.dev.com)
> As SQLClient cannot be assumed consider using jdbc - similar to the Upgrade 
> code
> Modify all configs to replace the hostnames as needed (not sure if plain 
> search and replace will suffice)
> Agents need to be re-configured if ambari-server hostname changes
> 
> 
> Diffs
> -
> 
>   ambari-server/sbin/ambari-server 1843cd6 
>   
> ambari-server/src/main/java/org/apache/ambari/server/configuration/Configuration.java
>  702e12d 
>   
> ambari-server/src/main/java/org/apache/ambari/server/state/ConfigHelper.java 
> 62c3b61 
>   
> ambari-server/src/main/java/org/apache/ambari/server/update/HostUpdateHelper.java
>  PRE-CREATION 
>   
> ambari-server/src/main/java/org/apache/ambari/server/upgrade/AbstractUpgradeCatalog.java
>  ed68313 
>   ambari-server/src/main/python/ambari-server.py 88df81a 
>   ambari-server/src/main/python/ambari_server/hostUpdate.py PRE-CREATION 
>   ambari-server/src/main/python/ambari_server/setupActions.py 6c6e7ea 
> 
> Diff: https://reviews.apache.org/r/39519/diff/
> 
> 
> Testing
> ---
> 
> mvn clean test
> 
> 
> Thanks,
> 
> Vitalyi Brodetskyi
> 
>

[jira] [Commented] (AMBARI-12701) Stop-and-Start Upgrade: Handle Core Services

[Hudson (JIRA)]

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

Hudson commented on AMBARI-12701:
-

FAILURE: Integrated in Ambari-trunk-Commit #3692 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/3692/])
AMBARI-12701. Stop-and-Start Upgrade: Handle Core Services (alejandro) 
(afernandez: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=7afe5a4ec9200c41922fb1c0809f34a0d8d700bd])
* 
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/journalnode_upgrade.py
* 
ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/ClusterGrouping.java
* 
ambari-server/src/main/resources/common-services/ZOOKEEPER/3.4.5.2.0/package/scripts/zookeeper_server.py
* ambari-server/src/test/python/stacks/2.0.6/YARN/test_nodemanager.py
* 
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/PreUpgradeCheckResourceProvider.java
* ambari-server/src/test/python/stacks/2.0.6/ZOOKEEPER/test_zookeeper_client.py
* 
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/datanode.py
* 
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/params_linux.py
* 
ambari-server/src/main/resources/common-services/ZOOKEEPER/3.4.5.2.0/package/scripts/zookeeper_client.py
* 
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/namenode.py
* 
ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/scripts/params_linux.py
* 
ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/scripts/historyserver.py
* 
ambari-server/src/main/resources/stacks/HDP/2.1/upgrades/nonrolling-upgrade-2.3.xml
* ambari-server/src/test/python/stacks/2.0.6/HDFS/test_namenode.py
* 
ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/nonrolling-upgrade-2.2.xml
* ambari-server/src/test/python/stacks/2.0.6/HDFS/test_hdfs_client.py
* ambari-server/src/test/python/stacks/2.1/YARN/test_apptimelineserver.py
* ambari-server/src/test/python/stacks/2.0.6/YARN/test_yarn_client.py
* ambari-common/src/main/python/resource_management/libraries/script/script.py
* 
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/namenode_upgrade.py
* 
ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/scripts/nodemanager.py
* ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/config-upgrade.xml
* ambari-server/src/test/python/stacks/2.0.6/HDFS/test_nfsgateway.py
* 
ambari-server/src/test/java/org/apache/ambari/server/state/stack/upgrade/StageWrapperBuilderTest.java
* 
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_client.py
* 
ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/scripts/application_timeline_server.py
* 
ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/scripts/resourcemanager.py
* 
ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/ServiceCheckGrouping.java
* 
ambari-server/src/main/resources/common-services/ZOOKEEPER/3.4.5.2.0/package/scripts/zookeeper_service.py
* 
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/journalnode.py
* ambari-server/src/test/python/stacks/2.0.6/HDFS/test_datanode.py
* ambari-server/src/test/python/stacks/2.0.6/YARN/test_resourcemanager.py
* 
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/datanode_upgrade.py
* 
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/utils.py
* 
ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/StageWrapper.java
* 
ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/scripts/yarn_client.py
* ambari-server/src/test/python/stacks/2.0.6/YARN/test_mapreduce2_client.py
* ambari-server/src/test/python/stacks/2.0.6/ZOOKEEPER/test_zookeeper_server.py
* ambari-server/src/test/python/stacks/2.0.6/YARN/test_historyserver.py
* 
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/nfsgateway.py
* 
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/UpgradeResourceProvider.java
* 
ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/StageWrapperBuilder.java
* 
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/snamenode.py
* 
ambari-server/src/main/resources/common-services/ZOOKEEPER/3.4.5.2.0/package/scripts/zookeeper.py
* 
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/setup_ranger_hdfs.py
* 
ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/TaskWrapperBuilder.java
* 
ambari-server/src/main/java/org/apache/ambari/server/stack/MasterHostResolver.java
* ambari-server/src/main/java/org/apache/ambari/server/state/UpgradeHelper.java
* 
ambari-server/src/main/java/org/apach

Re: Review Request 39513: AMBARI-13450 Bootstrap Cluster via different SSH Port Number

[Selim Ozcan]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/39513/#review103532
---

Ship it!


Ship It!

- Selim Ozcan


On Oct. 21, 2015, 8:43 a.m., Selim Ozcan wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/39513/
> ---
> 
> (Updated Oct. 21, 2015, 8:43 a.m.)
> 
> 
> Review request for Ambari.
> 
> 
> Bugs: https://issues.apache.org/jira/browse/AMBARI-13450
> 
> https://issues.apache.org/jira/browse/https://issues.apache.org/jira/browse/AMBARI-13450
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> https://issues.apache.org/jira/browse/AMBARI-13450
> 
> 
> For the time being, bootstrapping cluster is done via default port number 22 
> for SSH and SCP protocols without an option to specify the port number.
> 
> There was a need to bootstrap cluster via different port number at the 
> laboratory which I work at but Apache Ambari didn't have that option so we 
> add that functionality. It still uses the default port number 22 unless you 
> change it at Installer Wizard Step 2.
> 
> A Textfieldview (default written value '22' SSH Port number ) added to 
> installer wizard step 2, same as specifying ssh user field which is default 
> to 'root' user, to take the SSH port input from user. After that, Port number 
> is transferred to bootstrapping functions along with sshUser value.
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/java/org/apache/ambari/server/bootstrap/BSRunner.java 
> 0a55131 
>   
> ambari-server/src/main/java/org/apache/ambari/server/bootstrap/SshHostInfo.java
>  822e972 
>   ambari-server/src/main/python/bootstrap.py 3eba75c 
>   ambari-server/src/test/python/TestBootstrap.py e143a68 
>   ambari-web/app/controllers/wizard.js 2049099 
>   ambari-web/app/controllers/wizard/step2_controller.js 3b51761 
>   ambari-web/app/controllers/wizard/step3_controller.js b3645e9 
>   ambari-web/app/messages.js 349ae70 
>   ambari-web/app/styles/application.less 31d495e 
>   ambari-web/app/templates/wizard/step2.hbs a194cc0 
>   ambari-web/test/controllers/wizard/step2_test.js d62b247 
>   ambari-web/test/controllers/wizard/step3_test.js 74c62e6 
> 
> Diff: https://reviews.apache.org/r/39513/diff/
> 
> 
> Testing
> ---
> 
> https://issues.apache.org/jira/browse/AMBARI-13450?focusedCommentId=14965976&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14965976
> 
> 
> ++1 overall. Here are the results of testing the latest attachment
> http://issues.apache.org/jira/secure/attachment/12767586/diff_patch2.patch
> against trunk revision .
> 
> +1 @author. The patch does not contain any @author tags.
> 
> +1 tests included. The patch appears to include 3 new or modified test files.
> 
> +1 javac. The applied patch does not increase the total number of javac 
> compiler warnings.
> 
> +1 release audit. The applied patch does not increase the total number of 
> release audit warnings.
> 
> +1 core tests. The patch passed unit tests in ambari-server ambari-web.
> 
> Test results: 
> https://builds.apache.org/job/Ambari-trunk-test-patch/4016//testReport/
> Console output: 
> https://builds.apache.org/job/Ambari-trunk-test-patch/4016//console
> 
> This message is automatically generated.
> 
> 
> Thanks,
> 
> Selim Ozcan
> 
>

Re: Review Request 39519: Create a script to change host names for a stopped cluster

[Sid Wagle]

On Oct. 22, 2015, 5:22 a.m., Vitalyi Brodetskyi wrote:
> > Any reason to not have written unit tests for this?

Ignore this, just saw the update.


- Sid


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/39519/#review103527
---


On Oct. 21, 2015, 6:04 p.m., Vitalyi Brodetskyi wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/39519/
> ---
> 
> (Updated Oct. 21, 2015, 6:04 p.m.)
> 
> 
> Review request for Ambari, Dmitro Lisnichenko, Jonathan Hurley, Myroslav 
> Papirkovskyy, and Sumit Mohanty.
> 
> 
> Bugs: AMBARI-13507
> https://issues.apache.org/jira/browse/AMBARI-13507
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> At a high-level we may follow this approach:
> Ensure cluster is not kerberized
> Assume all services to be stopped (add a check to ensure that services are 
> stopped)
> We may also need to check and confirm that there are no commands pending 
> execution - or just mark them as aborted
> Update all host names in the database based on the mapping provided (e.g. 
> host1 --> master01.dev.com)
> As SQLClient cannot be assumed consider using jdbc - similar to the Upgrade 
> code
> Modify all configs to replace the hostnames as needed (not sure if plain 
> search and replace will suffice)
> Agents need to be re-configured if ambari-server hostname changes
> 
> 
> Diffs
> -
> 
>   ambari-server/sbin/ambari-server 1843cd6 
>   
> ambari-server/src/main/java/org/apache/ambari/server/configuration/Configuration.java
>  702e12d 
>   
> ambari-server/src/main/java/org/apache/ambari/server/state/ConfigHelper.java 
> 62c3b61 
>   
> ambari-server/src/main/java/org/apache/ambari/server/update/HostUpdateHelper.java
>  PRE-CREATION 
>   
> ambari-server/src/main/java/org/apache/ambari/server/upgrade/AbstractUpgradeCatalog.java
>  ed68313 
>   ambari-server/src/main/python/ambari-server.py 88df81a 
>   ambari-server/src/main/python/ambari_server/hostUpdate.py PRE-CREATION 
>   ambari-server/src/main/python/ambari_server/setupActions.py 6c6e7ea 
> 
> Diff: https://reviews.apache.org/r/39519/diff/
> 
> 
> Testing
> ---
> 
> mvn clean test
> 
> 
> Thanks,
> 
> Vitalyi Brodetskyi
> 
>

Re: Review Request 39519: Create a script to change host names for a stopped cluster

[Sid Wagle]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/39519/#review103527
---



ambari-server/sbin/ambari-server (line 147)


Lets call this update-hostname



ambari-server/src/main/java/org/apache/ambari/server/update/HostUpdateHelper.java
 (line 174)


Should there be an option to updated older configurations and not just the 
selected ones ?



ambari-server/src/main/java/org/apache/ambari/server/update/HostUpdateHelper.java
 (line 351)


What about config group associatons, are those by id ?


Any reason to not have written unit tests for this?

- Sid Wagle


On Oct. 21, 2015, 6:04 p.m., Vitalyi Brodetskyi wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/39519/
> ---
> 
> (Updated Oct. 21, 2015, 6:04 p.m.)
> 
> 
> Review request for Ambari, Dmitro Lisnichenko, Jonathan Hurley, Myroslav 
> Papirkovskyy, and Sumit Mohanty.
> 
> 
> Bugs: AMBARI-13507
> https://issues.apache.org/jira/browse/AMBARI-13507
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> At a high-level we may follow this approach:
> Ensure cluster is not kerberized
> Assume all services to be stopped (add a check to ensure that services are 
> stopped)
> We may also need to check and confirm that there are no commands pending 
> execution - or just mark them as aborted
> Update all host names in the database based on the mapping provided (e.g. 
> host1 --> master01.dev.com)
> As SQLClient cannot be assumed consider using jdbc - similar to the Upgrade 
> code
> Modify all configs to replace the hostnames as needed (not sure if plain 
> search and replace will suffice)
> Agents need to be re-configured if ambari-server hostname changes
> 
> 
> Diffs
> -
> 
>   ambari-server/sbin/ambari-server 1843cd6 
>   
> ambari-server/src/main/java/org/apache/ambari/server/configuration/Configuration.java
>  702e12d 
>   
> ambari-server/src/main/java/org/apache/ambari/server/state/ConfigHelper.java 
> 62c3b61 
>   
> ambari-server/src/main/java/org/apache/ambari/server/update/HostUpdateHelper.java
>  PRE-CREATION 
>   
> ambari-server/src/main/java/org/apache/ambari/server/upgrade/AbstractUpgradeCatalog.java
>  ed68313 
>   ambari-server/src/main/python/ambari-server.py 88df81a 
>   ambari-server/src/main/python/ambari_server/hostUpdate.py PRE-CREATION 
>   ambari-server/src/main/python/ambari_server/setupActions.py 6c6e7ea 
> 
> Diff: https://reviews.apache.org/r/39519/diff/
> 
> 
> Testing
> ---
> 
> mvn clean test
> 
> 
> Thanks,
> 
> Vitalyi Brodetskyi
> 
>

[jira] [Commented] (AMBARI-13515) When both RM are standby, Tez view can not be seen

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-13515:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12767922/Screen%20Shot%202015-10-21%20at%204.05.42%20PM.png
  against trunk revision .

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

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

This message is automatically generated.

> When both RM are standby, Tez view can not be seen
> --
>
> Key: AMBARI-13515
> URL: https://issues.apache.org/jira/browse/AMBARI-13515
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.1.2
>Reporter: DIPAYAN BHOWMICK
>Assignee: DIPAYAN BHOWMICK
> Fix For: 2.1.3
>
> Attachments: AMBARI-13515_branch-2.1.patch, Screen Shot 2015-10-21 at 
> 4.05.42 PM.png
>
>
> Steps :
> 1) Run a tez application
> 2) open Dag detail page for this application
> 3) Make both RMs to be standby (by stopping 2/3 Zks )
> 4) Refresh the tez view: dag detail page
> Here, the page remains blank and /status call gives 500 error without any 
> error displayed on the screen



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

[jira] [Commented] (AMBARI-13158) error message is not accurate when a directory field value has a space

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-13158:


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

This message is automatically generated.

> error message is not accurate when a directory field value has a space 
> ---
>
> Key: AMBARI-13158
> URL: https://issues.apache.org/jira/browse/AMBARI-13158
> Project: Ambari
>  Issue Type: Bug
>Reporter: jun aoki
>Assignee: jun aoki
>Priority: Trivial
> Attachments: AMBARI-13158-2.patch, AMBARI-13158.patch, 
> screenshot-1.png
>
>
> when, for example, dfs.datanode.data.dir.mount.file field in Configs tab has 
> a file path with a space, it warns "Must be a slash or drive at the start", 
> which should be "Wrong path " or something, or maybe a path with space is OK 
> too.



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

Re: Review Request 39536: Ambari Server JVM crashed after several clicks in Web UI to navigate graph timerange

[Sid Wagle]

> On Oct. 22, 2015, 2:47 a.m., Sumit Mohanty wrote:
> > ambari-server/src/main/java/org/apache/ambari/server/controller/metrics/timeline/cache/TimelineMetricsCacheSizeOfEngine.java,
> >  line 37
> > 
> >
> > Probably a non-issue, but should it be 1 as in initializeCache()

The SizeOfPolicyConfiguration overrides this, so real value is 10k. And yes, it 
doesn't really matter.


- Sid


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/39536/#review103513
---


On Oct. 22, 2015, 1:46 a.m., Sid Wagle wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/39536/
> ---
> 
> (Updated Oct. 22, 2015, 1:46 a.m.)
> 
> 
> Review request for Ambari, Alejandro Fernandez, Dmytro Sen, Jonathan Hurley, 
> and Sumit Mohanty.
> 
> 
> Bugs: AMBARI-13517
> https://issues.apache.org/jira/browse/AMBARI-13517
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> - Max Heap restriction problem: Ehcache library that we use has a limit of 
> how far in the object graph it traverses to find size of an Cached reference, 
> this is to make it performant. Default limit = 1000.
> - User gets following Warning which are harmless unless the data cannot fit 
> in memory and eviction does not kick in:
> 
> WARN [qtp-client-70] ObjectGraphWalker:209 - The configured limit of 1,000 
> object references was reached while attempting to calculate the size of the 
> object graph. Severe performance degradation could occur 
> if the sizing operation continues. This can be avoided by setting the 
> CacheManger or Cache  elements maxDepthExceededBehavior to 
> "abort" or adding stop points with @IgnoreSizeOf annotations. If performance 
> degradation 
> is NOT an issue at the configured limit, raise the limit value using the 
> CacheManager or Cache  elements maxDepth attribute. For more 
> information, see the Ehcache configuration documentation.
> 
> _Objective of the patch_:
> - Provide a custom Sizing engine for Ehcache that will provide a close 
> approximation of the data in the cache with significant perf gain. Premise: 
> Since we know the data structures we can make better estimates.
> - Expectation from sizing engine : Discrepancy of less than 10K for a DS of 
> size 10 MB (Proven with a unit test)
> 
> 
> Diffs
> -
> 
>   
> ambari-metrics/ambari-metrics-common/src/main/java/org/apache/hadoop/metrics2/sink/timeline/TimelineMetric.java
>  8b8df06 
>   
> ambari-metrics/ambari-metrics-common/src/main/java/org/apache/hadoop/metrics2/sink/timeline/cache/TimelineMetricsCache.java
>  224b490 
>   
> ambari-metrics/ambari-metrics-common/src/test/java/org/apache/hadoop/metrics2/sink/timeline/cache/TimelineMetricsCacheTest.java
>  4a13d63 
>   
> ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/HBaseTimelineMetricStore.java
>  9c0b94d 
>   
> ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/PhoenixHBaseAccessor.java
>  9488316 
>   
> ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/aggregators/TimelineMetricReadHelper.java
>  573e09d 
>   
> ambari-metrics/ambari-metrics-timelineservice/src/test/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/ITClusterAggregator.java
>  b7b1737 
>   
> ambari-metrics/ambari-metrics-timelineservice/src/test/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/ITMetricAggregator.java
>  a3640d0 
>   
> ambari-metrics/ambari-metrics-timelineservice/src/test/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/MetricTestHelper.java
>  26771d7 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/metrics/MetricsPaddingMethod.java
>  522c0bd 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/metrics/timeline/cache/TimelineMetricCacheProvider.java
>  6d80687 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/metrics/timeline/cache/TimelineMetricsCacheSizeOfEngine.java
>  PRE-CREATION 
>   
> ambari-server/src/test/java/org/apache/ambari/server/controller/metrics/timeline/MetricsPaddingMethodTest.java
>  c30c5eb 
>   
> ambari-server/src/test/java/org/apache/ambari/server/controller/metrics/timeline/cache/TimelineMetricCacheSizingTest.java
>  PRE-CREATION 
>   
> ambari-server/src/test/java/org/apache/ambari/server/controller/metrics/timeline/cache/TimelineMetricCacheTest.java
>  3432e1d 
> 
> Diff: https://reviews.apache.

[jira] [Commented] (AMBARI-13511) setup.py in python does not ambari_client include modules in subdirectories 'core' and 'model'

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-13511:


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

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

This message is automatically generated.

> setup.py in python does not ambari_client include modules in subdirectories 
> 'core' and 'model'
> --
>
> Key: AMBARI-13511
> URL: https://issues.apache.org/jira/browse/AMBARI-13511
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-client
>Affects Versions: trunk
>Reporter: Mark Bittmann
>Priority: Minor
> Attachments: AMBARI-13511.patch
>
>
> After running 'python setup.py install', the python modules in the 
> subdirectories 'core' and 'model' are not available. This appears to affect 
> the current distribution hosted on pypi as well (ambari_client 
> 1.0.3-SNAPSHOT). I have created a patch file and will upload. 
> Below is the error message: 
> >>> from ambari_client import ambari_api
> Traceback (most recent call last):
>   File "", line 1, in 
>   File "build/bdist.macosx-10.10-x86_64/egg/ambari_client/ambari_api.py", 
> line 19, in 
> ImportError: No module named core.http_client 



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

[jira] [Commented] (AMBARI-13507) Create a script to change host names for a stopped cluster

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-13507:


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

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

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

This message is automatically generated.

> Create a script to change host names for a stopped cluster
> --
>
> Key: AMBARI-13507
> URL: https://issues.apache.org/jira/browse/AMBARI-13507
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Affects Versions: 2.1.3
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: 2.1.3
>
> Attachments: AMBARI-13507.patch
>
>
> At a high-level we may follow this approach:
> Ensure cluster is not kerberized
> Assume all services to be stopped (add a check to ensure that services are 
> stopped)
> We may also need to check and confirm that there are no commands pending 
> execution - or just mark them as aborted
> Update all host names in the database based on the mapping provided (e.g. 
> host1 --> master01.dev.com)
> As SQLClient cannot be assumed consider using jdbc - similar to the Upgrade 
> code
> Modify all configs to replace the hostnames as needed (not sure if plain 
> search and replace will suffice)
> Agents need to be re-configured if ambari-server hostname changes



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

[jira] [Commented] (AMBARI-13510) Display sysctl and limits configuration on the HAWQ config UI screen

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-13510:


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

This message is automatically generated.

> Display sysctl and limits configuration on the HAWQ config UI screen
> 
>
> Key: AMBARI-13510
> URL: https://issues.apache.org/jira/browse/AMBARI-13510
> Project: Ambari
>  Issue Type: New Feature
>  Components: stacks
>Affects Versions: trunk
>Reporter: bhuvnesh chaudhary
>Assignee: bhuvnesh chaudhary
> Attachments: AMBARI-13510.patch
>
>
> User should be able to see the values of sysctl and limits parameters which 
> are configured for HAWQ.
> Sysctl parameters except vm.overcommit.memory are editable only during 
> install, after install they are read only. overcommit parameter can be 
> changed as needed.
> limits for hawq user(gpadmin) are editable.



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

[jira] [Commented] (AMBARI-12701) Stop-and-Start Upgrade: Handle Core Services

[Hudson (JIRA)]

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

Hudson commented on AMBARI-12701:
-

FAILURE: Integrated in Ambari-branch-2.1 #726 (See 
[https://builds.apache.org/job/Ambari-branch-2.1/726/])
AMBARI-12701. Stop-and-Start Upgrade: Handle Core Services (alejandro) 
(afernandez: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=2854b74573cbca468f0fba12de11996c2300547c])
* 
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/PreUpgradeCheckResourceProvider.java
* ambari-server/src/test/python/stacks/2.0.6/ZOOKEEPER/test_zookeeper_client.py
* 
ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/nonrolling-upgrade-2.2.xml
* 
ambari-server/src/main/resources/common-services/ZOOKEEPER/3.4.5.2.0/package/scripts/zookeeper_service.py
* 
ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/StageWrapperBuilder.java
* 
ambari-server/src/main/resources/common-services/ZOOKEEPER/3.4.5.2.0/package/scripts/zookeeper_server.py
* 
ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/ColocatedGrouping.java
* 
ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/scripts/yarn_client.py
* ambari-server/src/test/python/stacks/2.0.6/HDFS/test_nfsgateway.py
* 
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/params_linux.py
* 
ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/TaskWrapperBuilder.java
* 
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/setup_ranger_hdfs.py
* 
ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/scripts/application_timeline_server.py
* 
ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/StageWrapper.java
* 
ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/scripts/historyserver.py
* 
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/namenode_ha_state.py
* ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/config-upgrade.xml
* 
ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/scripts/resourcemanager.py
* 
ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/ClusterGrouping.java
* 
ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/TaskWrapper.java
* 
ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/scripts/params_linux.py
* 
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/UpgradeResourceProvider.java
* 
ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/scripts/nodemanager.py
* ambari-server/src/test/python/stacks/2.0.6/ZOOKEEPER/test_zookeeper_server.py
* 
ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/scripts/mapreduce2_client.py
* 
ambari-server/src/test/java/org/apache/ambari/server/state/stack/upgrade/StageWrapperBuilderTest.java
* 
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/datanode_upgrade.py
* 
ambari-server/src/main/resources/stacks/HDP/2.1/upgrades/nonrolling-upgrade-2.3.xml
* ambari-server/src/test/python/stacks/2.0.6/HDFS/test_datanode.py
* 
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/namenode.py
* 
ambari-server/src/main/java/org/apache/ambari/server/stack/MasterHostResolver.java
* 
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/zkfc_slave.py
* ambari-server/src/test/python/stacks/2.0.6/HDFS/test_journalnode.py
* ambari-server/src/test/python/stacks/2.0.6/HDFS/test_namenode.py
* ambari-common/src/main/python/resource_management/libraries/script/script.py
* ambari-server/src/main/java/org/apache/ambari/server/state/UpgradeHelper.java
* ambari-server/src/test/python/stacks/2.0.6/YARN/test_nodemanager.py
* 
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/namenode_upgrade.py
* 
ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/ServiceCheckGrouping.java
* 
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_client.py
* 
ambari-server/src/main/resources/common-services/ZOOKEEPER/3.4.5.2.0/package/scripts/zookeeper_client.py
* 
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/journalnode.py
* 
ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/Grouping.java
* ambari-server/src/test/python/stacks/2.0.6/YARN/test_yarn_client.py
* 
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/journalnode_upgrade.py
* 
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/utils.py
* ambari-server/src/test/python/stacks/2.1/YARN/test_apptimelineserver.py
* 
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/pac

[jira] [Commented] (AMBARI-13481) Ranger User Info tab: All subsequent subsection and their configs should be hidden if Ranger Usersync is disabled

[Hudson (JIRA)]

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

Hudson commented on AMBARI-13481:
-

FAILURE: Integrated in Ambari-branch-2.1 #726 (See 
[https://builds.apache.org/job/Ambari-branch-2.1/726/])
AMBARI-13481. Ranger User Info tab: All subsequent subsection and their 
(jaimin: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=e1395dac7db26b0dcf072656acd397e38b62c8e6])
* ambari-web/app/views/common/configs/service_config_layout_tab_view.js
* ambari-web/app/models/configs/theme/theme_condition.js
* ambari-web/app/models/configs/theme/sub_section_tab.js
* ambari-web/app/mappers/configs/themes_mapper.js
* ambari-web/app/models/configs/theme/sub_section.js
* ambari-web/app/views/common/configs/widgets/config_widget_view.js
* ambari-web/app/models.js
* ambari-web/app/models/configs/config_condition.js


> Ranger User Info tab: All subsequent subsection and their configs should be 
> hidden if Ranger Usersync is disabled
> -
>
> Key: AMBARI-13481
> URL: https://issues.apache.org/jira/browse/AMBARI-13481
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.1.3
>Reporter: Jaimin D Jetly
>Assignee: Jaimin D Jetly
> Fix For: 2.1.3
>
> Attachments: AMBARI-13481.patch, actual.png, expected.png
>
>
> All subsequent subsection and their configs should be hidden if Ranger 
> Usersync is disabled.
> To achieve this task visibility of entire subsection and subsection-tab is 
> dynamically changed depending upon the condition stated in theme.



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

[jira] [Commented] (AMBARI-13481) Ranger User Info tab: All subsequent subsection and their configs should be hidden if Ranger Usersync is disabled

[Hudson (JIRA)]

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

Hudson commented on AMBARI-13481:
-

FAILURE: Integrated in Ambari-trunk-Commit #3691 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/3691/])
AMBARI-13481. Ranger User Info tab: All subsequent subsection and their 
(jaimin: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=34a03533b1bf844a9f7b3f56919de1db3d24754c])
* ambari-web/app/views/common/configs/widgets/config_widget_view.js
* ambari-web/app/models/configs/theme/theme_condition.js
* ambari-web/app/models/configs/theme/sub_section.js
* ambari-web/app/models.js
* ambari-web/app/views/common/configs/service_config_layout_tab_view.js
* ambari-web/app/mappers/configs/themes_mapper.js
* ambari-web/app/models/configs/config_condition.js
* ambari-web/app/models/configs/theme/sub_section_tab.js


> Ranger User Info tab: All subsequent subsection and their configs should be 
> hidden if Ranger Usersync is disabled
> -
>
> Key: AMBARI-13481
> URL: https://issues.apache.org/jira/browse/AMBARI-13481
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.1.3
>Reporter: Jaimin D Jetly
>Assignee: Jaimin D Jetly
> Fix For: 2.1.3
>
> Attachments: AMBARI-13481.patch, actual.png, expected.png
>
>
> All subsequent subsection and their configs should be hidden if Ranger 
> Usersync is disabled.
> To achieve this task visibility of entire subsection and subsection-tab is 
> dynamically changed depending upon the condition stated in theme.



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

Re: Review Request 39524: Display sysctl and limits configuration on the HAWQ config UI screen

[bhuvnesh chaudhary]

> On Oct. 22, 2015, 1:07 a.m., Alejandro Fernandez wrote:
> > Ship It!

Thanks Alejandro


- bhuvnesh


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/39524/#review103502
---


On Oct. 21, 2015, 8:45 p.m., bhuvnesh chaudhary wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/39524/
> ---
> 
> (Updated Oct. 21, 2015, 8:45 p.m.)
> 
> 
> Review request for Ambari and jun aoki.
> 
> 
> Bugs: AMBARI-13510
> https://issues.apache.org/jira/browse/AMBARI-13510
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> User should be able to see the values of sysctl and limits parameters which 
> are configured for HAWQ.
> Sysctl parameters except vm.overcommit.memory are editable only during 
> install, after install they are read only. overcommit parameter can be 
> changed as needed.
> limits for hawq user(gpadmin) are editable.
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/resources/common-services/HAWQ/2.0.0.0/configuration/hawq-limits-env.xml
>  PRE-CREATION 
>   
> ambari-server/src/main/resources/common-services/HAWQ/2.0.0.0/configuration/hawq-sysctl-env.xml
>  PRE-CREATION 
>   
> ambari-server/src/main/resources/common-services/HAWQ/2.0.0.0/package/scripts/common.py
>  defd87c 
>   
> ambari-server/src/main/resources/common-services/HAWQ/2.0.0.0/package/scripts/constants.py
>  78a636e 
>   
> ambari-server/src/main/resources/common-services/HAWQ/2.0.0.0/package/scripts/hawqstatus.py
>  59742bd 
>   
> ambari-server/src/main/resources/common-services/HAWQ/2.0.0.0/package/scripts/master_helper.py
>  82a5168 
>   
> ambari-server/src/main/resources/common-services/HAWQ/2.0.0.0/package/scripts/params.py
>  df33d0b 
>   
> ambari-server/src/main/resources/common-services/HAWQ/2.0.0.0/package/scripts/utils.py
>  b42b3a6 
>   
> ambari-server/src/main/resources/common-services/HAWQ/2.0.0.0/package/templates/hawq.limits.conf.j2
>  93e027c 
>   
> ambari-server/src/main/resources/common-services/HAWQ/2.0.0.0/package/templates/hawq.sysctl.conf.j2
>  480228e 
> 
> Diff: https://reviews.apache.org/r/39524/diff/
> 
> 
> Testing
> ---
> 
> yes
> 
> 
> Thanks,
> 
> bhuvnesh chaudhary
> 
>

Re: Review Request 39536: Ambari Server JVM crashed after several clicks in Web UI to navigate graph timerange

[Sumit Mohanty]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/39536/#review103514
---

Ship it!


Ship It!

- Sumit Mohanty


On Oct. 22, 2015, 1:46 a.m., Sid Wagle wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/39536/
> ---
> 
> (Updated Oct. 22, 2015, 1:46 a.m.)
> 
> 
> Review request for Ambari, Alejandro Fernandez, Dmytro Sen, Jonathan Hurley, 
> and Sumit Mohanty.
> 
> 
> Bugs: AMBARI-13517
> https://issues.apache.org/jira/browse/AMBARI-13517
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> - Max Heap restriction problem: Ehcache library that we use has a limit of 
> how far in the object graph it traverses to find size of an Cached reference, 
> this is to make it performant. Default limit = 1000.
> - User gets following Warning which are harmless unless the data cannot fit 
> in memory and eviction does not kick in:
> 
> WARN [qtp-client-70] ObjectGraphWalker:209 - The configured limit of 1,000 
> object references was reached while attempting to calculate the size of the 
> object graph. Severe performance degradation could occur 
> if the sizing operation continues. This can be avoided by setting the 
> CacheManger or Cache  elements maxDepthExceededBehavior to 
> "abort" or adding stop points with @IgnoreSizeOf annotations. If performance 
> degradation 
> is NOT an issue at the configured limit, raise the limit value using the 
> CacheManager or Cache  elements maxDepth attribute. For more 
> information, see the Ehcache configuration documentation.
> 
> _Objective of the patch_:
> - Provide a custom Sizing engine for Ehcache that will provide a close 
> approximation of the data in the cache with significant perf gain. Premise: 
> Since we know the data structures we can make better estimates.
> - Expectation from sizing engine : Discrepancy of less than 10K for a DS of 
> size 10 MB (Proven with a unit test)
> 
> 
> Diffs
> -
> 
>   
> ambari-metrics/ambari-metrics-common/src/main/java/org/apache/hadoop/metrics2/sink/timeline/TimelineMetric.java
>  8b8df06 
>   
> ambari-metrics/ambari-metrics-common/src/main/java/org/apache/hadoop/metrics2/sink/timeline/cache/TimelineMetricsCache.java
>  224b490 
>   
> ambari-metrics/ambari-metrics-common/src/test/java/org/apache/hadoop/metrics2/sink/timeline/cache/TimelineMetricsCacheTest.java
>  4a13d63 
>   
> ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/HBaseTimelineMetricStore.java
>  9c0b94d 
>   
> ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/PhoenixHBaseAccessor.java
>  9488316 
>   
> ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/aggregators/TimelineMetricReadHelper.java
>  573e09d 
>   
> ambari-metrics/ambari-metrics-timelineservice/src/test/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/ITClusterAggregator.java
>  b7b1737 
>   
> ambari-metrics/ambari-metrics-timelineservice/src/test/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/ITMetricAggregator.java
>  a3640d0 
>   
> ambari-metrics/ambari-metrics-timelineservice/src/test/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/MetricTestHelper.java
>  26771d7 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/metrics/MetricsPaddingMethod.java
>  522c0bd 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/metrics/timeline/cache/TimelineMetricCacheProvider.java
>  6d80687 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/metrics/timeline/cache/TimelineMetricsCacheSizeOfEngine.java
>  PRE-CREATION 
>   
> ambari-server/src/test/java/org/apache/ambari/server/controller/metrics/timeline/MetricsPaddingMethodTest.java
>  c30c5eb 
>   
> ambari-server/src/test/java/org/apache/ambari/server/controller/metrics/timeline/cache/TimelineMetricCacheSizingTest.java
>  PRE-CREATION 
>   
> ambari-server/src/test/java/org/apache/ambari/server/controller/metrics/timeline/cache/TimelineMetricCacheTest.java
>  3432e1d 
> 
> Diff: https://reviews.apache.org/r/39536/diff/
> 
> 
> Testing
> ---
> 
> Relevant unit test pass.
> ambari-server:
>  AMSPropertyProviderTest
>  AMSReportPropertyProviderTest
>  StackDefinedPropertyProviderTest
>  TimelineMetricsCacheTest
>  TimleineMetricsCacheSizingTest
> ambari-metrics:
>  All test passed
> 
> 
> Thanks,
> 
> Sid Wagle
> 
>

Re: Review Request 39536: Ambari Server JVM crashed after several clicks in Web UI to navigate graph timerange

[Sumit Mohanty]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/39536/#review103513
---



ambari-server/src/main/java/org/apache/ambari/server/controller/metrics/timeline/cache/TimelineMetricsCacheSizeOfEngine.java
 (line 37)


Probably a non-issue, but should it be 1 as in initializeCache()


- Sumit Mohanty


On Oct. 22, 2015, 1:46 a.m., Sid Wagle wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/39536/
> ---
> 
> (Updated Oct. 22, 2015, 1:46 a.m.)
> 
> 
> Review request for Ambari, Alejandro Fernandez, Dmytro Sen, Jonathan Hurley, 
> and Sumit Mohanty.
> 
> 
> Bugs: AMBARI-13517
> https://issues.apache.org/jira/browse/AMBARI-13517
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> - Max Heap restriction problem: Ehcache library that we use has a limit of 
> how far in the object graph it traverses to find size of an Cached reference, 
> this is to make it performant. Default limit = 1000.
> - User gets following Warning which are harmless unless the data cannot fit 
> in memory and eviction does not kick in:
> 
> WARN [qtp-client-70] ObjectGraphWalker:209 - The configured limit of 1,000 
> object references was reached while attempting to calculate the size of the 
> object graph. Severe performance degradation could occur 
> if the sizing operation continues. This can be avoided by setting the 
> CacheManger or Cache  elements maxDepthExceededBehavior to 
> "abort" or adding stop points with @IgnoreSizeOf annotations. If performance 
> degradation 
> is NOT an issue at the configured limit, raise the limit value using the 
> CacheManager or Cache  elements maxDepth attribute. For more 
> information, see the Ehcache configuration documentation.
> 
> _Objective of the patch_:
> - Provide a custom Sizing engine for Ehcache that will provide a close 
> approximation of the data in the cache with significant perf gain. Premise: 
> Since we know the data structures we can make better estimates.
> - Expectation from sizing engine : Discrepancy of less than 10K for a DS of 
> size 10 MB (Proven with a unit test)
> 
> 
> Diffs
> -
> 
>   
> ambari-metrics/ambari-metrics-common/src/main/java/org/apache/hadoop/metrics2/sink/timeline/TimelineMetric.java
>  8b8df06 
>   
> ambari-metrics/ambari-metrics-common/src/main/java/org/apache/hadoop/metrics2/sink/timeline/cache/TimelineMetricsCache.java
>  224b490 
>   
> ambari-metrics/ambari-metrics-common/src/test/java/org/apache/hadoop/metrics2/sink/timeline/cache/TimelineMetricsCacheTest.java
>  4a13d63 
>   
> ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/HBaseTimelineMetricStore.java
>  9c0b94d 
>   
> ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/PhoenixHBaseAccessor.java
>  9488316 
>   
> ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/aggregators/TimelineMetricReadHelper.java
>  573e09d 
>   
> ambari-metrics/ambari-metrics-timelineservice/src/test/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/ITClusterAggregator.java
>  b7b1737 
>   
> ambari-metrics/ambari-metrics-timelineservice/src/test/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/ITMetricAggregator.java
>  a3640d0 
>   
> ambari-metrics/ambari-metrics-timelineservice/src/test/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/MetricTestHelper.java
>  26771d7 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/metrics/MetricsPaddingMethod.java
>  522c0bd 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/metrics/timeline/cache/TimelineMetricCacheProvider.java
>  6d80687 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/metrics/timeline/cache/TimelineMetricsCacheSizeOfEngine.java
>  PRE-CREATION 
>   
> ambari-server/src/test/java/org/apache/ambari/server/controller/metrics/timeline/MetricsPaddingMethodTest.java
>  c30c5eb 
>   
> ambari-server/src/test/java/org/apache/ambari/server/controller/metrics/timeline/cache/TimelineMetricCacheSizingTest.java
>  PRE-CREATION 
>   
> ambari-server/src/test/java/org/apache/ambari/server/controller/metrics/timeline/cache/TimelineMetricCacheTest.java
>  3432e1d 
> 
> Diff: https://reviews.apache.org/r/39536/diff/
> 
> 
> Testing
> ---
> 
> Relevant unit test pass.
> ambari-server:
>  AMSPropertyProviderTest
>  AMSReportPropertyProviderTest
>  StackDefinedPropertyProviderTest
> 

[jira] [Commented] (AMBARI-13421) Blueprints: install for Ranger Components (ranger-admin, ranger-usersync, ranger-kms, ...)

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-13421:


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

This message is automatically generated.

> Blueprints: install for Ranger Components (ranger-admin, ranger-usersync, 
> ranger-kms, ...)
> --
>
> Key: AMBARI-13421
> URL: https://issues.apache.org/jira/browse/AMBARI-13421
> Project: Ambari
>  Issue Type: New Feature
>  Components: blueprints
>Affects Versions: 2.0.0
>Reporter: Sebastian Toader
>Assignee: Sebastian Toader
> Attachments: AMBARI-13421.v2.patch
>
>
> Add support for installing Ranger and enabling ranger plugins through 
> Blueprints.



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

[jira] [Commented] (AMBARI-13512) Show a warning popup before user is about to be logged out

[Hudson (JIRA)]

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

Hudson commented on AMBARI-13512:
-

FAILURE: Integrated in Ambari-branch-2.1 #725 (See 
[https://builds.apache.org/job/Ambari-branch-2.1/725/])
AMBARI-13512. Show a warning popup before user is about to be logged out 
(rzang: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=7d7ae0a0d958503705bb293415fee5f9f632ab96])
* 
ambari-admin/src/main/resources/ui/admin-web/app/views/modals/TimeoutWarning.html
* 
ambari-admin/src/main/resources/ui/admin-web/app/scripts/controllers/mainCtrl.js
* ambari-web/app/controllers/main.js
* ambari-web/app/messages.js
* ambari-admin/src/main/resources/ui/admin-web/app/scripts/services/Auth.js
* ambari-web/app/config.js


> Show a warning popup before user is about to be logged out
> --
>
> Key: AMBARI-13512
> URL: https://issues.apache.org/jira/browse/AMBARI-13512
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-admin, ambari-web
>Affects Versions: 2.1.3
>Reporter: Richard Zang
>Assignee: Richard Zang
> Fix For: 2.1.3
>
> Attachments: AMBARI-13512.patch
>
>
> Show a warning popup 60 seconds before user is about to be logged out. It 
> will trigger browser user action when user is actually monitoring the screen 
> which will make the user active again. Otherwise user will be logged out 
> after 60 seconds.
> The warning message should say:
> "You will be automatically logged out in X seconds due to inactivity. [Log 
> Out Now] [Remain Logged In]"
> X should automatically count down from 60, once per second.
> Popup Title:
> Automatic Logout



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

[jira] [Resolved] (AMBARI-13243) Stop-and-Start Upgrade: Support NameNode HA and non-HA

[Alejandro Fernandez (JIRA)]

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

Alejandro Fernandez resolved AMBARI-13243.
--
Resolution: Fixed

Fixed as part of AMBARI-12701

Pushed to trunk
commit 7afe5a4ec9200c41922fb1c0809f34a0d8d700bd

Pushed to branch-2.1
commit 2854b74573cbca468f0fba12de11996c2300547c

> Stop-and-Start Upgrade: Support NameNode HA and non-HA
> --
>
> Key: AMBARI-13243
> URL: https://issues.apache.org/jira/browse/AMBARI-13243
> Project: Ambari
>  Issue Type: Story
>  Components: ambari-server
>Affects Versions: 2.2.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 2.2.0
>
>
> During Stop-the-World upgrade, the PreCheck constraints will be relaxed so 
> that NameNode HA is not a requirement. This means we need to support this 
> mode during upgrade.



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

Review Request 39536: Ambari Server JVM crashed after several clicks in Web UI to navigate graph timerange

[Sid Wagle]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/39536/
---

Review request for Ambari, Alejandro Fernandez, Dmytro Sen, Jonathan Hurley, 
and Sumit Mohanty.


Bugs: AMBARI-13517
https://issues.apache.org/jira/browse/AMBARI-13517


Repository: ambari


Description
---

- Max Heap restriction problem: Ehcache library that we use has a limit of how 
far in the object graph it traverses to find size of an Cached reference, this 
is to make it performant. Default limit = 1000.
- User gets following Warning which are harmless unless the data cannot fit in 
memory and eviction does not kick in:

WARN [qtp-client-70] ObjectGraphWalker:209 - The configured limit of 1,000 
object references was reached while attempting to calculate the size of the 
object graph. Severe performance degradation could occur 
if the sizing operation continues. This can be avoided by setting the 
CacheManger or Cache  elements maxDepthExceededBehavior to 
"abort" or adding stop points with @IgnoreSizeOf annotations. If performance 
degradation 
is NOT an issue at the configured limit, raise the limit value using the 
CacheManager or Cache  elements maxDepth attribute. For more 
information, see the Ehcache configuration documentation.

_Objective of the patch_:
- Provide a custom Sizing engine for Ehcache that will provide a close 
approximation of the data in the cache with significant perf gain. Premise: 
Since we know the data structures we can make better estimates.
- Expectation from sizing engine : Discrepancy of less than 10K for a DS of 
size 10 MB (Proven with a unit test)


Diffs
-

  
ambari-metrics/ambari-metrics-common/src/main/java/org/apache/hadoop/metrics2/sink/timeline/TimelineMetric.java
 8b8df06 
  
ambari-metrics/ambari-metrics-common/src/main/java/org/apache/hadoop/metrics2/sink/timeline/cache/TimelineMetricsCache.java
 224b490 
  
ambari-metrics/ambari-metrics-common/src/test/java/org/apache/hadoop/metrics2/sink/timeline/cache/TimelineMetricsCacheTest.java
 4a13d63 
  
ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/HBaseTimelineMetricStore.java
 9c0b94d 
  
ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/PhoenixHBaseAccessor.java
 9488316 
  
ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/aggregators/TimelineMetricReadHelper.java
 573e09d 
  
ambari-metrics/ambari-metrics-timelineservice/src/test/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/ITClusterAggregator.java
 b7b1737 
  
ambari-metrics/ambari-metrics-timelineservice/src/test/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/ITMetricAggregator.java
 a3640d0 
  
ambari-metrics/ambari-metrics-timelineservice/src/test/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/MetricTestHelper.java
 26771d7 
  
ambari-server/src/main/java/org/apache/ambari/server/controller/metrics/MetricsPaddingMethod.java
 522c0bd 
  
ambari-server/src/main/java/org/apache/ambari/server/controller/metrics/timeline/cache/TimelineMetricCacheProvider.java
 6d80687 
  
ambari-server/src/main/java/org/apache/ambari/server/controller/metrics/timeline/cache/TimelineMetricsCacheSizeOfEngine.java
 PRE-CREATION 
  
ambari-server/src/test/java/org/apache/ambari/server/controller/metrics/timeline/MetricsPaddingMethodTest.java
 c30c5eb 
  
ambari-server/src/test/java/org/apache/ambari/server/controller/metrics/timeline/cache/TimelineMetricCacheSizingTest.java
 PRE-CREATION 
  
ambari-server/src/test/java/org/apache/ambari/server/controller/metrics/timeline/cache/TimelineMetricCacheTest.java
 3432e1d 

Diff: https://reviews.apache.org/r/39536/diff/


Testing
---

Relevant unit test pass.
ambari-server:
 AMSPropertyProviderTest
 AMSReportPropertyProviderTest
 StackDefinedPropertyProviderTest
 TimelineMetricsCacheTest
 TimleineMetricsCacheSizingTest
ambari-metrics:
 All test passed


Thanks,

Sid Wagle

Re: Review Request 39530: Ambari-13513:[trunk][2.1.2] Add cmd option config to spark thrift server

[Sumit Mohanty]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/39530/#review103507
---



ambari-server/src/main/resources/stacks/HDP/2.3/services/SPARK/configuration/spark-thrift-cmd-opts-properties.xml
 (line 21)


What we meant is that you can introduce a property spark-thrift-cmd-opts in 
spark-env.xml and have it contain the value user wants to supply. Then in the 
scripts you can refer to it as spark_thrift_cmd_opts_properties = 
str(config['configurations']['spark-env']['spark-thrift-cmd-opts'])


- Sumit Mohanty


On Oct. 21, 2015, 10:33 p.m., Judy Nash wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/39530/
> ---
> 
> (Updated Oct. 21, 2015, 10:33 p.m.)
> 
> 
> Review request for Ambari, Alejandro Fernandez and Sumit Mohanty.
> 
> 
> Bugs: AMBARI-13513
> https://issues.apache.org/jira/browse/AMBARI-13513
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Ambari-13513:[trunk][2.1.2] Add cmd option config to spark thrift server
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/resources/common-services/SPARK/1.2.0.2.2/package/scripts/params.py
>  518ba6d 
>   
> ambari-server/src/main/resources/common-services/SPARK/1.2.0.2.2/package/scripts/spark_service.py
>  68a395b 
>   
> ambari-server/src/main/resources/stacks/HDP/2.3/services/SPARK/configuration/spark-thrift-cmd-opts-properties.xml
>  PRE-CREATION 
>   ambari-server/src/main/resources/stacks/HDP/2.3/services/SPARK/metainfo.xml 
> 14161b4 
>   ambari-server/src/test/python/stacks/2.3/SPARK/test_spark_thrift_server.py 
> b3b8235 
>   ambari-server/src/test/python/stacks/2.3/configs/spark_default.json 9f3fb90 
> 
> Diff: https://reviews.apache.org/r/39530/diff/
> 
> 
> Testing
> ---
> 
> 1. Updated Unit Tests 
> 2. E2E test on HDInsight cluster
> 
> 
> Thanks,
> 
> Judy Nash
> 
>

[jira] [Updated] (AMBARI-13517) Ambari Server JVM crashed after several clicks in Web UI to navigate graph timerange

[Siddharth Wagle (JIRA)]

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

Siddharth Wagle updated AMBARI-13517:
-
Description: 
- Max Heap restriction problem: Ehcache library that we use has a limit of how 
far in the object graph it traverses to find size of an Cached reference, this 
is to make it performant. Default limit = 1000.
- User gets following Warning which are harmless unless the data cannot fit in 
memory and eviction does not kick in:
{code}
WARN [qtp-client-70] ObjectGraphWalker:209 - The configured limit of 1,000 
object references was reached while attempting to calculate the size of the 
object graph. Severe performance degradation could occur 
if the sizing operation continues. This can be avoided by setting the 
CacheManger or Cache  elements maxDepthExceededBehavior to 
"abort" or adding stop points with @IgnoreSizeOf annotations. If performance 
degradation 
is NOT an issue at the configured limit, raise the limit value using the 
CacheManager or Cache  elements maxDepth attribute. For more 
information, see the Ehcache configuration documentation.
{code}

_Objective of the patch_:
- Provide a custom Sizing engine for Ehcache that will provide a close 
approximation of the data in the cache with significant perf gain. Premise: 
Since we know the data structures we can make better estimates.
- Expectation from sizing engine : Discrepancy of less than 10K for a DS of 
size 10 MB (Proven with a unit test)

  was:
Max Heap restriction problem: Ehcache library that we use has a limit of how 
far in the object graph it traverses to find size of an Cached reference, this 
is to make it performant. Default limit = 1000.
_Objective of the patch_:
- Provide a custom Sizing engine for Ehcache that will provide a close 
approximation of the data in the cache with significant perf gain. Premise: 
Since we know the data structures we can make better estimates.
- Expectation from sizing engine : Discrepancy of less than 10K for a DS of 
size 10 MB (Proven with a unit test)


> Ambari Server JVM crashed after several clicks in Web UI to navigate graph 
> timerange
> 
>
> Key: AMBARI-13517
> URL: https://issues.apache.org/jira/browse/AMBARI-13517
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.1.2
>Reporter: Siddharth Wagle
>Assignee: Siddharth Wagle
>Priority: Critical
> Fix For: 2.1.3
>
>
> - Max Heap restriction problem: Ehcache library that we use has a limit of 
> how far in the object graph it traverses to find size of an Cached reference, 
> this is to make it performant. Default limit = 1000.
> - User gets following Warning which are harmless unless the data cannot fit 
> in memory and eviction does not kick in:
> {code}
> WARN [qtp-client-70] ObjectGraphWalker:209 - The configured limit of 1,000 
> object references was reached while attempting to calculate the size of the 
> object graph. Severe performance degradation could occur 
> if the sizing operation continues. This can be avoided by setting the 
> CacheManger or Cache  elements maxDepthExceededBehavior to 
> "abort" or adding stop points with @IgnoreSizeOf annotations. If performance 
> degradation 
> is NOT an issue at the configured limit, raise the limit value using the 
> CacheManager or Cache  elements maxDepth attribute. For more 
> information, see the Ehcache configuration documentation.
> {code}
> _Objective of the patch_:
> - Provide a custom Sizing engine for Ehcache that will provide a close 
> approximation of the data in the cache with significant perf gain. Premise: 
> Since we know the data structures we can make better estimates.
> - Expectation from sizing engine : Discrepancy of less than 10K for a DS of 
> size 10 MB (Proven with a unit test)



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

[jira] [Created] (AMBARI-13517) Ambari Server JVM crashed after several clicks in Web UI to navigate graph timerange

[Siddharth Wagle (JIRA)]

Siddharth Wagle created AMBARI-13517:


 Summary: Ambari Server JVM crashed after several clicks in Web UI 
to navigate graph timerange
 Key: AMBARI-13517
 URL: https://issues.apache.org/jira/browse/AMBARI-13517
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: 2.1.2
Reporter: Siddharth Wagle
Assignee: Siddharth Wagle
Priority: Critical
 Fix For: 2.1.3


Max Heap restriction problem: Ehcache library that we use has a limit of how 
far in the object graph it traverses to find size of an Cached reference, this 
is to make it performant. Default limit = 1000.
_Objective of the patch_:
- Provide a custom Sizing engine for Ehcache that will provide a close 
approximation of the data in the cache with significant perf gain. Premise: 
Since we know the data structures we can make better estimates.
- Expectation from sizing engine : Discrepancy of less than 10K for a DS of 
size 10 MB (Proven with a unit test)



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

[jira] [Updated] (AMBARI-13158) error message is not accurate when a directory field value has a space

[jun aoki (JIRA)]

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

jun aoki updated AMBARI-13158:
--
Attachment: AMBARI-13158-2.patch

> error message is not accurate when a directory field value has a space 
> ---
>
> Key: AMBARI-13158
> URL: https://issues.apache.org/jira/browse/AMBARI-13158
> Project: Ambari
>  Issue Type: Bug
>Reporter: jun aoki
>Assignee: jun aoki
>Priority: Trivial
> Attachments: AMBARI-13158-2.patch, AMBARI-13158.patch, 
> screenshot-1.png
>
>
> when, for example, dfs.datanode.data.dir.mount.file field in Configs tab has 
> a file path with a space, it warns "Must be a slash or drive at the start", 
> which should be "Wrong path " or something, or maybe a path with space is OK 
> too.



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

Re: Review Request 39530: Ambari-13513:[trunk][2.1.2] Add cmd option config to spark thrift server

[Judy Nash]

> On Oct. 22, 2015, 12:59 a.m., Alejandro Fernandez wrote:
> > ambari-server/src/main/resources/stacks/HDP/2.3/services/SPARK/configuration/spark-thrift-cmd-opts-properties.xml,
> >  line 21
> > 
> >
> > ditto.
> > spark-env file already exists, so can add another property there, 
> > "spark_thrift_content" (or something like it)

Spark-env.sh doesn't have any spark thrift server property that can be used for 
this today. Using spark-env will require an apache spark commit. 

Can't read the property at runtime when kicking off ./start-thriftserver.sh 
neither, as spark-env.sh is not loaded until later at spark-class.sh. 

Are there other ways to make the property value consumable by ambari that I 
have not thought of?


- Judy


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/39530/#review103500
---


On Oct. 21, 2015, 10:33 p.m., Judy Nash wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/39530/
> ---
> 
> (Updated Oct. 21, 2015, 10:33 p.m.)
> 
> 
> Review request for Ambari, Alejandro Fernandez and Sumit Mohanty.
> 
> 
> Bugs: AMBARI-13513
> https://issues.apache.org/jira/browse/AMBARI-13513
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Ambari-13513:[trunk][2.1.2] Add cmd option config to spark thrift server
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/resources/common-services/SPARK/1.2.0.2.2/package/scripts/params.py
>  518ba6d 
>   
> ambari-server/src/main/resources/common-services/SPARK/1.2.0.2.2/package/scripts/spark_service.py
>  68a395b 
>   
> ambari-server/src/main/resources/stacks/HDP/2.3/services/SPARK/configuration/spark-thrift-cmd-opts-properties.xml
>  PRE-CREATION 
>   ambari-server/src/main/resources/stacks/HDP/2.3/services/SPARK/metainfo.xml 
> 14161b4 
>   ambari-server/src/test/python/stacks/2.3/SPARK/test_spark_thrift_server.py 
> b3b8235 
>   ambari-server/src/test/python/stacks/2.3/configs/spark_default.json 9f3fb90 
> 
> Diff: https://reviews.apache.org/r/39530/diff/
> 
> 
> Testing
> ---
> 
> 1. Updated Unit Tests 
> 2. E2E test on HDInsight cluster
> 
> 
> Thanks,
> 
> Judy Nash
> 
>

Re: Review Request 39491: AMBARI-13442: stack advisor layout and validations for HAWQ service master components

[jun aoki]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/39491/#review103504
---



ambari-server/src/main/resources/stacks/HDP/2.3/services/stack_advisor.py (line 
25)


Hi Alejandro,

While being pythonic is right, we found the stack_advisor.py files have the 
naming convention with camelCase, for some reasons.
e.g.

https://github.com/Pivotal-Hadoop/ambari/blob/trunk/ambari-server/src/main/resources/stacks/stack_advisor.py#L331
and

https://github.com/Pivotal-Hadoop/ambari/blob/trunk/ambari-server/src/main/resources/stacks/HDP/2.0.6/services/stack_advisor.py#L35

I initially had a feedback to rename some of the variables but we decided 
to go with the existing convention from HDP stack's.

How about we go with this camelCase here for now, and we will revisit to 
unify the naming convention across other stack_advisor.py files?


- jun aoki


On Oct. 22, 2015, 12:04 a.m., Alexander Denissov wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/39491/
> ---
> 
> (Updated Oct. 22, 2015, 12:04 a.m.)
> 
> 
> Review request for Ambari, Alejandro Fernandez, jun aoki, Jayush Luniya, 
> Mahadev Konar, and Oleksandr Diachenko.
> 
> 
> Bugs: AMBARI-13442
> https://issues.apache.org/jira/browse/AMBARI-13442
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Introduced layout recommendations and validations for Apache HAWQ service 
> master components.
> 
> Test cases use new test json files for input rather than hardcoding data in 
> the test case directly.
> 
> 
> Diffs
> -
> 
>   ambari-server/src/main/resources/stacks/HDP/2.3/services/stack_advisor.py 
> 501517f 
>   ambari-server/src/test/python/stacks/2.3/common/hosts-1-host.json 
> PRE-CREATION 
>   ambari-server/src/test/python/stacks/2.3/common/hosts-3-hosts.json 
> PRE-CREATION 
>   ambari-server/src/test/python/stacks/2.3/common/services-hawq-1-host.json 
> PRE-CREATION 
>   ambari-server/src/test/python/stacks/2.3/common/services-hawq-3-hosts.json 
> PRE-CREATION 
>   
> ambari-server/src/test/python/stacks/2.3/common/services-master_ambari_colo-3-hosts.json
>  PRE-CREATION 
>   
> ambari-server/src/test/python/stacks/2.3/common/services-master_standby_colo-3-hosts.json
>  PRE-CREATION 
>   
> ambari-server/src/test/python/stacks/2.3/common/services-nohawq-3-hosts.json 
> PRE-CREATION 
>   
> ambari-server/src/test/python/stacks/2.3/common/services-normal-hawq-3-hosts.json
>  PRE-CREATION 
>   
> ambari-server/src/test/python/stacks/2.3/common/services-normal-nohawq-3-hosts.json
>  PRE-CREATION 
>   
> ambari-server/src/test/python/stacks/2.3/common/services-standby_ambari_colo-3-hosts.json
>  PRE-CREATION 
>   ambari-server/src/test/python/stacks/2.3/common/test_stack_advisor.py 
> e0c6d28 
> 
> Diff: https://reviews.apache.org/r/39491/diff/
> 
> 
> Testing
> ---
> 
> Added new and ran python unit tests:
> --
> Total run:775
> Total errors:0
> Total failures:0
> OK
> 
> 
> File Attachments
> 
> 
> updated with fix
>   
> https://reviews.apache.org/media/uploaded/files/2015/10/22/b04e7344-e7d7-4577-aa34-d7850f5ef090__AMBARI-13442.patch.1
> 
> 
> Thanks,
> 
> Alexander Denissov
> 
>

[jira] [Updated] (AMBARI-12701) Stop-and-Start Upgrade: Handle Core Services

[Alejandro Fernandez (JIRA)]

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

Alejandro Fernandez updated AMBARI-12701:
-
Attachment: AMBARI-12701.branch-2.1.patch

> Stop-and-Start Upgrade: Handle Core Services
> 
>
> Key: AMBARI-12701
> URL: https://issues.apache.org/jira/browse/AMBARI-12701
> Project: Ambari
>  Issue Type: Story
>  Components: ambari-server
>Affects Versions: 2.2.0, 2.1.3
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>  Labels: branch:branch-dev-stop-all-upgrade
> Fix For: 2.2.0, 2.1.3
>
> Attachments: AMBARI-12701.branch-2.1.patch, AMBARI-12701.trunk.patch
>
>
> Stop-and-Start Upgrade of the Stack to handle core services: HDFS, YARN, MR, 
> ZK



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

[jira] [Updated] (AMBARI-12701) Stop-and-Start Upgrade: Handle Core Services

[Alejandro Fernandez (JIRA)]

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

Alejandro Fernandez updated AMBARI-12701:
-
Attachment: AMBARI-12701.trunk.patch

> Stop-and-Start Upgrade: Handle Core Services
> 
>
> Key: AMBARI-12701
> URL: https://issues.apache.org/jira/browse/AMBARI-12701
> Project: Ambari
>  Issue Type: Story
>  Components: ambari-server
>Affects Versions: 2.2.0, 2.1.3
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>  Labels: branch:branch-dev-stop-all-upgrade
> Fix For: 2.2.0, 2.1.3
>
> Attachments: AMBARI-12701.trunk.patch
>
>
> Stop-and-Start Upgrade of the Stack to handle core services: HDFS, YARN, MR, 
> ZK



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

Re: Review Request 39524: Display sysctl and limits configuration on the HAWQ config UI screen

[Alejandro Fernandez]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/39524/#review103502
---

Ship it!


Ship It!

- Alejandro Fernandez


On Oct. 21, 2015, 8:45 p.m., bhuvnesh chaudhary wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/39524/
> ---
> 
> (Updated Oct. 21, 2015, 8:45 p.m.)
> 
> 
> Review request for Ambari and jun aoki.
> 
> 
> Bugs: AMBARI-13510
> https://issues.apache.org/jira/browse/AMBARI-13510
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> User should be able to see the values of sysctl and limits parameters which 
> are configured for HAWQ.
> Sysctl parameters except vm.overcommit.memory are editable only during 
> install, after install they are read only. overcommit parameter can be 
> changed as needed.
> limits for hawq user(gpadmin) are editable.
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/resources/common-services/HAWQ/2.0.0.0/configuration/hawq-limits-env.xml
>  PRE-CREATION 
>   
> ambari-server/src/main/resources/common-services/HAWQ/2.0.0.0/configuration/hawq-sysctl-env.xml
>  PRE-CREATION 
>   
> ambari-server/src/main/resources/common-services/HAWQ/2.0.0.0/package/scripts/common.py
>  defd87c 
>   
> ambari-server/src/main/resources/common-services/HAWQ/2.0.0.0/package/scripts/constants.py
>  78a636e 
>   
> ambari-server/src/main/resources/common-services/HAWQ/2.0.0.0/package/scripts/hawqstatus.py
>  59742bd 
>   
> ambari-server/src/main/resources/common-services/HAWQ/2.0.0.0/package/scripts/master_helper.py
>  82a5168 
>   
> ambari-server/src/main/resources/common-services/HAWQ/2.0.0.0/package/scripts/params.py
>  df33d0b 
>   
> ambari-server/src/main/resources/common-services/HAWQ/2.0.0.0/package/scripts/utils.py
>  b42b3a6 
>   
> ambari-server/src/main/resources/common-services/HAWQ/2.0.0.0/package/templates/hawq.limits.conf.j2
>  93e027c 
>   
> ambari-server/src/main/resources/common-services/HAWQ/2.0.0.0/package/templates/hawq.sysctl.conf.j2
>  480228e 
> 
> Diff: https://reviews.apache.org/r/39524/diff/
> 
> 
> Testing
> ---
> 
> yes
> 
> 
> Thanks,
> 
> bhuvnesh chaudhary
> 
>

Re: Review Request 39491: AMBARI-13442: stack advisor layout and validations for HAWQ service master components

[Alejandro Fernandez]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/39491/#review103501
---

Ship it!



ambari-server/src/main/resources/stacks/HDP/2.3/services/stack_advisor.py (line 
25)


Please use pythonic_function_names and variables, lowercase and underscores

Also, add some documentation for this function.


- Alejandro Fernandez


On Oct. 22, 2015, 12:04 a.m., Alexander Denissov wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/39491/
> ---
> 
> (Updated Oct. 22, 2015, 12:04 a.m.)
> 
> 
> Review request for Ambari, Alejandro Fernandez, jun aoki, Jayush Luniya, 
> Mahadev Konar, and Oleksandr Diachenko.
> 
> 
> Bugs: AMBARI-13442
> https://issues.apache.org/jira/browse/AMBARI-13442
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Introduced layout recommendations and validations for Apache HAWQ service 
> master components.
> 
> Test cases use new test json files for input rather than hardcoding data in 
> the test case directly.
> 
> 
> Diffs
> -
> 
>   ambari-server/src/main/resources/stacks/HDP/2.3/services/stack_advisor.py 
> 501517f 
>   ambari-server/src/test/python/stacks/2.3/common/hosts-1-host.json 
> PRE-CREATION 
>   ambari-server/src/test/python/stacks/2.3/common/hosts-3-hosts.json 
> PRE-CREATION 
>   ambari-server/src/test/python/stacks/2.3/common/services-hawq-1-host.json 
> PRE-CREATION 
>   ambari-server/src/test/python/stacks/2.3/common/services-hawq-3-hosts.json 
> PRE-CREATION 
>   
> ambari-server/src/test/python/stacks/2.3/common/services-master_ambari_colo-3-hosts.json
>  PRE-CREATION 
>   
> ambari-server/src/test/python/stacks/2.3/common/services-master_standby_colo-3-hosts.json
>  PRE-CREATION 
>   
> ambari-server/src/test/python/stacks/2.3/common/services-nohawq-3-hosts.json 
> PRE-CREATION 
>   
> ambari-server/src/test/python/stacks/2.3/common/services-normal-hawq-3-hosts.json
>  PRE-CREATION 
>   
> ambari-server/src/test/python/stacks/2.3/common/services-normal-nohawq-3-hosts.json
>  PRE-CREATION 
>   
> ambari-server/src/test/python/stacks/2.3/common/services-standby_ambari_colo-3-hosts.json
>  PRE-CREATION 
>   ambari-server/src/test/python/stacks/2.3/common/test_stack_advisor.py 
> e0c6d28 
> 
> Diff: https://reviews.apache.org/r/39491/diff/
> 
> 
> Testing
> ---
> 
> Added new and ran python unit tests:
> --
> Total run:775
> Total errors:0
> Total failures:0
> OK
> 
> 
> File Attachments
> 
> 
> updated with fix
>   
> https://reviews.apache.org/media/uploaded/files/2015/10/22/b04e7344-e7d7-4577-aa34-d7850f5ef090__AMBARI-13442.patch.1
> 
> 
> Thanks,
> 
> Alexander Denissov
> 
>

Re: Review Request 39530: Ambari-13513:[trunk][2.1.2] Add cmd option config to spark thrift server

[Alejandro Fernandez]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/39530/#review103500
---



ambari-server/src/main/resources/stacks/HDP/2.3/services/SPARK/configuration/spark-thrift-cmd-opts-properties.xml
 (line 21)


ditto.
spark-env file already exists, so can add another property there, 
"spark_thrift_content" (or something like it)


- Alejandro Fernandez


On Oct. 21, 2015, 10:33 p.m., Judy Nash wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/39530/
> ---
> 
> (Updated Oct. 21, 2015, 10:33 p.m.)
> 
> 
> Review request for Ambari, Alejandro Fernandez and Sumit Mohanty.
> 
> 
> Bugs: AMBARI-13513
> https://issues.apache.org/jira/browse/AMBARI-13513
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Ambari-13513:[trunk][2.1.2] Add cmd option config to spark thrift server
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/resources/common-services/SPARK/1.2.0.2.2/package/scripts/params.py
>  518ba6d 
>   
> ambari-server/src/main/resources/common-services/SPARK/1.2.0.2.2/package/scripts/spark_service.py
>  68a395b 
>   
> ambari-server/src/main/resources/stacks/HDP/2.3/services/SPARK/configuration/spark-thrift-cmd-opts-properties.xml
>  PRE-CREATION 
>   ambari-server/src/main/resources/stacks/HDP/2.3/services/SPARK/metainfo.xml 
> 14161b4 
>   ambari-server/src/test/python/stacks/2.3/SPARK/test_spark_thrift_server.py 
> b3b8235 
>   ambari-server/src/test/python/stacks/2.3/configs/spark_default.json 9f3fb90 
> 
> Diff: https://reviews.apache.org/r/39530/diff/
> 
> 
> Testing
> ---
> 
> 1. Updated Unit Tests 
> 2. E2E test on HDInsight cluster
> 
> 
> Thanks,
> 
> Judy Nash
> 
>

[jira] [Commented] (AMBARI-13513) Add cmd option config to spark thrift server

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-13513:


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

This message is automatically generated.

> Add cmd option config to spark thrift server 
> -
>
> Key: AMBARI-13513
> URL: https://issues.apache.org/jira/browse/AMBARI-13513
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Affects Versions: trunk
>Reporter: Judy Nash
>Assignee: Judy Nash
> Attachments: SPARK-13513.patch
>
>
> When spark thrift server launches, customers may want to add additional 
> options to configure spark.
> i.e. 
> --driver-memory 
> --jars 
> Some of these configurations can only be submitted as command line options, 
> so adding a new config on ambari to give customers access. 



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

[jira] [Updated] (AMBARI-12701) Stop-and-Start Upgrade: Handle Core Services

[Alejandro Fernandez (JIRA)]

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

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

> Stop-and-Start Upgrade: Handle Core Services
> 
>
> Key: AMBARI-12701
> URL: https://issues.apache.org/jira/browse/AMBARI-12701
> Project: Ambari
>  Issue Type: Story
>  Components: ambari-server
>Affects Versions: 2.2.0, 2.1.3
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>  Labels: branch:branch-dev-stop-all-upgrade
> Fix For: 2.2.0, 2.1.3
>
>
> Stop-and-Start Upgrade of the Stack to handle core services: HDFS, YARN, MR, 
> ZK



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

[jira] [Updated] (AMBARI-12701) Stop-and-Start Upgrade: Handle Core Services

[Alejandro Fernandez (JIRA)]

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

Alejandro Fernandez updated AMBARI-12701:
-
Attachment: (was: AMBARI-12701.branch-2.1.patch)

> Stop-and-Start Upgrade: Handle Core Services
> 
>
> Key: AMBARI-12701
> URL: https://issues.apache.org/jira/browse/AMBARI-12701
> Project: Ambari
>  Issue Type: Story
>  Components: ambari-server
>Affects Versions: 2.2.0, 2.1.3
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>  Labels: branch:branch-dev-stop-all-upgrade
> Fix For: 2.2.0, 2.1.3
>
>
> Stop-and-Start Upgrade of the Stack to handle core services: HDFS, YARN, MR, 
> ZK



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

Re: Review Request 39111: AMBARI-12701. Stop-and-Start Upgrade: Handle Core Services

[Alejandro Fernandez]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/39111/
---

(Updated Oct. 22, 2015, 12:51 a.m.)


Review request for Ambari, Dmytro Grinenko, Dmitro Lisnichenko, Jonathan 
Hurley, and Nate Cole.


Bugs: AMBARI-12701
https://issues.apache.org/jira/browse/AMBARI-12701


Repository: ambari


Description
---

Stop-and-Start Upgrade of the Stack to handle core services: HDFS, YARN, MR, ZK

* Renamed the functions pre_rolling_upgrade and post_rolling_upgrade to 
pre_upgrade_restart and post_upgrade_restart that accept the upgrade_type 
(rolling|nonrolling) as a param.

* When NameNode HA is present, the command used to start NameNode is different 
between the active and the standby, so changed MasterHostResolver.java to pick 
one of the NameNodes to become the active and the other the standby, and pass 
it in a parameter called "desired_namenode_role"

* Wrote a function to take a backup of HDFS

* Changed the "hdfs" command to actually search which one to use depending on 
the stack and version to account for Express Upgrade from HDP 2.1 -> 2.3

* Tested Express Upgrade with and without NameNode HA


Diffs
-

  ambari-common/src/main/python/resource_management/libraries/script/script.py 
efd34e3 
  
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/PreUpgradeCheckResourceProvider.java
 9c5d87a 
  
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/UpgradeResourceProvider.java
 ecf22c2 
  
ambari-server/src/main/java/org/apache/ambari/server/stack/MasterHostResolver.java
 55fb12b 
  ambari-server/src/main/java/org/apache/ambari/server/state/UpgradeHelper.java 
b81d3fd 
  
ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/ClusterGrouping.java
 ba44408 
  
ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/ColocatedGrouping.java
 2aef43c 
  
ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/Grouping.java
 8f23803 
  
ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/ServiceCheckGrouping.java
 af63656 
  
ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/StageWrapper.java
 92df3b5 
  
ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/StageWrapperBuilder.java
 47a28d7 
  
ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/TaskWrapper.java
 f7cc930 
  
ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/TaskWrapperBuilder.java
 a5813e3 
  
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/datanode.py
 fa68435 
  
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/datanode_upgrade.py
 2e5ac19 
  
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_client.py
 dd0dca4 
  
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_namenode.py
 b11d7ea 
  
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/journalnode.py
 46c7272 
  
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/journalnode_upgrade.py
 e2ebbcb 
  
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/namenode.py
 23e775a 
  
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/namenode_ha_state.py
 e8c142c 
  
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/namenode_upgrade.py
 fb39878 
  
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/nfsgateway.py
 be6f0d5 
  
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/params_linux.py
 429ffa9 
  
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/setup_ranger_hdfs.py
 f5df86f 
  
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/snamenode.py
 108ef01 
  
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/utils.py
 d1e764a 
  
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/zkfc_slave.py
 14de094 
  
ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/scripts/application_timeline_server.py
 f3b3d11 
  
ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/scripts/historyserver.py
 229dcd8 
  
ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/scripts/mapreduce2_client.py
 5263d9f 
  
ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/scripts/nodemanager.py
 fd25651 
  
ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/scripts/params_linux.py
 c39e4c4 
  
ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/scripts/resourcemanager.py
 e67f1ce 
  
ambari-server/src/mai

Re: Review Request 39111: AMBARI-12701. Stop-and-Start Upgrade: Handle Core Services

[Alejandro Fernandez]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/39111/
---

(Updated Oct. 22, 2015, 12:50 a.m.)


Review request for Ambari, Dmytro Grinenko, Dmitro Lisnichenko, Jonathan 
Hurley, and Nate Cole.


Summary (updated)
-

AMBARI-12701. Stop-and-Start Upgrade: Handle Core Services


Bugs: AMBARI-12701
https://issues.apache.org/jira/browse/AMBARI-12701


Repository: ambari


Description
---

Stop-and-Start Upgrade of the Stack to handle core services: HDFS, YARN, MR, ZK

* Renamed the functions pre_rolling_upgrade and post_rolling_upgrade to 
pre_upgrade_restart and post_upgrade_restart that accept the upgrade_type 
(rolling|nonrolling) as a param.

* When NameNode HA is present, the command used to start NameNode is different 
between the active and the standby, so changed MasterHostResolver.java to pick 
one of the NameNodes to become the active and the other the standby, and pass 
it in a parameter called "desired_namenode_role"

* Wrote a function to take a backup of HDFS

* Changed the "hdfs" command to actually search which one to use depending on 
the stack and version to account for Express Upgrade from HDP 2.1 -> 2.3

* Tested Express Upgrade with and without NameNode HA


Diffs
-

  ambari-common/src/main/python/resource_management/libraries/script/script.py 
efd34e3 
  
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/PreUpgradeCheckResourceProvider.java
 9c5d87a 
  
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/UpgradeResourceProvider.java
 ecf22c2 
  
ambari-server/src/main/java/org/apache/ambari/server/stack/MasterHostResolver.java
 55fb12b 
  ambari-server/src/main/java/org/apache/ambari/server/state/UpgradeHelper.java 
b81d3fd 
  
ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/ClusterGrouping.java
 ba44408 
  
ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/ColocatedGrouping.java
 2aef43c 
  
ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/Grouping.java
 8f23803 
  
ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/ServiceCheckGrouping.java
 af63656 
  
ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/StageWrapper.java
 92df3b5 
  
ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/StageWrapperBuilder.java
 47a28d7 
  
ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/TaskWrapper.java
 f7cc930 
  
ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/TaskWrapperBuilder.java
 a5813e3 
  
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/datanode.py
 fa68435 
  
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/datanode_upgrade.py
 2e5ac19 
  
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_client.py
 dd0dca4 
  
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_namenode.py
 b11d7ea 
  
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/journalnode.py
 46c7272 
  
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/journalnode_upgrade.py
 e2ebbcb 
  
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/namenode.py
 23e775a 
  
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/namenode_ha_state.py
 e8c142c 
  
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/namenode_upgrade.py
 fb39878 
  
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/nfsgateway.py
 be6f0d5 
  
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/params_linux.py
 429ffa9 
  
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/setup_ranger_hdfs.py
 f5df86f 
  
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/snamenode.py
 108ef01 
  
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/utils.py
 d1e764a 
  
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/zkfc_slave.py
 14de094 
  
ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/scripts/application_timeline_server.py
 f3b3d11 
  
ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/scripts/historyserver.py
 229dcd8 
  
ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/scripts/mapreduce2_client.py
 5263d9f 
  
ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/scripts/nodemanager.py
 fd25651 
  
ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/scripts/params_linux.py
 c39e4c4 
  
ambari-server/src/main/resources/co

[jira] [Updated] (AMBARI-12701) Stop-and-Start Upgrade: Handle Core Services

[Alejandro Fernandez (JIRA)]

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

Alejandro Fernandez updated AMBARI-12701:
-
Attachment: AMBARI-12701.trunk.patch
AMBARI-12701.branch-2.1.patch

> Stop-and-Start Upgrade: Handle Core Services
> 
>
> Key: AMBARI-12701
> URL: https://issues.apache.org/jira/browse/AMBARI-12701
> Project: Ambari
>  Issue Type: Story
>  Components: ambari-server
>Affects Versions: 2.2.0, 2.1.3
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>  Labels: branch:branch-dev-stop-all-upgrade
> Fix For: 2.2.0, 2.1.3
>
> Attachments: AMBARI-12701.branch-2.1.patch, AMBARI-12701.trunk.patch
>
>
> Stop-and-Start Upgrade of the Stack to handle core services: HDFS, YARN, MR, 
> ZK



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

[jira] [Updated] (AMBARI-12701) Stop-and-Start Upgrade: Handle Core Services

[Alejandro Fernandez (JIRA)]

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

Alejandro Fernandez updated AMBARI-12701:
-
Attachment: (was: AMBARI-12701.branch-2.1.patch)

> Stop-and-Start Upgrade: Handle Core Services
> 
>
> Key: AMBARI-12701
> URL: https://issues.apache.org/jira/browse/AMBARI-12701
> Project: Ambari
>  Issue Type: Story
>  Components: ambari-server
>Affects Versions: 2.2.0, 2.1.3
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>  Labels: branch:branch-dev-stop-all-upgrade
> Fix For: 2.2.0, 2.1.3
>
>
> Stop-and-Start Upgrade of the Stack to handle core services: HDFS, YARN, MR, 
> ZK



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

[jira] [Updated] (AMBARI-12701) Stop-and-Start Upgrade: Handle Core Services

[Alejandro Fernandez (JIRA)]

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

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

> Stop-and-Start Upgrade: Handle Core Services
> 
>
> Key: AMBARI-12701
> URL: https://issues.apache.org/jira/browse/AMBARI-12701
> Project: Ambari
>  Issue Type: Story
>  Components: ambari-server
>Affects Versions: 2.2.0, 2.1.3
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>  Labels: branch:branch-dev-stop-all-upgrade
> Fix For: 2.2.0, 2.1.3
>
>
> Stop-and-Start Upgrade of the Stack to handle core services: HDFS, YARN, MR, 
> ZK



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

Re: Review Request 39111: [PREVIEW] Stop-and-Start Upgrade: Handle Core Services

[Alejandro Fernandez]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/39111/
---

(Updated Oct. 22, 2015, 12:50 a.m.)


Review request for Ambari, Dmytro Grinenko, Dmitro Lisnichenko, Jonathan 
Hurley, and Nate Cole.


Changes
---

Fixed unit tests, and addressed comments.


Bugs: AMBARI-12701
https://issues.apache.org/jira/browse/AMBARI-12701


Repository: ambari


Description
---

Stop-and-Start Upgrade of the Stack to handle core services: HDFS, YARN, MR, ZK

* Renamed the functions pre_rolling_upgrade and post_rolling_upgrade to 
pre_upgrade_restart and post_upgrade_restart that accept the upgrade_type 
(rolling|nonrolling) as a param.

* When NameNode HA is present, the command used to start NameNode is different 
between the active and the standby, so changed MasterHostResolver.java to pick 
one of the NameNodes to become the active and the other the standby, and pass 
it in a parameter called "desired_namenode_role"

* Wrote a function to take a backup of HDFS

* Changed the "hdfs" command to actually search which one to use depending on 
the stack and version to account for Express Upgrade from HDP 2.1 -> 2.3

* Tested Express Upgrade with and without NameNode HA


Diffs (updated)
-

  ambari-common/src/main/python/resource_management/libraries/script/script.py 
efd34e3 
  
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/PreUpgradeCheckResourceProvider.java
 9c5d87a 
  
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/UpgradeResourceProvider.java
 ecf22c2 
  
ambari-server/src/main/java/org/apache/ambari/server/stack/MasterHostResolver.java
 55fb12b 
  ambari-server/src/main/java/org/apache/ambari/server/state/UpgradeHelper.java 
b81d3fd 
  
ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/ClusterGrouping.java
 ba44408 
  
ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/ColocatedGrouping.java
 2aef43c 
  
ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/Grouping.java
 8f23803 
  
ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/ServiceCheckGrouping.java
 af63656 
  
ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/StageWrapper.java
 92df3b5 
  
ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/StageWrapperBuilder.java
 47a28d7 
  
ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/TaskWrapper.java
 f7cc930 
  
ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/TaskWrapperBuilder.java
 a5813e3 
  
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/datanode.py
 fa68435 
  
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/datanode_upgrade.py
 2e5ac19 
  
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_client.py
 dd0dca4 
  
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_namenode.py
 b11d7ea 
  
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/journalnode.py
 46c7272 
  
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/journalnode_upgrade.py
 e2ebbcb 
  
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/namenode.py
 23e775a 
  
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/namenode_ha_state.py
 e8c142c 
  
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/namenode_upgrade.py
 fb39878 
  
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/nfsgateway.py
 be6f0d5 
  
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/params_linux.py
 429ffa9 
  
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/setup_ranger_hdfs.py
 f5df86f 
  
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/snamenode.py
 108ef01 
  
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/utils.py
 d1e764a 
  
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/zkfc_slave.py
 14de094 
  
ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/scripts/application_timeline_server.py
 f3b3d11 
  
ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/scripts/historyserver.py
 229dcd8 
  
ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/scripts/mapreduce2_client.py
 5263d9f 
  
ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/scripts/nodemanager.py
 fd25651 
  
ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/scripts/params_linux.py
 c39e4c4 
  
ambari-server/src/main/resources/common-services/YARN/2.1.0.2.

Re: Review Request 39530: Ambari-13513:[trunk][2.1.2] Add cmd option config to spark thrift server

[Sumit Mohanty]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/39530/#review103499
---



ambari-server/src/main/resources/stacks/HDP/2.3/services/SPARK/configuration/spark-thrift-cmd-opts-properties.xml
 (line 21)


Why don't we add it to spark-env? Generally, env property files are for all 
properties that influence env.sh file or the start up parameters.


- Sumit Mohanty


On Oct. 21, 2015, 10:33 p.m., Judy Nash wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/39530/
> ---
> 
> (Updated Oct. 21, 2015, 10:33 p.m.)
> 
> 
> Review request for Ambari, Alejandro Fernandez and Sumit Mohanty.
> 
> 
> Bugs: AMBARI-13513
> https://issues.apache.org/jira/browse/AMBARI-13513
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Ambari-13513:[trunk][2.1.2] Add cmd option config to spark thrift server
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/resources/common-services/SPARK/1.2.0.2.2/package/scripts/params.py
>  518ba6d 
>   
> ambari-server/src/main/resources/common-services/SPARK/1.2.0.2.2/package/scripts/spark_service.py
>  68a395b 
>   
> ambari-server/src/main/resources/stacks/HDP/2.3/services/SPARK/configuration/spark-thrift-cmd-opts-properties.xml
>  PRE-CREATION 
>   ambari-server/src/main/resources/stacks/HDP/2.3/services/SPARK/metainfo.xml 
> 14161b4 
>   ambari-server/src/test/python/stacks/2.3/SPARK/test_spark_thrift_server.py 
> b3b8235 
>   ambari-server/src/test/python/stacks/2.3/configs/spark_default.json 9f3fb90 
> 
> Diff: https://reviews.apache.org/r/39530/diff/
> 
> 
> Testing
> ---
> 
> 1. Updated Unit Tests 
> 2. E2E test on HDInsight cluster
> 
> 
> Thanks,
> 
> Judy Nash
> 
>

[jira] [Updated] (AMBARI-12701) Stop-and-Start Upgrade: Handle Core Services

[Alejandro Fernandez (JIRA)]

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

Alejandro Fernandez updated AMBARI-12701:
-
Fix Version/s: 2.1.3

> Stop-and-Start Upgrade: Handle Core Services
> 
>
> Key: AMBARI-12701
> URL: https://issues.apache.org/jira/browse/AMBARI-12701
> Project: Ambari
>  Issue Type: Story
>  Components: ambari-server
>Affects Versions: 2.2.0, 2.1.3
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>  Labels: branch:branch-dev-stop-all-upgrade
> Fix For: 2.2.0, 2.1.3
>
>
> Stop-and-Start Upgrade of the Stack to handle core services: HDFS, YARN, MR, 
> ZK



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

[jira] [Updated] (AMBARI-12701) Stop-and-Start Upgrade: Handle Core Services

[Alejandro Fernandez (JIRA)]

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

Alejandro Fernandez updated AMBARI-12701:
-
Affects Version/s: (was: 2.2.0)
   2.1.3

> Stop-and-Start Upgrade: Handle Core Services
> 
>
> Key: AMBARI-12701
> URL: https://issues.apache.org/jira/browse/AMBARI-12701
> Project: Ambari
>  Issue Type: Story
>  Components: ambari-server
>Affects Versions: 2.2.0, 2.1.3
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>  Labels: branch:branch-dev-stop-all-upgrade
> Fix For: 2.2.0, 2.1.3
>
>
> Stop-and-Start Upgrade of the Stack to handle core services: HDFS, YARN, MR, 
> ZK



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

[jira] [Updated] (AMBARI-12701) Stop-and-Start Upgrade: Handle Core Services

[Alejandro Fernandez (JIRA)]

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

Alejandro Fernandez updated AMBARI-12701:
-
Affects Version/s: 2.2.0

> Stop-and-Start Upgrade: Handle Core Services
> 
>
> Key: AMBARI-12701
> URL: https://issues.apache.org/jira/browse/AMBARI-12701
> Project: Ambari
>  Issue Type: Story
>  Components: ambari-server
>Affects Versions: 2.2.0, 2.1.3
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>  Labels: branch:branch-dev-stop-all-upgrade
> Fix For: 2.2.0, 2.1.3
>
>
> Stop-and-Start Upgrade of the Stack to handle core services: HDFS, YARN, MR, 
> ZK



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

[jira] [Commented] (AMBARI-13513) Add cmd option config to spark thrift server

[Judy Nash (JIRA)]

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

Judy Nash commented on AMBARI-13513:


Here it is: https://reviews.apache.org/r/39530/


> Add cmd option config to spark thrift server 
> -
>
> Key: AMBARI-13513
> URL: https://issues.apache.org/jira/browse/AMBARI-13513
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Affects Versions: trunk
>Reporter: Judy Nash
>Assignee: Judy Nash
> Attachments: SPARK-13513.patch
>
>
> When spark thrift server launches, customers may want to add additional 
> options to configure spark.
> i.e. 
> --driver-memory 
> --jars 
> Some of these configurations can only be submitted as command line options, 
> so adding a new config on ambari to give customers access. 



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

[jira] [Commented] (AMBARI-13513) Add cmd option config to spark thrift server

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty commented on AMBARI-13513:


[~judynash] can you create a review request?

> Add cmd option config to spark thrift server 
> -
>
> Key: AMBARI-13513
> URL: https://issues.apache.org/jira/browse/AMBARI-13513
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Affects Versions: trunk
>Reporter: Judy Nash
>Assignee: Judy Nash
> Attachments: SPARK-13513.patch
>
>
> When spark thrift server launches, customers may want to add additional 
> options to configure spark.
> i.e. 
> --driver-memory 
> --jars 
> Some of these configurations can only be submitted as command line options, 
> so adding a new config on ambari to give customers access. 



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

[jira] [Commented] (AMBARI-13512) Show a warning popup before user is about to be logged out

[Hudson (JIRA)]

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

Hudson commented on AMBARI-13512:
-

SUCCESS: Integrated in Ambari-trunk-Commit #3690 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/3690/])
AMBARI-13512. Show a warning popup before user is about to be logged out 
(rzang: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=ac51d8b6cee62aee30b940d38da10f0f266ba7a5])
* ambari-web/app/controllers/main.js
* ambari-admin/src/main/resources/ui/admin-web/app/scripts/services/Auth.js
* 
ambari-admin/src/main/resources/ui/admin-web/app/views/modals/TimeoutWarning.html
* ambari-web/app/config.js
* ambari-web/app/messages.js
* 
ambari-admin/src/main/resources/ui/admin-web/app/scripts/controllers/mainCtrl.js


> Show a warning popup before user is about to be logged out
> --
>
> Key: AMBARI-13512
> URL: https://issues.apache.org/jira/browse/AMBARI-13512
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-admin, ambari-web
>Affects Versions: 2.1.3
>Reporter: Richard Zang
>Assignee: Richard Zang
> Fix For: 2.1.3
>
> Attachments: AMBARI-13512.patch
>
>
> Show a warning popup 60 seconds before user is about to be logged out. It 
> will trigger browser user action when user is actually monitoring the screen 
> which will make the user active again. Otherwise user will be logged out 
> after 60 seconds.
> The warning message should say:
> "You will be automatically logged out in X seconds due to inactivity. [Log 
> Out Now] [Remain Logged In]"
> X should automatically count down from 60, once per second.
> Popup Title:
> Automatic Logout



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

[jira] [Commented] (AMBARI-13469) spelling mistake in the help message for max capacity in capacity scheduler

[Hudson (JIRA)]

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

Hudson commented on AMBARI-13469:
-

SUCCESS: Integrated in Ambari-trunk-Commit #3690 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/3690/])
AMBARI-13469. spelling mistake in the help message for max capacity in (yusaku: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=a5162a71c4a03d3ac803c69e17492132b829fd9c])
* 
contrib/views/capacity-scheduler/src/main/resources/ui/app/templates/capacityEditForm.hbs


> spelling mistake in the help message for max capacity in capacity scheduler
> ---
>
> Key: AMBARI-13469
> URL: https://issues.apache.org/jira/browse/AMBARI-13469
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.1.2
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
> Fix For: 2.1.3
>
> Attachments: AMBARI-13469_branch-2.1.patch, message.jpg
>
>
> On the capacity scheduler page the help message for max capacity has a 
> spelling mistake where it says quire instead of queue



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

[jira] [Commented] (AMBARI-13479) Handle derivation of hawq's yarn related parameters where yarn is not configured

[Hudson (JIRA)]

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

Hudson commented on AMBARI-13479:
-

SUCCESS: Integrated in Ambari-trunk-Commit #3690 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/3690/])
AMBARI-13479: Handle derivation of hawq's yarn related parameters where (jaoki: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=844b1e9d3effd2d9d54d8b75532d208e1c629e40])
* ambari-web/app/utils/configs/config_property_helper.js


> Handle derivation of hawq's yarn related parameters where yarn is not 
> configured
> 
>
> Key: AMBARI-13479
> URL: https://issues.apache.org/jira/browse/AMBARI-13479
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: trunk
>Reporter: bhuvnesh chaudhary
>Assignee: bhuvnesh chaudhary
> Attachments: AMBARI-13479.patch
>
>
> In ambari-web/app/utils/configs/config_property_helper.js, the value of 
> masterComponentHostsInDB.findProperty('component', 
> 'RESOURCEMANAGER').hostName is calculated irrespective if Yarn 
> resourcemanager is configured or not. In cases, where Yarn resourcemanager is 
> not configured, masterComponentHostsInDB.findProperty('component', 
> 'RESOURCEMANAGER') will result in undefined and will eventually result in 
> Uncaught TypeError while trying to get the value of hostName.



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

[jira] [Commented] (AMBARI-13482) [CapSchedView] Mappings should be validated and invalid mappings should be disallowed

[Hudson (JIRA)]

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

Hudson commented on AMBARI-13482:
-

SUCCESS: Integrated in Ambari-trunk-Commit #3690 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/3690/])
AMBARI-13482. [CapSchedView] Mappings should be validated and invalid (yusaku: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=383aac0f581e833614b4307635d263e90ad90171])
* 
contrib/views/capacity-scheduler/src/main/resources/ui/app/templates/schedulerPanel.hbs
* 
contrib/views/capacity-scheduler/src/main/resources/ui/app/controllers/queues.js


> [CapSchedView] Mappings should be validated and invalid mappings should be 
> disallowed
> -
>
> Key: AMBARI-13482
> URL: https://issues.apache.org/jira/browse/AMBARI-13482
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.1.0
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
> Fix For: 2.1.3
>
> Attachments: AMBARI-13482_branch-2.1.patch
>
>
> Invalid queue mappings should not be allowed



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

[jira] [Commented] (AMBARI-13483) [CapSchedView] show leaf and non-leaf queues with different UI indicators

[Hudson (JIRA)]

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

Hudson commented on AMBARI-13483:
-

SUCCESS: Integrated in Ambari-trunk-Commit #3690 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/3690/])
AMBARI-13483. [CapSchedView] show leaf and non-leaf queues with (yusaku: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=8ef5beb857cc4c1fa077bdf2e0dbb1bc55ebb2f5])
* 
contrib/views/capacity-scheduler/src/main/resources/ui/app/templates/components/queueListItem.hbs


> [CapSchedView] show leaf and non-leaf queues with different UI indicators
> -
>
> Key: AMBARI-13483
> URL: https://issues.apache.org/jira/browse/AMBARI-13483
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.1.0
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
> Fix For: 2.1.3
>
> Attachments: AMBARI-13483_branch-2.1.patch
>
>




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

[jira] [Created] (AMBARI-13516) HAWQ service's order is not available in role_command_order.js

[Mithun Mathew (JIRA)]

Mithun Mathew created AMBARI-13516:
--

 Summary: HAWQ service's order is not available in 
role_command_order.js
 Key: AMBARI-13516
 URL: https://issues.apache.org/jira/browse/AMBARI-13516
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Reporter: Mithun Mathew
Assignee: Mithun Mathew
Priority: Minor


HAWQ dependencies are not available in role_command_order.js. Ensure that these 
dependencies are mentioned in this file.



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

[jira] [Commented] (AMBARI-13482) [CapSchedView] Mappings should be validated and invalid mappings should be disallowed

[Hudson (JIRA)]

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

Hudson commented on AMBARI-13482:
-

FAILURE: Integrated in Ambari-branch-2.1 #724 (See 
[https://builds.apache.org/job/Ambari-branch-2.1/724/])
AMBARI-13482. [CapSchedView] Mappings should be validated and invalid (yusaku: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=086633ab60e8500c1e43a9a8a578e12d27d2a644])
* 
contrib/views/capacity-scheduler/src/main/resources/ui/app/templates/schedulerPanel.hbs
* 
contrib/views/capacity-scheduler/src/main/resources/ui/app/controllers/queues.js


> [CapSchedView] Mappings should be validated and invalid mappings should be 
> disallowed
> -
>
> Key: AMBARI-13482
> URL: https://issues.apache.org/jira/browse/AMBARI-13482
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.1.0
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
> Fix For: 2.1.3
>
> Attachments: AMBARI-13482_branch-2.1.patch
>
>
> Invalid queue mappings should not be allowed



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

[jira] [Commented] (AMBARI-13483) [CapSchedView] show leaf and non-leaf queues with different UI indicators

[Hudson (JIRA)]

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

Hudson commented on AMBARI-13483:
-

FAILURE: Integrated in Ambari-branch-2.1 #724 (See 
[https://builds.apache.org/job/Ambari-branch-2.1/724/])
AMBARI-13483. [CapSchedView] show leaf and non-leaf queues with (yusaku: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=e75960bb9aee4e5b8e6d721b84409aeb6f0e0c10])
* 
contrib/views/capacity-scheduler/src/main/resources/ui/app/templates/components/queueListItem.hbs


> [CapSchedView] show leaf and non-leaf queues with different UI indicators
> -
>
> Key: AMBARI-13483
> URL: https://issues.apache.org/jira/browse/AMBARI-13483
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.1.0
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
> Fix For: 2.1.3
>
> Attachments: AMBARI-13483_branch-2.1.patch
>
>




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

[jira] [Commented] (AMBARI-13469) spelling mistake in the help message for max capacity in capacity scheduler

[Hudson (JIRA)]

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

Hudson commented on AMBARI-13469:
-

FAILURE: Integrated in Ambari-branch-2.1 #724 (See 
[https://builds.apache.org/job/Ambari-branch-2.1/724/])
AMBARI-13469. spelling mistake in the help message for max capacity in (yusaku: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=35f639ccb1e69c9699fc40a802898020985805a9])
* 
contrib/views/capacity-scheduler/src/main/resources/ui/app/templates/capacityEditForm.hbs


> spelling mistake in the help message for max capacity in capacity scheduler
> ---
>
> Key: AMBARI-13469
> URL: https://issues.apache.org/jira/browse/AMBARI-13469
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.1.2
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
> Fix For: 2.1.3
>
> Attachments: AMBARI-13469_branch-2.1.patch, message.jpg
>
>
> On the capacity scheduler page the help message for max capacity has a 
> spelling mistake where it says quire instead of queue



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

[jira] [Updated] (AMBARI-13515) When both RM are standby, Tez view can not be seen

[DIPAYAN BHOWMICK (JIRA)]

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

DIPAYAN BHOWMICK updated AMBARI-13515:
--
Attachment: Screen Shot 2015-10-21 at 4.05.42 PM.png

> When both RM are standby, Tez view can not be seen
> --
>
> Key: AMBARI-13515
> URL: https://issues.apache.org/jira/browse/AMBARI-13515
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.1.2
>Reporter: DIPAYAN BHOWMICK
>Assignee: DIPAYAN BHOWMICK
> Fix For: 2.1.3
>
> Attachments: AMBARI-13515_branch-2.1.patch, Screen Shot 2015-10-21 at 
> 4.05.42 PM.png
>
>
> Steps :
> 1) Run a tez application
> 2) open Dag detail page for this application
> 3) Make both RMs to be standby (by stopping 2/3 Zks )
> 4) Refresh the tez view: dag detail page
> Here, the page remains blank and /status call gives 500 error without any 
> error displayed on the screen



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

[jira] [Updated] (AMBARI-13515) When both RM are standby, Tez view can not be seen

[DIPAYAN BHOWMICK (JIRA)]

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

DIPAYAN BHOWMICK updated AMBARI-13515:
--
Attachment: AMBARI-13515_branch-2.1.patch

> When both RM are standby, Tez view can not be seen
> --
>
> Key: AMBARI-13515
> URL: https://issues.apache.org/jira/browse/AMBARI-13515
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.1.2
>Reporter: DIPAYAN BHOWMICK
>Assignee: DIPAYAN BHOWMICK
> Fix For: 2.1.3
>
> Attachments: AMBARI-13515_branch-2.1.patch, Screen Shot 2015-10-21 at 
> 4.05.42 PM.png
>
>
> Steps :
> 1) Run a tez application
> 2) open Dag detail page for this application
> 3) Make both RMs to be standby (by stopping 2/3 Zks )
> 4) Refresh the tez view: dag detail page
> Here, the page remains blank and /status call gives 500 error without any 
> error displayed on the screen



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

Re: Review Request 39491: AMBARI-13442: stack advisor layout and validations for HAWQ service master components

[Alexander Denissov]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/39491/
---

(Updated Oct. 22, 2015, 12:04 a.m.)


Review request for Ambari, Alejandro Fernandez, jun aoki, Jayush Luniya, 
Mahadev Konar, and Oleksandr Diachenko.


Changes
---

updated with code review fix


Bugs: AMBARI-13442
https://issues.apache.org/jira/browse/AMBARI-13442


Repository: ambari


Description
---

Introduced layout recommendations and validations for Apache HAWQ service 
master components.

Test cases use new test json files for input rather than hardcoding data in the 
test case directly.


Diffs (updated)
-

  ambari-server/src/main/resources/stacks/HDP/2.3/services/stack_advisor.py 
501517f 
  ambari-server/src/test/python/stacks/2.3/common/hosts-1-host.json 
PRE-CREATION 
  ambari-server/src/test/python/stacks/2.3/common/hosts-3-hosts.json 
PRE-CREATION 
  ambari-server/src/test/python/stacks/2.3/common/services-hawq-1-host.json 
PRE-CREATION 
  ambari-server/src/test/python/stacks/2.3/common/services-hawq-3-hosts.json 
PRE-CREATION 
  
ambari-server/src/test/python/stacks/2.3/common/services-master_ambari_colo-3-hosts.json
 PRE-CREATION 
  
ambari-server/src/test/python/stacks/2.3/common/services-master_standby_colo-3-hosts.json
 PRE-CREATION 
  ambari-server/src/test/python/stacks/2.3/common/services-nohawq-3-hosts.json 
PRE-CREATION 
  
ambari-server/src/test/python/stacks/2.3/common/services-normal-hawq-3-hosts.json
 PRE-CREATION 
  
ambari-server/src/test/python/stacks/2.3/common/services-normal-nohawq-3-hosts.json
 PRE-CREATION 
  
ambari-server/src/test/python/stacks/2.3/common/services-standby_ambari_colo-3-hosts.json
 PRE-CREATION 
  ambari-server/src/test/python/stacks/2.3/common/test_stack_advisor.py e0c6d28 

Diff: https://reviews.apache.org/r/39491/diff/


Testing
---

Added new and ran python unit tests:
--
Total run:775
Total errors:0
Total failures:0
OK


File Attachments (updated)


updated with fix
  
https://reviews.apache.org/media/uploaded/files/2015/10/22/b04e7344-e7d7-4577-aa34-d7850f5ef090__AMBARI-13442.patch.1


Thanks,

Alexander Denissov

[jira] [Updated] (AMBARI-13442) stack advisor layout and validations for HAWQ service master components

[Alexander Denissov (JIRA)]

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

Alexander Denissov updated AMBARI-13442:

Attachment: AMBARI-13442.patch.1

fixed review comments

> stack advisor layout and validations for HAWQ service master components
> ---
>
> Key: AMBARI-13442
> URL: https://issues.apache.org/jira/browse/AMBARI-13442
> Project: Ambari
>  Issue Type: Story
>Affects Versions: 2.1.2
>Reporter: Alexander Denissov
>Assignee: Alexander Denissov
> Fix For: 2.1.3
>
> Attachments: AMBARI-13442.patch, AMBARI-13442.patch.1
>
>
> Apache HAWQ will be a common service. When installing the service via UI 
> wizard, HAWQ Master and HAWQ Standby Master need to be placed on master 
> nodes. They should not be collocated with each other (causing an ERROR 
> message) and with Ambari Server (causing a WARN message).



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

[jira] [Created] (AMBARI-13515) When both RM are standby, Tez view can not be seen

[DIPAYAN BHOWMICK (JIRA)]

DIPAYAN BHOWMICK created AMBARI-13515:
-

 Summary: When both RM are standby, Tez view can not be seen
 Key: AMBARI-13515
 URL: https://issues.apache.org/jira/browse/AMBARI-13515
 Project: Ambari
  Issue Type: Bug
  Components: ambari-views
Affects Versions: 2.1.2
Reporter: DIPAYAN BHOWMICK
Assignee: DIPAYAN BHOWMICK
 Fix For: 2.1.3


Steps :
1) Run a tez application
2) open Dag detail page for this application
3) Make both RMs to be standby (by stopping 2/3 Zks )
4) Refresh the tez view: dag detail page
Here, the page remains blank and /status call gives 500 error without any error 
displayed on the screen



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

[jira] [Commented] (AMBARI-13158) error message is not accurate when a directory field value has a space

[Newton Alex (JIRA)]

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

Newton Alex commented on AMBARI-13158:
--

Spoke to Jun. Since the scope of this ticket was only with the error msg, I 
guess we can decide to fix the isValidDir() in a different ticket.

Small wording recommendation: 
'Must be a slash or drive at the start; and must not contain white spaces'

> error message is not accurate when a directory field value has a space 
> ---
>
> Key: AMBARI-13158
> URL: https://issues.apache.org/jira/browse/AMBARI-13158
> Project: Ambari
>  Issue Type: Bug
>Reporter: jun aoki
>Assignee: jun aoki
>Priority: Trivial
> Attachments: AMBARI-13158.patch, screenshot-1.png
>
>
> when, for example, dfs.datanode.data.dir.mount.file field in Configs tab has 
> a file path with a space, it warns "Must be a slash or drive at the start", 
> which should be "Wrong path " or something, or maybe a path with space is OK 
> too.



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

Review request: 39524 / JIRA Number: AMBARI-13510

[Bhuvnesh Chaudhary]

Team,

For your review: https://reviews.apache.org/r/39524/

Thanks,
Bhuvnesh Chaudhary
Email: bchau dh...@pivotal.io
Desk: +1-650-846-1696 | Mobile: +1-973-906-6976

[jira] [Created] (AMBARI-13514) Service deploy wizard is not always restored to the correct state If browser session is lost while deploy is running

[Sangeeta Ravindran (JIRA)]

Sangeeta Ravindran created AMBARI-13514:
---

 Summary: Service deploy wizard is not always restored to the 
correct state If browser session is lost while deploy is running
 Key: AMBARI-13514
 URL: https://issues.apache.org/jira/browse/AMBARI-13514
 Project: Ambari
  Issue Type: Bug
  Components: ambari-web
Affects Versions: 2.1.0
Reporter: Sangeeta Ravindran


Reproduction Steps: 

1.Select one or more services and click on "Deploy" button. While deploy is 
running, kill the browser.
2. Restart web browser and login to ambari-server. The UI will go back to the 
service deploy wizard review page.
3. Click on "Deploy" again and you will get an error indicating that you are 
trying to add a service that is already installed.

for e.g.
org.apache.ambari.server.controller.spi.ResourceAlreadyExistsException: 
Attempted to create a host_component which already exists: 
[clusterName=hdpcluster, hostName=myhost.mydomain.com componentName=HDFS_CLIENT]

This happens because the services have now either already been deployed or are 
in the middle of deploying. 

The only way to recover is to exit out of the wizard by clicking on the X at 
the right hand top edge.

Expected results: 

Ambari should either retrieve the status of the deploy wizard to reflect the 
actual state of deploy, or go back to the dash board if browser session is lost.



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

Review Request 39530: Ambari-13513:[trunk][2.1.2] Add cmd option config to spark thrift server

[Judy Nash]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/39530/
---

Review request for Ambari, Alejandro Fernandez and Sumit Mohanty.


Bugs: AMBARI-13513
https://issues.apache.org/jira/browse/AMBARI-13513


Repository: ambari


Description
---

Ambari-13513:[trunk][2.1.2] Add cmd option config to spark thrift server


Diffs
-

  
ambari-server/src/main/resources/common-services/SPARK/1.2.0.2.2/package/scripts/params.py
 518ba6d 
  
ambari-server/src/main/resources/common-services/SPARK/1.2.0.2.2/package/scripts/spark_service.py
 68a395b 
  
ambari-server/src/main/resources/stacks/HDP/2.3/services/SPARK/configuration/spark-thrift-cmd-opts-properties.xml
 PRE-CREATION 
  ambari-server/src/main/resources/stacks/HDP/2.3/services/SPARK/metainfo.xml 
14161b4 
  ambari-server/src/test/python/stacks/2.3/SPARK/test_spark_thrift_server.py 
b3b8235 
  ambari-server/src/test/python/stacks/2.3/configs/spark_default.json 9f3fb90 

Diff: https://reviews.apache.org/r/39530/diff/


Testing
---

1. Updated Unit Tests 
2. E2E test on HDInsight cluster


Thanks,

Judy Nash

[jira] [Updated] (AMBARI-13513) Add cmd option config to spark thrift server

[Judy Nash (JIRA)]

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

Judy Nash updated AMBARI-13513:
---
Attachment: (was: SPARK-13513.patch)

> Add cmd option config to spark thrift server 
> -
>
> Key: AMBARI-13513
> URL: https://issues.apache.org/jira/browse/AMBARI-13513
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Affects Versions: 2.1.2, trunk
>Reporter: Judy Nash
>Assignee: Judy Nash
> Attachments: SPARK-13513.patch
>
>
> When spark thrift server launches, customers may want to add additional 
> options to configure spark.
> i.e. 
> --driver-memory 
> --jars 
> Some of these configurations can only be submitted as command line options, 
> so adding a new config on ambari to give customers access. 



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

[jira] [Updated] (AMBARI-13513) Add cmd option config to spark thrift server

[Judy Nash (JIRA)]

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

Judy Nash updated AMBARI-13513:
---
Attachment: SPARK-13513.patch

> Add cmd option config to spark thrift server 
> -
>
> Key: AMBARI-13513
> URL: https://issues.apache.org/jira/browse/AMBARI-13513
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Affects Versions: 2.1.2, trunk
>Reporter: Judy Nash
>Assignee: Judy Nash
> Attachments: SPARK-13513.patch
>
>
> When spark thrift server launches, customers may want to add additional 
> options to configure spark.
> i.e. 
> --driver-memory 
> --jars 
> Some of these configurations can only be submitted as command line options, 
> so adding a new config on ambari to give customers access. 



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

[jira] [Updated] (AMBARI-13512) Show a warning popup before user is about to be logged out

[Richard Zang (JIRA)]

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

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

> Show a warning popup before user is about to be logged out
> --
>
> Key: AMBARI-13512
> URL: https://issues.apache.org/jira/browse/AMBARI-13512
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-admin, ambari-web
>Affects Versions: 2.1.3
>Reporter: Richard Zang
>Assignee: Richard Zang
> Fix For: 2.1.3
>
> Attachments: AMBARI-13512.patch
>
>
> Show a warning popup 60 seconds before user is about to be logged out. It 
> will trigger browser user action when user is actually monitoring the screen 
> which will make the user active again. Otherwise user will be logged out 
> after 60 seconds.
> The warning message should say:
> "You will be automatically logged out in X seconds due to inactivity. [Log 
> Out Now] [Remain Logged In]"
> X should automatically count down from 60, once per second.
> Popup Title:
> Automatic Logout



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

[jira] [Updated] (AMBARI-13512) Show a warning popup before user is about to be logged out

[Richard Zang (JIRA)]

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

Richard Zang updated AMBARI-13512:
--
Attachment: (was: AMBARI-13512.patch)

> Show a warning popup before user is about to be logged out
> --
>
> Key: AMBARI-13512
> URL: https://issues.apache.org/jira/browse/AMBARI-13512
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-admin, ambari-web
>Affects Versions: 2.1.3
>Reporter: Richard Zang
>Assignee: Richard Zang
> Fix For: 2.1.3
>
> Attachments: AMBARI-13512.patch
>
>
> Show a warning popup 60 seconds before user is about to be logged out. It 
> will trigger browser user action when user is actually monitoring the screen 
> which will make the user active again. Otherwise user will be logged out 
> after 60 seconds.
> The warning message should say:
> "You will be automatically logged out in X seconds due to inactivity. [Log 
> Out Now] [Remain Logged In]"
> X should automatically count down from 60, once per second.
> Popup Title:
> Automatic Logout



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

Re: Review Request 39470: [CapSchedView] show leaf and non-leaf queues with different UI indicators

[Yusaku Sako]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/39470/#review103487
---

Ship it!


Ship It!

- Yusaku Sako


On Oct. 20, 2015, 7:26 a.m., Gaurav Nagar wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/39470/
> ---
> 
> (Updated Oct. 20, 2015, 7:26 a.m.)
> 
> 
> Review request for Ambari, Srimanth Gunturi, Sid Wagle, and Yusaku Sako.
> 
> 
> Bugs: AMBARI-13483
> https://issues.apache.org/jira/browse/AMBARI-13483
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Added leaf icon for leaf queues.
> 
> 
> Diffs
> -
> 
>   
> contrib/views/capacity-scheduler/src/main/resources/ui/app/templates/components/queueListItem.hbs
>  075f9cd 
> 
> Diff: https://reviews.apache.org/r/39470/diff/
> 
> 
> Testing
> ---
> 
> Manual testing done.
> mvn clean install
> 
> 
> Thanks,
> 
> Gaurav Nagar
> 
>

[jira] [Commented] (AMBARI-13479) Handle derivation of hawq's yarn related parameters where yarn is not configured

[jun aoki (JIRA)]

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

jun aoki commented on AMBARI-13479:
---

Committed to trunk
844b1e9d3effd2d9d54d8b75532d208e1c629e40

> Handle derivation of hawq's yarn related parameters where yarn is not 
> configured
> 
>
> Key: AMBARI-13479
> URL: https://issues.apache.org/jira/browse/AMBARI-13479
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: trunk
>Reporter: bhuvnesh chaudhary
>Assignee: bhuvnesh chaudhary
> Attachments: AMBARI-13479.patch
>
>
> In ambari-web/app/utils/configs/config_property_helper.js, the value of 
> masterComponentHostsInDB.findProperty('component', 
> 'RESOURCEMANAGER').hostName is calculated irrespective if Yarn 
> resourcemanager is configured or not. In cases, where Yarn resourcemanager is 
> not configured, masterComponentHostsInDB.findProperty('component', 
> 'RESOURCEMANAGER') will result in undefined and will eventually result in 
> Uncaught TypeError while trying to get the value of hostName.



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

Re: Review Request 39521: Show a warning popup before user is about to be logged out

[Richard Zang]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/39521/
---

(Updated Oct. 21, 2015, 10:23 p.m.)


Review request for Ambari, Jaimin Jetly and Yusaku Sako.


Changes
---

Do not show close button. Externalize remainTime for testing.


Bugs: AMBARI-13512
https://issues.apache.org/jira/browse/AMBARI-13512


Repository: ambari


Description
---

Show a warning popup 60 seconds before user is about to be logged out. It will 
trigger browser user action when user is actually monitoring the screen which 
will make the user active again. Otherwise user will be logged out after 60 
seconds.
The warning message should say:
"You will be automatically logged out in X seconds due to inactivity. [Log Out 
Now] [Remain Logged In]"
X should automatically count down from 60, once per second.
Popup Title:
Automatic Logout


Diffs (updated)
-

  
ambari-admin/src/main/resources/ui/admin-web/app/scripts/controllers/mainCtrl.js
 2c9e1c9 
  ambari-admin/src/main/resources/ui/admin-web/app/scripts/services/Auth.js 
a73c540 
  
ambari-admin/src/main/resources/ui/admin-web/app/views/modals/TimeoutWarning.html
 PRE-CREATION 
  ambari-web/app/config.js 26f0553 
  ambari-web/app/controllers/main.js fb73770 
  ambari-web/app/messages.js 1c19b7d 

Diff: https://reviews.apache.org/r/39521/diff/


Testing
---

Manually tested on live cluster.
  All unit tests passed.
  10071 tests complete (10 seconds)
  105 tests pending


Thanks,

Richard Zang

Re: Review Request 39521: Show a warning popup before user is about to be logged out

[Jaimin Jetly]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/39521/#review103485
---

Ship it!


Ship It!

- Jaimin Jetly


On Oct. 21, 2015, 10:23 p.m., Richard Zang wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/39521/
> ---
> 
> (Updated Oct. 21, 2015, 10:23 p.m.)
> 
> 
> Review request for Ambari, Jaimin Jetly and Yusaku Sako.
> 
> 
> Bugs: AMBARI-13512
> https://issues.apache.org/jira/browse/AMBARI-13512
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Show a warning popup 60 seconds before user is about to be logged out. It 
> will trigger browser user action when user is actually monitoring the screen 
> which will make the user active again. Otherwise user will be logged out 
> after 60 seconds.
> The warning message should say:
> "You will be automatically logged out in X seconds due to inactivity. [Log 
> Out Now] [Remain Logged In]"
> X should automatically count down from 60, once per second.
> Popup Title:
> Automatic Logout
> 
> 
> Diffs
> -
> 
>   
> ambari-admin/src/main/resources/ui/admin-web/app/scripts/controllers/mainCtrl.js
>  2c9e1c9 
>   ambari-admin/src/main/resources/ui/admin-web/app/scripts/services/Auth.js 
> a73c540 
>   
> ambari-admin/src/main/resources/ui/admin-web/app/views/modals/TimeoutWarning.html
>  PRE-CREATION 
>   ambari-web/app/config.js 26f0553 
>   ambari-web/app/controllers/main.js fb73770 
>   ambari-web/app/messages.js 1c19b7d 
> 
> Diff: https://reviews.apache.org/r/39521/diff/
> 
> 
> Testing
> ---
> 
> Manually tested on live cluster.
>   All unit tests passed.
>   10071 tests complete (10 seconds)
>   105 tests pending
> 
> 
> Thanks,
> 
> Richard Zang
> 
>

Re: Review Request 39469: [CapSchedView] Mappings should be validated and invalid mappings should be disallowed

[Yusaku Sako]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/39469/#review103483
---

Ship it!


Ship It!

- Yusaku Sako


On Oct. 20, 2015, 6:50 a.m., Gaurav Nagar wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/39469/
> ---
> 
> (Updated Oct. 20, 2015, 6:50 a.m.)
> 
> 
> Review request for Ambari, Srimanth Gunturi, Sid Wagle, and Yusaku Sako.
> 
> 
> Bugs: AMBARI-13482
> https://issues.apache.org/jira/browse/AMBARI-13482
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Added a propert in 'hasInvalidQueueMappings'in queues controller that will 
> validate queue_mappings.
> 
> 
> Diffs
> -
> 
>   
> contrib/views/capacity-scheduler/src/main/resources/ui/app/controllers/queues.js
>  429832f 
>   
> contrib/views/capacity-scheduler/src/main/resources/ui/app/templates/schedulerPanel.hbs
>  388bc60 
> 
> Diff: https://reviews.apache.org/r/39469/diff/
> 
> 
> Testing
> ---
> 
> Manual Testing done
> mvn clean install
> 
> 
> Thanks,
> 
> Gaurav Nagar
> 
>

Re: Review Request 39436: spelling mistake in the help message for max capacity in capacity scheduler

[Yusaku Sako]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/39436/#review103479
---

Ship it!


Ship It!

- Yusaku Sako


On Oct. 19, 2015, 11:32 a.m., Gaurav Nagar wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/39436/
> ---
> 
> (Updated Oct. 19, 2015, 11:32 a.m.)
> 
> 
> Review request for Ambari, Srimanth Gunturi, Sid Wagle, and Yusaku Sako.
> 
> 
> Bugs: AMBARI-13469
> https://issues.apache.org/jira/browse/AMBARI-13469
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Corrected spelling mistake
> 
> 
> Diffs
> -
> 
>   
> contrib/views/capacity-scheduler/src/main/resources/ui/app/templates/capacityEditForm.hbs
>  dd55396 
> 
> Diff: https://reviews.apache.org/r/39436/diff/
> 
> 
> Testing
> ---
> 
> Manually Tested
> mvn clean install
> 
> 
> Thanks,
> 
> Gaurav Nagar
> 
>

[jira] [Updated] (AMBARI-13513) Add cmd option config to spark thrift server

[Judy Nash (JIRA)]

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

Judy Nash updated AMBARI-13513:
---
Attachment: (was: AMBARI-13513.patch)

> Add cmd option config to spark thrift server 
> -
>
> Key: AMBARI-13513
> URL: https://issues.apache.org/jira/browse/AMBARI-13513
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Affects Versions: 2.1.2, trunk
>Reporter: Judy Nash
>Assignee: Judy Nash
> Attachments: SPARK-13513.patch
>
>
> When spark thrift server launches, customers may want to add additional 
> options to configure spark.
> i.e. 
> --driver-memory 
> --jars 
> Some of these configurations can only be submitted as command line options, 
> so adding a new config on ambari to give customers access. 



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

[jira] [Updated] (AMBARI-13513) Add cmd option config to spark thrift server

[Judy Nash (JIRA)]

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

Judy Nash updated AMBARI-13513:
---
Attachment: SPARK-13513.patch

> Add cmd option config to spark thrift server 
> -
>
> Key: AMBARI-13513
> URL: https://issues.apache.org/jira/browse/AMBARI-13513
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Affects Versions: 2.1.2, trunk
>Reporter: Judy Nash
>Assignee: Judy Nash
> Attachments: SPARK-13513.patch
>
>
> When spark thrift server launches, customers may want to add additional 
> options to configure spark.
> i.e. 
> --driver-memory 
> --jars 
> Some of these configurations can only be submitted as command line options, 
> so adding a new config on ambari to give customers access. 



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

[jira] [Updated] (AMBARI-13421) Blueprints: install for Ranger Components (ranger-admin, ranger-usersync, ranger-kms, ...)

[Sebastian Toader (JIRA)]

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

Sebastian Toader updated AMBARI-13421:
--
Attachment: AMBARI-13421.v2.patch

> Blueprints: install for Ranger Components (ranger-admin, ranger-usersync, 
> ranger-kms, ...)
> --
>
> Key: AMBARI-13421
> URL: https://issues.apache.org/jira/browse/AMBARI-13421
> Project: Ambari
>  Issue Type: New Feature
>  Components: blueprints
>Affects Versions: 2.0.0
>Reporter: Sebastian Toader
>Assignee: Sebastian Toader
> Attachments: AMBARI-13421.v2.patch
>
>
> Add support for installing Ranger and enabling ranger plugins through 
> Blueprints.



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

[jira] [Updated] (AMBARI-13421) Blueprints: install for Ranger Components (ranger-admin, ranger-usersync, ranger-kms, ...)

[Sebastian Toader (JIRA)]

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

Sebastian Toader updated AMBARI-13421:
--
Attachment: (was: AMBARI-13421.v2.patch)

> Blueprints: install for Ranger Components (ranger-admin, ranger-usersync, 
> ranger-kms, ...)
> --
>
> Key: AMBARI-13421
> URL: https://issues.apache.org/jira/browse/AMBARI-13421
> Project: Ambari
>  Issue Type: New Feature
>  Components: blueprints
>Affects Versions: 2.0.0
>Reporter: Sebastian Toader
>Assignee: Sebastian Toader
>
> Add support for installing Ranger and enabling ranger plugins through 
> Blueprints.



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

[jira] [Commented] (AMBARI-13335) Install package command during RU should honor excluded packages

[Hudson (JIRA)]

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

Hudson commented on AMBARI-13335:
-

FAILURE: Integrated in Ambari-branch-2.1 #723 (See 
[https://builds.apache.org/job/Ambari-branch-2.1/723/])
AMBARI-13335. Install package command during RU should honor excluded 
(dlysnichenko: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=a0a005b2a88ed356a49671204c670097a74b3107])
* ambari-server/conf/unix/ambari.properties
* 
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/HostStackVersionResourceProvider.java
* 
ambari-server/src/main/java/org/apache/ambari/server/configuration/Configuration.java
* 
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ClusterStackVersionResourceProvider.java


> Install package command during RU should honor excluded packages
> 
>
> Key: AMBARI-13335
> URL: https://issues.apache.org/jira/browse/AMBARI-13335
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.1.2
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Fix For: 2.1.3
>
> Attachments: AMBARI-13335.patch
>
>
> It seems that install package custom action is not taking into account the 
> logic in the stack to exclude packages. Therefore, it is installing 
> hadooplzo, phoenix, even if they should be installed. This causes issue for 
> folks using local repo which may not include these packages.
> We need a design where package exclusion logic lives in a single location - 
> perhaps stack definition itself - that is shared by Upgrade code as well as 
> regular stack install code.
> Meanwhile, we may need a hot-fix to avoid installing hadooplzo during RU. 
> This can be a bit hacky as its needed on 2.1.2.



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

Re: Review Request 39318: Blueprints: install for Ranger Components (ranger-admin, ranger-usersync, ranger-kms)

[Sebastian Toader]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/39318/
---

(Updated Oct. 21, 2015, 9:36 p.m.)


Review request for Ambari, Laszlo Puskas, Sumit Mohanty, and Sid Wagle.


Changes
---

Rebase patch on latest trunk


Bugs: AMBARI-13421
https://issues.apache.org/jira/browse/AMBARI-13421


Repository: ambari


Description
---

1. Configured role command order such as all ranger plugins are started after 
ranger admin+ranger user sync are up in order to ensure that plugins if enabled 
can regsiter with Ranger
2. In the case of Ranger and ranger plugins being installed to different host 
the ordering described above is not apply as we don't have cluster wide 
ordering. Modified the library used by plugins to regsiter with ranger such as 
to fail if ranger is down provided command "retry" is enabled. If command retry 
is not enabled than keep the original logic which is just log an error and 
continue with the processing.


Diffs (updated)
-

  
ambari-common/src/main/python/resource_management/libraries/functions/ranger_functions.py
 de58976 
  
ambari-common/src/main/python/resource_management/libraries/functions/ranger_functions_v2.py
 81658bf 
  
ambari-common/src/main/python/resource_management/libraries/functions/setup_ranger_plugin.py
 e4a19aa 
  
ambari-common/src/main/python/resource_management/libraries/functions/setup_ranger_plugin_xml.py
 0b404a9 
  ambari-server/src/main/java/org/apache/ambari/server/Role.java df60988 
  
ambari-server/src/main/resources/common-services/HBASE/0.96.0.2.0/package/scripts/params.py
 36dd07f 
  
ambari-server/src/main/resources/common-services/HBASE/0.96.0.2.0/package/scripts/setup_ranger_hbase.py
 6b4dfaa 
  
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/params.py
 b89eefd 
  
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/setup_ranger_hdfs.py
 f5df86f 
  
ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/params.py
 36f7983 
  
ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/setup_ranger_hive.py
 b0f0c3f 
  
ambari-server/src/main/resources/common-services/KAFKA/0.8.1.2.2/package/scripts/params.py
 dc0c087 
  
ambari-server/src/main/resources/common-services/KAFKA/0.8.1.2.2/package/scripts/setup_ranger_kafka.py
 540bb9a 
  
ambari-server/src/main/resources/common-services/KNOX/0.5.0.2.2/package/scripts/params.py
 8fe1028 
  
ambari-server/src/main/resources/common-services/KNOX/0.5.0.2.2/package/scripts/setup_ranger_knox.py
 f1319b3 
  
ambari-server/src/main/resources/common-services/RANGER_KMS/0.5.0.2.3/package/scripts/kms.py
 570b2b7 
  
ambari-server/src/main/resources/common-services/STORM/0.9.1.2.1/package/scripts/params.py
 1e591f4 
  
ambari-server/src/main/resources/common-services/STORM/0.9.1.2.1/package/scripts/setup_ranger_storm.py
 d874ba3 
  
ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/scripts/params.py
 5695e83 
  
ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/scripts/setup_ranger_yarn.py
 c8b12df 
  ambari-server/src/main/resources/stacks/HDP/2.2/role_command_order.json 
3571a6c 
  
ambari-server/src/test/java/org/apache/ambari/server/stack/StackManagerTest.java
 be8b073 

Diff: https://reviews.apache.org/r/39318/diff/


Testing
---

Unit test:

---
Ran 247 tests in 6.472s

OK
--
Total run:770
Total errors:0
Total failures:0
OK
StackAdvisor implementation for stack HDP1, version 2.0.6 was not found
Returning DefaultStackAdvisor implementation
StackAdvisor implementation for stack XYZ, version 1.0.0 was loaded
StackAdvisor implementation for stack XYZ, version 1.0.1 was loaded
Returning XYZ101StackAdvisor implementation
[INFO] 
[INFO] BUILD SUCCESS
[INFO] 
[INFO] Total time: 1:04:49.578s
[INFO] Finished at: Wed Oct 14 15:56:27 CEST 2015
[INFO] Final Memory: 39M/1098M
[INFO] 


Manual testing:

1. Deployed 3 node cluster with Ranger, Resource Manager, Namenode on the same 
host to verify the hoat wide start order. 
2. Deployed 3 node cluster with Ranger and NameNode on different hosts to 
verify retry logic.


File Attachments


AMBARI-1342.v1.patch
  
https://reviews.apache.org/media/uploaded/files/2015/10/14/8adbd842-7d7a-4b52-801b-85e0e5b42cc0__AMBARI-13421.v1.patch


Thanks,

Sebastian Toader

[jira] [Updated] (AMBARI-13513) Add cmd option config to spark thrift server

[Judy Nash (JIRA)]

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

Judy Nash updated AMBARI-13513:
---
Attachment: AMBARI-13513.patch

> Add cmd option config to spark thrift server 
> -
>
> Key: AMBARI-13513
> URL: https://issues.apache.org/jira/browse/AMBARI-13513
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Affects Versions: 2.1.2, trunk
>Reporter: Judy Nash
>Assignee: Judy Nash
> Attachments: AMBARI-13513.patch
>
>
> When spark thrift server launches, customers may want to add additional 
> options to configure spark.
> i.e. 
> --driver-memory 
> --jars 
> Some of these configurations can only be submitted as command line options, 
> so adding a new config on ambari to give customers access. 



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

[jira] [Commented] (AMBARI-13476) Ranger usersync LDAP properties should be set same to ambari if ambari is configured with LDAP

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-13476:


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

This message is automatically generated.

> Ranger usersync LDAP properties should be set same to ambari if ambari is 
> configured with LDAP
> --
>
> Key: AMBARI-13476
> URL: https://issues.apache.org/jira/browse/AMBARI-13476
> Project: Ambari
>  Issue Type: Task
>  Components: stacks
>Affects Versions: 2.1.3
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: 2.1.3
>
> Attachments: AMBARI-13476-2.patch
>
>
> Following are the LDAP related properties found in ambari-server properties 
> file when ambari is configured with LDAP:
> ambari.ldap.isConfigured=true
> authentication.ldap.baseDn=dc=apache,dc=org
> authentication.ldap.bindAnonymously=false
> authentication.ldap.dnAttribute=dn
> authentication.ldap.groupMembershipAttr=memberUid
> authentication.ldap.groupNamingAttr=cn
> authentication.ldap.groupObjectClass=posixGroup
> authentication.ldap.managerDn=uid=hdfs,ou=people,ou=dev,dc=apache,dc=org
> authentication.ldap.managerPassword=/etc/ambari-server/conf/ldap-password.dat
> authentication.ldap.primaryUrl=c6403.ambari.apache.org:389
> authentication.ldap.secondaryUrl=c6403.ambari.apache.org:389
> authentication.ldap.useSSL=false
> authentication.ldap.userObjectClass=posixAccount
> authentication.ldap.usernameAttribute=uid



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

[jira] [Updated] (AMBARI-13513) Add cmd option config to spark thrift server

[Judy Nash (JIRA)]

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

Judy Nash updated AMBARI-13513:
---
Summary: Add cmd option config to spark thrift server   (was: Add cmd opt 
config to spark thrift server )

> Add cmd option config to spark thrift server 
> -
>
> Key: AMBARI-13513
> URL: https://issues.apache.org/jira/browse/AMBARI-13513
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Affects Versions: 2.1.2, trunk
>Reporter: Judy Nash
>Assignee: Judy Nash
>
> When spark thrift server launches, customers may want to add additional 
> options to configure spark.
> i.e. 
> --driver-memory 
> --jars 
> Some of these configurations can only be submitted as command line options, 
> so adding a new config on ambari to give customers access. 



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

[jira] [Created] (AMBARI-13513) Add cmd opt config to spark thrift server

[Judy Nash (JIRA)]

Judy Nash created AMBARI-13513:
--

 Summary: Add cmd opt config to spark thrift server 
 Key: AMBARI-13513
 URL: https://issues.apache.org/jira/browse/AMBARI-13513
 Project: Ambari
  Issue Type: Improvement
  Components: ambari-server
Affects Versions: 2.1.2, trunk
Reporter: Judy Nash
Assignee: Judy Nash


When spark thrift server launches, customers may want to add additional options 
to configure spark.
i.e. 
--driver-memory 
--jars 

Some of these configurations can only be submitted as command line options, so 
adding a new config on ambari to give customers access. 



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

[jira] [Commented] (AMBARI-13335) Install package command during RU should honor excluded packages

[Hudson (JIRA)]

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

Hudson commented on AMBARI-13335:
-

FAILURE: Integrated in Ambari-trunk-Commit #3689 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/3689/])
AMBARI-13335. Install package command during RU should honor excluded 
(dlysnichenko: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=85bd7cdbc01da56b9d16abd29f18153cefcdead6])
* ambari-server/conf/unix/ambari.properties
* 
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ClusterStackVersionResourceProvider.java
* 
ambari-server/src/main/java/org/apache/ambari/server/configuration/Configuration.java
* 
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/HostStackVersionResourceProvider.java


> Install package command during RU should honor excluded packages
> 
>
> Key: AMBARI-13335
> URL: https://issues.apache.org/jira/browse/AMBARI-13335
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.1.2
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Fix For: 2.1.3
>
> Attachments: AMBARI-13335.patch
>
>
> It seems that install package custom action is not taking into account the 
> logic in the stack to exclude packages. Therefore, it is installing 
> hadooplzo, phoenix, even if they should be installed. This causes issue for 
> folks using local repo which may not include these packages.
> We need a design where package exclusion logic lives in a single location - 
> perhaps stack definition itself - that is shared by Upgrade code as well as 
> regular stack install code.
> Meanwhile, we may need a hot-fix to avoid installing hadooplzo during RU. 
> This can be a bit hacky as its needed on 2.1.2.



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

Re: Review Request 39521: Show a warning popup before user is about to be logged out

[Yusaku Sako]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/39521/#review103470
---

Ship it!


Ship It!

- Yusaku Sako


On Oct. 21, 2015, 7:16 p.m., Richard Zang wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/39521/
> ---
> 
> (Updated Oct. 21, 2015, 7:16 p.m.)
> 
> 
> Review request for Ambari, Jaimin Jetly and Yusaku Sako.
> 
> 
> Bugs: AMBARI-13512
> https://issues.apache.org/jira/browse/AMBARI-13512
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Show a warning popup 60 seconds before user is about to be logged out. It 
> will trigger browser user action when user is actually monitoring the screen 
> which will make the user active again. Otherwise user will be logged out 
> after 60 seconds.
> The warning message should say:
> "You will be automatically logged out in X seconds due to inactivity. [Log 
> Out Now] [Remain Logged In]"
> X should automatically count down from 60, once per second.
> Popup Title:
> Automatic Logout
> 
> 
> Diffs
> -
> 
>   
> ambari-admin/src/main/resources/ui/admin-web/app/scripts/controllers/mainCtrl.js
>  2c9e1c9 
>   ambari-admin/src/main/resources/ui/admin-web/app/scripts/services/Auth.js 
> a73c540 
>   
> ambari-admin/src/main/resources/ui/admin-web/app/views/modals/TimeoutWarning.html
>  PRE-CREATION 
>   ambari-web/app/controllers/main.js fb73770 
>   ambari-web/app/messages.js 1c19b7d 
> 
> Diff: https://reviews.apache.org/r/39521/diff/
> 
> 
> Testing
> ---
> 
> Manually tested on live cluster.
>   All unit tests passed.
>   10071 tests complete (10 seconds)
>   105 tests pending
> 
> 
> Thanks,
> 
> Richard Zang
> 
>

Re: Review Request 39524: Display sysctl and limits configuration on the HAWQ config UI screen

[bhuvnesh chaudhary]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/39524/
---

(Updated Oct. 21, 2015, 8:45 p.m.)


Review request for Ambari and jun aoki.


Changes
---

Updated jira number AMBARI-13510


Bugs: AMBARI-13510
https://issues.apache.org/jira/browse/AMBARI-13510


Repository: ambari


Description
---

User should be able to see the values of sysctl and limits parameters which are 
configured for HAWQ.
Sysctl parameters except vm.overcommit.memory are editable only during install, 
after install they are read only. overcommit parameter can be changed as needed.
limits for hawq user(gpadmin) are editable.


Diffs
-

  
ambari-server/src/main/resources/common-services/HAWQ/2.0.0.0/configuration/hawq-limits-env.xml
 PRE-CREATION 
  
ambari-server/src/main/resources/common-services/HAWQ/2.0.0.0/configuration/hawq-sysctl-env.xml
 PRE-CREATION 
  
ambari-server/src/main/resources/common-services/HAWQ/2.0.0.0/package/scripts/common.py
 defd87c 
  
ambari-server/src/main/resources/common-services/HAWQ/2.0.0.0/package/scripts/constants.py
 78a636e 
  
ambari-server/src/main/resources/common-services/HAWQ/2.0.0.0/package/scripts/hawqstatus.py
 59742bd 
  
ambari-server/src/main/resources/common-services/HAWQ/2.0.0.0/package/scripts/master_helper.py
 82a5168 
  
ambari-server/src/main/resources/common-services/HAWQ/2.0.0.0/package/scripts/params.py
 df33d0b 
  
ambari-server/src/main/resources/common-services/HAWQ/2.0.0.0/package/scripts/utils.py
 b42b3a6 
  
ambari-server/src/main/resources/common-services/HAWQ/2.0.0.0/package/templates/hawq.limits.conf.j2
 93e027c 
  
ambari-server/src/main/resources/common-services/HAWQ/2.0.0.0/package/templates/hawq.sysctl.conf.j2
 480228e 

Diff: https://reviews.apache.org/r/39524/diff/


Testing
---

yes


Thanks,

bhuvnesh chaudhary

Re: Review Request 39524: Display sysctl and limits configuration on the HAWQ config UI screen

[bhuvnesh chaudhary]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/39524/
---

(Updated Oct. 21, 2015, 8:43 p.m.)


Review request for Ambari and jun aoki.


Repository: ambari


Description (updated)
---

User should be able to see the values of sysctl and limits parameters which are 
configured for HAWQ.
Sysctl parameters except vm.overcommit.memory are editable only during install, 
after install they are read only. overcommit parameter can be changed as needed.
limits for hawq user(gpadmin) are editable.


Diffs
-

  
ambari-server/src/main/resources/common-services/HAWQ/2.0.0.0/configuration/hawq-limits-env.xml
 PRE-CREATION 
  
ambari-server/src/main/resources/common-services/HAWQ/2.0.0.0/configuration/hawq-sysctl-env.xml
 PRE-CREATION 
  
ambari-server/src/main/resources/common-services/HAWQ/2.0.0.0/package/scripts/common.py
 defd87c 
  
ambari-server/src/main/resources/common-services/HAWQ/2.0.0.0/package/scripts/constants.py
 78a636e 
  
ambari-server/src/main/resources/common-services/HAWQ/2.0.0.0/package/scripts/hawqstatus.py
 59742bd 
  
ambari-server/src/main/resources/common-services/HAWQ/2.0.0.0/package/scripts/master_helper.py
 82a5168 
  
ambari-server/src/main/resources/common-services/HAWQ/2.0.0.0/package/scripts/params.py
 df33d0b 
  
ambari-server/src/main/resources/common-services/HAWQ/2.0.0.0/package/scripts/utils.py
 b42b3a6 
  
ambari-server/src/main/resources/common-services/HAWQ/2.0.0.0/package/templates/hawq.limits.conf.j2
 93e027c 
  
ambari-server/src/main/resources/common-services/HAWQ/2.0.0.0/package/templates/hawq.sysctl.conf.j2
 480228e 

Diff: https://reviews.apache.org/r/39524/diff/


Testing
---

yes


Thanks,

bhuvnesh chaudhary

Review Request 39524: Display sysctl and limits configuration on the HAWQ config UI screen

[bhuvnesh chaudhary]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/39524/
---

Review request for Ambari and jun aoki.


Repository: ambari


Description
---

ser should be able to see the values of sysctl and limits parameters which are 
configured for HAWQ.
Sysctl parameters except vm.overcommit.memory are editable only during install, 
after install they are read only. overcommit parameter can be changed as needed.
limits for hawq user(gpadmin) are editable.


Diffs
-

  
ambari-server/src/main/resources/common-services/HAWQ/2.0.0.0/configuration/hawq-limits-env.xml
 PRE-CREATION 
  
ambari-server/src/main/resources/common-services/HAWQ/2.0.0.0/configuration/hawq-sysctl-env.xml
 PRE-CREATION 
  
ambari-server/src/main/resources/common-services/HAWQ/2.0.0.0/package/scripts/common.py
 defd87c 
  
ambari-server/src/main/resources/common-services/HAWQ/2.0.0.0/package/scripts/constants.py
 78a636e 
  
ambari-server/src/main/resources/common-services/HAWQ/2.0.0.0/package/scripts/hawqstatus.py
 59742bd 
  
ambari-server/src/main/resources/common-services/HAWQ/2.0.0.0/package/scripts/master_helper.py
 82a5168 
  
ambari-server/src/main/resources/common-services/HAWQ/2.0.0.0/package/scripts/params.py
 df33d0b 
  
ambari-server/src/main/resources/common-services/HAWQ/2.0.0.0/package/scripts/utils.py
 b42b3a6 
  
ambari-server/src/main/resources/common-services/HAWQ/2.0.0.0/package/templates/hawq.limits.conf.j2
 93e027c 
  
ambari-server/src/main/resources/common-services/HAWQ/2.0.0.0/package/templates/hawq.sysctl.conf.j2
 480228e 

Diff: https://reviews.apache.org/r/39524/diff/


Testing
---

yes


Thanks,

bhuvnesh chaudhary

[jira] [Updated] (AMBARI-13510) Display sysctl and limits configuration on the HAWQ config UI screen

[bhuvnesh chaudhary (JIRA)]

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

bhuvnesh chaudhary updated AMBARI-13510:

Attachment: AMBARI-13510.patch

> Display sysctl and limits configuration on the HAWQ config UI screen
> 
>
> Key: AMBARI-13510
> URL: https://issues.apache.org/jira/browse/AMBARI-13510
> Project: Ambari
>  Issue Type: New Feature
>  Components: stacks
>Affects Versions: trunk
>Reporter: bhuvnesh chaudhary
>Assignee: bhuvnesh chaudhary
> Attachments: AMBARI-13510.patch
>
>
> User should be able to see the values of sysctl and limits parameters which 
> are configured for HAWQ.
> Sysctl parameters except vm.overcommit.memory are editable only during 
> install, after install they are read only. overcommit parameter can be 
> changed as needed.
> limits for hawq user(gpadmin) are editable.



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

Re: Review Request 39111: [PREVIEW] Stop-and-Start Upgrade: Handle Core Services

[Alejandro Fernandez]

> On Oct. 20, 2015, 12:14 p.m., Nate Cole wrote:
> > What's the state of this review?  If it's already integrated, please close 
> > it.

I was off-site on Monday and Tuesday; will fix unit tests and commit asap.


- Alejandro


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/39111/#review103245
---


On Oct. 16, 2015, 6:37 p.m., Alejandro Fernandez wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/39111/
> ---
> 
> (Updated Oct. 16, 2015, 6:37 p.m.)
> 
> 
> Review request for Ambari, Dmytro Grinenko, Dmitro Lisnichenko, Jonathan 
> Hurley, and Nate Cole.
> 
> 
> Bugs: AMBARI-12701
> https://issues.apache.org/jira/browse/AMBARI-12701
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Stop-and-Start Upgrade of the Stack to handle core services: HDFS, YARN, MR, 
> ZK
> 
> * Renamed the functions pre_rolling_upgrade and post_rolling_upgrade to 
> pre_upgrade_restart and post_upgrade_restart that accept the upgrade_type 
> (rolling|nonrolling) as a param.
> 
> * When NameNode HA is present, the command used to start NameNode is 
> different between the active and the standby, so changed 
> MasterHostResolver.java to pick one of the NameNodes to become the active and 
> the other the standby, and pass it in a parameter called 
> "desired_namenode_role"
> 
> * Wrote a function to take a backup of HDFS
> 
> * Changed the "hdfs" command to actually search which one to use depending on 
> the stack and version to account for Express Upgrade from HDP 2.1 -> 2.3
> 
> * Tested Express Upgrade with and without NameNode HA
> 
> 
> Diffs
> -
> 
>   
> ambari-common/src/main/python/resource_management/libraries/script/script.py 
> efd34e3 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/internal/PreUpgradeCheckResourceProvider.java
>  9c5d87a 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/internal/UpgradeResourceProvider.java
>  a31f805 
>   
> ambari-server/src/main/java/org/apache/ambari/server/stack/MasterHostResolver.java
>  55fb12b 
>   
> ambari-server/src/main/java/org/apache/ambari/server/state/UpgradeHelper.java 
> b81d3fd 
>   
> ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/ClusterGrouping.java
>  ba44408 
>   
> ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/ColocatedGrouping.java
>  2aef43c 
>   
> ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/Grouping.java
>  8f23803 
>   
> ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/ServiceCheckGrouping.java
>  af63656 
>   
> ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/StageWrapper.java
>  92df3b5 
>   
> ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/StageWrapperBuilder.java
>  47a28d7 
>   
> ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/TaskWrapper.java
>  f7cc930 
>   
> ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/TaskWrapperBuilder.java
>  a5813e3 
>   
> ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/datanode.py
>  fa68435 
>   
> ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/datanode_upgrade.py
>  2e5ac19 
>   
> ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_client.py
>  dd0dca4 
>   
> ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_namenode.py
>  b11d7ea 
>   
> ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/journalnode.py
>  46c7272 
>   
> ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/journalnode_upgrade.py
>  e2ebbcb 
>   
> ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/namenode.py
>  23e775a 
>   
> ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/namenode_ha_state.py
>  e8c142c 
>   
> ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/namenode_upgrade.py
>  fb39878 
>   
> ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/nfsgateway.py
>  be6f0d5 
>   
> ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/params_linux.py
>  0b38957 
>   
> ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/setup_ranger_hdfs.py
>  f5df86f 
>   
> ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/snamenode.py
>  108ef01 
>   
> ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/utils.py
>  d1e764a 
>   
> ambari-server/src/main/r

Re: Review Request 39440: RU: Fix hbase snapshot

[Alejandro Fernandez]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/39440/#review103468
---

Ship it!


Ship It!

- Alejandro Fernandez


On Oct. 19, 2015, 2:31 p.m., Dmitro Lisnichenko wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/39440/
> ---
> 
> (Updated Oct. 19, 2015, 2:31 p.m.)
> 
> 
> Review request for Ambari, Alejandro Fernandez, Dmytro Grinenko, Jonathan 
> Hurley, and Nate Cole.
> 
> 
> Bugs: AMBARI-13474
> https://issues.apache.org/jira/browse/AMBARI-13474
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Looks like someone has changed the function name in hbase script from 
> snapshot() to take_snapshot() but looks like the upgrade pack (HDP 2.2 & 2.3) 
> still reflects old function name.
> 
> https://github.com/apache/ambari/blob/trunk/ambari-server/src/main/resources/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_upgrade.py#L27
> 
> 
> Diffs
> -
> 
>   ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/upgrade-2.2.xml 
> e54f0d8 
>   ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/upgrade-2.3.xml 
> 8c8db7c 
>   ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.3.xml 
> 08b34be 
> 
> Diff: https://reviews.apache.org/r/39440/diff/
> 
> 
> Testing
> ---
> 
> mvn clean test
> 
> 
> Thanks,
> 
> Dmitro Lisnichenko
> 
>

Re: Review Request 38479: AMBARI-13138 Use ranger port value from configs for alerts in Ambari (HDP-2.2)

[Alejandro Fernandez]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/38479/#review103466
---



ambari-server/src/main/resources/common-services/RANGER/0.4.0/configuration/ranger-site.xml
 (line 44)


Does this value have to change for Stack Upgrades?
Say HDP 2.2->2.3?


- Alejandro Fernandez


On Oct. 20, 2015, 12:58 p.m., Gautam Borad wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/38479/
> ---
> 
> (Updated Oct. 20, 2015, 12:58 p.m.)
> 
> 
> Review request for Ambari, Alejandro Fernandez, Jaimin Jetly, Mahadev Konar, 
> Sumit Mohanty, Selvamohan Neethiraj, Velmurugan Periasamy, and Yusaku Sako.
> 
> 
> Bugs: AMBARI-13138
> https://issues.apache.org/jira/browse/AMBARI-13138
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> For HDP-2.2
> Alerts uses default port value i.e. 6080 instead of using expected port 
> values from configs. Need to take the port value from configs.
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog210.java
>  12a1f44 
>   ambari-server/src/main/resources/common-services/RANGER/0.4.0/alerts.json 
> 05ccc1d 
>   
> ambari-server/src/main/resources/common-services/RANGER/0.4.0/configuration/ranger-site.xml
>  293c925 
> 
> Diff: https://reviews.apache.org/r/38479/diff/
> 
> 
> Testing
> ---
> 
> Ranger installation was successful on centos6. Alerts were working as 
> expected when http, https ports values are changed.
> 
> 
> Thanks,
> 
> Gautam Borad
> 
>

Re: Review Request 39476: AMBARI-13488 : Add recommendation for 'hive.conf.restricted.list' property under hiveserver2-site (For Ranger Plugin)

[Alejandro Fernandez]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/39476/#review103465
---



ambari-server/src/main/resources/stacks/HDP/2.2/services/HIVE/configuration/hiveserver2-site.xml
 (line 76)


Does this property change need to be handled for customers upgrading from 
HDP 2.1 -> 2.2?


- Alejandro Fernandez


On Oct. 20, 2015, 1:06 p.m., Gautam Borad wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/39476/
> ---
> 
> (Updated Oct. 20, 2015, 1:06 p.m.)
> 
> 
> Review request for Ambari, Alejandro Fernandez, Jaimin Jetly, Mahadev Konar, 
> Sumit Mohanty, Selvamohan Neethiraj, Velmurugan Periasamy, and Yusaku Sako.
> 
> 
> Bugs: AMBARI-13488
> https://issues.apache.org/jira/browse/AMBARI-13488
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Added 'hive.conf.restricted.list' property to hive-server2-site.xml and added 
> Stack Advisor recommendations as well as validations for the same, when 
> Ranger Hive Plugin is Enabled.
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/resources/stacks/HDP/2.2/services/HIVE/configuration/hiveserver2-site.xml
>  12a78db 
>   ambari-server/src/main/resources/stacks/HDP/2.2/services/stack_advisor.py 
> 3192ca2 
>   ambari-server/src/main/resources/stacks/HDP/2.3/services/stack_advisor.py 
> 501517f 
>   ambari-server/src/test/python/stacks/2.2/common/test_stack_advisor.py 
> 3362c94 
> 
> Diff: https://reviews.apache.org/r/39476/diff/
> 
> 
> Testing
> ---
> 
> Verifed property addition and Stack advisor validation for 
> 'hive.conf.restricted.list' on a cluster having Ranger and Hive installed via 
> Ambari (after enabling Ranger Hive Plugin).
> 
> 
> Thanks,
> 
> Gautam Borad
> 
>

[jira] [Assigned] (AMBARI-13408) Ambari build process should have the ability to generate source tarballs

[Ashish Singh (JIRA)]

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

Ashish Singh reassigned AMBARI-13408:
-

Assignee: Ashish Singh

> Ambari build process should have the ability to generate source tarballs
> 
>
> Key: AMBARI-13408
> URL: https://issues.apache.org/jira/browse/AMBARI-13408
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.1.2
>Reporter: Sumit Mohanty
>Assignee: Ashish Singh
> Fix For: 2.2.0
>
>
> Need to add an option to create source tar ball through the mvn command. This 
> will provide a consistent way to create the tarballs. 



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

[jira] [Updated] (AMBARI-13512) Show a warning popup before user is about to be logged out

[Richard Zang (JIRA)]

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

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

> Show a warning popup before user is about to be logged out
> --
>
> Key: AMBARI-13512
> URL: https://issues.apache.org/jira/browse/AMBARI-13512
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-admin, ambari-web
>Affects Versions: 2.1.3
>Reporter: Richard Zang
>Assignee: Richard Zang
> Fix For: 2.1.3
>
> Attachments: AMBARI-13512.patch
>
>
> Show a warning popup 60 seconds before user is about to be logged out. It 
> will trigger browser user action when user is actually monitoring the screen 
> which will make the user active again. Otherwise user will be logged out 
> after 60 seconds.
> The warning message should say:
> "You will be automatically logged out in X seconds due to inactivity. [Log 
> Out Now] [Remain Logged In]"
> X should automatically count down from 60, once per second.
> Popup Title:
> Automatic Logout



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

Review Request 39521: Show a warning popup before user is about to be logged out

[Richard Zang]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/39521/
---

Review request for Ambari, Jaimin Jetly and Yusaku Sako.


Bugs: AMBARI-13512
https://issues.apache.org/jira/browse/AMBARI-13512


Repository: ambari


Description
---

Show a warning popup 60 seconds before user is about to be logged out. It will 
trigger browser user action when user is actually monitoring the screen which 
will make the user active again. Otherwise user will be logged out after 60 
seconds.
The warning message should say:
"You will be automatically logged out in X seconds due to inactivity. [Log Out 
Now] [Remain Logged In]"
X should automatically count down from 60, once per second.
Popup Title:
Automatic Logout


Diffs
-

  
ambari-admin/src/main/resources/ui/admin-web/app/scripts/controllers/mainCtrl.js
 2c9e1c9 
  ambari-admin/src/main/resources/ui/admin-web/app/scripts/services/Auth.js 
a73c540 
  
ambari-admin/src/main/resources/ui/admin-web/app/views/modals/TimeoutWarning.html
 PRE-CREATION 
  ambari-web/app/controllers/main.js fb73770 
  ambari-web/app/messages.js 1c19b7d 

Diff: https://reviews.apache.org/r/39521/diff/


Testing
---

Manually tested on live cluster.
  All unit tests passed.
  10071 tests complete (10 seconds)
  105 tests pending


Thanks,

Richard Zang