date:20160203


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

Andrii Tkach updated AMBARI-14897:
--
Attachment: AMBARI-14897.patch

> Rolling Upgrade: upgrade group status not updated
> -
>
> Key: AMBARI-14897
> URL: https://issues.apache.org/jira/browse/AMBARI-14897
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.2.1
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-14897.patch, AMBARI-14897_branch-2.2.patch, 
> Selection_127.png
>
>
> ambari-server version: ambari-server-2.2.1.0-156.x86_64
> ambari-server --hash: 9a9ecca7809c57e16cfe273c3e7b6df7f63a47c7
> HDP Stack: 2.3
> HDP Version: 2.3.0.0-2557
> 2.4.0.0-149
> Ambari DB: :MySQL
> Oozie/Hive DB: MySQL/MySQL
> Security:no
> Security Type:AD/AD
> Blueprints: false
> Umask: 
> JDK: OracleJDK8
> HA: yes



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

[jira] [Commented] (AMBARI-14894) Add Custom action to sync Standby with Master and rename stop hawq cluster to service


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

Hadoop QA commented on AMBARI-14894:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12785913/AMBARI-14894.branch-2.2-v2.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/5175//console

This message is automatically generated.

> Add Custom action to sync Standby with Master and rename stop hawq cluster to 
> service
> -
>
> Key: AMBARI-14894
> URL: https://issues.apache.org/jira/browse/AMBARI-14894
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.2.2
>Reporter: Goutam Tadi
>Assignee: Goutam Tadi
>Priority: Minor
> Fix For: 2.2.2
>
> Attachments: AMBARI-14894.branch-2.2-v2.patch
>
>




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

[jira] [Updated] (AMBARI-14897) Rolling Upgrade: upgrade group status not updated


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

Andrii Tkach updated AMBARI-14897:
--
Attachment: AMBARI-14897_branch-2.2.patch

> Rolling Upgrade: upgrade group status not updated
> -
>
> Key: AMBARI-14897
> URL: https://issues.apache.org/jira/browse/AMBARI-14897
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.2.1
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-14897_branch-2.2.patch, Selection_127.png
>
>
> ambari-server version: ambari-server-2.2.1.0-156.x86_64
> ambari-server --hash: 9a9ecca7809c57e16cfe273c3e7b6df7f63a47c7
> HDP Stack: 2.3
> HDP Version: 2.3.0.0-2557
> 2.4.0.0-149
> Ambari DB: :MySQL
> Oozie/Hive DB: MySQL/MySQL
> Security:no
> Security Type:AD/AD
> Blueprints: false
> Umask: 
> JDK: OracleJDK8
> HA: yes



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

[jira] [Commented] (AMBARI-14855) Add Alert for HAWQSTANDBY sync status with HAWQMASTER


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

Hadoop QA commented on AMBARI-14855:


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

This message is automatically generated.

> Add Alert for HAWQSTANDBY sync status with HAWQMASTER
> -
>
> Key: AMBARI-14855
> URL: https://issues.apache.org/jira/browse/AMBARI-14855
> Project: Ambari
>  Issue Type: New Feature
>  Components: stacks
>Reporter: Matt
>Assignee: Matt
>Priority: Minor
> Fix For: trunk, 2.2.2
>
> Attachments: AMBARI-14855-branch-2.2.patch, 
> AMBARI-14855-trunk-v-2.patch, AMBARI-14855-trunk-v-3.patch, 
> AMBARI-14855-trunk-v-4.patch, AMBARI-14855-trunk-v-5.patch, 
> AMBARI-14855-trunk-v-6.patch, AMBARI-14855-trunk.patch
>
>
> HAWQSTANDBY can go out of sync with HAWQMASTER. Show an alert when 
> HAWQSTANDBY is not in sync with HAWQMASTER.



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

Re: Review Request 43125: [INITIAL PATCH] AMBARI-14892 Add Grafana as a component to AMS


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




ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py
 (line 31)


We should install ambari-metrics-grafana.rpm

Lets just remove these Excecute's from install() and install 
ambari-metrics-grafana.rpm manually


- Dmytro Sen


On Фев. 3, 2016, 12:49 д.п., Aravindan Vijayan wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/43125/
> ---
> 
> (Updated Фев. 3, 2016, 12:49 д.п.)
> 
> 
> Review request for Ambari, Dmytro Sen, Sumit Mohanty, Sid Wagle, and Yusaku 
> Sako.
> 
> 
> Bugs: AMBARI-14892
> https://issues.apache.org/jira/browse/AMBARI-14892
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Add a MASTER component called Grafana to AMS service.
> 
> Include install and start/stop/status scripts for the grafana server.
> 
> Config Management for Ambari Metrics - Grafana also part of this patch.
> 
> 
> Diffs
> -
> 
>   
> ambari-metrics/ambari-metrics-timelineservice/conf/unix/ambari-metrics-grafana
>  PRE-CREATION 
>   
> ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/configuration/ams-grafana-env.xml
>  PRE-CREATION 
>   
> ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/configuration/ams-grafana-ini.xml
>  PRE-CREATION 
>   
> ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/metainfo.xml
>  48469df 
>   
> ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/ams.py
>  8fdf4ba 
>   
> ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py
>  PRE-CREATION 
>   
> ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/params.py
>  a1de919 
>   
> ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/status.py
>  59466ad 
>   
> ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/status_params.py
>  d446baa 
> 
> Diff: https://reviews.apache.org/r/43125/diff/
> 
> 
> Testing
> ---
> 
> Manual testing done.
> 
> 
> Thanks,
> 
> Aravindan Vijayan
> 
>

[jira] [Commented] (AMBARI-14884) Hawq standby host config should be removed on single node cluster during initial cluster installation


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

Hadoop QA commented on AMBARI-14884:


{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12785944/AMBARI-14884-1.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-web.

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

This message is automatically generated.

> Hawq standby host config should be removed on single node cluster during 
> initial cluster installation
> -
>
> Key: AMBARI-14884
> URL: https://issues.apache.org/jira/browse/AMBARI-14884
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: trunk
>Reporter: bhuvnesh chaudhary
>Assignee: bhuvnesh chaudhary
>Priority: Trivial
> Fix For: trunk
>
> Attachments: AMBARI-14884-1.patch, AMBARI-14884.patch
>
>
> Hawq standby host config should be removed on single node cluster during 
> initial cluster installation.
> Currently, it works only if the cluster is installed and Hawq is added later, 
> but during initial single node installation of cluster with Hawq, it does not.



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

[jira] [Commented] (AMBARI-14893) Add Grafana-based Ambari Metrics Dashboard Builder


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

Hadoop QA commented on AMBARI-14893:


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

This message is automatically generated.

> Add Grafana-based Ambari Metrics Dashboard Builder
> --
>
> Key: AMBARI-14893
> URL: https://issues.apache.org/jira/browse/AMBARI-14893
> Project: Ambari
>  Issue Type: New Feature
>  Components: ambari-metrics
>Affects Versions: 2.2.2
>Reporter: Yusaku Sako
>Assignee: Prajwal Rao
> Fix For: 2.2.2
>
> Attachments: AMBARI-14893.patch, screenshots.tar.gz
>
>
> This is a Grafana datasource that allows visualization of metrics stored in 
> Ambari Metrics Collector.



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

Re: Review Request 43092: [Ambari tarballs] Refactor postinstall and postremove scripts to use install-helper.sh exclusively

2016-02-03 Thread Dmitro Lisnichenko


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


Ship it!




Ship It!

- Dmitro Lisnichenko


On Feb. 3, 2016, 11:50 a.m., Andrew Onischuk wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/43092/
> ---
> 
> (Updated Feb. 3, 2016, 11:50 a.m.)
> 
> 
> Review request for Ambari and Dmitro Lisnichenko.
> 
> 
> Bugs: AMBARI-14877
> https://issues.apache.org/jira/browse/AMBARI-14877
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> We will need this refactoring, to use install-helper.sh while installing
> tar.gz
> 
> 
> Diffs
> -
> 
>   ambari-agent/conf/unix/install-helper.sh 185290c 
>   ambari-agent/src/main/package/deb/control/postinst ceca9be 
>   ambari-agent/src/main/package/deb/control/posttrm 21a01fa 
>   ambari-agent/src/main/package/deb/control/prerm 70a9c63 
>   ambari-agent/src/main/package/rpm/postinstall.sh 56c6573 
>   ambari-agent/src/main/package/rpm/preremove.sh 2078acd 
>   ambari-agent/src/packages/tarball/all.xml d4ed2ff 
>   ambari-server/conf/unix/install-helper.sh 2635694 
>   ambari-server/src/main/assemblies/server.xml c24bce6 
>   ambari-server/src/main/package/deb/control/postinst c3b6235 
>   ambari-server/src/main/package/deb/control/posttrm 21a01fa 
>   ambari-server/src/main/package/deb/control/prerm 927ba4c 
>   ambari-server/src/main/package/rpm/postinstall.sh 9b0b54a 
>   ambari-server/src/main/package/rpm/preremove.sh 6febaa8 
> 
> Diff: https://reviews.apache.org/r/43092/diff/
> 
> 
> Testing
> ---
> 
> mvn clean test
> 
> 
> Thanks,
> 
> Andrew Onischuk
> 
>

[jira] [Created] (AMBARI-14897) Rolling Upgrade: upgrade group status not updated

Andrii Tkach created AMBARI-14897:
-

 Summary: Rolling Upgrade: upgrade group status not updated
 Key: AMBARI-14897
 URL: https://issues.apache.org/jira/browse/AMBARI-14897
 Project: Ambari
  Issue Type: Bug
  Components: ambari-web
Affects Versions: 2.2.1
Reporter: Andrii Tkach
Assignee: Andrii Tkach
Priority: Critical
 Fix For: 2.2.2
 Attachments: Selection_127.png

ambari-server version: ambari-server-2.2.1.0-156.x86_64
ambari-server --hash: 9a9ecca7809c57e16cfe273c3e7b6df7f63a47c7
HDP Stack: 2.3
HDP Version: 2.3.0.0-2557
2.4.0.0-149
Ambari DB: :MySQL
Oozie/Hive DB: MySQL/MySQL
Security:no
Security Type:AD/AD
Blueprints: false
Umask: 
JDK: OracleJDK8
HA: yes



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

Re: Review Request 43123: RU/EU should only delete configs on downgrade if source stack matches stack whose status is CURRENT

2016-02-03 Thread Dmitro Lisnichenko


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


Ship it!




Ship It!

- Dmitro Lisnichenko


On Feb. 3, 2016, 2:25 a.m., Alejandro Fernandez wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/43123/
> ---
> 
> (Updated Feb. 3, 2016, 2:25 a.m.)
> 
> 
> Review request for Ambari, Dmytro Grinenko, Dmitro Lisnichenko, Jonathan 
> Hurley, Nate Cole, and Swapan Shridhar.
> 
> 
> Bugs: AMBARI-14891
> https://issues.apache.org/jira/browse/AMBARI-14891
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Saw a case with a customer in which they did the following.
> 
> * Ambari 2.1.2
> * Rolling Upgrade from HDP 2.2 to 2.3.0.0 and skipped the Finalize step, so 
> Ambari never called "Save DB State". Hence, the current stack version was 
> still 2.2. They then modified the host_version and cluster_version records in 
> the DB to mark HDP 2.3 as CURRENT.
> * Forgot to call ambari-server set-current-version
> * Registered and installed bits for HDP 2.3.4.0 and began another RU. After 
> running into an issue, they decided to downgrade, which then completely 
> removed the configs for the target stack (which is HDP 2.3!)
> 
> In order to prevent deleting configs in cases where the user has modified the 
> database, add stronger validation to FinalizeUpgradeAction so that we check 
> that the request's source target stack equals the stack of the repo marked as 
> CURRENT. In this case, they were 2.2 and 2.3, respectively.
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/java/org/apache/ambari/server/serveraction/upgrades/FinalizeUpgradeAction.java
>  9331ef0 
>   
> ambari-server/src/test/java/org/apache/ambari/server/serveraction/upgrades/UpgradeActionTest.java
>  b6bc82e 
> 
> Diff: https://reviews.apache.org/r/43123/diff/
> 
> 
> Testing
> ---
> 
> Ran unit tests in UpgradeActionTest.java and verified on a live cluster
> 
> 
> Thanks,
> 
> Alejandro Fernandez
> 
>

[jira] [Commented] (AMBARI-14525) Longer cluster names extend beyond the frame in the Ambari Admin view.


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

Hadoop QA commented on AMBARI-14525:


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

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

This message is automatically generated.

> Longer cluster names extend beyond the frame in the Ambari Admin view.
> --
>
> Key: AMBARI-14525
> URL: https://issues.apache.org/jira/browse/AMBARI-14525
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-admin
>Affects Versions: 2.1.0
>Reporter: Sangeeta Ravindran
>Assignee: Sangeeta Ravindran
>Priority: Minor
> Attachments: AMBARI-14525.patch, AMBARI-14525_0129.patch, 
> AMBARI-14525_0201.patch, AMBARI-14525_0202.patch, ClusterRenameAlert.jpg, 
> ConfirmClusterRenameModalDlg.jpg, LongClusterNameAdminView.jpg, Screen Shot 
> 2016-02-01 at 18.25.04.jpg, Screen Shot 2016-02-01 at 18.29.11.jpg, 
> ViewInstanceCreationMessage.jpg
>
>
> If the cluster name is long (25+ characters), it extends beyond the frame in 
> the Ambari Admin view and spills into the adjacent frame.
> There also seem similar issues in the alerts and confirmation modal dialog 
> displayed.



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

[jira] [Commented] (AMBARI-14897) Rolling Upgrade: upgrade group status not updated


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

Andrii Tkach commented on AMBARI-14897:
---

24106 tests complete (28 seconds)
  166 tests pending

> Rolling Upgrade: upgrade group status not updated
> -
>
> Key: AMBARI-14897
> URL: https://issues.apache.org/jira/browse/AMBARI-14897
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.2.1
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-14897.patch, AMBARI-14897_branch-2.2.patch, 
> Selection_127.png
>
>
> ambari-server version: ambari-server-2.2.1.0-156.x86_64
> ambari-server --hash: 9a9ecca7809c57e16cfe273c3e7b6df7f63a47c7
> HDP Stack: 2.3
> HDP Version: 2.3.0.0-2557
> 2.4.0.0-149
> Ambari DB: :MySQL
> Oozie/Hive DB: MySQL/MySQL
> Security:no
> Security Type:AD/AD
> Blueprints: false
> Umask: 
> JDK: OracleJDK8
> HA: yes



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

[jira] [Updated] (AMBARI-13946) Non NameNode-HA properties still in hdfs-site.xml causing (at least) Balancer and ATS to fail


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

Benoit Perroud updated AMBARI-13946:

Description: 
After enabling NameNode-HA, {{hdfs-site.xml}} does still contain non-HA 
properties, including

* dfs.namenode.rpc-address
* dfs.namenode.http-address
* dfs.namenode.https-address

This cause the balancer to fail with the following symptoms in Balancer:

{code}
...
15/11/18 15:48:30 INFO balancer.Balancer: namenodes  = [hdfs://daplab2, 
hdfs://daplab-rt-11.fri.lan:8020]
...
java.io.IOException: Another Balancer is running..  Exiting ...
{code}

And ATS:

{code}
_assert_valid
self.target_status = self._get_file_status(target)
  File 
"/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
 line 292, in _get_file_status
list_status = self.util.run_command(target, 'GETFILESTATUS', method='GET', 
ignore_status_codes=['404'], assertable_result=False)
  File 
"/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
 line 210, in run_command
raise Fail(err_msg)
resource_management.core.exceptions.Fail: Execution of 'curl -sS -L -w 
'%{http_code}' -X GET 
'http://pvvsccmn1-brn1:50070/webhdfs/v1/ats/done?op=GETFILESTATUS=hdfs''
 returned status_code=403. 
{
  "RemoteException": {
"exception": "StandbyException", 
"javaClassName": "org.apache.hadoop.ipc.StandbyException", 
"message": "Operation category READ is not supported in state standby"
  }
}
{code}

These should be removed from the config.

Steps to reproduce: after turning on NameNode HA, {{grep 
dfs.namenode.rpc-address|dfs.namenode.http-address 
/etc/hadoop/conf/hdfs-site.xml}} shouldn't return anything


  was:
After enabling NameNode-HA, {{hdfs-site.xml}} does still contain non-HA 
properties, including

* dfs.namenode.rpc-address
* dfs.namenode.http-address
* dfs.namenode.https-address

This cause the balancer to fail with the following symptoms:

{code}
...
15/11/18 15:48:30 INFO balancer.Balancer: namenodes  = [hdfs://daplab2, 
hdfs://daplab-rt-11.fri.lan:8020]
...
java.io.IOException: Another Balancer is running..  Exiting ...
{code}

These should be removed from the config.

Steps to reproduce: after turning on NameNode HA, {{grep 
dfs.namenode.rpc-address /etc/hadoop/conf/hdfs-site.xml}} shouldn't return 
anything


> Non NameNode-HA properties still in hdfs-site.xml causing (at least) Balancer 
> and ATS to fail
> -
>
> Key: AMBARI-13946
> URL: https://issues.apache.org/jira/browse/AMBARI-13946
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.1.2, 2.2.0
> Environment: CentOS6.7, HDP2.3-2950
>Reporter: Benoit Perroud
>
> After enabling NameNode-HA, {{hdfs-site.xml}} does still contain non-HA 
> properties, including
> * dfs.namenode.rpc-address
> * dfs.namenode.http-address
> * dfs.namenode.https-address
> This cause the balancer to fail with the following symptoms in Balancer:
> {code}
> ...
> 15/11/18 15:48:30 INFO balancer.Balancer: namenodes  = [hdfs://daplab2, 
> hdfs://daplab-rt-11.fri.lan:8020]
> ...
> java.io.IOException: Another Balancer is running..  Exiting ...
> {code}
> And ATS:
> {code}
> _assert_valid
> self.target_status = self._get_file_status(target)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
>  line 292, in _get_file_status
> list_status = self.util.run_command(target, 'GETFILESTATUS', 
> method='GET', ignore_status_codes=['404'], assertable_result=False)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
>  line 210, in run_command
> raise Fail(err_msg)
> resource_management.core.exceptions.Fail: Execution of 'curl -sS -L -w 
> '%{http_code}' -X GET 
> 'http://pvvsccmn1-brn1:50070/webhdfs/v1/ats/done?op=GETFILESTATUS=hdfs''
>  returned status_code=403. 
> {
>   "RemoteException": {
> "exception": "StandbyException", 
> "javaClassName": "org.apache.hadoop.ipc.StandbyException", 
> "message": "Operation category READ is not supported in state standby"
>   }
> }
> {code}
> These should be removed from the config.
> Steps to reproduce: after turning on NameNode HA, {{grep 
> dfs.namenode.rpc-address|dfs.namenode.http-address 
> /etc/hadoop/conf/hdfs-site.xml}} shouldn't return anything



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

[jira] [Updated] (AMBARI-14525) Longer cluster names extend beyond the frame in the Ambari Admin view.


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

Antonenko Alexander updated AMBARI-14525:
-
Fix Version/s: 2.4.0

> Longer cluster names extend beyond the frame in the Ambari Admin view.
> --
>
> Key: AMBARI-14525
> URL: https://issues.apache.org/jira/browse/AMBARI-14525
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-admin
>Affects Versions: 2.1.0
>Reporter: Sangeeta Ravindran
>Assignee: Sangeeta Ravindran
>Priority: Minor
> Fix For: 2.4.0
>
> Attachments: AMBARI-14525.patch, AMBARI-14525_0129.patch, 
> AMBARI-14525_0201.patch, AMBARI-14525_0202.patch, ClusterRenameAlert.jpg, 
> ConfirmClusterRenameModalDlg.jpg, LongClusterNameAdminView.jpg, Screen Shot 
> 2016-02-01 at 18.25.04.jpg, Screen Shot 2016-02-01 at 18.29.11.jpg, 
> ViewInstanceCreationMessage.jpg
>
>
> If the cluster name is long (25+ characters), it extends beyond the frame in 
> the Ambari Admin view and spills into the adjacent frame.
> There also seem similar issues in the alerts and confirmation modal dialog 
> displayed.



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

Re: Review Request 43125: [INITIAL PATCH] AMBARI-14892 Add Grafana as a component to AMS


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




ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/metainfo.xml
 (line 69)


Cardinality 1 means - it should be always installed. If we set 0+ , user 
can decide to install grafana or not


- Dmytro Sen


On Фев. 3, 2016, 12:49 д.п., Aravindan Vijayan wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/43125/
> ---
> 
> (Updated Фев. 3, 2016, 12:49 д.п.)
> 
> 
> Review request for Ambari, Dmytro Sen, Sumit Mohanty, Sid Wagle, and Yusaku 
> Sako.
> 
> 
> Bugs: AMBARI-14892
> https://issues.apache.org/jira/browse/AMBARI-14892
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Add a MASTER component called Grafana to AMS service.
> 
> Include install and start/stop/status scripts for the grafana server.
> 
> Config Management for Ambari Metrics - Grafana also part of this patch.
> 
> 
> Diffs
> -
> 
>   
> ambari-metrics/ambari-metrics-timelineservice/conf/unix/ambari-metrics-grafana
>  PRE-CREATION 
>   
> ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/configuration/ams-grafana-env.xml
>  PRE-CREATION 
>   
> ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/configuration/ams-grafana-ini.xml
>  PRE-CREATION 
>   
> ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/metainfo.xml
>  48469df 
>   
> ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/ams.py
>  8fdf4ba 
>   
> ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py
>  PRE-CREATION 
>   
> ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/params.py
>  a1de919 
>   
> ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/status.py
>  59466ad 
>   
> ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/status_params.py
>  d446baa 
> 
> Diff: https://reviews.apache.org/r/43125/diff/
> 
> 
> Testing
> ---
> 
> Manual testing done.
> 
> 
> Thanks,
> 
> Aravindan Vijayan
> 
>

Re: Review Request 43123: RU/EU should only delete configs on downgrade if source stack matches stack whose status is CURRENT

2016-02-03 Thread Nate Cole


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


Ship it!





ambari-server/src/main/java/org/apache/ambari/server/serveraction/upgrades/FinalizeUpgradeAction.java
 (lines 321 - 323)


You're formatting with a mix of text here and a constant.  Would make it a 
bit easier to follow to make it all a constant format string.


- Nate Cole


On Feb. 2, 2016, 7:25 p.m., Alejandro Fernandez wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/43123/
> ---
> 
> (Updated Feb. 2, 2016, 7:25 p.m.)
> 
> 
> Review request for Ambari, Dmytro Grinenko, Dmitro Lisnichenko, Jonathan 
> Hurley, Nate Cole, and Swapan Shridhar.
> 
> 
> Bugs: AMBARI-14891
> https://issues.apache.org/jira/browse/AMBARI-14891
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Saw a case with a customer in which they did the following.
> 
> * Ambari 2.1.2
> * Rolling Upgrade from HDP 2.2 to 2.3.0.0 and skipped the Finalize step, so 
> Ambari never called "Save DB State". Hence, the current stack version was 
> still 2.2. They then modified the host_version and cluster_version records in 
> the DB to mark HDP 2.3 as CURRENT.
> * Forgot to call ambari-server set-current-version
> * Registered and installed bits for HDP 2.3.4.0 and began another RU. After 
> running into an issue, they decided to downgrade, which then completely 
> removed the configs for the target stack (which is HDP 2.3!)
> 
> In order to prevent deleting configs in cases where the user has modified the 
> database, add stronger validation to FinalizeUpgradeAction so that we check 
> that the request's source target stack equals the stack of the repo marked as 
> CURRENT. In this case, they were 2.2 and 2.3, respectively.
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/java/org/apache/ambari/server/serveraction/upgrades/FinalizeUpgradeAction.java
>  9331ef0 
>   
> ambari-server/src/test/java/org/apache/ambari/server/serveraction/upgrades/UpgradeActionTest.java
>  b6bc82e 
> 
> Diff: https://reviews.apache.org/r/43123/diff/
> 
> 
> Testing
> ---
> 
> Ran unit tests in UpgradeActionTest.java and verified on a live cluster
> 
> 
> Thanks,
> 
> Alejandro Fernandez
> 
>

[jira] [Commented] (AMBARI-13946) Non NameNode-HA properties still in hdfs-site.xml causing (at least) Balancer and ATS to fail


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

Benoit Perroud commented on AMBARI-13946:
-

Also in Ambari 2.2.0.0

> Non NameNode-HA properties still in hdfs-site.xml causing (at least) Balancer 
> and ATS to fail
> -
>
> Key: AMBARI-13946
> URL: https://issues.apache.org/jira/browse/AMBARI-13946
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.1.2, 2.2.0
> Environment: CentOS6.7, HDP2.3-2950
>Reporter: Benoit Perroud
>
> After enabling NameNode-HA, {{hdfs-site.xml}} does still contain non-HA 
> properties, including
> * dfs.namenode.rpc-address
> * dfs.namenode.http-address
> * dfs.namenode.https-address
> This cause the balancer to fail with the following symptoms:
> {code}
> ...
> 15/11/18 15:48:30 INFO balancer.Balancer: namenodes  = [hdfs://daplab2, 
> hdfs://daplab-rt-11.fri.lan:8020]
> ...
> java.io.IOException: Another Balancer is running..  Exiting ...
> {code}
> These should be removed from the config.
> Steps to reproduce: after turning on NameNode HA, {{grep 
> dfs.namenode.rpc-address /etc/hadoop/conf/hdfs-site.xml}} shouldn't return 
> anything



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

Re: Review Request 43125: [INITIAL PATCH] AMBARI-14892 Add Grafana as a component to AMS



> On Фев. 3, 2016, 12:57 п.п., Dmytro Sen wrote:
> > ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/metainfo.xml,
> >  line 69
> > 
> >
> > Cardinality 1 means - it should be always installed. If we set 0+ , 
> > user can decide to install grafana or not

or cardinality 0-1


- Dmytro


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


On Фев. 3, 2016, 12:49 д.п., Aravindan Vijayan wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/43125/
> ---
> 
> (Updated Фев. 3, 2016, 12:49 д.п.)
> 
> 
> Review request for Ambari, Dmytro Sen, Sumit Mohanty, Sid Wagle, and Yusaku 
> Sako.
> 
> 
> Bugs: AMBARI-14892
> https://issues.apache.org/jira/browse/AMBARI-14892
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Add a MASTER component called Grafana to AMS service.
> 
> Include install and start/stop/status scripts for the grafana server.
> 
> Config Management for Ambari Metrics - Grafana also part of this patch.
> 
> 
> Diffs
> -
> 
>   
> ambari-metrics/ambari-metrics-timelineservice/conf/unix/ambari-metrics-grafana
>  PRE-CREATION 
>   
> ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/configuration/ams-grafana-env.xml
>  PRE-CREATION 
>   
> ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/configuration/ams-grafana-ini.xml
>  PRE-CREATION 
>   
> ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/metainfo.xml
>  48469df 
>   
> ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/ams.py
>  8fdf4ba 
>   
> ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py
>  PRE-CREATION 
>   
> ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/params.py
>  a1de919 
>   
> ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/status.py
>  59466ad 
>   
> ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/status_params.py
>  d446baa 
> 
> Diff: https://reviews.apache.org/r/43125/diff/
> 
> 
> Testing
> ---
> 
> Manual testing done.
> 
> 
> Thanks,
> 
> Aravindan Vijayan
> 
>

[jira] [Updated] (AMBARI-14897) Rolling Upgrade: upgrade group status not updated


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

Andrii Tkach updated AMBARI-14897:
--
Attachment: Selection_127.png

> Rolling Upgrade: upgrade group status not updated
> -
>
> Key: AMBARI-14897
> URL: https://issues.apache.org/jira/browse/AMBARI-14897
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.2.1
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: Selection_127.png
>
>
> ambari-server version: ambari-server-2.2.1.0-156.x86_64
> ambari-server --hash: 9a9ecca7809c57e16cfe273c3e7b6df7f63a47c7
> HDP Stack: 2.3
> HDP Version: 2.3.0.0-2557
> 2.4.0.0-149
> Ambari DB: :MySQL
> Oozie/Hive DB: MySQL/MySQL
> Security:no
> Security Type:AD/AD
> Blueprints: false
> Umask: 
> JDK: OracleJDK8
> HA: yes



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

[jira] [Commented] (AMBARI-14897) Rolling Upgrade: upgrade group status not updated


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

Oleg Nechiporenko commented on AMBARI-14897:


+1 for patches

> Rolling Upgrade: upgrade group status not updated
> -
>
> Key: AMBARI-14897
> URL: https://issues.apache.org/jira/browse/AMBARI-14897
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.2.1
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-14897.patch, AMBARI-14897_branch-2.2.patch, 
> Selection_127.png
>
>
> ambari-server version: ambari-server-2.2.1.0-156.x86_64
> ambari-server --hash: 9a9ecca7809c57e16cfe273c3e7b6df7f63a47c7
> HDP Stack: 2.3
> HDP Version: 2.3.0.0-2557
> 2.4.0.0-149
> Ambari DB: :MySQL
> Oozie/Hive DB: MySQL/MySQL
> Security:no
> Security Type:AD/AD
> Blueprints: false
> Umask: 
> JDK: OracleJDK8
> HA: yes



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

[jira] [Commented] (AMBARI-14897) Rolling Upgrade: upgrade group status not updated


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

Hadoop QA commented on AMBARI-14897:


{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12786004/AMBARI-14897.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-web.

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

This message is automatically generated.

> Rolling Upgrade: upgrade group status not updated
> -
>
> Key: AMBARI-14897
> URL: https://issues.apache.org/jira/browse/AMBARI-14897
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.2.1
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-14897.patch, AMBARI-14897_branch-2.2.patch, 
> Selection_127.png
>
>
> ambari-server version: ambari-server-2.2.1.0-156.x86_64
> ambari-server --hash: 9a9ecca7809c57e16cfe273c3e7b6df7f63a47c7
> HDP Stack: 2.3
> HDP Version: 2.3.0.0-2557
> 2.4.0.0-149
> Ambari DB: :MySQL
> Oozie/Hive DB: MySQL/MySQL
> Security:no
> Security Type:AD/AD
> Blueprints: false
> Umask: 
> JDK: OracleJDK8
> HA: yes



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

[jira] [Updated] (AMBARI-13946) Non NameNode-HA properties still in hdfs-site.xml causing (at least) Balancer and ATS to fail


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

Benoit Perroud updated AMBARI-13946:

Summary: Non NameNode-HA properties still in hdfs-site.xml causing (at 
least) Balancer and ATS to fail  (was: Non NameNode-HA properties still in 
hdfs-site.xml causing (at least) Balancer to fail)

> Non NameNode-HA properties still in hdfs-site.xml causing (at least) Balancer 
> and ATS to fail
> -
>
> Key: AMBARI-13946
> URL: https://issues.apache.org/jira/browse/AMBARI-13946
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.1.2, 2.2.0
> Environment: CentOS6.7, HDP2.3-2950
>Reporter: Benoit Perroud
>
> After enabling NameNode-HA, {{hdfs-site.xml}} does still contain non-HA 
> properties, including
> * dfs.namenode.rpc-address
> * dfs.namenode.http-address
> * dfs.namenode.https-address
> This cause the balancer to fail with the following symptoms:
> {code}
> ...
> 15/11/18 15:48:30 INFO balancer.Balancer: namenodes  = [hdfs://daplab2, 
> hdfs://daplab-rt-11.fri.lan:8020]
> ...
> java.io.IOException: Another Balancer is running..  Exiting ...
> {code}
> These should be removed from the config.
> Steps to reproduce: after turning on NameNode HA, {{grep 
> dfs.namenode.rpc-address /etc/hadoop/conf/hdfs-site.xml}} shouldn't return 
> anything



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

[jira] [Updated] (AMBARI-13946) Non NameNode-HA properties still in hdfs-site.xml causing (at least) Balancer and ATS to fail


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

Benoit Perroud updated AMBARI-13946:

Affects Version/s: 2.2.0

> Non NameNode-HA properties still in hdfs-site.xml causing (at least) Balancer 
> and ATS to fail
> -
>
> Key: AMBARI-13946
> URL: https://issues.apache.org/jira/browse/AMBARI-13946
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.1.2, 2.2.0
> Environment: CentOS6.7, HDP2.3-2950
>Reporter: Benoit Perroud
>
> After enabling NameNode-HA, {{hdfs-site.xml}} does still contain non-HA 
> properties, including
> * dfs.namenode.rpc-address
> * dfs.namenode.http-address
> * dfs.namenode.https-address
> This cause the balancer to fail with the following symptoms:
> {code}
> ...
> 15/11/18 15:48:30 INFO balancer.Balancer: namenodes  = [hdfs://daplab2, 
> hdfs://daplab-rt-11.fri.lan:8020]
> ...
> java.io.IOException: Another Balancer is running..  Exiting ...
> {code}
> These should be removed from the config.
> Steps to reproduce: after turning on NameNode HA, {{grep 
> dfs.namenode.rpc-address /etc/hadoop/conf/hdfs-site.xml}} shouldn't return 
> anything



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

[jira] [Created] (AMBARI-14898) Alerts: Ability to customize props and thresholds on SCRIPT alerts via Ambari Web UI

Oleg Nechiporenko created AMBARI-14898:
--

 Summary: Alerts: Ability to customize props and thresholds on 
SCRIPT alerts via Ambari Web UI
 Key: AMBARI-14898
 URL: https://issues.apache.org/jira/browse/AMBARI-14898
 Project: Ambari
  Issue Type: Bug
  Components: ambari-web
Affects Versions: 2.4.0
Reporter: Oleg Nechiporenko
Assignee: Oleg Nechiporenko
 Fix For: 2.4.0


Script alerts, such as *Ambari Agent / Host Disk Usage* needs to have some 
metrics Externalized. 

The Usage screens relies on the alert_disk_space.py script to collect metrics 
such as Disk utilization (percentage) and directory being checked. 

The problem is that the directories being check in this script are: 
1. ROOT ("/") 
2. /usr/hdp 
If ROOT is OK, then "/usr/hdp" is checked subsequently. However if ROOT is NOT 
OK (>80% utilization) then "/usr/hdp" is ignored and the "CRITICAL" tag applies 
to ROOT. 

This would work on a OOTB standard cluster. However, many users, have 
Partitions for the hadoop directories. In this instance, "/" is static, no new 
content will be added. In this instance being at 80 or 90% is OK, this 
directory will never grow beyond that. 
"/usr/hdp" is a separate partition that grows in time. 

Based on the above described check, the 80% of the root partition will trigger 
a "CRITICAL" message, although the "/usr/hdp" partition is OK. 

The selection of what directory is being checked should be EXTERNALIZED to a 
configurable property to avoid these kinds of misleading messages. 

CONVERSELY --- what constitutes "OK" "WARN" or "CRIT" (the percentage that 
triggers these) should be left up to the user, not hardcoded in the script. 

This is a request to externalize the directories that should be checked, as 
well as the Percentages into an external configurable property.



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

[jira] [Commented] (AMBARI-14820) Implement Activate HAWQ Standby wizard to allow doing failover in HA mode


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

Hadoop QA commented on AMBARI-14820:


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

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

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

This message is automatically generated.

> Implement Activate HAWQ Standby wizard to allow doing failover in HA mode
> -
>
> Key: AMBARI-14820
> URL: https://issues.apache.org/jira/browse/AMBARI-14820
> Project: Ambari
>  Issue Type: New Feature
>  Components: stacks
>Affects Versions: trunk
>Reporter: bhuvnesh chaudhary
>Assignee: bhuvnesh chaudhary
> Fix For: trunk, 2.2.0
>
> Attachments: AMBARI-14820-1.patch, AMBARI-14820-branch-2.2.patch, 
> AMBARI-14820.patch
>
>
> h1. Activate HAWQ Standby Wizard
> h4. Abstract:
> All configuration changes done on Ambari managed clusters must be done via 
> Ambari, otherwise during restart of services, Ambari pushes the configuration 
> stored in its database and overwrites the changes done manually.
> Activation of HAWQ Standby to active master involves manual command execution 
> which updates the configuration files. In order to keep the configuration in 
> sync and reflect the correct state of the HAWQ components on Ambari, we need 
> to introduce a wizard, i.e *“Activate HAWQ Standby Wizard”*. 
> This wizard will also automate the process of activating standby and the user 
> now will need to walk-through the wizard to activate standby. 
> h4. Overview of activate standby operation:
> * In HA configuration, HAWQ is configured with a master and standby 
> component. 
> * To activate / promote standby to a master, “hawq activate standby” command 
> needs to be executed on the standby
> * This operation updates the value of hawq_master_address_host and 
> hawq_standby_address_host properties available in hawq-site.xml to below
> ** hawq_master_address_host : Initially Configured HAWQ Standby Host
> ** hawq_standby_address_host : This property is removed.
> * After the operation is completed, HAWQ cluster will be running in non-ha 
> mode and will  not have a configured standby.
> h4. Overview of the wizard pages and operation performed:
> The wizard consists of 3 pages, a brief of them is as below:
> # “Get Started”: This page is the first page seen by the user, and it gives 
> introduction of the activity going to be performed. 
> # “Review”: This page is the second page which informs the user about the 
> changes which will happen. A confirmation is requested before proceeding to 
> the next step.
> # “Configure Components”: This page is the third and last page which shows 
> the progress for the steps executed. It does the below:
> ## Execute command to activate HAWQ standby
> ## Stop HAWQ service
> ## Reconfigure HAWQ to push updated configs
> ### hawq_standby_address_host is removed
> ### hawq_master_address_host is updated to previous standby
> ## Install HAWQ Master Ambari Component on the Standby Host
> ## Delete HAWQ Standby Ambari Component on the Standby Host
> ## Delete HAWQ Master Ambari Component on the Master host
> ## Start HAWQ Service



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

Review Request 43152: Pop up to confirm clean directories while adding HAWQ standby

2016-02-03 Thread Newton Alex


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

Review request for Ambari.


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


Repository: ambari


Description
---

Pop up to confirm clean directories while adding HAWQ standby


Diffs
-

  
ambari-web/app/controllers/main/admin/highAvailability/hawq/addStandby/step3_controller.js
 0cb256d 
  ambari-web/app/messages.js 8861b2a 

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


Testing
---

Manual testing done.

Unit tests pass:
--
test loaded in: 0.00ms
Calling set on destroyed view
Calling set on destroyed view
Calling set on destroyed view
Calling set on destroyed view
Missing translation: admin.highAvailability.wizard.step2.header.title
Missing translation: admin.highAvailability.wizard.step2.notice.inProgress

  24140 tests complete (36 seconds)
  156 tests pending

[INFO] 
[INFO] --- apache-rat-plugin:0.11:check (default) @ ambari-web ---
[INFO] RAT will not execute since it is configured to be skipped via system 
property 'rat.skip'.
[INFO] 
[INFO] BUILD SUCCESS
[INFO] 
[INFO] Total time: 53.062s
[INFO] Finished at: Wed Feb 03 14:10:46 PST 2016
[INFO] Final Memory: 5M/81M
[INFO] 
nalex@office-5-146:~/Git/pivotal/ambari/ambari-web# 
--


Thanks,

Newton Alex

[jira] [Created] (AMBARI-14908) AmbariServer:819 - Failed to run the Ambari Server

2016-02-03 Thread sara arroyo (JIRA)

sara arroyo created AMBARI-14908:


 Summary: AmbariServer:819 - Failed to run the Ambari Server
 Key: AMBARI-14908
 URL: https://issues.apache.org/jira/browse/AMBARI-14908
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: 2.1.0
 Environment: DEV
Reporter: sara arroyo


Hi 
I am facing this issue trying to start ambari server:
AmbariServer:819 - Failed to run the Ambari Server

the ambari agent start successfully but for the ambari server: 
I got this in the log:
03 Feb 2016 10:48:53,000  INFO [main] AmbariServer:173 - Found 
org/apache/ambari/server/controller/AmbariServer.class class in 
file:/usr/lib/ambari-server/amba
ri-server-2.2.0_IBM_1-SNAPSHOT.jar!/org/apache/ambari/server/controller/AmbariServer.class
03 Feb 2016 10:48:53,059  INFO [main] Configuration:749 - Reading password from 
existing file
03 Feb 2016 10:48:53,067  INFO [main] Configuration:1079 - Hosts Mapping File 
null
03 Feb 2016 10:48:53,067  INFO [main] HostsMap:60 - Using hostsmap file null
03 Feb 2016 10:48:53,509  INFO [main] ControllerModule:193 - Detected POSTGRES 
as the database type from the JDBC URL
03 Feb 2016 10:48:54,863  INFO [main] ControllerModule:578 - Binding and 
registering notification dispatcher class 
org.apache.ambari.server.notifications.dispa
tchers.AlertScriptDispatcher
03 Feb 2016 10:48:54,869  INFO [main] ControllerModule:578 - Binding and 
registering notification dispatcher class 
org.apache.ambari.server.notifications.dispa
tchers.EmailDispatcher
03 Feb 2016 10:48:54,925  INFO [main] ControllerModule:578 - Binding and 
registering notification dispatcher class 
org.apache.ambari.server.notifications.dispa
tchers.SNMPDispatcher
03 Feb 2016 10:48:57,103  INFO [main] AmbariServer:807 - Getting the controller
03 Feb 2016 10:48:58,055  INFO [main] StackManager:107 - Initializing the stack 
manager...
03 Feb 2016 10:48:58,056  INFO [main] StackManager:267 - Validating stack 
directory /var/lib/ambari-server/resources/stacks ...
03 Feb 2016 10:48:58,056  INFO [main] StackManager:243 - Validating common 
services directory /var/lib/ambari-server/resources/common-services ...
03 Feb 2016 10:48:58,879  INFO [main] StackDirectory:472 - Stack 
'/var/lib/ambari-server/resources/stacks/BigInsights/4.0' doesn't contain 
config upgrade pack
file
03 Feb 2016 10:48:58,896  INFO [main] StackDirectory:488 - Role command order 
info was loaded from file: 
/var/lib/ambari-server/resources/stacks/BigInsights/4.
0/role_command_order.json
03 Feb 2016 10:48:58,909  INFO [main] StackDirectory:472 - Stack 
'/var/lib/ambari-server/resources/stacks/BigInsights/4.1' doesn't contain 
config upgrade pack
file
03 Feb 2016 10:48:58,928  INFO [main] StackDirectory:488 - Role command order 
info was loaded from file: 
/var/lib/ambari-server/resources/stacks/BigInsights/4.
1/role_command_order.json
03 Feb 2016 10:48:58,943  INFO [main] StackDirectory:472 - Stack 
'/var/lib/ambari-server/resources/stacks/BigInsights/4.2' doesn't contain 
config upgrade pack
file
03 Feb 2016 10:48:58,963  INFO [main] StackDirectory:488 - Role command order 
info was loaded from file: 
/var/lib/ambari-server/resources/stacks/BigInsights/4.
2/role_command_order.json
03 Feb 2016 10:48:59,462  INFO [main] ActionDefinitionManager:124 - Added 
custom action definition for check_host
03 Feb 2016 10:48:59,462  INFO [main] ActionDefinitionManager:124 - Added 
custom action definition for update_repo
03 Feb 2016 10:48:59,462  INFO [main] ActionDefinitionManager:124 - Added 
custom action definition for validate_configs
03 Feb 2016 10:48:59,463  INFO [main] ActionDefinitionManager:124 - Added 
custom action definition for install_packages
03 Feb 2016 10:48:59,463  INFO [main] ActionDefinitionManager:124 - Added 
custom action definition for ru_execute_tasks
03 Feb 2016 10:48:59,466  INFO [main] CertificateManager:68 - Initialization of 
root certificate
03 Feb 2016 10:48:59,466  INFO [main] CertificateManager:70 - Certificate 
exists:true
03 Feb 2016 10:48:59,625  INFO [main] Configuration:846 - Credential provider 
creation failed. Reason: Master key initialization failed.
03 Feb 2016 10:48:59,637  INFO [main] ClustersImpl:166 - Initializing the 
ClustersImpl
03 Feb 2016 10:48:59,935  INFO [main] CredentialStoreServiceImpl:59 - 
Initialized the temporary credential store. KeyStore entries will be retained 
for 90 minu
tes and will be actively purged
03 Feb 2016 10:48:59,936  INFO [main] AmbariManagementControllerImpl:304 - 
Initializing the AmbariManagementControllerImpl
03 Feb 2016 10:48:59,991  INFO [main] DatabaseChecker:151 - Checking DB store 
version
03 Feb 2016 10:48:59,993  INFO [main] DatabaseChecker:177 - DB store version is 
compatible
03 Feb 2016 10:48:59,993  INFO [main] DatabaseChecker:55 - Checking DB 
consistency
03 Feb 2016 10:49:00,048 ERROR [main] AmbariServer:819 - Failed to run the 
Ambari

[jira] [Commented] (AMBARI-14834) Register Version: make the 'Repositories' category editable and addable


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

Hadoop QA commented on AMBARI-14834:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12786075/Screen%20Shot%202016-01-27%20at%204.08.17%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/5189//console

This message is automatically generated.

> Register Version: make the 'Repositories' category editable and addable
> ---
>
> Key: AMBARI-14834
> URL: https://issues.apache.org/jira/browse/AMBARI-14834
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Xi Wang
>Assignee: Xi Wang
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-14834.patch, Screen Shot 2016-01-27 at 4.08.17 
> PM.png
>
>
> This one is the third part to implement" Manage Ambari > Register Version" 
> page. 
> Should implement:
> 1. Display all the repo urls loaded from version definition file.
> 2. Each of the urls should be editable.
> 3. Add ability to add new OS (new repo urls for new OS).
> 4. Validate urls, avoid redundant OS, at least one OS .etc



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

Re: Review Request 43140: Make AMS Grafana component available as a repo package

2016-02-03 Thread Sid Wagle


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


Ship it!




Does the exectuion get called for debian as well?
https://cwiki.apache.org/confluence/display/AMBARI/Build+Instructions

- Sid Wagle


On Feb. 3, 2016, 4:15 p.m., Dmytro Sen wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/43140/
> ---
> 
> (Updated Feb. 3, 2016, 4:15 p.m.)
> 
> 
> Review request for Ambari, Aravindan Vijayan, Sid Wagle, and Yusaku Sako.
> 
> 
> Bugs: AMBARI-14902
> https://issues.apache.org/jira/browse/AMBARI-14902
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Grafana 2.6.0 to be installed as an AMS component. We need this to be a part 
> of the Ambari repo so that Ambari can install it with AMS.
> 
> 
> Diffs
> -
> 
>   ambari-metrics/ambari-metrics-assembly/pom.xml e963b00 
>   ambari-metrics/ambari-metrics-assembly/src/main/assembly/grafana.xml 
> PRE-CREATION 
>   ambari-metrics/ambari-metrics-grafana/conf/unix/ambari-metrics-grafana 
> PRE-CREATION 
>   ambari-metrics/ambari-metrics-grafana/conf/unix/ams-grafana-env.sh 
> PRE-CREATION 
>   ambari-metrics/ambari-metrics-grafana/conf/unix/ams-grafana.ini 
> PRE-CREATION 
>   ambari-metrics/ambari-metrics-grafana/pom.xml PRE-CREATION 
>   ambari-metrics/ambari-metrics-grafana/src/main/assemblies/empty.xml 
> PRE-CREATION 
>   ambari-metrics/pom.xml 44964d4 
>   pom.xml fe139b8 
> 
> Diff: https://reviews.apache.org/r/43140/diff/
> 
> 
> Testing
> ---
> 
> Unit tests passed
> 
> 
> Thanks,
> 
> Dmytro Sen
> 
>

[jira] [Commented] (AMBARI-14855) Add Alert for HAWQSTANDBY sync status with HAWQMASTER

2016-02-03 Thread Hudson (JIRA)


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

Hudson commented on AMBARI-14855:
-

FAILURE: Integrated in Ambari-branch-2.2 #286 (See 
[https://builds.apache.org/job/Ambari-branch-2.2/286/])
AMBARI-14855: Add Alert for HAWQSTANDBY sync status with HAWQMASTER (jaoki: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=78c7755c00e4142898403ab5bc3af89820ad80f2])
* ambari-server/src/test/python/stacks/2.3/HAWQ/test_alert_sync_status.py
* 
ambari-server/src/main/resources/common-services/HAWQ/2.0.0/package/alerts/alert_sync_status.py
* ambari-server/src/main/resources/common-services/HAWQ/2.0.0/alerts.json


> Add Alert for HAWQSTANDBY sync status with HAWQMASTER
> -
>
> Key: AMBARI-14855
> URL: https://issues.apache.org/jira/browse/AMBARI-14855
> Project: Ambari
>  Issue Type: New Feature
>  Components: stacks
>Reporter: Matt
>Assignee: Matt
>Priority: Minor
> Fix For: trunk, 2.2.2
>
> Attachments: AMBARI-14855-branch-2.2.patch, 
> AMBARI-14855-trunk-v-2.patch, AMBARI-14855-trunk-v-3.patch, 
> AMBARI-14855-trunk-v-4.patch, AMBARI-14855-trunk-v-5.patch, 
> AMBARI-14855-trunk-v-6.patch, AMBARI-14855-trunk.patch
>
>
> HAWQSTANDBY can go out of sync with HAWQMASTER. Show an alert when 
> HAWQSTANDBY is not in sync with HAWQMASTER.



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

[jira] [Commented] (AMBARI-14909) Add a clean data dir confirmation pop-up to HAWQ add slave wizard

2016-02-03 Thread Newton Alex (JIRA)


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

Newton Alex commented on AMBARI-14909:
--

The same patch applies fine on both trunk and branch-2.2.

> Add a clean data dir confirmation pop-up to HAWQ add slave wizard
> -
>
> Key: AMBARI-14909
> URL: https://issues.apache.org/jira/browse/AMBARI-14909
> Project: Ambari
>  Issue Type: New Feature
>Affects Versions: 2.2.1
>Reporter: Newton Alex
>Assignee: Newton Alex
> Fix For: 2.3.0
>
> Attachments: AMBARI-14909.patch
>
>
> In the HAWQ add slave wizard, in step3, add a confirmation pop-up asking the 
> user if the data directory has been cleaned up.



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

[jira] [Commented] (AMBARI-14907) Metrics not displayed for "Last 1 year" period.


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

Hadoop QA commented on AMBARI-14907:


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

This message is automatically generated.

> Metrics not displayed for "Last 1 year" period.
> ---
>
> Key: AMBARI-14907
> URL: https://issues.apache.org/jira/browse/AMBARI-14907
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics
>Affects Versions: 2.2.1
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>  Labels: ambari-metrics
> Fix For: 2.2.2
>
> Attachments: AMBARI-14907.patch
>
>
> PROBLEM
> Metrics not displayed for Last 1 year period interval on Ambari.
> BUG
> The daily aggregator discards the last timestamp because it is fractionally 
> more in the past than the cutOff time. We use 1*DAY as current cutoff. This 
> can cause checkpoints to be dropped intermittently.
> FIX
> Change cutOff multiplier for daily aggregators from 1 to 2.



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

Review Request 43146: Add API directive to force toggling Kerberos if the cluster's security type has not changed

2016-02-03 Thread Robert Levas


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

Review request for Ambari, Jonathan Hurley, Nate Cole, and Robert Nettleton.


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


Repository: ambari


Description
---

Add an API directive to force toggling Kerberos if the cluster's security type 
has not changed.  

This is useful for _retry_ attempts to enable or disable Kerberos when the 
workflow progressed far enough to store the _new_ security type.  

Trying to enable Kerberos when the cluster's security type is already set to 
`KERBEROS` will result in a successful response from the Ambari server but no 
actions will be performed.  Same for attempting to disable Kerberos when the 
cluster's security type is already set to `NONE`.  

By forcing the operation using the `force_toggle_kerberos=true` directive, the 
security type check is avoided, thus allowing the _retry_ operation to proceed. 

Example: 
```
PUT /api/v1/clusters/CLUSTER_NAME?force_toggle_kerberos=true
{
  "Clusters" : {
"security_type" : "KERBEROS"
}
}
```


Diffs
-

  
ambari-server/src/main/java/org/apache/ambari/server/api/resources/ClusterResourceDefinition.java
 b2be291 
  
ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariManagementControllerImpl.java
 5010311 
  
ambari-server/src/main/java/org/apache/ambari/server/controller/KerberosHelper.java
 5008d60 
  
ambari-server/src/main/java/org/apache/ambari/server/controller/KerberosHelperImpl.java
 63aa92d 
  
ambari-server/src/test/java/org/apache/ambari/server/controller/AmbariManagementControllerImplTest.java
 5838001 
  
ambari-server/src/test/java/org/apache/ambari/server/controller/KerberosHelperTest.java
 869d187 

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


Testing
---

Manually tested (via API calls)

# Local test results: 
[INFO] 
[INFO] BUILD SUCCESS
[INFO] 
[INFO] Total time: 57:10.059s
[INFO] Finished at: Wed Feb 03 15:24:15 EST 2016
[INFO] Final Memory: 71M/1409M
[INFO] 

# Jenkins test results: PENDING


Thanks,

Robert Levas

[jira] [Updated] (AMBARI-14908) AmbariServer:819 - Failed to run the Ambari Server

2016-02-03 Thread sara arroyo (JIRA)


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

sara arroyo updated AMBARI-14908:
-
Affects Version/s: (was: 2.1.0)
   2.2.0

> AmbariServer:819 - Failed to run the Ambari Server
> --
>
> Key: AMBARI-14908
> URL: https://issues.apache.org/jira/browse/AMBARI-14908
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.2.0
> Environment: DEV
>Reporter: sara arroyo
>
> Hi 
> I am facing this issue trying to start ambari server:
> AmbariServer:819 - Failed to run the Ambari Server
> the ambari agent start successfully but for the ambari server: 
> I got this in the log:
> 03 Feb 2016 10:48:53,000  INFO [main] AmbariServer:173 - Found 
> org/apache/ambari/server/controller/AmbariServer.class class in 
> file:/usr/lib/ambari-server/amba
> ri-server-2.2.0_IBM_1-SNAPSHOT.jar!/org/apache/ambari/server/controller/AmbariServer.class
> 03 Feb 2016 10:48:53,059  INFO [main] Configuration:749 - Reading password 
> from existing file
> 03 Feb 2016 10:48:53,067  INFO [main] Configuration:1079 - Hosts Mapping File 
> null
> 03 Feb 2016 10:48:53,067  INFO [main] HostsMap:60 - Using hostsmap file null
> 03 Feb 2016 10:48:53,509  INFO [main] ControllerModule:193 - Detected 
> POSTGRES as the database type from the JDBC URL
> 03 Feb 2016 10:48:54,863  INFO [main] ControllerModule:578 - Binding and 
> registering notification dispatcher class 
> org.apache.ambari.server.notifications.dispa
> tchers.AlertScriptDispatcher
> 03 Feb 2016 10:48:54,869  INFO [main] ControllerModule:578 - Binding and 
> registering notification dispatcher class 
> org.apache.ambari.server.notifications.dispa
> tchers.EmailDispatcher
> 03 Feb 2016 10:48:54,925  INFO [main] ControllerModule:578 - Binding and 
> registering notification dispatcher class 
> org.apache.ambari.server.notifications.dispa
> tchers.SNMPDispatcher
> 03 Feb 2016 10:48:57,103  INFO [main] AmbariServer:807 - Getting the 
> controller
> 03 Feb 2016 10:48:58,055  INFO [main] StackManager:107 - Initializing the 
> stack manager...
> 03 Feb 2016 10:48:58,056  INFO [main] StackManager:267 - Validating stack 
> directory /var/lib/ambari-server/resources/stacks ...
> 03 Feb 2016 10:48:58,056  INFO [main] StackManager:243 - Validating common 
> services directory /var/lib/ambari-server/resources/common-services ...
> 03 Feb 2016 10:48:58,879  INFO [main] StackDirectory:472 - Stack 
> '/var/lib/ambari-server/resources/stacks/BigInsights/4.0' doesn't contain 
> config upgrade pack
> file
> 03 Feb 2016 10:48:58,896  INFO [main] StackDirectory:488 - Role command order 
> info was loaded from file: 
> /var/lib/ambari-server/resources/stacks/BigInsights/4.
> 0/role_command_order.json
> 03 Feb 2016 10:48:58,909  INFO [main] StackDirectory:472 - Stack 
> '/var/lib/ambari-server/resources/stacks/BigInsights/4.1' doesn't contain 
> config upgrade pack
> file
> 03 Feb 2016 10:48:58,928  INFO [main] StackDirectory:488 - Role command order 
> info was loaded from file: 
> /var/lib/ambari-server/resources/stacks/BigInsights/4.
> 1/role_command_order.json
> 03 Feb 2016 10:48:58,943  INFO [main] StackDirectory:472 - Stack 
> '/var/lib/ambari-server/resources/stacks/BigInsights/4.2' doesn't contain 
> config upgrade pack
> file
> 03 Feb 2016 10:48:58,963  INFO [main] StackDirectory:488 - Role command order 
> info was loaded from file: 
> /var/lib/ambari-server/resources/stacks/BigInsights/4.
> 2/role_command_order.json
> 03 Feb 2016 10:48:59,462  INFO [main] ActionDefinitionManager:124 - Added 
> custom action definition for check_host
> 03 Feb 2016 10:48:59,462  INFO [main] ActionDefinitionManager:124 - Added 
> custom action definition for update_repo
> 03 Feb 2016 10:48:59,462  INFO [main] ActionDefinitionManager:124 - Added 
> custom action definition for validate_configs
> 03 Feb 2016 10:48:59,463  INFO [main] ActionDefinitionManager:124 - Added 
> custom action definition for install_packages
> 03 Feb 2016 10:48:59,463  INFO [main] ActionDefinitionManager:124 - Added 
> custom action definition for ru_execute_tasks
> 03 Feb 2016 10:48:59,466  INFO [main] CertificateManager:68 - Initialization 
> of root certificate
> 03 Feb 2016 10:48:59,466  INFO [main] CertificateManager:70 - Certificate 
> exists:true
> 03 Feb 2016 10:48:59,625  INFO [main] Configuration:846 - Credential provider 
> creation failed. Reason: Master key initialization failed.
> 03 Feb 2016 10:48:59,637  INFO [main] ClustersImpl:166 - Initializing the 
> ClustersImpl
> 03 Feb 2016 10:48:59,935  INFO [main] CredentialStoreServiceImpl:59 - 
> Initialized the temporary credential store. KeyStore entries will be retained 
> for 90 minu
> tes and will be actively purged
> 03 Feb 2016 10:48:59,936  INFO [main]

Review Request 43147: AMBARI-14906: Text update for conf_select.py

2016-02-03 Thread Di Li


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

Review request for Ambari and Jaimin Jetly.


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


Repository: ambari


Description
---

A small text update for conf_select.py


Diffs
-

  
ambari-common/src/main/python/resource_management/libraries/functions/conf_select.py
 2bc01ee 

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


Testing
---

manually patch a cluster to test it out.


Thanks,

Di Li

[jira] [Created] (AMBARI-14909) Add a clean data dir confirmation pop-up to HAWQ add slave wizard

2016-02-03 Thread Newton Alex (JIRA)

Newton Alex created AMBARI-14909:


 Summary: Add a clean data dir confirmation pop-up to HAWQ add 
slave wizard
 Key: AMBARI-14909
 URL: https://issues.apache.org/jira/browse/AMBARI-14909
 Project: Ambari
  Issue Type: New Feature
Affects Versions: 2.2.1
Reporter: Newton Alex
Assignee: Newton Alex
 Fix For: 2.3.0


In the HAWQ add slave wizard, in step3, add a confirmation pop-up asking the 
user if the data directory has been cleaned up.



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

Re: [VOTE] Apache Ambari 2.2.1 RC2

2016-02-03 Thread Mahadev Konar

+1




On 2/3/16, 9:59 AM, "Jayush Luniya"  wrote:

>+1 for RC2.
>
>On 2/3/16, 6:59 AM, "Nate Cole"  wrote:
>
>>+1 for RC2
>>
>>On 2/1/16, 5:44 PM, "Robert Levas"  wrote:
>>
>>>Team...
>>>
>>>I have created a new ambari-2.2.1 release candidate.
>>>
>>>GIT source tag (release-2.2.1-rc2)
>>>https://git-wip-us.apache.org/repos/asf/ambari/repo?p=ambari.git;a=log;h=
>>>r
>>>efs/tags/release-2.2.1-rc2
>>>
>>>Staging site: http://people.apache.org/~rlevas/apache-ambari-2.2.1-rc2
>>>
>>>PGP release keys (signed using 0EF56BD9)
>>>http://pgp.mit.edu:11371/pks/lookup?op=vindex=0x0EF56BD9
>>>
>>>One can look into the issues fixed in this release at
>>>https://issues.apache.org/jira/browse/AMBARI/fixforversion/12334307/?sele
>>>c
>>>tedTab=com.atlassian.jira.jira-projects-plugin:version-summary-panel
>>>
>>>Vote will be open for 72 hours.
>>>[ ] +1 approve
>>>[ ] +0 no opinion
>>>[ ] -1 disapprove (and reason why)
>>>
>>>
>>>
>>>Thanks
>>>Rob
>>>
>>>
>>>
>>
>>
>
>

Re: NEW Ambari Functionality - Proposal: Users should be able to add repositories on existing cluster

2016-02-03 Thread Di Li

Hello Matt,

Please also take a look at two existing JIRAs attacking issues that cover 
adding new repos vs installing/patching rpms, extending stacks.

AMBARI-12556 >> Patch management (different purposes of allowing adding new 
repos)
https://issues.apache.org/jira/browse/AMBARI-12556

AMBARI-12885 >> Stack extension (cover both extending stacks as well as add new 
repos)
This one also has a branch with work in process code changes already...
https://issues.apache.org/jira/browse/AMBARI-12885


Thank you.
Di


  From: Mithun Mathew 
 To: dev@ambari.apache.org 
 Sent: Wednesday, February 3, 2016 2:07 PM
 Subject: NEW Ambari Functionality - Proposal: Users should be able to add 
repositories on existing cluster
   
Hi Ambari Developers

There is a JIRA for introducing new Ambari functionality, for adding new 
repositories to an existing cluster.
JIRA: https://issues.apache.org/jira/browse/AMBARI-13216
Brief description: "Current Ambari (2.2.0) does not support adding new 
repositories to the existing ones that arepredefined in the stack." The 
proposal is to bring in new functionality for users to add repositories through 
UI. This would allow them to install any pluggable services using rpms/tars 
hosted on external repositories.  
A design document has been attached to the JIRA. Please feel free to review it, 
add comments and suggest possible enhancements.

RegardsMatt
-- 
Mithun Mathew (Matt)   
   -   
 - www.linkedin.com/in/mithunmatt/

[jira] [Updated] (AMBARI-14871) Better messages when Ambari web UI can't resolve hosts to build quicklinks

2016-02-03 Thread Di Li (JIRA)


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

Di Li updated AMBARI-14871:
---
Attachment: AMBARI-14871.patch

> Better messages when Ambari web UI can't resolve hosts to build quicklinks
> --
>
> Key: AMBARI-14871
> URL: https://issues.apache.org/jira/browse/AMBARI-14871
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: trunk
>Reporter: Di Li
>Assignee: Di Li
> Fix For: trunk
>
> Attachments: AMBARI-14871.patch
>
>
> It currently says "Hostname is undefined". This JIRA is to update the logic a 
> little bit in an attempt to display better error messages.



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

[jira] [Commented] (AMBARI-14893) Add Grafana-based Ambari Metrics Dashboard Builder


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

Hadoop QA commented on AMBARI-14893:


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

This message is automatically generated.

> Add Grafana-based Ambari Metrics Dashboard Builder
> --
>
> Key: AMBARI-14893
> URL: https://issues.apache.org/jira/browse/AMBARI-14893
> Project: Ambari
>  Issue Type: New Feature
>  Components: ambari-metrics
>Affects Versions: 2.2.2
>Reporter: Yusaku Sako
>Assignee: Prajwal Rao
> Fix For: 2.2.2
>
> Attachments: AMBARI-14893.patch, screenshots.tar.gz
>
>
> This is a Grafana datasource that allows visualization of metrics stored in 
> Ambari Metrics Collector.



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

[jira] [Commented] (AMBARI-14902) Make AMS Grafana component available as a repo package


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

Hadoop QA commented on AMBARI-14902:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12786055/AMBARI-14902-trunk-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:red}-1 javac{color}.  The applied patch generated 68 javac 
compiler warnings (more than the trunk's current 65 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/5191//testReport/
Javac warnings: 
https://builds.apache.org/job/Ambari-trunk-test-patch/5191//artifact/trunk/patchprocess/diffJavacWarnings.txt
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/5191//console

This message is automatically generated.

> Make AMS Grafana component available as a repo package
> --
>
> Key: AMBARI-14902
> URL: https://issues.apache.org/jira/browse/AMBARI-14902
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-metrics
>Affects Versions: 2.2.2
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-14902-trunk-2.patch
>
>
> Grafana 2.6.0 to be installed as an AMS component. We need this to be a part 
> of the Ambari repo so that Ambari can install it with AMS.



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

Re: [VOTE] Apache Ambari 2.2.1 RC2

2016-02-03 Thread Siddharth Wagle

+1 for RC2.

- Sid

From: Jayush Luniya 
Sent: Wednesday, February 03, 2016 9:59 AM
To: dev@ambari.apache.org
Subject: Re: [VOTE] Apache Ambari 2.2.1 RC2

+1 for RC2.

On 2/3/16, 6:59 AM, "Nate Cole"  wrote:

>+1 for RC2
>
>On 2/1/16, 5:44 PM, "Robert Levas"  wrote:
>
>>Team...
>>
>>I have created a new ambari-2.2.1 release candidate.
>>
>>GIT source tag (release-2.2.1-rc2)
>>https://git-wip-us.apache.org/repos/asf/ambari/repo?p=ambari.git;a=log;h=
>>r
>>efs/tags/release-2.2.1-rc2
>>
>>Staging site: http://people.apache.org/~rlevas/apache-ambari-2.2.1-rc2
>>
>>PGP release keys (signed using 0EF56BD9)
>>http://pgp.mit.edu:11371/pks/lookup?op=vindex=0x0EF56BD9
>>
>>One can look into the issues fixed in this release at
>>https://issues.apache.org/jira/browse/AMBARI/fixforversion/12334307/?sele
>>c
>>tedTab=com.atlassian.jira.jira-projects-plugin:version-summary-panel
>>
>>Vote will be open for 72 hours.
>>[ ] +1 approve
>>[ ] +0 no opinion
>>[ ] -1 disapprove (and reason why)
>>
>>
>>
>>Thanks
>>Rob
>>
>>
>>
>
>

[jira] [Commented] (AMBARI-14855) Add Alert for HAWQSTANDBY sync status with HAWQMASTER

2016-02-03 Thread Hudson (JIRA)


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

Hudson commented on AMBARI-14855:
-

SUCCESS: Integrated in Ambari-trunk-Commit #4270 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/4270/])
AMBARI-14855: Add Alert for HAWQSTANDBY sync status with HAWQMASTER (jaoki: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=424cca6c3744eca2c44dff0fbc47791492845f88])
* ambari-server/src/test/python/stacks/2.3/HAWQ/test_alert_sync_status.py
* 
ambari-server/src/main/resources/common-services/HAWQ/2.0.0/package/alerts/alert_sync_status.py
* ambari-server/src/main/resources/common-services/HAWQ/2.0.0/alerts.json


> Add Alert for HAWQSTANDBY sync status with HAWQMASTER
> -
>
> Key: AMBARI-14855
> URL: https://issues.apache.org/jira/browse/AMBARI-14855
> Project: Ambari
>  Issue Type: New Feature
>  Components: stacks
>Reporter: Matt
>Assignee: Matt
>Priority: Minor
> Fix For: trunk, 2.2.2
>
> Attachments: AMBARI-14855-branch-2.2.patch, 
> AMBARI-14855-trunk-v-2.patch, AMBARI-14855-trunk-v-3.patch, 
> AMBARI-14855-trunk-v-4.patch, AMBARI-14855-trunk-v-5.patch, 
> AMBARI-14855-trunk-v-6.patch, AMBARI-14855-trunk.patch
>
>
> HAWQSTANDBY can go out of sync with HAWQMASTER. Show an alert when 
> HAWQSTANDBY is not in sync with HAWQMASTER.



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

[jira] [Commented] (AMBARI-12885) Dynamic stack extensions - install and upgrade support for custom services

2016-02-03 Thread Di Li (JIRA)


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

Di Li commented on AMBARI-12885:


Matt suggested a design for AMBARI-13216 that covers adding new repos to an 
existing cluster...

> Dynamic stack extensions - install and upgrade support for custom services
> --
>
> Key: AMBARI-12885
> URL: https://issues.apache.org/jira/browse/AMBARI-12885
> Project: Ambari
>  Issue Type: New Feature
>  Components: ambari-agent, ambari-server, ambari-web
>Reporter: Tim Thorpe
>Assignee: Tim Thorpe
> Attachments: Dynamic Stack Extensions - High Level Design v4.pdf
>
>
> The purpose of this proposal is to facilitate adding custom services to an 
> existing stack.  Ideally this would support adding and upgrading custom 
> services separately from the core services defined in the stack.  In 
> particular we are looking at custom services that need to support several 
> different stacks (different distributions of Ambari).  The release cycle of 
> the custom services may be different from that of the core stack; that is, a 
> custom service may be upgraded at a different rate than the core distribution 
> itself and may be upgraded multiple times within the lifespan of a single 
> release of the core distribution.
> One possible approach to handling this would be dynamically extending a stack 
> (after install time).  It would be best to extend the stack in packages where 
> a stack extension package can have one or more custom services.



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

[jira] [Updated] (AMBARI-14905) Add API directive to force toggling Kerberos if the cluster's security type has not changed

2016-02-03 Thread Robert Levas (JIRA)


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

Robert Levas updated AMBARI-14905:
--
Attachment: AMBARI-14905_trunk_01.patch
AMBARI-14905_branch-2.2_01.patch

> Add API directive to force toggling Kerberos if the cluster's security type 
> has not changed
> ---
>
> Key: AMBARI-14905
> URL: https://issues.apache.org/jira/browse/AMBARI-14905
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Affects Versions: 2.2.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>  Labels: kerberos, rest_api
> Fix For: 2.2.2
>
> Attachments: AMBARI-14905_branch-2.2_01.patch, 
> AMBARI-14905_trunk_01.patch
>
>
> Add an API directive to force toggling Kerberos if the cluster's security 
> type has not changed.  
> This is useful for _retry_ attempts to enable or disable Kerberos when the 
> workflow progressed far enough to store the _new_ security type.  
> Trying to enable Kerberos when the cluster's security type is already set to 
> {{KERBEROS}} will result in a successful response from the Ambari server but 
> no actions will be performed.  Same for attempting to disable Kerberos when 
> the cluster's security type is already set to {{NONE}}.  
> By forcing the operation using the {{force_toggle_kerberos=true}} directive, 
> the security type check is avoided, thus allowing the _retry_ operation to 
> proceed. 
> Example: 
> {code}
> PUT /api/v1/clusters/CLUSTER_NAME?force_toggle_kerberos=true
> {
>   "Clusters" : {
> "security_type" : "KERBEROS"
> }
> }
> {code}



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

[jira] [Commented] (AMBARI-14884) Hawq standby host config should be removed on single node cluster during initial cluster installation


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

Hadoop QA commented on AMBARI-14884:


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

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

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

This message is automatically generated.

> Hawq standby host config should be removed on single node cluster during 
> initial cluster installation
> -
>
> Key: AMBARI-14884
> URL: https://issues.apache.org/jira/browse/AMBARI-14884
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: trunk
>Reporter: bhuvnesh chaudhary
>Assignee: bhuvnesh chaudhary
>Priority: Trivial
> Fix For: trunk, 2.2.0
>
> Attachments: AMBARI-14884-1.patch, AMBARI-14884-branch-2.2.patch, 
> AMBARI-14884.patch
>
>
> Hawq standby host config should be removed on single node cluster during 
> initial cluster installation.
> Currently, it works only if the cluster is installed and Hawq is added later, 
> but during initial single node installation of cluster with Hawq, it does not.



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

[jira] [Commented] (AMBARI-14906) Text update for conf_select.py


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

Hadoop QA commented on AMBARI-14906:


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

This message is automatically generated.

> Text update for conf_select.py
> --
>
> Key: AMBARI-14906
> URL: https://issues.apache.org/jira/browse/AMBARI-14906
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk
>Reporter: Di Li
>Assignee: Di Li
>Priority: Minor
> Fix For: trunk
>
> Attachments: AMBARI-14906.patch
>
>
> A small text update for conf_select.py



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

[jira] [Updated] (AMBARI-14909) Add a clean data dir confirmation pop-up to HAWQ add slave wizard

2016-02-03 Thread Newton Alex (JIRA)


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

Newton Alex updated AMBARI-14909:
-
Attachment: AMBARI-14909.patch

> Add a clean data dir confirmation pop-up to HAWQ add slave wizard
> -
>
> Key: AMBARI-14909
> URL: https://issues.apache.org/jira/browse/AMBARI-14909
> Project: Ambari
>  Issue Type: New Feature
>Affects Versions: 2.2.1
>Reporter: Newton Alex
>Assignee: Newton Alex
> Fix For: 2.3.0
>
> Attachments: AMBARI-14909.patch
>
>
> In the HAWQ add slave wizard, in step3, add a confirmation pop-up asking the 
> user if the data directory has been cleaned up.



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

Re: Review Request 43125: [INITIAL PATCH] AMBARI-14892 Add Grafana as a component to AMS

2016-02-03 Thread Aravindan Vijayan


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

(Updated Feb. 3, 2016, 8:55 p.m.)


Review request for Ambari, Dmytro Sen, Sumit Mohanty, Sid Wagle, and Yusaku 
Sako.


Changes
---

Addressed review comments.


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


Repository: ambari


Description
---

Add a MASTER component called Grafana to AMS service.

Include install and start/stop/status scripts for the grafana server.

Config Management for Ambari Metrics - Grafana also part of this patch.


Diffs (updated)
-

  
ambari-metrics/ambari-metrics-timelineservice/conf/unix/ambari-metrics-grafana 
PRE-CREATION 
  
ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/configuration/ams-grafana-env.xml
 PRE-CREATION 
  
ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/configuration/ams-grafana-ini.xml
 PRE-CREATION 
  
ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/metainfo.xml
 48469df 
  
ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/ams.py
 8fdf4ba 
  
ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py
 PRE-CREATION 
  
ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/params.py
 a1de919 
  
ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/status.py
 59466ad 
  
ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/status_params.py
 d446baa 

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


Testing
---

Manual testing done.


Thanks,

Aravindan Vijayan

[jira] [Updated] (AMBARI-14871) Better messages when Ambari web UI can't resolve hosts to build quicklinks

2016-02-03 Thread Di Li (JIRA)


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

Di Li updated AMBARI-14871:
---
Attachment: (was: AMBARI-14871.patch)

> Better messages when Ambari web UI can't resolve hosts to build quicklinks
> --
>
> Key: AMBARI-14871
> URL: https://issues.apache.org/jira/browse/AMBARI-14871
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: trunk
>Reporter: Di Li
>Assignee: Di Li
> Fix For: trunk
>
>
> It currently says "Hostname is undefined". This JIRA is to update the logic a 
> little bit in an attempt to display better error messages.



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

Re: Review Request 43147: AMBARI-14906: Text update for conf_select.py

2016-02-03 Thread Alejandro Fernandez


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


Ship it!




- Alejandro Fernandez


On Feb. 3, 2016, 9:31 p.m., Di Li wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/43147/
> ---
> 
> (Updated Feb. 3, 2016, 9:31 p.m.)
> 
> 
> Review request for Ambari and Alejandro Fernandez.
> 
> 
> Bugs: AMBARI-14906
> https://issues.apache.org/jira/browse/AMBARI-14906
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> A small text update for conf_select.py
> 
> 
> Diffs
> -
> 
>   
> ambari-common/src/main/python/resource_management/libraries/functions/conf_select.py
>  2bc01ee 
> 
> Diff: https://reviews.apache.org/r/43147/diff/
> 
> 
> Testing
> ---
> 
> manually patch a cluster to test it out.
> 
> 
> Thanks,
> 
> Di Li
> 
>

[jira] [Commented] (AMBARI-14898) Alerts: Ability to customize props and thresholds on SCRIPT alerts via Ambari Web UI


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

Oleg Nechiporenko commented on AMBARI-14898:


  24136 tests complete (19 seconds)
  156 tests pending

> Alerts: Ability to customize props and thresholds on SCRIPT alerts via Ambari 
> Web UI
> 
>
> Key: AMBARI-14898
> URL: https://issues.apache.org/jira/browse/AMBARI-14898
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: 2.4.0
>
> Attachments: AMBARI-14898.patch
>
>
> Script alerts, such as *Ambari Agent / Host Disk Usage* needs to have some 
> metrics Externalized. 
> The Usage screens relies on the alert_disk_space.py script to collect metrics 
> such as Disk utilization (percentage) and directory being checked. 
> The problem is that the directories being check in this script are: 
> 1. ROOT ("/") 
> 2. /usr/hdp 
> If ROOT is OK, then "/usr/hdp" is checked subsequently. However if ROOT is 
> NOT OK (>80% utilization) then "/usr/hdp" is ignored and the "CRITICAL" tag 
> applies to ROOT. 
> This would work on a OOTB standard cluster. However, many users, have 
> Partitions for the hadoop directories. In this instance, "/" is static, no 
> new content will be added. In this instance being at 80 or 90% is OK, this 
> directory will never grow beyond that. 
> "/usr/hdp" is a separate partition that grows in time. 
> Based on the above described check, the 80% of the root partition will 
> trigger a "CRITICAL" message, although the "/usr/hdp" partition is OK. 
> The selection of what directory is being checked should be EXTERNALIZED to a 
> configurable property to avoid these kinds of misleading messages. 
> CONVERSELY --- what constitutes "OK" "WARN" or "CRIT" (the percentage that 
> triggers these) should be left up to the user, not hardcoded in the script. 
> This is a request to externalize the directories that should be checked, as 
> well as the Percentages into an external configurable property.



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

[jira] [Commented] (AMBARI-14877) [Ambari tarballs] Refactor postinstall and postremove scripts to use install-helper.sh exclusively

2016-02-03 Thread Hudson (JIRA)


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

Hudson commented on AMBARI-14877:
-

ABORTED: Integrated in Ambari-trunk-Commit #4267 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/4267/])
AMBARI-14877. [Ambari tarballs] Refactor postinstall and postremove (aonishuk: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=f6a75a609caa1ce24c6cf9ab1f6303eb5bc9e923])
* ambari-server/src/main/package/deb/control/postinst
* ambari-server/src/main/package/deb/control/prerm
* ambari-agent/conf/unix/install-helper.sh
* ambari-server/src/main/assemblies/server.xml
* ambari-server/src/main/package/rpm/postinstall.sh
* ambari-agent/src/main/package/deb/control/prerm
* ambari-agent/src/main/package/deb/control/postinst
* ambari-server/src/main/package/deb/control/posttrm
* ambari-agent/src/packages/tarball/all.xml
* ambari-server/conf/unix/install-helper.sh
* ambari-agent/src/main/package/rpm/preremove.sh
* ambari-server/src/main/package/rpm/preremove.sh
* ambari-agent/src/main/package/rpm/postinstall.sh
* ambari-agent/src/main/package/deb/control/posttrm


> [Ambari tarballs] Refactor postinstall and postremove scripts to use 
> install-helper.sh exclusively
> --
>
> Key: AMBARI-14877
> URL: https://issues.apache.org/jira/browse/AMBARI-14877
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.4.0
>
> Attachments: AMBARI-14877.patch
>
>
> We will need this refactoring, to use install-helper.sh while installing
> tar.gz



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

Re: Review Request 43045: AMBARI-14859 : Ranger - Keep all temporary files in the tmp directory defined in the Agent's configuration

2016-02-03 Thread Jonathan Hurley


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


Ship it!




Ship It!

- Jonathan Hurley


On Feb. 2, 2016, 5:37 a.m., Gautam Borad wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/43045/
> ---
> 
> (Updated Feb. 2, 2016, 5:37 a.m.)
> 
> 
> Review request for Ambari, Alejandro Fernandez, Jaimin Jetly, Jonathan 
> Hurley, Mahadev Konar, Sumit Mohanty, Selvamohan Neethiraj, and Velmurugan 
> Periasamy.
> 
> 
> Bugs: AMBARI-14859
> https://issues.apache.org/jira/browse/AMBARI-14859
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> **Problem Statement** :
> Move temporary files created by Ambari code, they should reside in the tmp 
> directory defined in the Agent's configuration. (Refer: 
> https://reviews.apache.org/r/34296 )
> 
> 
> ** Suggested Solution ** :
> Removed the hard coding of /tmp/ directory for saving temperary files during 
> the process of upgrade and use tmp directory defined in the Agent's 
> configuration
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/resources/common-services/RANGER/0.4.0/package/scripts/params.py
>  b6e5ee9 
>   
> ambari-server/src/main/resources/common-services/RANGER/0.4.0/package/scripts/ranger_admin.py
>  a0007b3 
>   
> ambari-server/src/main/resources/common-services/RANGER/0.4.0/package/scripts/service_check.py
>  699e3c4 
>   
> ambari-server/src/main/resources/common-services/RANGER/0.4.0/package/scripts/status_params.py
>  PRE-CREATION 
> 
> Diff: https://reviews.apache.org/r/43045/diff/
> 
> 
> Testing
> ---
> 
> Tested Ranger Installation and Express upgrade from 2.2 to 2.3
> 
> 
> Thanks,
> 
> Gautam Borad
> 
>

Re: Review Request 43040: Add Alert for HAWQSTANDBY sync status with HAWQMASTER

2016-02-03 Thread Jonathan Hurley


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


Ship it!




Ship It!

- Jonathan Hurley


On Feb. 2, 2016, 2:49 p.m., Matt wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/43040/
> ---
> 
> (Updated Feb. 2, 2016, 2:49 p.m.)
> 
> 
> Review request for Ambari, Alexander Denissov, Alejandro Fernandez, bhuvnesh 
> chaudhary, Dmytro Sen, Goutam Tadi, Jaimin Jetly, jun aoki, Jonathan Hurley, 
> Lav Jain, Newton Alex, and Vitalyi Brodetskyi.
> 
> 
> Bugs: AMBARI-14855
> https://issues.apache.org/jira/browse/AMBARI-14855
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> HAWQSTANDBY can go out of sync with HAWQMASTER. Show an alert when 
> HAWQSTANDBY is not in sync with HAWQMASTER.
> 
> 
> Diffs
> -
> 
>   ambari-server/src/main/resources/common-services/HAWQ/2.0.0/alerts.json 
> PRE-CREATION 
>   
> ambari-server/src/main/resources/common-services/HAWQ/2.0.0/package/alerts/alert_sync_status.py
>  PRE-CREATION 
>   ambari-server/src/test/python/stacks/2.3/HAWQ/test_alert_sync_status.py 
> PRE-CREATION 
> 
> Diff: https://reviews.apache.org/r/43040/diff/
> 
> 
> Testing
> ---
> 
> Manually Tested.
> Added an additional unit test.
> 
> All unit tests passed.
> 
> 
> Thanks,
> 
> Matt
> 
>

[jira] [Commented] (AMBARI-14898) Alerts: Ability to customize props and thresholds on SCRIPT alerts via Ambari Web UI

2016-02-03 Thread Aleksandr Kovalenko (JIRA)


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

Aleksandr Kovalenko commented on AMBARI-14898:
--

+1 for the patch

> Alerts: Ability to customize props and thresholds on SCRIPT alerts via Ambari 
> Web UI
> 
>
> Key: AMBARI-14898
> URL: https://issues.apache.org/jira/browse/AMBARI-14898
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-14898.patch
>
>
> Script alerts, such as *Ambari Agent / Host Disk Usage* needs to have some 
> metrics Externalized. 
> The Usage screens relies on the alert_disk_space.py script to collect metrics 
> such as Disk utilization (percentage) and directory being checked. 
> The problem is that the directories being check in this script are: 
> 1. ROOT ("/") 
> 2. /usr/hdp 
> If ROOT is OK, then "/usr/hdp" is checked subsequently. However if ROOT is 
> NOT OK (>80% utilization) then "/usr/hdp" is ignored and the "CRITICAL" tag 
> applies to ROOT. 
> This would work on a OOTB standard cluster. However, many users, have 
> Partitions for the hadoop directories. In this instance, "/" is static, no 
> new content will be added. In this instance being at 80 or 90% is OK, this 
> directory will never grow beyond that. 
> "/usr/hdp" is a separate partition that grows in time. 
> Based on the above described check, the 80% of the root partition will 
> trigger a "CRITICAL" message, although the "/usr/hdp" partition is OK. 
> The selection of what directory is being checked should be EXTERNALIZED to a 
> configurable property to avoid these kinds of misleading messages. 
> CONVERSELY --- what constitutes "OK" "WARN" or "CRIT" (the percentage that 
> triggers these) should be left up to the user, not hardcoded in the script. 
> This is a request to externalize the directories that should be checked, as 
> well as the Percentages into an external configurable property.



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

[jira] [Created] (AMBARI-14901) NPE when configuring Kerberos at provisioning secure cluster with Blueprint

2016-02-03 Thread Sandor Magyari (JIRA)

Sandor Magyari created AMBARI-14901:
---

 Summary: NPE when configuring Kerberos at provisioning secure 
cluster with Blueprint
 Key: AMBARI-14901
 URL: https://issues.apache.org/jira/browse/AMBARI-14901
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: 2.2.1
Reporter: Sandor Magyari
Assignee: Sandor Magyari
 Fix For: 2.2.2


Provision a cluster with blueprint and enable kerberos with it. 
config_recommendation_strategy is ONLY_STACK_DEFAULTS_APPLY. The cluster 
installation will fail.
java.lang.NullPointerException
at 
org.apache.ambari.server.topology.ClusterConfigurationRequest.configureKerberos(ClusterConfigurationRequest.java:151)
at 
org.apache.ambari.server.topology.ClusterConfigurationRequest.process(ClusterConfigurationRequest.java:103)
at 
org.apache.ambari.server.topology.TopologyManager$ConfigureClusterTask.call(TopologyManager.java:764)
at 
org.apache.ambari.server.topology.TopologyManager$ConfigureClusterTask.call(TopologyManager.java:738)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Suspicious code snippet:
Map propertyMap = updatedConfigs.get(configType);
Map clusterConfigProperties = 
existingConfigurations.get(configType);
Map stackDefaultConfigProperties = 
stackDefaultProps.get(configType);
for (String property : propertyMap.keySet()) {
  if (clusterConfigProperties == null || 
!clusterConfigProperties.containsKey(property)
|| (clusterConfigProperties.get(property) == null && 
stackDefaultConfigProperties.get(property) == null)
|| (clusterConfigProperties.get(property) != null && 
clusterConfigProperties.get(property).equals(stackDefaultConfigProperties.get(property



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

[jira] [Updated] (AMBARI-14901) NPE when configuring Kerberos at provisioning secure cluster with Blueprint

2016-02-03 Thread Sandor Magyari (JIRA)


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

Sandor Magyari updated AMBARI-14901:

Description: 
Provision a cluster with blueprint and enable kerberos with it. 
config_recommendation_strategy is ONLY_STACK_DEFAULTS_APPLY. The cluster 
installation will fail.

java.lang.NullPointerException
at 
org.apache.ambari.server.topology.ClusterConfigurationRequest.configureKerberos(ClusterConfigurationRequest.java:151)
at 
org.apache.ambari.server.topology.ClusterConfigurationRequest.process(ClusterConfigurationRequest.java:103)
at 
org.apache.ambari.server.topology.TopologyManager$ConfigureClusterTask.call(TopologyManager.java:764)
at 
org.apache.ambari.server.topology.TopologyManager$ConfigureClusterTask.call(TopologyManager.java:738)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)

Suspicious code snippet:
{code:java}
Map propertyMap = updatedConfigs.get(configType);
Map clusterConfigProperties = 
existingConfigurations.get(configType);
Map stackDefaultConfigProperties = 
stackDefaultProps.get(configType);
for (String property : propertyMap.keySet()) {
  if (clusterConfigProperties == null || 
!clusterConfigProperties.containsKey(property)
|| (clusterConfigProperties.get(property) == null && 
stackDefaultConfigProperties.get(property) == null)
|| (clusterConfigProperties.get(property) != null && 
clusterConfigProperties.get(property).equals(stackDefaultConfigProperties.get(property
{code}

  was:
Provision a cluster with blueprint and enable kerberos with it. 
config_recommendation_strategy is ONLY_STACK_DEFAULTS_APPLY. The cluster 
installation will fail.
java.lang.NullPointerException
at 
org.apache.ambari.server.topology.ClusterConfigurationRequest.configureKerberos(ClusterConfigurationRequest.java:151)
at 
org.apache.ambari.server.topology.ClusterConfigurationRequest.process(ClusterConfigurationRequest.java:103)
at 
org.apache.ambari.server.topology.TopologyManager$ConfigureClusterTask.call(TopologyManager.java:764)
at 
org.apache.ambari.server.topology.TopologyManager$ConfigureClusterTask.call(TopologyManager.java:738)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Suspicious code snippet:
Map propertyMap = updatedConfigs.get(configType);
Map clusterConfigProperties = 
existingConfigurations.get(configType);
Map stackDefaultConfigProperties = 
stackDefaultProps.get(configType);
for (String property : propertyMap.keySet()) {
  if (clusterConfigProperties == null || 
!clusterConfigProperties.containsKey(property)
|| (clusterConfigProperties.get(property) == null && 
stackDefaultConfigProperties.get(property) == null)
|| (clusterConfigProperties.get(property) != null && 
clusterConfigProperties.get(property).equals(stackDefaultConfigProperties.get(property


> NPE when configuring Kerberos at provisioning secure cluster with Blueprint
> ---
>
> Key: AMBARI-14901
> URL: https://issues.apache.org/jira/browse/AMBARI-14901
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.2.1
>Reporter: Sandor Magyari
>Assignee: Sandor Magyari
> Fix For: 2.2.2
>
>
> Provision a cluster with blueprint and enable kerberos with it. 
> config_recommendation_strategy is ONLY_STACK_DEFAULTS_APPLY. The cluster 
> installation will fail.
> java.lang.NullPointerException
> at 
> org.apache.ambari.server.topology.ClusterConfigurationRequest.configureKerberos(ClusterConfigurationRequest.java:151)
> at 
>

[jira] [Commented] (AMBARI-14897) Rolling Upgrade: upgrade group status not updated


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

Andrii Tkach commented on AMBARI-14897:
---

committed to trunk and branch-2.2

> Rolling Upgrade: upgrade group status not updated
> -
>
> Key: AMBARI-14897
> URL: https://issues.apache.org/jira/browse/AMBARI-14897
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.2.1
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-14897.patch, AMBARI-14897_branch-2.2.patch, 
> Selection_127.png
>
>
> ambari-server version: ambari-server-2.2.1.0-156.x86_64
> ambari-server --hash: 9a9ecca7809c57e16cfe273c3e7b6df7f63a47c7
> HDP Stack: 2.3
> HDP Version: 2.3.0.0-2557
> 2.4.0.0-149
> Ambari DB: :MySQL
> Oozie/Hive DB: MySQL/MySQL
> Security:no
> Security Type:AD/AD
> Blueprints: false
> Umask: 
> JDK: OracleJDK8
> HA: yes



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

Re: [VOTE] Apache Ambari 2.2.1 RC2

2016-02-03 Thread Nate Cole

+1 for RC2

On 2/1/16, 5:44 PM, "Robert Levas"  wrote:

>Team...
>
>I have created a new ambari-2.2.1 release candidate.
>
>GIT source tag (release-2.2.1-rc2)
>https://git-wip-us.apache.org/repos/asf/ambari/repo?p=ambari.git;a=log;h=r
>efs/tags/release-2.2.1-rc2
>
>Staging site: http://people.apache.org/~rlevas/apache-ambari-2.2.1-rc2
>
>PGP release keys (signed using 0EF56BD9)
>http://pgp.mit.edu:11371/pks/lookup?op=vindex=0x0EF56BD9
>
>One can look into the issues fixed in this release at
>https://issues.apache.org/jira/browse/AMBARI/fixforversion/12334307/?selec
>tedTab=com.atlassian.jira.jira-projects-plugin:version-summary-panel
>
>Vote will be open for 72 hours.
>[ ] +1 approve
>[ ] +0 no opinion
>[ ] -1 disapprove (and reason why)
>
>
>
>Thanks
>Rob
>
>
>

[jira] [Updated] (AMBARI-14900) Ambari Admin: Create LDAP Setup page


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

Antonenko Alexander updated AMBARI-14900:
-
Attachment: AMBARI-14900.patch

> Ambari Admin: Create LDAP Setup page
> 
>
> Key: AMBARI-14900
> URL: https://issues.apache.org/jira/browse/AMBARI-14900
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 2.4.0
>
> Attachments: AMBARI-14900.patch, ldap-form.mp4
>
>
> See attached



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

[jira] [Updated] (AMBARI-14898) Alerts: Ability to customize props and thresholds on SCRIPT alerts via Ambari Web UI


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

Oleg Nechiporenko updated AMBARI-14898:
---
Priority: Critical  (was: Major)

> Alerts: Ability to customize props and thresholds on SCRIPT alerts via Ambari 
> Web UI
> 
>
> Key: AMBARI-14898
> URL: https://issues.apache.org/jira/browse/AMBARI-14898
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-14898.patch
>
>
> Script alerts, such as *Ambari Agent / Host Disk Usage* needs to have some 
> metrics Externalized. 
> The Usage screens relies on the alert_disk_space.py script to collect metrics 
> such as Disk utilization (percentage) and directory being checked. 
> The problem is that the directories being check in this script are: 
> 1. ROOT ("/") 
> 2. /usr/hdp 
> If ROOT is OK, then "/usr/hdp" is checked subsequently. However if ROOT is 
> NOT OK (>80% utilization) then "/usr/hdp" is ignored and the "CRITICAL" tag 
> applies to ROOT. 
> This would work on a OOTB standard cluster. However, many users, have 
> Partitions for the hadoop directories. In this instance, "/" is static, no 
> new content will be added. In this instance being at 80 or 90% is OK, this 
> directory will never grow beyond that. 
> "/usr/hdp" is a separate partition that grows in time. 
> Based on the above described check, the 80% of the root partition will 
> trigger a "CRITICAL" message, although the "/usr/hdp" partition is OK. 
> The selection of what directory is being checked should be EXTERNALIZED to a 
> configurable property to avoid these kinds of misleading messages. 
> CONVERSELY --- what constitutes "OK" "WARN" or "CRIT" (the percentage that 
> triggers these) should be left up to the user, not hardcoded in the script. 
> This is a request to externalize the directories that should be checked, as 
> well as the Percentages into an external configurable property.



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

[jira] [Updated] (AMBARI-14898) Alerts: Ability to customize props and thresholds on SCRIPT alerts via Ambari Web UI


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

Oleg Nechiporenko updated AMBARI-14898:
---
Attachment: AMBARI-14898.patch

> Alerts: Ability to customize props and thresholds on SCRIPT alerts via Ambari 
> Web UI
> 
>
> Key: AMBARI-14898
> URL: https://issues.apache.org/jira/browse/AMBARI-14898
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: 2.4.0
>
> Attachments: AMBARI-14898.patch
>
>
> Script alerts, such as *Ambari Agent / Host Disk Usage* needs to have some 
> metrics Externalized. 
> The Usage screens relies on the alert_disk_space.py script to collect metrics 
> such as Disk utilization (percentage) and directory being checked. 
> The problem is that the directories being check in this script are: 
> 1. ROOT ("/") 
> 2. /usr/hdp 
> If ROOT is OK, then "/usr/hdp" is checked subsequently. However if ROOT is 
> NOT OK (>80% utilization) then "/usr/hdp" is ignored and the "CRITICAL" tag 
> applies to ROOT. 
> This would work on a OOTB standard cluster. However, many users, have 
> Partitions for the hadoop directories. In this instance, "/" is static, no 
> new content will be added. In this instance being at 80 or 90% is OK, this 
> directory will never grow beyond that. 
> "/usr/hdp" is a separate partition that grows in time. 
> Based on the above described check, the 80% of the root partition will 
> trigger a "CRITICAL" message, although the "/usr/hdp" partition is OK. 
> The selection of what directory is being checked should be EXTERNALIZED to a 
> configurable property to avoid these kinds of misleading messages. 
> CONVERSELY --- what constitutes "OK" "WARN" or "CRIT" (the percentage that 
> triggers these) should be left up to the user, not hardcoded in the script. 
> This is a request to externalize the directories that should be checked, as 
> well as the Percentages into an external configurable property.



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

Re: [VOTE] Apache Ambari 2.2.1 RC2

2016-02-03 Thread Robert Levas

Team…

This is a reminder to vote for 2.2.1 RC2. I haven’t received any votes yet and 
we are coming close to the 72 hour deadline.

Thanks,
Rob





On 2/1/16, 5:44 PM, "Robert Levas"  wrote:

>Team...
>
>I have created a new ambari-2.2.1 release candidate.
>
>GIT source tag (release-2.2.1-rc2) 
>https://git-wip-us.apache.org/repos/asf/ambari/repo?p=ambari.git;a=log;h=refs/tags/release-2.2.1-rc2
>
>Staging site: http://people.apache.org/~rlevas/apache-ambari-2.2.1-rc2
>
>PGP release keys (signed using 0EF56BD9) 
>http://pgp.mit.edu:11371/pks/lookup?op=vindex=0x0EF56BD9
>
>One can look into the issues fixed in this release at 
>https://issues.apache.org/jira/browse/AMBARI/fixforversion/12334307/?selectedTab=com.atlassian.jira.jira-projects-plugin:version-summary-panel
>
>Vote will be open for 72 hours.
>[ ] +1 approve
>[ ] +0 no opinion
>[ ] -1 disapprove (and reason why)
>
>
>
>Thanks
>Rob
>
>
>

[jira] [Updated] (AMBARI-14901) NPE when configuring Kerberos at provisioning secure cluster with Blueprint

2016-02-03 Thread Sandor Magyari (JIRA)


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

Sandor Magyari updated AMBARI-14901:

Attachment: AMBARI-14901.patch

> NPE when configuring Kerberos at provisioning secure cluster with Blueprint
> ---
>
> Key: AMBARI-14901
> URL: https://issues.apache.org/jira/browse/AMBARI-14901
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.2.1
>Reporter: Sandor Magyari
>Assignee: Sandor Magyari
> Fix For: 2.2.2
>
> Attachments: AMBARI-14901.patch
>
>
> Provision a cluster with blueprint and enable kerberos with it. 
> config_recommendation_strategy is ONLY_STACK_DEFAULTS_APPLY. The cluster 
> installation will fail.
> java.lang.NullPointerException
> at 
> org.apache.ambari.server.topology.ClusterConfigurationRequest.configureKerberos(ClusterConfigurationRequest.java:151)
> at 
> org.apache.ambari.server.topology.ClusterConfigurationRequest.process(ClusterConfigurationRequest.java:103)
> at 
> org.apache.ambari.server.topology.TopologyManager$ConfigureClusterTask.call(TopologyManager.java:764)
> at 
> org.apache.ambari.server.topology.TopologyManager$ConfigureClusterTask.call(TopologyManager.java:738)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
> at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> Suspicious code snippet:
> {code:java}
> Map propertyMap = updatedConfigs.get(configType);
> Map clusterConfigProperties = 
> existingConfigurations.get(configType);
> Map stackDefaultConfigProperties = 
> stackDefaultProps.get(configType);
> for (String property : propertyMap.keySet()) {
>   if (clusterConfigProperties == null || 
> !clusterConfigProperties.containsKey(property)
> || (clusterConfigProperties.get(property) == null && 
> stackDefaultConfigProperties.get(property) == null)
> || (clusterConfigProperties.get(property) != null && 
> clusterConfigProperties.get(property).equals(stackDefaultConfigProperties.get(property
> {code}



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

[jira] [Updated] (AMBARI-14900) Ambari Admin: Create LDAP Setup page


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

Antonenko Alexander updated AMBARI-14900:
-
Attachment: ldap-form.mp4

> Ambari Admin: Create LDAP Setup page
> 
>
> Key: AMBARI-14900
> URL: https://issues.apache.org/jira/browse/AMBARI-14900
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 2.4.0
>
> Attachments: ldap-form.mp4
>
>
> See attached



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

[jira] [Commented] (AMBARI-14898) Alerts: Ability to customize props and thresholds on SCRIPT alerts via Ambari Web UI


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

Hadoop QA commented on AMBARI-14898:


{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12786018/AMBARI-14898.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 3 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-web.

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

This message is automatically generated.

> Alerts: Ability to customize props and thresholds on SCRIPT alerts via Ambari 
> Web UI
> 
>
> Key: AMBARI-14898
> URL: https://issues.apache.org/jira/browse/AMBARI-14898
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-14898.patch
>
>
> Script alerts, such as *Ambari Agent / Host Disk Usage* needs to have some 
> metrics Externalized. 
> The Usage screens relies on the alert_disk_space.py script to collect metrics 
> such as Disk utilization (percentage) and directory being checked. 
> The problem is that the directories being check in this script are: 
> 1. ROOT ("/") 
> 2. /usr/hdp 
> If ROOT is OK, then "/usr/hdp" is checked subsequently. However if ROOT is 
> NOT OK (>80% utilization) then "/usr/hdp" is ignored and the "CRITICAL" tag 
> applies to ROOT. 
> This would work on a OOTB standard cluster. However, many users, have 
> Partitions for the hadoop directories. In this instance, "/" is static, no 
> new content will be added. In this instance being at 80 or 90% is OK, this 
> directory will never grow beyond that. 
> "/usr/hdp" is a separate partition that grows in time. 
> Based on the above described check, the 80% of the root partition will 
> trigger a "CRITICAL" message, although the "/usr/hdp" partition is OK. 
> The selection of what directory is being checked should be EXTERNALIZED to a 
> configurable property to avoid these kinds of misleading messages. 
> CONVERSELY --- what constitutes "OK" "WARN" or "CRIT" (the percentage that 
> triggers these) should be left up to the user, not hardcoded in the script. 
> This is a request to externalize the directories that should be checked, as 
> well as the Percentages into an external configurable property.



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

[jira] [Created] (AMBARI-14899) UI part of rename Admin Setting API

Antonenko Alexander created AMBARI-14899:


 Summary: UI part of rename Admin Setting API
 Key: AMBARI-14899
 URL: https://issues.apache.org/jira/browse/AMBARI-14899
 Project: Ambari
  Issue Type: Bug
  Components: ambari-web
Affects Versions: 2.4.0
Reporter: Antonenko Alexander
Assignee: Antonenko Alexander
 Fix For: 2.4.0


Currently API endpoint is /admin-settings. Change it to /settings and all 
modelling accordingly.

POST
{code}
curl -u admin:admin  -H 'X-Requested-By: ambari' -X POST  
http://SERVER-NAME:8080/api/v1/settings -d '{"Settings" : {
"content" : "{test_content : test_value}",
"name" : "motd",
"setting_type" : "ambari-server"
  }}'
Response:
{
  "resources" : [
{
  "href" : "http://SERVER-NAME:8080/api/v1/settings/motd;,
  "Settings" : {
"name" : "motd"
  }
}
  ]
}
{code}

GET
{code}
curl -u admin:admin  -H 'X-Requested-By: ambari' -X GET  
http://SERVER-NAME:8080/api/v1/settings/motd
Response:
{
  "href" : "http://SERVER-NAME:8080/api/v1/settings/motd;,
  "Settings" : {
"content" : "{test_content : test_value}",
"name" : "motd",
"setting_type" : "ambari-server",
"update_timestamp" : 1454102699484,
"updated_by" : "admin"
  }
}
{code}

PUT
{code}
curl -u admin:admin  -H 'X-Requested-By: ambari' -X PUT  
http://SERVER-NAME:8080/api/v1/settings/motd -d '{"Settings" : {
"content" : "{test_content1 : test_value1}",
"setting_type" : "ambari-server"
  }}'
{code}

LIST
{code}
curl -u admin:admin  -H 'X-Requested-By: ambari' -X GET  
http://SERVER-NAME:8080/api/v1/settings
Response:
{
  "href" : "http://SERVER-NAME:8080/api/v1/settings;,
  "items" : [
{
  "href" : "http://SERVER-NAME:8080/api/v1/settings/motd;,
  "Settings" : {
"name" : "motd"
  }
}
  ]
}
{code}

DELETE
{code}
curl -u admin:admin  -H 'X-Requested-By: ambari' -X DELETE  
http://SERVER-NAME:8080/api/v1/settings/motd
{code}



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

[jira] [Created] (AMBARI-14900) Ambari Admin: Create LDAP Setup page

Antonenko Alexander created AMBARI-14900:


 Summary: Ambari Admin: Create LDAP Setup page
 Key: AMBARI-14900
 URL: https://issues.apache.org/jira/browse/AMBARI-14900
 Project: Ambari
  Issue Type: Bug
  Components: ambari-web
Affects Versions: 2.4.0
Reporter: Antonenko Alexander
Assignee: Antonenko Alexander
 Fix For: 2.4.0
 Attachments: ldap-form.mp4

See attached



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

[jira] [Updated] (AMBARI-14898) Alerts: Ability to customize props and thresholds on SCRIPT alerts via Ambari Web UI


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

Oleg Nechiporenko updated AMBARI-14898:
---
Issue Type: Task  (was: Bug)

> Alerts: Ability to customize props and thresholds on SCRIPT alerts via Ambari 
> Web UI
> 
>
> Key: AMBARI-14898
> URL: https://issues.apache.org/jira/browse/AMBARI-14898
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: 2.4.0
>
> Attachments: AMBARI-14898.patch
>
>
> Script alerts, such as *Ambari Agent / Host Disk Usage* needs to have some 
> metrics Externalized. 
> The Usage screens relies on the alert_disk_space.py script to collect metrics 
> such as Disk utilization (percentage) and directory being checked. 
> The problem is that the directories being check in this script are: 
> 1. ROOT ("/") 
> 2. /usr/hdp 
> If ROOT is OK, then "/usr/hdp" is checked subsequently. However if ROOT is 
> NOT OK (>80% utilization) then "/usr/hdp" is ignored and the "CRITICAL" tag 
> applies to ROOT. 
> This would work on a OOTB standard cluster. However, many users, have 
> Partitions for the hadoop directories. In this instance, "/" is static, no 
> new content will be added. In this instance being at 80 or 90% is OK, this 
> directory will never grow beyond that. 
> "/usr/hdp" is a separate partition that grows in time. 
> Based on the above described check, the 80% of the root partition will 
> trigger a "CRITICAL" message, although the "/usr/hdp" partition is OK. 
> The selection of what directory is being checked should be EXTERNALIZED to a 
> configurable property to avoid these kinds of misleading messages. 
> CONVERSELY --- what constitutes "OK" "WARN" or "CRIT" (the percentage that 
> triggers these) should be left up to the user, not hardcoded in the script. 
> This is a request to externalize the directories that should be checked, as 
> well as the Percentages into an external configurable property.



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

[jira] [Updated] (AMBARI-14899) UI part of rename Admin Setting API


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

Antonenko Alexander updated AMBARI-14899:
-
Attachment: AMBARI-14899.patch

> UI part of rename Admin Setting API
> ---
>
> Key: AMBARI-14899
> URL: https://issues.apache.org/jira/browse/AMBARI-14899
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 2.4.0
>
> Attachments: AMBARI-14899.patch
>
>
> Currently API endpoint is /admin-settings. Change it to /settings and all 
> modelling accordingly.
> POST
> {code}
> curl -u admin:admin  -H 'X-Requested-By: ambari' -X POST  
> http://SERVER-NAME:8080/api/v1/settings -d '{"Settings" : {
> "content" : "{test_content : test_value}",
> "name" : "motd",
> "setting_type" : "ambari-server"
>   }}'
> Response:
> {
>   "resources" : [
> {
>   "href" : "http://SERVER-NAME:8080/api/v1/settings/motd;,
>   "Settings" : {
> "name" : "motd"
>   }
> }
>   ]
> }
> {code}
> GET
> {code}
> curl -u admin:admin  -H 'X-Requested-By: ambari' -X GET  
> http://SERVER-NAME:8080/api/v1/settings/motd
> Response:
> {
>   "href" : "http://SERVER-NAME:8080/api/v1/settings/motd;,
>   "Settings" : {
> "content" : "{test_content : test_value}",
> "name" : "motd",
> "setting_type" : "ambari-server",
> "update_timestamp" : 1454102699484,
> "updated_by" : "admin"
>   }
> }
> {code}
> PUT
> {code}
> curl -u admin:admin  -H 'X-Requested-By: ambari' -X PUT  
> http://SERVER-NAME:8080/api/v1/settings/motd -d '{"Settings" : {
> "content" : "{test_content1 : test_value1}",
> "setting_type" : "ambari-server"
>   }}'
> {code}
> LIST
> {code}
> curl -u admin:admin  -H 'X-Requested-By: ambari' -X GET  
> http://SERVER-NAME:8080/api/v1/settings
> Response:
> {
>   "href" : "http://SERVER-NAME:8080/api/v1/settings;,
>   "items" : [
> {
>   "href" : "http://SERVER-NAME:8080/api/v1/settings/motd;,
>   "Settings" : {
> "name" : "motd"
>   }
> }
>   ]
> }
> {code}
> DELETE
> {code}
> curl -u admin:admin  -H 'X-Requested-By: ambari' -X DELETE  
> http://SERVER-NAME:8080/api/v1/settings/motd
> {code}



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

[jira] [Commented] (AMBARI-14898) Alerts: Ability to customize props and thresholds on SCRIPT alerts via Ambari Web UI


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

Hadoop QA commented on AMBARI-14898:


{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12786018/AMBARI-14898.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 3 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-web.

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

This message is automatically generated.

> Alerts: Ability to customize props and thresholds on SCRIPT alerts via Ambari 
> Web UI
> 
>
> Key: AMBARI-14898
> URL: https://issues.apache.org/jira/browse/AMBARI-14898
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-14898.patch
>
>
> Script alerts, such as *Ambari Agent / Host Disk Usage* needs to have some 
> metrics Externalized. 
> The Usage screens relies on the alert_disk_space.py script to collect metrics 
> such as Disk utilization (percentage) and directory being checked. 
> The problem is that the directories being check in this script are: 
> 1. ROOT ("/") 
> 2. /usr/hdp 
> If ROOT is OK, then "/usr/hdp" is checked subsequently. However if ROOT is 
> NOT OK (>80% utilization) then "/usr/hdp" is ignored and the "CRITICAL" tag 
> applies to ROOT. 
> This would work on a OOTB standard cluster. However, many users, have 
> Partitions for the hadoop directories. In this instance, "/" is static, no 
> new content will be added. In this instance being at 80 or 90% is OK, this 
> directory will never grow beyond that. 
> "/usr/hdp" is a separate partition that grows in time. 
> Based on the above described check, the 80% of the root partition will 
> trigger a "CRITICAL" message, although the "/usr/hdp" partition is OK. 
> The selection of what directory is being checked should be EXTERNALIZED to a 
> configurable property to avoid these kinds of misleading messages. 
> CONVERSELY --- what constitutes "OK" "WARN" or "CRIT" (the percentage that 
> triggers these) should be left up to the user, not hardcoded in the script. 
> This is a request to externalize the directories that should be checked, as 
> well as the Percentages into an external configurable property.



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

Re: Review Request 43140: Make AMS Grafana component available as a repo package



> On Фев. 3, 2016, 9:33 п.п., Sid Wagle wrote:
> > Does the exectuion get called for debian as well?
> > https://cwiki.apache.org/confluence/display/AMBARI/Build+Instructions

No. Only RPM as of now.


- Dmytro


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


On Фев. 3, 2016, 4:15 п.п., Dmytro Sen wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/43140/
> ---
> 
> (Updated Фев. 3, 2016, 4:15 п.п.)
> 
> 
> Review request for Ambari, Aravindan Vijayan, Sid Wagle, and Yusaku Sako.
> 
> 
> Bugs: AMBARI-14902
> https://issues.apache.org/jira/browse/AMBARI-14902
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Grafana 2.6.0 to be installed as an AMS component. We need this to be a part 
> of the Ambari repo so that Ambari can install it with AMS.
> 
> 
> Diffs
> -
> 
>   ambari-metrics/ambari-metrics-assembly/pom.xml e963b00 
>   ambari-metrics/ambari-metrics-assembly/src/main/assembly/grafana.xml 
> PRE-CREATION 
>   ambari-metrics/ambari-metrics-grafana/conf/unix/ambari-metrics-grafana 
> PRE-CREATION 
>   ambari-metrics/ambari-metrics-grafana/conf/unix/ams-grafana-env.sh 
> PRE-CREATION 
>   ambari-metrics/ambari-metrics-grafana/conf/unix/ams-grafana.ini 
> PRE-CREATION 
>   ambari-metrics/ambari-metrics-grafana/pom.xml PRE-CREATION 
>   ambari-metrics/ambari-metrics-grafana/src/main/assemblies/empty.xml 
> PRE-CREATION 
>   ambari-metrics/pom.xml 44964d4 
>   pom.xml fe139b8 
> 
> Diff: https://reviews.apache.org/r/43140/diff/
> 
> 
> Testing
> ---
> 
> Unit tests passed
> 
> 
> Thanks,
> 
> Dmytro Sen
> 
>

[jira] [Updated] (AMBARI-14894) Add Custom action to sync Standby with Master and rename stop hawq cluster to service

2016-02-03 Thread Goutam Tadi (JIRA)


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

Goutam Tadi updated AMBARI-14894:
-
Attachment: AMBARI-14894-branch2-.2-v3.patch

> Add Custom action to sync Standby with Master and rename stop hawq cluster to 
> service
> -
>
> Key: AMBARI-14894
> URL: https://issues.apache.org/jira/browse/AMBARI-14894
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.2.2
>Reporter: Goutam Tadi
>Assignee: Goutam Tadi
>Priority: Minor
> Fix For: 2.2.2
>
> Attachments: AMBARI-14894-branch2-.2-v3.patch, 
> AMBARI-14894.branch-2.2-v2.patch
>
>




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

[jira] [Updated] (AMBARI-14820) Implement Activate HAWQ Standby wizard to allow doing failover in HA mode


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

jun aoki updated AMBARI-14820:
--
Fix Version/s: (was: 2.2.0)
   2.2.2

> Implement Activate HAWQ Standby wizard to allow doing failover in HA mode
> -
>
> Key: AMBARI-14820
> URL: https://issues.apache.org/jira/browse/AMBARI-14820
> Project: Ambari
>  Issue Type: New Feature
>  Components: stacks
>Affects Versions: trunk
>Reporter: bhuvnesh chaudhary
>Assignee: bhuvnesh chaudhary
> Fix For: trunk, 2.2.2
>
> Attachments: AMBARI-14820-1.patch, AMBARI-14820-branch-2.2.patch, 
> AMBARI-14820.patch
>
>
> h1. Activate HAWQ Standby Wizard
> h4. Abstract:
> All configuration changes done on Ambari managed clusters must be done via 
> Ambari, otherwise during restart of services, Ambari pushes the configuration 
> stored in its database and overwrites the changes done manually.
> Activation of HAWQ Standby to active master involves manual command execution 
> which updates the configuration files. In order to keep the configuration in 
> sync and reflect the correct state of the HAWQ components on Ambari, we need 
> to introduce a wizard, i.e *“Activate HAWQ Standby Wizard”*. 
> This wizard will also automate the process of activating standby and the user 
> now will need to walk-through the wizard to activate standby. 
> h4. Overview of activate standby operation:
> * In HA configuration, HAWQ is configured with a master and standby 
> component. 
> * To activate / promote standby to a master, “hawq activate standby” command 
> needs to be executed on the standby
> * This operation updates the value of hawq_master_address_host and 
> hawq_standby_address_host properties available in hawq-site.xml to below
> ** hawq_master_address_host : Initially Configured HAWQ Standby Host
> ** hawq_standby_address_host : This property is removed.
> * After the operation is completed, HAWQ cluster will be running in non-ha 
> mode and will  not have a configured standby.
> h4. Overview of the wizard pages and operation performed:
> The wizard consists of 3 pages, a brief of them is as below:
> # “Get Started”: This page is the first page seen by the user, and it gives 
> introduction of the activity going to be performed. 
> # “Review”: This page is the second page which informs the user about the 
> changes which will happen. A confirmation is requested before proceeding to 
> the next step.
> # “Configure Components”: This page is the third and last page which shows 
> the progress for the steps executed. It does the below:
> ## Execute command to activate HAWQ standby
> ## Stop HAWQ service
> ## Reconfigure HAWQ to push updated configs
> ### hawq_standby_address_host is removed
> ### hawq_master_address_host is updated to previous standby
> ## Install HAWQ Master Ambari Component on the Standby Host
> ## Delete HAWQ Standby Ambari Component on the Standby Host
> ## Delete HAWQ Master Ambari Component on the Master host
> ## Start HAWQ Service



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

[jira] [Commented] (AMBARI-14795) Register Version: add ability to load new version definition file


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

Xi Wang commented on AMBARI-14795:
--

Got +1 from review board

> Register Version: add ability to load new version definition file
> -
>
> Key: AMBARI-14795
> URL: https://issues.apache.org/jira/browse/AMBARI-14795
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Xi Wang
>Assignee: Xi Wang
>Priority: Critical
>  Labels: Patch-Upgrade
> Fix For: 2.4.0
>
> Attachments: AMBARI-14795.patch, register version -1.png, register 
> version -2.png
>
>
> This one belongs to UI work of Patch Upgrade ( Provide ability to apply 
> single patches on top of RU release), and is the first part to implement" 
> Manage Ambari > Register Version" page.
> Should generate a new "Register Version" page, and add the ability to load 
> new version definition file through two options:
> 1. Browse local files and then Upload file,
> 2. Enter the Url then click on "Read Version File" button,
> After either option, the Version File (a .xml file) should be POST to server, 
> then loaded (GET call) to the page content.
> Be sure to load the mock data, will integrate API later.



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

[jira] [Created] (AMBARI-14912) Provide upgrade support for Settings feature

2016-02-03 Thread Ajit Kumar (JIRA)

Ajit Kumar created AMBARI-14912:
---

 Summary: Provide upgrade support for Settings feature
 Key: AMBARI-14912
 URL: https://issues.apache.org/jira/browse/AMBARI-14912
 Project: Ambari
  Issue Type: Task
Reporter: Ajit Kumar


Update upgrade catalog 240 and add db schema changes for settings table.



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

Re: Review Request 43125: [INITIAL PATCH] AMBARI-14892 Add Grafana as a component to AMS

2016-02-03 Thread Aravindan Vijayan


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

(Updated Feb. 3, 2016, 11:05 p.m.)


Review request for Ambari, Dmytro Sen, Sumit Mohanty, Sid Wagle, and Yusaku 
Sako.


Changes
---

Fix issues with GRAFANA STOP.


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


Repository: ambari


Description
---

Add a MASTER component called Grafana to AMS service.

Include install and start/stop/status scripts for the grafana server.

Config Management for Ambari Metrics - Grafana also part of this patch.


Diffs (updated)
-

  
ambari-metrics/ambari-metrics-timelineservice/conf/unix/ambari-metrics-grafana 
PRE-CREATION 
  
ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/configuration/ams-grafana-env.xml
 PRE-CREATION 
  
ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/configuration/ams-grafana-ini.xml
 PRE-CREATION 
  
ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/metainfo.xml
 48469df 
  
ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/ams.py
 8fdf4ba 
  
ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py
 PRE-CREATION 
  
ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/params.py
 a1de919 
  
ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/status.py
 59466ad 
  
ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/status_params.py
 d446baa 

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


Testing
---

Manual testing done.


Thanks,

Aravindan Vijayan

[jira] [Commented] (AMBARI-14820) Implement Activate HAWQ Standby wizard to allow doing failover in HA mode


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

jun aoki commented on AMBARI-14820:
---

+1

> Implement Activate HAWQ Standby wizard to allow doing failover in HA mode
> -
>
> Key: AMBARI-14820
> URL: https://issues.apache.org/jira/browse/AMBARI-14820
> Project: Ambari
>  Issue Type: New Feature
>  Components: stacks
>Affects Versions: trunk
>Reporter: bhuvnesh chaudhary
>Assignee: bhuvnesh chaudhary
> Fix For: trunk, 2.2.0
>
> Attachments: AMBARI-14820-1.patch, AMBARI-14820-branch-2.2.patch, 
> AMBARI-14820.patch
>
>
> h1. Activate HAWQ Standby Wizard
> h4. Abstract:
> All configuration changes done on Ambari managed clusters must be done via 
> Ambari, otherwise during restart of services, Ambari pushes the configuration 
> stored in its database and overwrites the changes done manually.
> Activation of HAWQ Standby to active master involves manual command execution 
> which updates the configuration files. In order to keep the configuration in 
> sync and reflect the correct state of the HAWQ components on Ambari, we need 
> to introduce a wizard, i.e *“Activate HAWQ Standby Wizard”*. 
> This wizard will also automate the process of activating standby and the user 
> now will need to walk-through the wizard to activate standby. 
> h4. Overview of activate standby operation:
> * In HA configuration, HAWQ is configured with a master and standby 
> component. 
> * To activate / promote standby to a master, “hawq activate standby” command 
> needs to be executed on the standby
> * This operation updates the value of hawq_master_address_host and 
> hawq_standby_address_host properties available in hawq-site.xml to below
> ** hawq_master_address_host : Initially Configured HAWQ Standby Host
> ** hawq_standby_address_host : This property is removed.
> * After the operation is completed, HAWQ cluster will be running in non-ha 
> mode and will  not have a configured standby.
> h4. Overview of the wizard pages and operation performed:
> The wizard consists of 3 pages, a brief of them is as below:
> # “Get Started”: This page is the first page seen by the user, and it gives 
> introduction of the activity going to be performed. 
> # “Review”: This page is the second page which informs the user about the 
> changes which will happen. A confirmation is requested before proceeding to 
> the next step.
> # “Configure Components”: This page is the third and last page which shows 
> the progress for the steps executed. It does the below:
> ## Execute command to activate HAWQ standby
> ## Stop HAWQ service
> ## Reconfigure HAWQ to push updated configs
> ### hawq_standby_address_host is removed
> ### hawq_master_address_host is updated to previous standby
> ## Install HAWQ Master Ambari Component on the Standby Host
> ## Delete HAWQ Standby Ambari Component on the Standby Host
> ## Delete HAWQ Master Ambari Component on the Master host
> ## Start HAWQ Service



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

Review Request 43154: AMBARI-14766: Selecting ALL groups does not work under Manage Alert Notifications

2016-02-03 Thread Keta Patel

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

Review request for Ambari, Alexandr Antonenko, Di Li, and Oleg Nechiporenko.

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

Repository: ambari

Description
---

Selecting "ALL" groups does not work under Manage Alert Notifications.

Reproduction Steps:-
1. Go to Alerts Tab in Ambari GUI
2. Actions --> Manage Notifications
3. Create New Alert Notification (Click the custom radio button for groups and
select couple of options eg HDFS, PIG)
4. Save it.
5. Edit the newly created Alert notification by clicking on the All radio
button. Everything gets selected.
6. Save it

Expected results:
On Saving the Alert notification, the dialog box "Manage Alert Notification"
should show Groups as ALL ( or Show all the values eg HDFS, PIG, MR2).
Basically all the values should be selected.

Diffs
-

ambari-server/src/main/java/org/apache/ambari/server/controller/internal/AlertTargetResourceProvider.java
d28987d

ambari-server/src/test/java/org/apache/ambari/server/controller/internal/AlertTargetResourceProviderTest.java
f80b6f7

ambari-web/app/controllers/main/alerts/manage_alert_notifications_controller.js
38e4e75

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

Testing
---

FIX:

The UI did not show "All" even after selecting "ALL" for Groups in the Edit
Alert Target pop-up because the property "selectedAlertGroup" was not set to
true even after the selection. This is fixed in the
"manageAlertGroupsController" in ambari-web.

However, this only resolved the UI issue. The alert notifications were still
not sent for all services after this change. This was because there was no
corresponding update made in the server code for this "ALL" Groups selection
for a Target. The DB has a table for AlertTarget (alert_target) and AlertGroup
(alert_group). There is a many-to-many mapping between these 2 tables, which is
tracked in the combination table alert_group_target.
1. This combination table was not getting updated for the "ALL" Groups
selection.
2. Also, the Target was not updated as global in the DB.

The "updateAlertTargets()" in "AlertTargetResourceProvider" is updated with the
fix for both these issues.
The global property in Target is set if the ALL selection is made.
And, if the Target is global, all the groups in the DB are upadted with the
current Target in the alert_group_target table.

TESTS:
==
2 test cases are added to test for Custom and All Group selections.
In case of Custom, the request to the REST API has group IDs passed and the
global paramter is false.
The Target after this update must have global as false and should be mapped to
only the selected groups passed in the request.

In case of All, the request to the REST API does not have group IDs passed and
the global paramter is true.
The Target after this update must contain global as true and should be mapped
to all the groups in the DB.

Thanks,

Keta Patel

[jira] [Commented] (AMBARI-14884) Hawq standby host config should be removed on single node cluster during initial cluster installation


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

jun aoki commented on AMBARI-14884:
---

Committed to trunk
4fbf172c31e65bab503ab8e0acbfefd2b7a3adbe

> Hawq standby host config should be removed on single node cluster during 
> initial cluster installation
> -
>
> Key: AMBARI-14884
> URL: https://issues.apache.org/jira/browse/AMBARI-14884
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: trunk
>Reporter: bhuvnesh chaudhary
>Assignee: bhuvnesh chaudhary
>Priority: Trivial
> Fix For: trunk, 2.2.2
>
> Attachments: AMBARI-14884-1.patch, AMBARI-14884-branch-2.2.patch, 
> AMBARI-14884.patch
>
>
> Hawq standby host config should be removed on single node cluster during 
> initial cluster installation.
> Currently, it works only if the cluster is installed and Hawq is added later, 
> but during initial single node installation of cluster with Hawq, it does not.



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

[jira] [Updated] (AMBARI-14884) Hawq standby host config should be removed on single node cluster during initial cluster installation


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

jun aoki updated AMBARI-14884:
--
Fix Version/s: (was: 2.2.0)
   2.2.2

> Hawq standby host config should be removed on single node cluster during 
> initial cluster installation
> -
>
> Key: AMBARI-14884
> URL: https://issues.apache.org/jira/browse/AMBARI-14884
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: trunk
>Reporter: bhuvnesh chaudhary
>Assignee: bhuvnesh chaudhary
>Priority: Trivial
> Fix For: trunk, 2.2.2
>
> Attachments: AMBARI-14884-1.patch, AMBARI-14884-branch-2.2.patch, 
> AMBARI-14884.patch
>
>
> Hawq standby host config should be removed on single node cluster during 
> initial cluster installation.
> Currently, it works only if the cluster is installed and Hawq is added later, 
> but during initial single node installation of cluster with Hawq, it does not.



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

[jira] [Commented] (AMBARI-14901) NPE when configuring Kerberos at provisioning secure cluster with Blueprint


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

Hadoop QA commented on AMBARI-14901:


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

This message is automatically generated.

> NPE when configuring Kerberos at provisioning secure cluster with Blueprint
> ---
>
> Key: AMBARI-14901
> URL: https://issues.apache.org/jira/browse/AMBARI-14901
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.2.1
>Reporter: Sandor Magyari
>Assignee: Sandor Magyari
> Fix For: 2.2.2
>
> Attachments: AMBARI-14901.patch
>
>
> Provision a cluster with blueprint and enable kerberos with it. 
> config_recommendation_strategy is ONLY_STACK_DEFAULTS_APPLY. The cluster 
> installation will fail.
> java.lang.NullPointerException
> at 
> org.apache.ambari.server.topology.ClusterConfigurationRequest.configureKerberos(ClusterConfigurationRequest.java:151)
> at 
> org.apache.ambari.server.topology.ClusterConfigurationRequest.process(ClusterConfigurationRequest.java:103)
> at 
> org.apache.ambari.server.topology.TopologyManager$ConfigureClusterTask.call(TopologyManager.java:764)
> at 
> org.apache.ambari.server.topology.TopologyManager$ConfigureClusterTask.call(TopologyManager.java:738)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
> at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> Suspicious code snippet:
> {code:java}
> Map propertyMap = updatedConfigs.get(configType);
> Map clusterConfigProperties = 
> existingConfigurations.get(configType);
> Map stackDefaultConfigProperties = 
> stackDefaultProps.get(configType);
> for (String property : propertyMap.keySet()) {
>   if (clusterConfigProperties == null || 
> !clusterConfigProperties.containsKey(property)
> || (clusterConfigProperties.get(property) == null && 
> stackDefaultConfigProperties.get(property) == null)
> || (clusterConfigProperties.get(property) != null && 
> clusterConfigProperties.get(property).equals(stackDefaultConfigProperties.get(property
> {code}



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

[jira] [Created] (AMBARI-14911) Populate hawq_site properties when YARN is installed after HAWQ.

2016-02-03 Thread Alexander Denissov (JIRA)

Alexander Denissov created AMBARI-14911:
---

 Summary: Populate hawq_site properties when YARN is installed 
after HAWQ.
 Key: AMBARI-14911
 URL: https://issues.apache.org/jira/browse/AMBARI-14911
 Project: Ambari
  Issue Type: Improvement
Reporter: Alexander Denissov
Assignee: Alexander Denissov
Priority: Minor






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

Review Request 42838: Add upgrade support for Setting feature

2016-02-03 Thread Ajit Kumar


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

Review request for Ambari, Jayush Luniya, Nahappan Somasundaram, and Sumit 
Mohanty.


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


Repository: ambari


Description
---

Update upgrade catalog 240 and add db schema changes for settings table.


Diffs
-

  
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog240.java
 3414388b9a738a4fc7cc5d0f484fe553cce840ee 
  
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog240Test.java
 d1d68f24871422936321ad0c940499fc1ef4cbec 

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


Testing
---

Unit testing. Currently my local trunk build is breaking even w/o my changes. 
I'll run mvn clean install when it is fixed.


Thanks,

Ajit Kumar

[jira] [Updated] (AMBARI-14797) Register Version: display loaded version definition info in different categories and Save them


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

Xi Wang updated AMBARI-14797:
-
Attachment: AMBARI-14797.patch

> Register Version: display loaded version definition info in different 
> categories and Save them
> --
>
> Key: AMBARI-14797
> URL: https://issues.apache.org/jira/browse/AMBARI-14797
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Xi Wang
>Assignee: Xi Wang
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-14797.patch, AMBARI-14797.patch, register version 
> -1.png, register version -2.png
>
>
> Belongs to UI work of Patch Upgrade ( Provide ability to apply single patches 
> on top of RU release).
> This one is the second part to implement" Manage Ambari > Register Version" 
> page.
> 1. Should generate the UI template for all three categories, then show loaded 
> version definition info in three different categories as:
>  
> Just show what loaded for this one, will file another ticket to make 
> 'Repositories' category more functional.
> 2. Click on "Save" button on the bottom of this page, will PUT the 
> information to server side.



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

[jira] [Updated] (AMBARI-14797) Register Version: display loaded version definition info in different categories and Save them


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

Xi Wang updated AMBARI-14797:
-
Attachment: (was: AMBARI-14797.patch)

> Register Version: display loaded version definition info in different 
> categories and Save them
> --
>
> Key: AMBARI-14797
> URL: https://issues.apache.org/jira/browse/AMBARI-14797
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Xi Wang
>Assignee: Xi Wang
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-14797.patch, register version -1.png, register 
> version -2.png
>
>
> Belongs to UI work of Patch Upgrade ( Provide ability to apply single patches 
> on top of RU release).
> This one is the second part to implement" Manage Ambari > Register Version" 
> page.
> 1. Should generate the UI template for all three categories, then show loaded 
> version definition info in three different categories as:
>  
> Just show what loaded for this one, will file another ticket to make 
> 'Repositories' category more functional.
> 2. Click on "Save" button on the bottom of this page, will PUT the 
> information to server side.



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

[jira] [Updated] (AMBARI-14910) HAWQ hdfs-client.xml should be updated when NN HA in enabled

2016-02-03 Thread Matt (JIRA)


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

Matt updated AMBARI-14910:
--
Attachment: AMBARI-14910-branch-2.2.patch

> HAWQ hdfs-client.xml should be updated when NN HA in enabled
> 
>
> Key: AMBARI-14910
> URL: https://issues.apache.org/jira/browse/AMBARI-14910
> Project: Ambari
>  Issue Type: New Feature
>  Components: ambari-web
>Reporter: Matt
>Assignee: Matt
>Priority: Minor
> Fix For: trunk, 2.2.2
>
> Attachments: AMBARI-14910-branch-2.2.patch
>
>
> Scenario:
> - Install Ambari
> - Install a cluster with HDFS and HAWQ
> - Enable NN HA
> After enabling NN HA, HAWQ's hdfs-client.xml is not populated with the HA 
> related parameters.
> Ensure that HAWQ works after NN HA enabled on a cluster with HAWQ.



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

Re: Review Request 43158: HAWQ hdfs-client.xml should be updated when NN HA in enabled

2016-02-03 Thread bhuvnesh chaudhary


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


Ship it!




Ship It!

- bhuvnesh chaudhary


On Feb. 3, 2016, 10:53 p.m., Matt wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/43158/
> ---
> 
> (Updated Feb. 3, 2016, 10:53 p.m.)
> 
> 
> Review request for Ambari, Alexander Denissov, Alejandro Fernandez, bhuvnesh 
> chaudhary, Goutam Tadi, jun aoki, Lav Jain, Newton Alex, and Oleksandr 
> Diachenko.
> 
> 
> Bugs: AMBARI-14910
> https://issues.apache.org/jira/browse/AMBARI-14910
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Scenario:
> - Install Ambari
> - Install a cluster with HDFS and HAWQ
> - Enable NN HA
> 
> After enabling NN HA, HAWQ's hdfs-client.xml is not populated with the HA 
> related parameters.
> 
> Ensure that HAWQ works after NN HA enabled on a cluster with HAWQ.
> 
> 
> Diffs
> -
> 
>   
> ambari-web/app/controllers/main/admin/highAvailability/nameNode/rollback_controller.js
>  4aa2d73 
>   
> ambari-web/app/controllers/main/admin/highAvailability/nameNode/step3_controller.js
>  bf5b96a 
>   
> ambari-web/app/controllers/main/admin/highAvailability/nameNode/step9_controller.js
>  7745c6b 
>   ambari-web/app/data/HDP2/ha_properties.js 8b2960d 
> 
> Diff: https://reviews.apache.org/r/43158/diff/
> 
> 
> Testing
> ---
> 
> Manually Tested.
> 
> Unit test results:
>   10357 tests complete (9 seconds)
>   121 tests pending
> 
> [INFO] 
> 
> [INFO] BUILD SUCCESS
> [INFO] 
> 
> [INFO] Total time: 54.181 s
> [INFO] Finished at: 2016-02-03T14:52:11-08:00
> [INFO] Final Memory: 12M/311M
> [INFO] 
> 
> 
> 
> Thanks,
> 
> Matt
> 
>

[jira] [Commented] (AMBARI-14884) Hawq standby host config should be removed on single node cluster during initial cluster installation


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

jun aoki commented on AMBARI-14884:
---

Committed to branch-2.2
16ff8f30a9108a904ebd656ebe7b162b6c3c258d

> Hawq standby host config should be removed on single node cluster during 
> initial cluster installation
> -
>
> Key: AMBARI-14884
> URL: https://issues.apache.org/jira/browse/AMBARI-14884
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: trunk
>Reporter: bhuvnesh chaudhary
>Assignee: bhuvnesh chaudhary
>Priority: Trivial
> Fix For: trunk, 2.2.2
>
> Attachments: AMBARI-14884-1.patch, AMBARI-14884-branch-2.2.patch, 
> AMBARI-14884.patch
>
>
> Hawq standby host config should be removed on single node cluster during 
> initial cluster installation.
> Currently, it works only if the cluster is installed and Hawq is added later, 
> but during initial single node installation of cluster with Hawq, it does not.



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

Review Request 43158: HAWQ hdfs-client.xml should be updated when NN HA in enabled

2016-02-03 Thread Matt


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

Review request for Ambari, Alexander Denissov, Alejandro Fernandez, bhuvnesh 
chaudhary, Goutam Tadi, jun aoki, Lav Jain, Newton Alex, and Oleksandr 
Diachenko.


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


Repository: ambari


Description
---

Scenario:
- Install Ambari
- Install a cluster with HDFS and HAWQ
- Enable NN HA

After enabling NN HA, HAWQ's hdfs-client.xml is not populated with the HA 
related parameters.

Ensure that HAWQ works after NN HA enabled on a cluster with HAWQ.


Diffs
-

  
ambari-web/app/controllers/main/admin/highAvailability/nameNode/rollback_controller.js
 4aa2d73 
  
ambari-web/app/controllers/main/admin/highAvailability/nameNode/step3_controller.js
 bf5b96a 
  
ambari-web/app/controllers/main/admin/highAvailability/nameNode/step9_controller.js
 7745c6b 
  ambari-web/app/data/HDP2/ha_properties.js 8b2960d 

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


Testing
---

Manually Tested.

Unit test results:
  10357 tests complete (9 seconds)
  121 tests pending

[INFO] 
[INFO] BUILD SUCCESS
[INFO] 
[INFO] Total time: 54.181 s
[INFO] Finished at: 2016-02-03T14:52:11-08:00
[INFO] Final Memory: 12M/311M
[INFO] 


Thanks,

Matt

[jira] [Updated] (AMBARI-14797) Register Version: display loaded version definition info in different categories and Save them


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

Xi Wang updated AMBARI-14797:
-
Attachment: AMBARI-14797.patch

> Register Version: display loaded version definition info in different 
> categories and Save them
> --
>
> Key: AMBARI-14797
> URL: https://issues.apache.org/jira/browse/AMBARI-14797
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Xi Wang
>Assignee: Xi Wang
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-14797.patch, AMBARI-14797.patch, register version 
> -1.png, register version -2.png
>
>
> Belongs to UI work of Patch Upgrade ( Provide ability to apply single patches 
> on top of RU release).
> This one is the second part to implement" Manage Ambari > Register Version" 
> page.
> 1. Should generate the UI template for all three categories, then show loaded 
> version definition info in three different categories as:
>  
> Just show what loaded for this one, will file another ticket to make 
> 'Repositories' category more functional.
> 2. Click on "Save" button on the bottom of this page, will PUT the 
> information to server side.



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

[jira] [Updated] (AMBARI-14837) Versions: display all versions as tabs on left side, version details on selecting


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

Xi Wang updated AMBARI-14837:
-
Attachment: AMBARI-14837.patch

> Versions: display all versions as tabs on left side, version details on 
> selecting
> -
>
> Key: AMBARI-14837
> URL: https://issues.apache.org/jira/browse/AMBARI-14837
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Xi Wang
>Assignee: Xi Wang
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-14837.patch, AMBARI-14837.patch, 
> AMBARI-14837.patch, Screen Shot 2016-01-29 at 5.59.13 PM.png, Screen Shot 
> 2016-01-29 at 5.59.28 PM.png, Screen Shot 2016-02-01 at 11.33.35 AM.png
>
>
> This one is to implement" Manage Ambari > Versions" page. 
> 1. All versions show be displayed as tabs on the left side,  each patch 
> version should be a child of its parent stack version.
> 2. On selecting a version (either patch version or original stack version), 
> all the version definition info show up on the right side.
> This look should be the same as register version page. "Details" and 
> "Contents" are un-editable, "Repos" is editable and addable.
> 3. Add a mark/icon to the patch versions to differentiate them from original 
> stack versions. 
> Related API:
> {code}
> GET /api/v1/stacks/HDP/versions/2.3/repository_versions
> PUT /api/v1/stacks/HDP/versions/2.3/repository_versions   // for editing repo 
> urls
> {code}



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

[jira] [Updated] (AMBARI-14913) Show HAWQ default_segment_num parameter in General section

2016-02-03 Thread Matt (JIRA)


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

Matt updated AMBARI-14913:
--
Attachment: AMBARI-14913-branch-2.2.patch

> Show HAWQ default_segment_num parameter in General section
> --
>
> Key: AMBARI-14913
> URL: https://issues.apache.org/jira/browse/AMBARI-14913
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-web
>Reporter: Matt
>Assignee: Matt
>Priority: Trivial
> Fix For: trunk, 2.2.2
>
> Attachments: AMBARI-14913-branch-2.2.patch
>
>
> Given the importance of the parameter and likelihood of tuning it 
> occasionally, HAWQ default_segment_num parameter should be displayed in 
> General section.



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

[jira] [Commented] (AMBARI-14871) Better messages when Ambari web UI can't resolve hosts to build quicklinks