[jira] [Commented] (AMBARI-15090) [Ambari tarballs] ambari-server python scripts should support running from custom root

[Andrew Onischuk (JIRA)]

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

Andrew Onischuk commented on AMBARI-15090:
--

The hanging hudson build is not related to the change, for some reason it 
hanged in python-client, which was not changed in scope of this.

> [Ambari tarballs] ambari-server python scripts should support running from 
> custom root
> --
>
> Key: AMBARI-15090
> URL: https://issues.apache.org/jira/browse/AMBARI-15090
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.4.0
>
> Attachments: AMBARI-15090.patch
>
>




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

[jira] [Commented] (AMBARI-15086) SCRIPT alert params should tooltip the description

[Oleg Nechiporenko (JIRA)]

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

Oleg Nechiporenko commented on AMBARI-15086:


Build is aborted not because of this patch.

> SCRIPT alert params should tooltip the description
> --
>
> Key: AMBARI-15086
> URL: https://issues.apache.org/jira/browse/AMBARI-15086
> 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-15086.patch
>
>
> When showing params in the UI for SCRIPT alerts, the description should be 
> available via Tooltip. For example "The maximum time before this alert is 
> considered to be CRITICAL" should be tooltip on the Connection Timeout field 
> in the UI
> {code}
> "parameters": [
> {
>   "name": "connection.timeout",
>   "display_name": "Connection Timeout",
>   "value": 5.0,
>   "type": "NUMERIC",
>   "description": "The maximum time before this alert is 
> considered to be CRITICAL",
>   "units": "seconds",
>   "threshold": "CRITICAL"
> },
> {code}



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

[jira] [Commented] (AMBARI-15046) Hive View: Upload table should support XML and JSON and storage type ORC

[Nitiraj Singh Rathore (JIRA)]

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

Nitiraj Singh Rathore commented on AMBARI-15046:


JSON Format supported : 
Input json file should contain an array of json objects.
example : 
[ 
{ "col1Name" : "value-1-1", "col2Name" : "value-1-2"}
,
{ "col1Name" : "value-2-1", "col2Name" : "value-2-2"}
]
XML format supported : 
 
 
row1-col1-Data 
row1-col2-Data 
row1-col3-Data 
row1-col4-Data 
 
 
row2-col1-Data 
row2-col2-Data 
row2-col3-Data 
row2-col4-Data 
 



> Hive View: Upload table should support XML and JSON and storage type ORC
> 
>
> Key: AMBARI-15046
> URL: https://issues.apache.org/jira/browse/AMBARI-15046
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.2.0
>Reporter: Nitiraj Singh Rathore
>Assignee: Nitiraj Singh Rathore
> Fix For: 2.2.2
>
> Attachments: AMBARI-15046_branch-2.2.patch
>
>
> Hive View should add support to the file upload feature for the following:
> Create table using JSON/XML/CSV format
> File source can be local upload or HDFS
> Internal Hive storage type of ORC and others should be supported, with ORC as 
> default.



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

Re: Review Request 43753: Update description for HAWQ Sync standby alert

[Goutam Tadi]

> On Feb. 19, 2016, 3:57 a.m., bhuvnesh chaudhary wrote:
> > ambari-server/src/main/resources/common-services/HAWQ/2.0.0/alerts.json, 
> > line 7
> > 
> >
> > We might need to still rephrase it and may be what we had earlier was 
> > okay, as there are situation where the status will be mentioned as Not 
> > Synchronized but resynchronize will not fix it. Re-sync will not work on 
> > all the situations.
> > 
> > Once has to remove the standby and re-init it. 
> > 
> > Refer to the greenplum article, HAWQ should be behaving the same. 
> > 
> > https://support.pivotal.io/hc/en-us/articles/201157218-gpstate-f-reports-Standby-master-too-far-behind-
> 
> Matt wrote:
> So what are you suggesting?
> - Leave the message as it is, and let the user figure it out somehow? Not 
> a good idea to leave the user in the dark.
> - Add an additional line saying: "If HAWQ Standby is too far behind HAWQ 
> Master, HAWQ Standby might have to be deleted and installed again"?

Suggestion to addendum: "Try resynchronizing Standby (Re-Synchronize HAWQ 
Standby). If this doesn't work  reinstall Standby."


- Goutam


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


On Feb. 19, 2016, 3:33 a.m., Matt wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/43753/
> ---
> 
> (Updated Feb. 19, 2016, 3:33 a.m.)
> 
> 
> Review request for Ambari, Alexander Denissov, bhuvnesh chaudhary, Goutam 
> Tadi, jun aoki, Lav Jain, and Newton Alex.
> 
> 
> Bugs: AMBARI-15104
> https://issues.apache.org/jira/browse/AMBARI-15104
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Update the description for the alert so that the user knows what to do if the 
> alert is triggered from the description on the alert page
> 
> 
> Diffs
> -
> 
>   ambari-server/src/main/resources/common-services/HAWQ/2.0.0/alerts.json 
> 3119a0c 
> 
> Diff: https://reviews.apache.org/r/43753/diff/
> 
> 
> Testing
> ---
> 
> Manually Tested. Descriptions appears on the alerts page.
> 
> No additional unit tests required.
> 
> 
> Thanks,
> 
> Matt
> 
>

Re: Review Request 43752: Move HAWQ system password to General Accordion tab

[Goutam Tadi]

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


Ship it!




Ship It!

- Goutam Tadi


On Feb. 19, 2016, 3:34 a.m., Matt wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/43752/
> ---
> 
> (Updated Feb. 19, 2016, 3:34 a.m.)
> 
> 
> Review request for Ambari, Alexander Denissov, bhuvnesh chaudhary, Goutam 
> Tadi, jun aoki, Lav Jain, and Newton Alex.
> 
> 
> Bugs: AMBARI-15103
> https://issues.apache.org/jira/browse/AMBARI-15103
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> The password is currently under Advanced hawq-env. Move it to General section.
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/resources/common-services/HAWQ/2.0.0/configuration/hawq-env.xml
>  e3a97fd 
>   ambari-web/app/data/HDP2.3/site_properties.js c5fb525 
> 
> Diff: https://reviews.apache.org/r/43752/diff/
> 
> 
> Testing
> ---
> 
> Manually Tested.
> 
> No additional unit tests required.
> 
> Unit tests passed on Ambari-web:
>   10412 tests complete (10 seconds)
>   121 tests pending
> 
> [INFO] 
> 
> [INFO] BUILD SUCCESS
> [INFO] 
> 
> [INFO] Total time: 39.598 s
> [INFO] Finished at: 2016-02-18T19:17:30-08:00
> [INFO] Final Memory: 12M/311M
> [INFO] 
> 
> 
> 
> Thanks,
> 
> Matt
> 
>

[jira] [Created] (AMBARI-15108) Ambari should auto generate cluster.xml when Falcon is installed

[Vlad (JIRA)]

Vlad created AMBARI-15108:
-

 Summary: Ambari should auto generate cluster.xml when Falcon is 
installed
 Key: AMBARI-15108
 URL: https://issues.apache.org/jira/browse/AMBARI-15108
 Project: Ambari
  Issue Type: Improvement
Reporter: Vlad


Every use of Falcon starts with creating a cluster.xml file, and making Falcon 
aware of it.  This task should be automated by Ambari as it has all of the 
needed information.  The HDFS directories can be requested from the user 
through the Ambari UI if the user doesn't accept sensible defaults.

https://falcon.apache.org/EntitySpecification.html#Cluster_Specification



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

[jira] [Created] (AMBARI-15107) Add meta-data for HAWQ configurations

[Matt (JIRA)]

Matt created AMBARI-15107:
-

 Summary: Add meta-data for HAWQ configurations
 Key: AMBARI-15107
 URL: https://issues.apache.org/jira/browse/AMBARI-15107
 Project: Ambari
  Issue Type: Technical task
Reporter: Matt
Priority: Minor






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

[jira] [Created] (AMBARI-15106) Ambari should manage Sqoop metastore to facilitate incremental loads

[Vlad (JIRA)]

Vlad created AMBARI-15106:
-

 Summary: Ambari should manage Sqoop metastore to facilitate 
incremental loads
 Key: AMBARI-15106
 URL: https://issues.apache.org/jira/browse/AMBARI-15106
 Project: Ambari
  Issue Type: Improvement
Reporter: Vlad


Sqoop metastore is needed to enable incremental import jobs executed through 
Oozie. This metastore should be managed (install/start/stop/monitor) by Ambari.

Sqoop incremental import jobs require --last-value parameter.   So that a user 
doesn't have to remember the parameter after each Sqoop execution a Sqoop job 
can be saved to the metastore where this parameter is remembered.  With out a 
central metastore Sqoop saves the data to $HOME/.sqoop/ and that does not work 
when executing a Sqoop job from Oozie.



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

[jira] [Commented] (AMBARI-15080) HBase unittest fails when using python 2.6

[Hudson (JIRA)]

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

Hudson commented on AMBARI-15080:
-

SUCCESS: Integrated in Ambari-trunk-Commit #4355 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/4355/])
AMBARI-15080. HBase unittest fails when using python 2.6(Lav Jain via 
(odiachenko: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=defbeddae55d110b3323b389c2666071eec6883d])
* ambari-server/src/test/python/stacks/2.0.6/HBASE/test_phoenix_queryserver.py


> HBase unittest fails when using python 2.6
> --
>
> Key: AMBARI-15080
> URL: https://issues.apache.org/jira/browse/AMBARI-15080
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk
>Reporter: Lav Jain
>Assignee: Lav Jain
>Priority: Critical
> Fix For: 2.3.0
>
> Attachments: AMBARI-15080.patch
>
>
> {code}
> [root@c6401 ambari-server]# python
> Python 2.6.6 (r266:84292, Jul 23 2015, 15:22:56)
> [GCC 4.4.7 20120313 (Red Hat 4.4.7-11)] on linux2
> Type "help", "copyright", "credits" or "license" for more information.
> [root@c6401 ambari-server]# mvn test
> .
> .
> .
> --
> Failed tests:
> ERROR: Failed to load test files ['test_phoenix_queryserver', 
> 'test_hbase_master', 'test_hbase_client', 'test_hbase_service_check', 
> 'test_hbase_regionserver']
> --
> Traceback (most recent call last):
>   File "unitTests.py", line 120, in stack_test_executor
> modules]
>   File "/usr/lib64/python2.6/unittest.py", line 575, in loadTestsFromName
> module = __import__('.'.join(parts_copy))
>   File 
> "/root/ambari/ambari-server/src/test/python/stacks/2.0.6/HBASE/test_phoenix_queryserver.py",
>  line 21, in 
> from unittest import SkipTest
> ImportError: cannot import name SkipTest
> --
> {code}



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

[jira] [Commented] (AMBARI-15067) Add custom commands for HAWQ to run check and clear cache

[Hudson (JIRA)]

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

Hudson commented on AMBARI-15067:
-

SUCCESS: Integrated in Ambari-trunk-Commit #4355 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/4355/])
AMBARI-15067: Add custom commands for HAWQ to run check and clear (jaoki: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=0941997b0f68f1044242354c9f3f0f4b3a476c7d])
* ambari-web/app/models/host_component.js
* ambari-web/app/messages.js
* ambari-web/app/utils/helper.js
* 
ambari-server/src/main/resources/common-services/HAWQ/2.0.0/package/scripts/master_helper.py
* 
ambari-server/src/main/resources/common-services/HAWQ/2.0.0/package/scripts/params.py
* ambari-web/app/views/main/service/item.js
* 
ambari-server/src/main/resources/common-services/HAWQ/2.0.0/package/templates/slaves.j2
* 
ambari-server/src/main/resources/common-services/HAWQ/2.0.0/package/templates/hawq-hosts.j2
* ambari-server/src/main/resources/common-services/HAWQ/2.0.0/metainfo.xml
* 
ambari-server/src/main/resources/common-services/HAWQ/2.0.0/package/scripts/hawqmaster.py
* 
ambari-server/src/main/resources/common-services/HAWQ/2.0.0/package/scripts/hawq_constants.py


> Add custom commands for HAWQ to run check and clear cache
> -
>
> Key: AMBARI-15067
> URL: https://issues.apache.org/jira/browse/AMBARI-15067
> Project: Ambari
>  Issue Type: Story
>  Components: ambari-web, stacks
>Reporter: Matt
>Assignee: Matt
>Priority: Minor
> Fix For: trunk, 2.2.2
>
> Attachments: AMBARI-15067-branch-2.2-orig.patch, 
> AMBARI-15067-trunk-orig.patch
>
>
> A HAWQ user should be able to run hawq check and clear HDFS Metadata cache 
> from the Ambari UI.



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

[jira] [Commented] (AMBARI-15101) Remove the dependency between ZK start and Ranger user sync start

[Hudson (JIRA)]

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

Hudson commented on AMBARI-15101:
-

SUCCESS: Integrated in Ambari-trunk-Commit #4355 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/4355/])
AMBARI-15101. Remove the dependency between ZK start and Ranger user (smohanty: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=183f71f90495cfbba29961182b293c9408d3effb])
* ambari-server/src/main/resources/stacks/HDP/2.2/role_command_order.json


> Remove the dependency between ZK start and Ranger user sync start
> -
>
> Key: AMBARI-15101
> URL: https://issues.apache.org/jira/browse/AMBARI-15101
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.2.2
>Reporter: Sumit Mohanty
>Assignee: Sumit Mohanty
> Fix For: 2.2.2
>
> Attachments: AMBARI-15101.patch
>
>
> ZK start should not depend on Ranger user sync start. We should remove the 
> dependency.



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

[jira] [Commented] (AMBARI-15099) Ambari missing metrics in UI with Vip settings enabled.

[Hudson (JIRA)]

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

Hudson commented on AMBARI-15099:
-

SUCCESS: Integrated in Ambari-trunk-Commit #4355 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/4355/])
AMBARI-15099 : Ambari missing metrics in UI with Vip settings enabled 
(avijayan: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=5ae72ac59e14dc033140ee4626dbe0761a574893])
* 
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/AbstractProviderModule.java


> Ambari missing metrics in UI with Vip settings enabled.
> ---
>
> Key: AMBARI-15099
> URL: https://issues.apache.org/jira/browse/AMBARI-15099
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.2.1
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15099.patch
>
>
> When using a vip settings for a cluster with 2 Collectors (1 active at a 
> time), no metrics are seen unless Ambari Server is restarted.



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

Re: Review Request 43753: Update description for HAWQ Sync standby alert

[Matt]

> On Feb. 18, 2016, 7:57 p.m., bhuvnesh chaudhary wrote:
> > ambari-server/src/main/resources/common-services/HAWQ/2.0.0/alerts.json, 
> > line 7
> > 
> >
> > We might need to still rephrase it and may be what we had earlier was 
> > okay, as there are situation where the status will be mentioned as Not 
> > Synchronized but resynchronize will not fix it. Re-sync will not work on 
> > all the situations.
> > 
> > Once has to remove the standby and re-init it. 
> > 
> > Refer to the greenplum article, HAWQ should be behaving the same. 
> > 
> > https://support.pivotal.io/hc/en-us/articles/201157218-gpstate-f-reports-Standby-master-too-far-behind-

So what are you suggesting?
- Leave the message as it is, and let the user figure it out somehow? Not a 
good idea to leave the user in the dark.
- Add an additional line saying: "If HAWQ Standby is too far behind HAWQ 
Master, HAWQ Standby might have to be deleted and installed again"?


- Matt


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


On Feb. 18, 2016, 7:33 p.m., Matt wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/43753/
> ---
> 
> (Updated Feb. 18, 2016, 7:33 p.m.)
> 
> 
> Review request for Ambari, Alexander Denissov, bhuvnesh chaudhary, Goutam 
> Tadi, jun aoki, Lav Jain, and Newton Alex.
> 
> 
> Bugs: AMBARI-15104
> https://issues.apache.org/jira/browse/AMBARI-15104
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Update the description for the alert so that the user knows what to do if the 
> alert is triggered from the description on the alert page
> 
> 
> Diffs
> -
> 
>   ambari-server/src/main/resources/common-services/HAWQ/2.0.0/alerts.json 
> 3119a0c 
> 
> Diff: https://reviews.apache.org/r/43753/diff/
> 
> 
> Testing
> ---
> 
> Manually Tested. Descriptions appears on the alerts page.
> 
> No additional unit tests required.
> 
> 
> Thanks,
> 
> Matt
> 
>

[jira] [Commented] (AMBARI-15067) Add custom commands for HAWQ to run check and clear cache

[Hudson (JIRA)]

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

Hudson commented on AMBARI-15067:
-

SUCCESS: Integrated in Ambari-branch-2.2 #360 (See 
[https://builds.apache.org/job/Ambari-branch-2.2/360/])
AMBARI-15067: Add custom commands for HAWQ to run check and clear (jaoki: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=1e93caf4f7ba92f0190433303b7920eaf54c57eb])
* ambari-web/app/utils/helper.js
* 
ambari-server/src/main/resources/common-services/HAWQ/2.0.0/package/scripts/params.py
* ambari-web/app/models/host_component.js
* 
ambari-server/src/main/resources/common-services/HAWQ/2.0.0/package/scripts/master_helper.py
* 
ambari-server/src/main/resources/common-services/HAWQ/2.0.0/package/scripts/hawqmaster.py
* 
ambari-server/src/main/resources/common-services/HAWQ/2.0.0/package/templates/hawq-hosts.j2
* ambari-web/app/messages.js
* ambari-web/app/views/main/service/item.js
* 
ambari-server/src/main/resources/common-services/HAWQ/2.0.0/package/scripts/hawq_constants.py
* 
ambari-server/src/main/resources/common-services/HAWQ/2.0.0/package/templates/slaves.j2
* ambari-server/src/main/resources/common-services/HAWQ/2.0.0/metainfo.xml


> Add custom commands for HAWQ to run check and clear cache
> -
>
> Key: AMBARI-15067
> URL: https://issues.apache.org/jira/browse/AMBARI-15067
> Project: Ambari
>  Issue Type: Story
>  Components: ambari-web, stacks
>Reporter: Matt
>Assignee: Matt
>Priority: Minor
> Fix For: trunk, 2.2.2
>
> Attachments: AMBARI-15067-branch-2.2-orig.patch, 
> AMBARI-15067-trunk-orig.patch
>
>
> A HAWQ user should be able to run hawq check and clear HDFS Metadata cache 
> from the Ambari UI.



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

Re: Review Request 43748: Add alerts for HAWQ components status

[Matt]

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


Ship it!




Ship It!

- Matt


On Feb. 18, 2016, 4:59 p.m., bhuvnesh chaudhary wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/43748/
> ---
> 
> (Updated Feb. 18, 2016, 4:59 p.m.)
> 
> 
> Review request for Ambari, Alejandro Fernandez, Jaimin Jetly, jun aoki, 
> Jonathan Hurley, Jayush Luniya, Oleksandr Diachenko, Richard Zang, Sumit 
> Mohanty, and Yusaku Sako.
> 
> 
> Bugs: AMBARI-15105
> https://issues.apache.org/jira/browse/AMBARI-15105
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> This patch introduces alerts for HAWQ components based on PORT. The below 
> components are covered.
> - Master
> - Standby
> - Segment
> 
> 
> Diffs
> -
> 
>   ambari-server/src/main/resources/common-services/HAWQ/2.0.0/alerts.json 
> 3119a0c 
> 
> Diff: https://reviews.apache.org/r/43748/diff/
> 
> 
> Testing
> ---
> 
> yes, manual.
> 
> 
> Thanks,
> 
> bhuvnesh chaudhary
> 
>

Re: Review Request 43748: Add alerts for HAWQ components status

[Matt]

> On Feb. 18, 2016, 5:56 p.m., Matt wrote:
> > ambari-server/src/main/resources/common-services/HAWQ/2.0.0/alerts.json, 
> > line 49
> > 
> >
> > Should this be HOST? I believe it is more of a service level alert.
> 
> Jonathan Hurley wrote:
> HAWQSEGMENT is a slave with cardinality of 1+ ... makes sense to keep it 
> as HOST.

Thanks for clarifying Jonathon!


- Matt


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


On Feb. 18, 2016, 4:59 p.m., bhuvnesh chaudhary wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/43748/
> ---
> 
> (Updated Feb. 18, 2016, 4:59 p.m.)
> 
> 
> Review request for Ambari, Alejandro Fernandez, Jaimin Jetly, jun aoki, 
> Jonathan Hurley, Jayush Luniya, Oleksandr Diachenko, Richard Zang, Sumit 
> Mohanty, and Yusaku Sako.
> 
> 
> Bugs: AMBARI-15105
> https://issues.apache.org/jira/browse/AMBARI-15105
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> This patch introduces alerts for HAWQ components based on PORT. The below 
> components are covered.
> - Master
> - Standby
> - Segment
> 
> 
> Diffs
> -
> 
>   ambari-server/src/main/resources/common-services/HAWQ/2.0.0/alerts.json 
> 3119a0c 
> 
> Diff: https://reviews.apache.org/r/43748/diff/
> 
> 
> Testing
> ---
> 
> yes, manual.
> 
> 
> Thanks,
> 
> bhuvnesh chaudhary
> 
>

Re: Review Request 43748: Add alerts for HAWQ components status

[Jayush Luniya]

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


Ship it!




Ship It!

- Jayush Luniya


On Feb. 19, 2016, 12:59 a.m., bhuvnesh chaudhary wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/43748/
> ---
> 
> (Updated Feb. 19, 2016, 12:59 a.m.)
> 
> 
> Review request for Ambari, Alejandro Fernandez, Jaimin Jetly, jun aoki, 
> Jonathan Hurley, Jayush Luniya, Oleksandr Diachenko, Richard Zang, Sumit 
> Mohanty, and Yusaku Sako.
> 
> 
> Bugs: AMBARI-15105
> https://issues.apache.org/jira/browse/AMBARI-15105
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> This patch introduces alerts for HAWQ components based on PORT. The below 
> components are covered.
> - Master
> - Standby
> - Segment
> 
> 
> Diffs
> -
> 
>   ambari-server/src/main/resources/common-services/HAWQ/2.0.0/alerts.json 
> 3119a0c 
> 
> Diff: https://reviews.apache.org/r/43748/diff/
> 
> 
> Testing
> ---
> 
> yes, manual.
> 
> 
> Thanks,
> 
> bhuvnesh chaudhary
> 
>

[jira] [Updated] (AMBARI-15061) PXF Service checks fails with timeout

[bhuvnesh chaudhary (JIRA)]

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

bhuvnesh chaudhary updated AMBARI-15061:

Attachment: AMBARI-15061-2.patch

> PXF Service checks fails with timeout
> -
>
> Key: AMBARI-15061
> URL: https://issues.apache.org/jira/browse/AMBARI-15061
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: trunk, 2.2.0
>Reporter: bhuvnesh chaudhary
>Assignee: bhuvnesh chaudhary
> Fix For: trunk, 2.2.0
>
> Attachments: AMBARI-15061-1.patch, AMBARI-15061-2.patch, 
> AMBARI-15061-branch-2.2.patch
>
>
> During PXF service check, in order to execute hbase / hive command, we do 
> initialize the shell everytime (hbase shell / hive) and then run the command. 
> Initializing the shell takes time and we do that around 3-4 times which 
> consumes majority of the time.
> We should initialize the shell once, and execute the commands using a file 
> instead of doing individually.



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

Re: Review Request 43663: PXF Service checks fails with timeout

[bhuvnesh chaudhary]

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

(Updated Feb. 19, 2016, 4:39 a.m.)


Review request for Ambari, Alejandro Fernandez, jun aoki, Jayush Luniya, 
Oleksandr Diachenko, Richard Zang, and Yusaku Sako.


Changes
---

Applied feedback


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


Repository: ambari


Description
---

During PXF service check, in order to execute hbase / hive command, we do 
initialize the shell everytime (hbase shell / hive) and then run the command. 
Initializing the shell takes time and we do that around 3-4 times which 
consumes majority of the time.
We should initialize the shell once, and execute the commands using a file 
instead of doing individually.


Diffs (updated)
-

  
ambari-server/src/main/resources/common-services/PXF/3.0.0/package/scripts/params.py
 b3e85e4 
  
ambari-server/src/main/resources/common-services/PXF/3.0.0/package/scripts/pxf_constants.py
 9d93a38 
  
ambari-server/src/main/resources/common-services/PXF/3.0.0/package/scripts/service_check.py
 21b7c5d 

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


Testing
---

yes. manual.


Thanks,

bhuvnesh chaudhary

Re: Review Request 43663: PXF Service checks fails with timeout

[bhuvnesh chaudhary]

> On Feb. 19, 2016, 1:37 a.m., jun aoki wrote:
> > ambari-server/src/main/resources/common-services/PXF/3.0.0/package/files/hbase-cleanup-data.sh,
> >  line 22
> > 
> >
> > Could this be InlineTemplate?

will do


> On Feb. 19, 2016, 1:37 a.m., jun aoki wrote:
> > ambari-server/src/main/resources/common-services/PXF/3.0.0/package/files/hbase-populate-data.sh,
> >  line 22
> > 
> >
> > Could this be InlineTemplate?

will do


> On Feb. 19, 2016, 1:37 a.m., jun aoki wrote:
> > ambari-server/src/main/resources/common-services/PXF/3.0.0/package/scripts/pxf_constants.py,
> >  line 27
> > 
> >
> > will be nice if we have more consistent naming ?
> > e.g.
> > ```
> > hbase_populate_data_script = "hbase-populate-data.sh"
> > hbase_cleanup_data_script = "hbase-cleanup-data.sh"
> > ```

will do


> On Feb. 19, 2016, 1:37 a.m., jun aoki wrote:
> > ambari-server/src/main/resources/common-services/PXF/3.0.0/package/scripts/service_check.py,
> >  line 266
> > 
> >
> > how about 
> > ```
> > 
> > def __create_hbase_script(self, script_name)
> >   File("{0}/{1}".format(params.exec_tmp_dir, script_name),
> >  content=StaticFile("{0}".format(script_name)),
> >  mode=0755)
> > 
> > ...
> > 
> > # caller
> > __create_hbase_script(pxf_constants.hbase_load_script)
> > __create_hbase_script(pxf_constants.hbase_cleanup_script)
> > ```

Makes sense, but since its used only 2 times, would not prefer creating another 
wrapper over File here.


> On Feb. 19, 2016, 1:37 a.m., jun aoki wrote:
> > ambari-server/src/main/resources/common-services/PXF/3.0.0/package/scripts/service_check.py,
> >  line 329
> > 
> >
> > At this point, it is guaranteed the table does not exist?

hbase script to populate data has the commands to disable and drop before 
creating, so yes, it will take care of it.


- bhuvnesh


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


On Feb. 17, 2016, 10:46 p.m., bhuvnesh chaudhary wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/43663/
> ---
> 
> (Updated Feb. 17, 2016, 10:46 p.m.)
> 
> 
> Review request for Ambari, Alejandro Fernandez, jun aoki, Jayush Luniya, 
> Oleksandr Diachenko, Richard Zang, and Yusaku Sako.
> 
> 
> Bugs: AMBARI-15061
> https://issues.apache.org/jira/browse/AMBARI-15061
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> During PXF service check, in order to execute hbase / hive command, we do 
> initialize the shell everytime (hbase shell / hive) and then run the command. 
> Initializing the shell takes time and we do that around 3-4 times which 
> consumes majority of the time.
> We should initialize the shell once, and execute the commands using a file 
> instead of doing individually.
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/resources/common-services/PXF/3.0.0/package/files/hbase-cleanup-data.sh
>  PRE-CREATION 
>   
> ambari-server/src/main/resources/common-services/PXF/3.0.0/package/files/hbase-populate-data.sh
>  PRE-CREATION 
>   
> ambari-server/src/main/resources/common-services/PXF/3.0.0/package/scripts/params.py
>  b3e85e4 
>   
> ambari-server/src/main/resources/common-services/PXF/3.0.0/package/scripts/pxf_constants.py
>  9d93a38 
>   
> ambari-server/src/main/resources/common-services/PXF/3.0.0/package/scripts/service_check.py
>  21b7c5d 
> 
> Diff: https://reviews.apache.org/r/43663/diff/
> 
> 
> Testing
> ---
> 
> yes. manual.
> 
> 
> Thanks,
> 
> bhuvnesh chaudhary
> 
>

Re: Review Request 43753: Update description for HAWQ Sync standby alert

[bhuvnesh chaudhary]

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




ambari-server/src/main/resources/common-services/HAWQ/2.0.0/alerts.json (line 7)


We might need to still rephrase it and may be what we had earlier was okay, 
as there are situation where the status will be mentioned as Not Synchronized 
but resynchronize will not fix it. Re-sync will not work on all the situations.

Once has to remove the standby and re-init it. 

Refer to the greenplum article, HAWQ should be behaving the same. 

https://support.pivotal.io/hc/en-us/articles/201157218-gpstate-f-reports-Standby-master-too-far-behind-


- bhuvnesh chaudhary


On Feb. 19, 2016, 3:33 a.m., Matt wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/43753/
> ---
> 
> (Updated Feb. 19, 2016, 3:33 a.m.)
> 
> 
> Review request for Ambari, Alexander Denissov, bhuvnesh chaudhary, Goutam 
> Tadi, jun aoki, Lav Jain, and Newton Alex.
> 
> 
> Bugs: AMBARI-15104
> https://issues.apache.org/jira/browse/AMBARI-15104
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Update the description for the alert so that the user knows what to do if the 
> alert is triggered from the description on the alert page
> 
> 
> Diffs
> -
> 
>   ambari-server/src/main/resources/common-services/HAWQ/2.0.0/alerts.json 
> 3119a0c 
> 
> Diff: https://reviews.apache.org/r/43753/diff/
> 
> 
> Testing
> ---
> 
> Manually Tested. Descriptions appears on the alerts page.
> 
> No additional unit tests required.
> 
> 
> Thanks,
> 
> Matt
> 
>

[jira] [Commented] (AMBARI-15104) Update description for HAWQ Sync standby alert

[Matt (JIRA)]

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

Matt commented on AMBARI-15104:
---

Both patches are identical.

> Update description for HAWQ Sync standby alert
> --
>
> Key: AMBARI-15104
> URL: https://issues.apache.org/jira/browse/AMBARI-15104
> Project: Ambari
>  Issue Type: Sub-task
>  Components: stacks
>Reporter: Matt
>Assignee: Matt
>Priority: Minor
> Fix For: trunk, 2.2.2
>
> Attachments: AMBARI-15104-branch-2.2-orig.patch, 
> AMBARI-15104-trunk-orig.patch
>
>
> Update the description for the alert so that the user knows what to do if the 
> alert is triggered from the description on the alert page



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

[jira] [Commented] (AMBARI-15103) Move HAWQ system password to General Accordion tab

[Matt (JIRA)]

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

Matt commented on AMBARI-15103:
---

Both patches are identical.

> Move HAWQ system password to General Accordion tab
> --
>
> Key: AMBARI-15103
> URL: https://issues.apache.org/jira/browse/AMBARI-15103
> Project: Ambari
>  Issue Type: Sub-task
>  Components: ambari-web
>Reporter: Matt
>Assignee: Matt
>Priority: Minor
> Fix For: trunk, 2.2.2
>
> Attachments: AMBARI-15103-branch-2.2-orig.patch, 
> AMBARI-15103-trunk-orig.patch
>
>
> The password is currently under Advanced hawq-env. Move it to General section.



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

Review Request 43753: Update description for HAWQ Sync standby alert

[Matt]

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

Review request for Ambari and jun aoki.


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


Repository: ambari


Description
---

Update the description for the alert so that the user knows what to do if the 
alert is triggered from the description on the alert page


Diffs
-

  ambari-server/src/main/resources/common-services/HAWQ/2.0.0/alerts.json 
3119a0c 

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


Testing
---

Manually Tested. Descriptions appears on the alerts page.

No additional unit tests required.


Thanks,

Matt

[jira] [Updated] (AMBARI-15104) Update description for HAWQ Sync standby alert

[Matt (JIRA)]

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

Matt updated AMBARI-15104:
--
Attachment: AMBARI-15104-trunk-orig.patch

> Update description for HAWQ Sync standby alert
> --
>
> Key: AMBARI-15104
> URL: https://issues.apache.org/jira/browse/AMBARI-15104
> Project: Ambari
>  Issue Type: Sub-task
>  Components: stacks
>Reporter: Matt
>Assignee: Matt
>Priority: Minor
> Fix For: trunk, 2.2.2
>
> Attachments: AMBARI-15104-branch-2.2-orig.patch, 
> AMBARI-15104-trunk-orig.patch
>
>
> Update the description for the alert so that the user knows what to do if the 
> alert is triggered from the description on the alert page



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

[jira] [Updated] (AMBARI-15104) Update description for HAWQ Sync standby alert

[Matt (JIRA)]

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

Matt updated AMBARI-15104:
--
Attachment: AMBARI-15104-branch-2.2-orig.patch

> Update description for HAWQ Sync standby alert
> --
>
> Key: AMBARI-15104
> URL: https://issues.apache.org/jira/browse/AMBARI-15104
> Project: Ambari
>  Issue Type: Sub-task
>  Components: stacks
>Reporter: Matt
>Assignee: Matt
>Priority: Minor
> Fix For: trunk, 2.2.2
>
> Attachments: AMBARI-15104-branch-2.2-orig.patch, 
> AMBARI-15104-trunk-orig.patch
>
>
> Update the description for the alert so that the user knows what to do if the 
> alert is triggered from the description on the alert page



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

[jira] [Updated] (AMBARI-15103) Move HAWQ system password to General Accordion tab

[Matt (JIRA)]

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

Matt updated AMBARI-15103:
--
Attachment: AMBARI-15103-trunk-orig.patch

> Move HAWQ system password to General Accordion tab
> --
>
> Key: AMBARI-15103
> URL: https://issues.apache.org/jira/browse/AMBARI-15103
> Project: Ambari
>  Issue Type: Sub-task
>  Components: ambari-web
>Reporter: Matt
>Assignee: Matt
>Priority: Minor
> Fix For: trunk, 2.2.2
>
> Attachments: AMBARI-15103-branch-2.2-orig.patch, 
> AMBARI-15103-trunk-orig.patch
>
>
> The password is currently under Advanced hawq-env. Move it to General section.



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

[jira] [Updated] (AMBARI-15103) Move HAWQ system password to General Accordion tab

[Matt (JIRA)]

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

Matt updated AMBARI-15103:
--
Attachment: AMBARI-15103-branch-2.2-orig.patch

> Move HAWQ system password to General Accordion tab
> --
>
> Key: AMBARI-15103
> URL: https://issues.apache.org/jira/browse/AMBARI-15103
> Project: Ambari
>  Issue Type: Sub-task
>  Components: ambari-web
>Reporter: Matt
>Assignee: Matt
>Priority: Minor
> Fix For: trunk, 2.2.2
>
> Attachments: AMBARI-15103-branch-2.2-orig.patch, 
> AMBARI-15103-trunk-orig.patch
>
>
> The password is currently under Advanced hawq-env. Move it to General section.



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

Review Request 43752: Move HAWQ system password to General Accordion tab

[Matt]

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

Review request for Ambari and jun aoki.


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


Repository: ambari


Description
---

The password is currently under Advanced hawq-env. Move it to General section.


Diffs
-

  
ambari-server/src/main/resources/common-services/HAWQ/2.0.0/configuration/hawq-env.xml
 e3a97fd 
  ambari-web/app/data/HDP2.3/site_properties.js c5fb525 

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


Testing
---

Manually Tested.

No additional unit tests required.

Unit tests passed on Ambari-web:
  10412 tests complete (10 seconds)
  121 tests pending

[INFO] 
[INFO] BUILD SUCCESS
[INFO] 
[INFO] Total time: 39.598 s
[INFO] Finished at: 2016-02-18T19:17:30-08:00
[INFO] Final Memory: 12M/311M
[INFO] 


Thanks,

Matt

[jira] [Updated] (AMBARI-15103) Move HAWQ system password to General Accordion tab

[Matt (JIRA)]

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

Matt updated AMBARI-15103:
--
Description: The password is currently n  (was: The pasw)

> Move HAWQ system password to General Accordion tab
> --
>
> Key: AMBARI-15103
> URL: https://issues.apache.org/jira/browse/AMBARI-15103
> Project: Ambari
>  Issue Type: Sub-task
>  Components: ambari-web
>Reporter: Matt
>Assignee: Matt
>Priority: Minor
> Fix For: trunk, 2.2.2
>
>
> The password is currently n



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

[jira] [Updated] (AMBARI-15103) Move HAWQ system password to General Accordion tab

[Matt (JIRA)]

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

Matt updated AMBARI-15103:
--
Description: The password is currently under Advanced hawq-env. Move it to 
General section.  (was: The password is currently n)

> Move HAWQ system password to General Accordion tab
> --
>
> Key: AMBARI-15103
> URL: https://issues.apache.org/jira/browse/AMBARI-15103
> Project: Ambari
>  Issue Type: Sub-task
>  Components: ambari-web
>Reporter: Matt
>Assignee: Matt
>Priority: Minor
> Fix For: trunk, 2.2.2
>
>
> The password is currently under Advanced hawq-env. Move it to General section.



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

[jira] [Updated] (AMBARI-15104) Update description for HAWQ Sync standby alert

[Matt (JIRA)]

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

Matt updated AMBARI-15104:
--
Description: Update the description for the alert so that the user knows 
what to do if the alert is triggered from the description on the alert page

> Update description for HAWQ Sync standby alert
> --
>
> Key: AMBARI-15104
> URL: https://issues.apache.org/jira/browse/AMBARI-15104
> Project: Ambari
>  Issue Type: Sub-task
>  Components: stacks
>Reporter: Matt
>Assignee: Matt
>Priority: Minor
> Fix For: trunk, 2.2.2
>
>
> Update the description for the alert so that the user knows what to do if the 
> alert is triggered from the description on the alert page



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

[jira] [Updated] (AMBARI-15103) Move HAWQ system password to General Accordion tab

[Matt (JIRA)]

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

Matt updated AMBARI-15103:
--
Description: The pasw

> Move HAWQ system password to General Accordion tab
> --
>
> Key: AMBARI-15103
> URL: https://issues.apache.org/jira/browse/AMBARI-15103
> Project: Ambari
>  Issue Type: Sub-task
>  Components: ambari-web
>Reporter: Matt
>Assignee: Matt
>Priority: Minor
> Fix For: trunk, 2.2.2
>
>
> The pasw



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

[jira] [Updated] (AMBARI-15104) Update description for HAWQ Sync standby alert

[Matt (JIRA)]

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

Matt updated AMBARI-15104:
--
Summary: Update description for HAWQ Sync standby alert  (was: Change 
description for HAWQ Sync standby alert)

> Update description for HAWQ Sync standby alert
> --
>
> Key: AMBARI-15104
> URL: https://issues.apache.org/jira/browse/AMBARI-15104
> Project: Ambari
>  Issue Type: Sub-task
>  Components: stacks
>Reporter: Matt
>Assignee: Matt
>Priority: Minor
> Fix For: trunk, 2.2.2
>
>




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

[jira] [Commented] (AMBARI-15083) Add Stack Advisor validations for hawq_global_rm_type property in HAWQ

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-15083:


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

This message is automatically generated.

> Add Stack Advisor validations for hawq_global_rm_type property in HAWQ
> --
>
> Key: AMBARI-15083
> URL: https://issues.apache.org/jira/browse/AMBARI-15083
> Project: Ambari
>  Issue Type: Improvement
>  Components: stacks
>Affects Versions: trunk, 2.2.0
>Reporter: bhuvnesh chaudhary
>Assignee: bhuvnesh chaudhary
>Priority: Minor
> Fix For: trunk, 2.2.0
>
> Attachments: AMBARI-15083-branch-2.2.patch, AMBARI-15083.patch
>
>
> Add Stack Advisor validations for hawq_global_rm_type property in HAWQ. The 
> below 2 cases must be covered:
> #1:
> If YARN service is not installed, and hawq_global_rm_type is set as yarn, a 
> validation error should be thrown
> #2:
> If YARN service is installed, and hawq_gloabl_rm_type is set as yarn, no 
> validation error should be thrown



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

[jira] [Commented] (AMBARI-15096) Edit WEB Alert should show Critical for Connection Timeout

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-15096:


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

This message is automatically generated.

> Edit WEB Alert should show Critical for Connection Timeout
> --
>
> Key: AMBARI-15096
> URL: https://issues.apache.org/jira/browse/AMBARI-15096
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.2.2
>Reporter: Zhe (Joe) Wang
>Assignee: Zhe (Joe) Wang
> Fix For: 2.2.2
>
> Attachments: AMBARI-15096_branch_2_2.0.patch, 
> AMBARI-15096_trunk.0.patch, AMBARI-15096_trunk.1.patch
>
>
> For WEB alerts, the Connection Timeout fields should show CRITICAL badge 
> since if the connection times out, it is a critical situation.



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

[jira] [Commented] (AMBARI-15105) Add alerts for HAWQ components status

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-15105:


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

This message is automatically generated.

> Add alerts for HAWQ components status
> -
>
> Key: AMBARI-15105
> URL: https://issues.apache.org/jira/browse/AMBARI-15105
> Project: Ambari
>  Issue Type: New Feature
>  Components: alerts
>Affects Versions: trunk, 2.2.0
>Reporter: bhuvnesh chaudhary
>Assignee: bhuvnesh chaudhary
> Fix For: trunk, 2.2.0
>
> Attachments: AMBARI-15105-1.patch, AMBARI-15105.patch
>
>
> Add alerts for HAWQ components based on PORT. The below components are 
> covered.
> - Master
> - Standby
> - Segment



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

[jira] [Updated] (AMBARI-15060) Ambari should show no. of HAWQ segments live on main dashboard

[Matt (JIRA)]

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

Matt updated AMBARI-15060:
--
Attachment: AMBARI-15060-branch-2.2-v2.patch

> Ambari should show no. of HAWQ segments live on main dashboard
> --
>
> Key: AMBARI-15060
> URL: https://issues.apache.org/jira/browse/AMBARI-15060
> Project: Ambari
>  Issue Type: Story
>  Components: ambari-web
>Reporter: Matt
>Assignee: Matt
>Priority: Minor
> Fix For: trunk, 2.2.2
>
> Attachments: AMBARI-15060-branch-2.2-orig.patch, 
> AMBARI-15060-branch-2.2-v1.patch, AMBARI-15060-branch-2.2-v2.patch, 
> AMBARI-15060-trunk-orig.patch, AMBARI-15060-trunk-v1.patch, 
> AMBARI-15060-trunk-v2.patch, green.png, orange.png, red.png
>
>
> The no. of HAWQ segments alive should be displayed as a widget on Ambari's 
> main dashboard.



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

Re: Review Request 43644: Ambari should show no. of HAWQ segments live on main dashboard

[Matt]

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

(Updated Feb. 18, 2016, 6:37 p.m.)


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


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


Repository: ambari


Description
---

The no. of HAWQ segments alive should be displayed as a widget on Ambari's main 
dashboard.


Diffs
-

  ambari-web/app/assets/test/tests.js 25c3f43 
  ambari-web/app/mappers/components_state_mapper.js 0f2b627 
  ambari-web/app/messages.js a7e4ff3 
  ambari-web/app/views.js 7e461f9 
  ambari-web/app/views/main/dashboard/widgets.js b99d881 
  ambari-web/app/views/main/dashboard/widgets/hawqsegment_live.js PRE-CREATION 
  ambari-web/test/views/main/dashboard/widgets/hawqsegment_live_test.js 
PRE-CREATION 

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


Testing (updated)
---

Manually Tested. 
Images attached to JIRA.

Added additional unit test.
  10416 tests complete (10 seconds)
  121 tests pending

[INFO] 
[INFO] BUILD SUCCESS
[INFO] 
[INFO] Total time: 37.827 s
[INFO] Finished at: 2016-02-18T17:51:42-08:00
[INFO] Final Memory: 12M/310M
[INFO] 


Thanks,

Matt

Re: Review Request 43644: Ambari should show no. of HAWQ segments live on main dashboard

[Matt]

> On Feb. 18, 2016, 5:16 p.m., jun aoki wrote:
> > ambari-web/app/models/service/hawq.js, line 1
> > 
> >
> > Is this required?

It wasn't required. Thanks for reviewing Jun!


- Matt


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


On Feb. 18, 2016, 6:37 p.m., Matt wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/43644/
> ---
> 
> (Updated Feb. 18, 2016, 6:37 p.m.)
> 
> 
> Review request for Ambari, Alexander Denissov, Alejandro Fernandez, bhuvnesh 
> chaudhary, Goutam Tadi, Jaimin Jetly, jun aoki, Lav Jain, Newton Alex, and 
> Oleksandr Diachenko.
> 
> 
> Bugs: AMBARI-15060
> https://issues.apache.org/jira/browse/AMBARI-15060
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> The no. of HAWQ segments alive should be displayed as a widget on Ambari's 
> main dashboard.
> 
> 
> Diffs
> -
> 
>   ambari-web/app/assets/test/tests.js 25c3f43 
>   ambari-web/app/mappers/components_state_mapper.js 0f2b627 
>   ambari-web/app/messages.js a7e4ff3 
>   ambari-web/app/views.js 7e461f9 
>   ambari-web/app/views/main/dashboard/widgets.js b99d881 
>   ambari-web/app/views/main/dashboard/widgets/hawqsegment_live.js 
> PRE-CREATION 
>   ambari-web/test/views/main/dashboard/widgets/hawqsegment_live_test.js 
> PRE-CREATION 
> 
> Diff: https://reviews.apache.org/r/43644/diff/
> 
> 
> Testing
> ---
> 
> Manually Tested. 
> Images attached to JIRA.
> 
> Added additional unit test.
>   10416 tests complete (10 seconds)
>   121 tests pending
> 
> [INFO] 
> 
> [INFO] BUILD SUCCESS
> [INFO] 
> 
> [INFO] Total time: 37.827 s
> [INFO] Finished at: 2016-02-18T17:51:42-08:00
> [INFO] Final Memory: 12M/310M
> [INFO] 
> 
> 
> 
> Thanks,
> 
> Matt
> 
>

[jira] [Updated] (AMBARI-15060) Ambari should show no. of HAWQ segments live on main dashboard

[Matt (JIRA)]

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

Matt updated AMBARI-15060:
--
Attachment: AMBARI-15060-trunk-v2.patch

> Ambari should show no. of HAWQ segments live on main dashboard
> --
>
> Key: AMBARI-15060
> URL: https://issues.apache.org/jira/browse/AMBARI-15060
> Project: Ambari
>  Issue Type: Story
>  Components: ambari-web
>Reporter: Matt
>Assignee: Matt
>Priority: Minor
> Fix For: trunk, 2.2.2
>
> Attachments: AMBARI-15060-branch-2.2-orig.patch, 
> AMBARI-15060-branch-2.2-v1.patch, AMBARI-15060-branch-2.2-v2.patch, 
> AMBARI-15060-trunk-orig.patch, AMBARI-15060-trunk-v1.patch, 
> AMBARI-15060-trunk-v2.patch, green.png, orange.png, red.png
>
>
> The no. of HAWQ segments alive should be displayed as a widget on Ambari's 
> main dashboard.



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

[jira] [Updated] (AMBARI-15105) Add alerts for HAWQ components status

[bhuvnesh chaudhary (JIRA)]

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

bhuvnesh chaudhary updated AMBARI-15105:

Attachment: AMBARI-15105-1.patch

> Add alerts for HAWQ components status
> -
>
> Key: AMBARI-15105
> URL: https://issues.apache.org/jira/browse/AMBARI-15105
> Project: Ambari
>  Issue Type: New Feature
>  Components: alerts
>Affects Versions: trunk, 2.2.0
>Reporter: bhuvnesh chaudhary
>Assignee: bhuvnesh chaudhary
> Fix For: trunk, 2.2.0
>
> Attachments: AMBARI-15105-1.patch, AMBARI-15105.patch
>
>
> Add alerts for HAWQ components based on PORT. The below components are 
> covered.
> - Master
> - Standby
> - Segment



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

Re: Review Request 43644: Ambari should show no. of HAWQ segments live on main dashboard

[Matt]

> On Feb. 18, 2016, 5:16 p.m., jun aoki wrote:
> > ambari-web/app/views/main/dashboard/widgets/hawqsegment_live.js, line 51
> > 
> >
> > This may not be used as it is about started vs total?

It is being used for stopped. You'll see it when you hover over the widget.

Installed refers to that the component is in actual stopped state. It is better 
than computing the difference between total and started. A possible state is 
'starting' which is neither 'started' not 'installed' (which corresponds to 
stopped).


- Matt


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


On Feb. 18, 2016, 5:52 p.m., Matt wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/43644/
> ---
> 
> (Updated Feb. 18, 2016, 5:52 p.m.)
> 
> 
> Review request for Ambari, Alexander Denissov, Alejandro Fernandez, bhuvnesh 
> chaudhary, Goutam Tadi, Jaimin Jetly, jun aoki, Lav Jain, Newton Alex, and 
> Oleksandr Diachenko.
> 
> 
> Bugs: AMBARI-15060
> https://issues.apache.org/jira/browse/AMBARI-15060
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> The no. of HAWQ segments alive should be displayed as a widget on Ambari's 
> main dashboard.
> 
> 
> Diffs
> -
> 
>   ambari-web/app/assets/test/tests.js 25c3f43 
>   ambari-web/app/mappers/components_state_mapper.js 0f2b627 
>   ambari-web/app/messages.js a7e4ff3 
>   ambari-web/app/views.js 7e461f9 
>   ambari-web/app/views/main/dashboard/widgets.js b99d881 
>   ambari-web/app/views/main/dashboard/widgets/hawqsegment_live.js 
> PRE-CREATION 
>   ambari-web/test/views/main/dashboard/widgets/hawqsegment_live_test.js 
> PRE-CREATION 
> 
> Diff: https://reviews.apache.org/r/43644/diff/
> 
> 
> Testing
> ---
> 
> Manually Test: results pending. 
> Images attached to JIRA.
> 
> Added additional unit test.
>   10416 tests complete (10 seconds)
>   121 tests pending
> 
> [INFO] 
> 
> [INFO] BUILD SUCCESS
> [INFO] 
> 
> [INFO] Total time: 37.827 s
> [INFO] Finished at: 2016-02-18T17:51:42-08:00
> [INFO] Final Memory: 12M/310M
> [INFO] 
> 
> 
> 
> Thanks,
> 
> Matt
> 
>

Re: Review Request 43748: Add alerts for HAWQ components status

[Jonathan Hurley]

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


Ship it!




Ship It!

- Jonathan Hurley


On Feb. 18, 2016, 7:59 p.m., bhuvnesh chaudhary wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/43748/
> ---
> 
> (Updated Feb. 18, 2016, 7:59 p.m.)
> 
> 
> Review request for Ambari, Alejandro Fernandez, Jaimin Jetly, jun aoki, 
> Jonathan Hurley, Jayush Luniya, Oleksandr Diachenko, Richard Zang, Sumit 
> Mohanty, and Yusaku Sako.
> 
> 
> Bugs: AMBARI-15105
> https://issues.apache.org/jira/browse/AMBARI-15105
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> This patch introduces alerts for HAWQ components based on PORT. The below 
> components are covered.
> - Master
> - Standby
> - Segment
> 
> 
> Diffs
> -
> 
>   ambari-server/src/main/resources/common-services/HAWQ/2.0.0/alerts.json 
> 3119a0c 
> 
> Diff: https://reviews.apache.org/r/43748/diff/
> 
> 
> Testing
> ---
> 
> yes, manual.
> 
> 
> Thanks,
> 
> bhuvnesh chaudhary
> 
>

Re: Review Request 43748: Add alerts for HAWQ components status

[Jonathan Hurley]

> On Feb. 18, 2016, 8:56 p.m., Matt wrote:
> > ambari-server/src/main/resources/common-services/HAWQ/2.0.0/alerts.json, 
> > line 49
> > 
> >
> > Should this be HOST? I believe it is more of a service level alert.

HAWQSEGMENT is a slave with cardinality of 1+ ... makes sense to keep it as 
HOST.


- Jonathan


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


On Feb. 18, 2016, 7:59 p.m., bhuvnesh chaudhary wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/43748/
> ---
> 
> (Updated Feb. 18, 2016, 7:59 p.m.)
> 
> 
> Review request for Ambari, Alejandro Fernandez, Jaimin Jetly, jun aoki, 
> Jonathan Hurley, Jayush Luniya, Oleksandr Diachenko, Richard Zang, Sumit 
> Mohanty, and Yusaku Sako.
> 
> 
> Bugs: AMBARI-15105
> https://issues.apache.org/jira/browse/AMBARI-15105
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> This patch introduces alerts for HAWQ components based on PORT. The below 
> components are covered.
> - Master
> - Standby
> - Segment
> 
> 
> Diffs
> -
> 
>   ambari-server/src/main/resources/common-services/HAWQ/2.0.0/alerts.json 
> 3119a0c 
> 
> Diff: https://reviews.apache.org/r/43748/diff/
> 
> 
> Testing
> ---
> 
> yes, manual.
> 
> 
> Thanks,
> 
> bhuvnesh chaudhary
> 
>

Re: Review Request 43748: Add alerts for HAWQ components status

[Jonathan Hurley]

> On Feb. 18, 2016, 9:05 p.m., jun aoki wrote:
> > ambari-server/src/main/resources/common-services/HAWQ/2.0.0/alerts.json, 
> > line 24
> > 
> >
> > Is type OK for checking a process is down?
> > I don't know if a type called "PROCESS", but otherwise maybe "SCRIPT" 
> > to issue same ps with process names?
> 
> bhuvnesh chaudhary wrote:
> Good point. I see a possibility of some other process occupying the port 
> and might be listening on it, even though Hawq process may be down. In that 
> case, an alert will not be sent, but such occurence may be limited.
> 
> Also, as a standard/recommended practice we should have hawq being run on 
> reserved port, since if we let HAWQ run on the current unreserved port range, 
> HAWQ component startup can also fail if some process is already occupying 
> that port. That change should also resolve the issue mentioned above.
> 
> Ensuring check for process name is something which we can possibily have 
> an enhancement on alerts and add a field regex_pattern in alerts.json to 
> search for the process on the port to avoid such issue, instead of creating a 
> separate script for process check since type PORT is common across all the 
> services and used similarly. The same issue can manifests for all the 
> services.
> 
> If you are okay, i will create a separate JIRA on alerts for enhancement 
> and drop this issue here ?
> and for ensuring that HAWQ is run on a reserved port range will work 
> internally ?

Typically, yes, using a PORT to check and see if a process is down is good 
enough. Typically, if there's a WEB endpoint we'll use that. In cases where we 
also want to test functionality of the component, a SCRIPT alert will be 
written.


- Jonathan


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


On Feb. 18, 2016, 7:59 p.m., bhuvnesh chaudhary wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/43748/
> ---
> 
> (Updated Feb. 18, 2016, 7:59 p.m.)
> 
> 
> Review request for Ambari, Alejandro Fernandez, Jaimin Jetly, jun aoki, 
> Jonathan Hurley, Jayush Luniya, Oleksandr Diachenko, Richard Zang, Sumit 
> Mohanty, and Yusaku Sako.
> 
> 
> Bugs: AMBARI-15105
> https://issues.apache.org/jira/browse/AMBARI-15105
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> This patch introduces alerts for HAWQ components based on PORT. The below 
> components are covered.
> - Master
> - Standby
> - Segment
> 
> 
> Diffs
> -
> 
>   ambari-server/src/main/resources/common-services/HAWQ/2.0.0/alerts.json 
> 3119a0c 
> 
> Diff: https://reviews.apache.org/r/43748/diff/
> 
> 
> Testing
> ---
> 
> yes, manual.
> 
> 
> Thanks,
> 
> bhuvnesh chaudhary
> 
>

Re: Review Request 43748: Add alerts for HAWQ components status

[bhuvnesh chaudhary]

> On Feb. 19, 2016, 2:05 a.m., jun aoki wrote:
> > ambari-server/src/main/resources/common-services/HAWQ/2.0.0/alerts.json, 
> > line 24
> > 
> >
> > Is type OK for checking a process is down?
> > I don't know if a type called "PROCESS", but otherwise maybe "SCRIPT" 
> > to issue same ps with process names?

Good point. I see a possibility of some other process occupying the port and 
might be listening on it, even though Hawq process may be down. In that case, 
an alert will not be sent, but such occurence may be limited.

Also, as a standard/recommended practice we should have hawq being run on 
reserved port, since if we let HAWQ run on the current unreserved port range, 
HAWQ component startup can also fail if some process is already occupying that 
port. That change should also resolve the issue mentioned above.

Ensuring check for process name is something which we can possibily have an 
enhancement on alerts and add a field regex_pattern in alerts.json to search 
for the process on the port to avoid such issue, instead of creating a separate 
script for process check since type PORT is common across all the services and 
used similarly. The same issue can manifests for all the services.

If you are okay, i will create a separate JIRA on alerts for enhancement and 
drop this issue here ?
and for ensuring that HAWQ is run on a reserved port range will work internally 
?


- bhuvnesh


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


On Feb. 19, 2016, 12:59 a.m., bhuvnesh chaudhary wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/43748/
> ---
> 
> (Updated Feb. 19, 2016, 12:59 a.m.)
> 
> 
> Review request for Ambari, Alejandro Fernandez, Jaimin Jetly, jun aoki, 
> Jonathan Hurley, Jayush Luniya, Oleksandr Diachenko, Richard Zang, Sumit 
> Mohanty, and Yusaku Sako.
> 
> 
> Bugs: AMBARI-15105
> https://issues.apache.org/jira/browse/AMBARI-15105
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> This patch introduces alerts for HAWQ components based on PORT. The below 
> components are covered.
> - Master
> - Standby
> - Segment
> 
> 
> Diffs
> -
> 
>   ambari-server/src/main/resources/common-services/HAWQ/2.0.0/alerts.json 
> 3119a0c 
> 
> Diff: https://reviews.apache.org/r/43748/diff/
> 
> 
> Testing
> ---
> 
> yes, manual.
> 
> 
> Thanks,
> 
> bhuvnesh chaudhary
> 
>

Re: Review Request 43743: AMBARI-13424. Allow disabling RU/EU PreChecks

[Jonathan Hurley]

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


Fix it, then Ship it!





ambari-server/conf/unix/ambari.properties (lines 101 - 102)


I don't think we need to ship with this property exposed. In fact, in 99.9% 
of cases, we don't want anyone knowing about it.


- Jonathan Hurley


On Feb. 18, 2016, 6:10 p.m., Alejandro Fernandez wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/43743/
> ---
> 
> (Updated Feb. 18, 2016, 6:10 p.m.)
> 
> 
> Review request for Ambari, Dmitro Lisnichenko, Jonathan Hurley, Nate Cole, 
> Richard Zang, and Xi Wang.
> 
> 
> Bugs: AMBARI-13424
> https://issues.apache.org/jira/browse/AMBARI-13424
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> In some environments, the customer still wants to proceed with RU & EU even 
> if PreChecks fail. E.g.,
> NameNode HA doesn't actually exist if they have their own distribution of HDFS
> Hosts be down at the time the upgrade is starting, but will come online 
> during the upgrade.
> 
> Today, they are unable to start RU/EU if any of the PreChecks fail.
> Introduce a config in ambari.properties file called 
> "stack.upgrade.bypass.prechecks" whose default value is "false"
> 
> 
> Diffs
> -
> 
>   ambari-server/conf/unix/ambari.properties 81ef446 
>   
> ambari-server/src/main/java/org/apache/ambari/server/checks/AbstractCheckDescriptor.java
>  8a81aa9 
>   
> ambari-server/src/main/java/org/apache/ambari/server/configuration/Configuration.java
>  cfc2f51 
>   ambari-server/src/main/java/org/apache/ambari/server/state/CheckHelper.java 
> 5a8d4fd 
>   
> ambari-server/src/main/java/org/apache/ambari/server/state/stack/PrereqCheckStatus.java
>  f8009e3 
>   ambari-web/app/controllers/main/admin/stack_and_upgrade_controller.js 
> c226059 
>   ambari-web/app/messages.js 9d24b4f 
>   ambari-web/app/styles/stack_versions.less ab27a84 
>   ambari-web/app/templates/common/modal_popups/cluster_check_dialog.hbs 
> 8fd2746 
>   ambari-web/app/templates/main/admin/stack_upgrade/upgrade_options.hbs 
> 268ea1d 
>   ambari-web/app/views/common/modal_popups/cluster_check_popup.js 54f20ba 
> 
> Diff: https://reviews.apache.org/r/43743/diff/
> 
> 
> Testing
> ---
> 
> Verified on PreChecks for RU/EU when put hosts in maintenance mode and tested 
> with/without the config "stack.upgrade.bypass.prechecks"
> See screenshots in Apache Jira.
> 
> Waiting for unit test results.
> 
> 
> Thanks,
> 
> Alejandro Fernandez
> 
>

Re: Review Request 43748: Add alerts for HAWQ components status

[bhuvnesh chaudhary]

> On Feb. 19, 2016, 1:55 a.m., Matt wrote:
> > ambari-server/src/main/resources/common-services/HAWQ/2.0.0/alerts.json, 
> > line 20
> > 
> >
> > Capitalize M for master.
> > The description would show up on the UI

Will do.


- bhuvnesh


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


On Feb. 19, 2016, 12:59 a.m., bhuvnesh chaudhary wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/43748/
> ---
> 
> (Updated Feb. 19, 2016, 12:59 a.m.)
> 
> 
> Review request for Ambari, Alejandro Fernandez, Jaimin Jetly, jun aoki, 
> Jonathan Hurley, Jayush Luniya, Oleksandr Diachenko, Richard Zang, Sumit 
> Mohanty, and Yusaku Sako.
> 
> 
> Bugs: AMBARI-15105
> https://issues.apache.org/jira/browse/AMBARI-15105
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> This patch introduces alerts for HAWQ components based on PORT. The below 
> components are covered.
> - Master
> - Standby
> - Segment
> 
> 
> Diffs
> -
> 
>   ambari-server/src/main/resources/common-services/HAWQ/2.0.0/alerts.json 
> 3119a0c 
> 
> Diff: https://reviews.apache.org/r/43748/diff/
> 
> 
> Testing
> ---
> 
> yes, manual.
> 
> 
> Thanks,
> 
> bhuvnesh chaudhary
> 
>

Re: Review Request 43748: Add alerts for HAWQ components status

[bhuvnesh chaudhary]

> On Feb. 19, 2016, 1:54 a.m., Matt wrote:
> > ambari-server/src/main/resources/common-services/HAWQ/2.0.0/alerts.json, 
> > line 26
> > 
> >
> > Was the alert tested with another port?

yes. Tested it on single node with port 5433.


- bhuvnesh


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


On Feb. 19, 2016, 12:59 a.m., bhuvnesh chaudhary wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/43748/
> ---
> 
> (Updated Feb. 19, 2016, 12:59 a.m.)
> 
> 
> Review request for Ambari, Alejandro Fernandez, Jaimin Jetly, jun aoki, 
> Jonathan Hurley, Jayush Luniya, Oleksandr Diachenko, Richard Zang, Sumit 
> Mohanty, and Yusaku Sako.
> 
> 
> Bugs: AMBARI-15105
> https://issues.apache.org/jira/browse/AMBARI-15105
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> This patch introduces alerts for HAWQ components based on PORT. The below 
> components are covered.
> - Master
> - Standby
> - Segment
> 
> 
> Diffs
> -
> 
>   ambari-server/src/main/resources/common-services/HAWQ/2.0.0/alerts.json 
> 3119a0c 
> 
> Diff: https://reviews.apache.org/r/43748/diff/
> 
> 
> Testing
> ---
> 
> yes, manual.
> 
> 
> Thanks,
> 
> bhuvnesh chaudhary
> 
>

Re: Review Request 43748: Add alerts for HAWQ components status

[jun aoki]

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




ambari-server/src/main/resources/common-services/HAWQ/2.0.0/alerts.json (line 
24)


Is type OK for checking a process is down?
I don't know if a type called "PROCESS", but otherwise maybe "SCRIPT" to 
issue same ps with process names?


- jun aoki


On Feb. 19, 2016, 12:59 a.m., bhuvnesh chaudhary wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/43748/
> ---
> 
> (Updated Feb. 19, 2016, 12:59 a.m.)
> 
> 
> Review request for Ambari, Alejandro Fernandez, Jaimin Jetly, jun aoki, 
> Jonathan Hurley, Jayush Luniya, Oleksandr Diachenko, Richard Zang, Sumit 
> Mohanty, and Yusaku Sako.
> 
> 
> Bugs: AMBARI-15105
> https://issues.apache.org/jira/browse/AMBARI-15105
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> This patch introduces alerts for HAWQ components based on PORT. The below 
> components are covered.
> - Master
> - Standby
> - Segment
> 
> 
> Diffs
> -
> 
>   ambari-server/src/main/resources/common-services/HAWQ/2.0.0/alerts.json 
> 3119a0c 
> 
> Diff: https://reviews.apache.org/r/43748/diff/
> 
> 
> Testing
> ---
> 
> yes, manual.
> 
> 
> Thanks,
> 
> bhuvnesh chaudhary
> 
>

Re: Review Request 43748: Add alerts for HAWQ components status

[Goutam Tadi]

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


Ship it!




Ship It!

- Goutam Tadi


On Feb. 19, 2016, 12:59 a.m., bhuvnesh chaudhary wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/43748/
> ---
> 
> (Updated Feb. 19, 2016, 12:59 a.m.)
> 
> 
> Review request for Ambari, Alejandro Fernandez, Jaimin Jetly, jun aoki, 
> Jonathan Hurley, Jayush Luniya, Oleksandr Diachenko, Richard Zang, Sumit 
> Mohanty, and Yusaku Sako.
> 
> 
> Bugs: AMBARI-15105
> https://issues.apache.org/jira/browse/AMBARI-15105
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> This patch introduces alerts for HAWQ components based on PORT. The below 
> components are covered.
> - Master
> - Standby
> - Segment
> 
> 
> Diffs
> -
> 
>   ambari-server/src/main/resources/common-services/HAWQ/2.0.0/alerts.json 
> 3119a0c 
> 
> Diff: https://reviews.apache.org/r/43748/diff/
> 
> 
> Testing
> ---
> 
> yes, manual.
> 
> 
> Thanks,
> 
> bhuvnesh chaudhary
> 
>

Re: Review Request 43748: Add alerts for HAWQ components status

[Matt]

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




ambari-server/src/main/resources/common-services/HAWQ/2.0.0/alerts.json (line 
49)


Should this be HOST? I believe it is more of a service level alert.


- Matt


On Feb. 18, 2016, 4:59 p.m., bhuvnesh chaudhary wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/43748/
> ---
> 
> (Updated Feb. 18, 2016, 4:59 p.m.)
> 
> 
> Review request for Ambari, Alejandro Fernandez, Jaimin Jetly, jun aoki, 
> Jonathan Hurley, Jayush Luniya, Oleksandr Diachenko, Richard Zang, Sumit 
> Mohanty, and Yusaku Sako.
> 
> 
> Bugs: AMBARI-15105
> https://issues.apache.org/jira/browse/AMBARI-15105
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> This patch introduces alerts for HAWQ components based on PORT. The below 
> components are covered.
> - Master
> - Standby
> - Segment
> 
> 
> Diffs
> -
> 
>   ambari-server/src/main/resources/common-services/HAWQ/2.0.0/alerts.json 
> 3119a0c 
> 
> Diff: https://reviews.apache.org/r/43748/diff/
> 
> 
> Testing
> ---
> 
> yes, manual.
> 
> 
> Thanks,
> 
> bhuvnesh chaudhary
> 
>

Re: Review Request 43748: Add alerts for HAWQ components status

[Matt]

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




ambari-server/src/main/resources/common-services/HAWQ/2.0.0/alerts.json (line 
20)


Capitalize M for master.
The description would show up on the UI


- Matt


On Feb. 18, 2016, 4:59 p.m., bhuvnesh chaudhary wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/43748/
> ---
> 
> (Updated Feb. 18, 2016, 4:59 p.m.)
> 
> 
> Review request for Ambari, Alejandro Fernandez, Jaimin Jetly, jun aoki, 
> Jonathan Hurley, Jayush Luniya, Oleksandr Diachenko, Richard Zang, Sumit 
> Mohanty, and Yusaku Sako.
> 
> 
> Bugs: AMBARI-15105
> https://issues.apache.org/jira/browse/AMBARI-15105
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> This patch introduces alerts for HAWQ components based on PORT. The below 
> components are covered.
> - Master
> - Standby
> - Segment
> 
> 
> Diffs
> -
> 
>   ambari-server/src/main/resources/common-services/HAWQ/2.0.0/alerts.json 
> 3119a0c 
> 
> Diff: https://reviews.apache.org/r/43748/diff/
> 
> 
> Testing
> ---
> 
> yes, manual.
> 
> 
> Thanks,
> 
> bhuvnesh chaudhary
> 
>

Re: Review Request 43748: Add alerts for HAWQ components status

[Matt]

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




ambari-server/src/main/resources/common-services/HAWQ/2.0.0/alerts.json (line 
26)


Was the alert tested with another port?


- Matt


On Feb. 18, 2016, 4:59 p.m., bhuvnesh chaudhary wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/43748/
> ---
> 
> (Updated Feb. 18, 2016, 4:59 p.m.)
> 
> 
> Review request for Ambari, Alejandro Fernandez, Jaimin Jetly, jun aoki, 
> Jonathan Hurley, Jayush Luniya, Oleksandr Diachenko, Richard Zang, Sumit 
> Mohanty, and Yusaku Sako.
> 
> 
> Bugs: AMBARI-15105
> https://issues.apache.org/jira/browse/AMBARI-15105
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> This patch introduces alerts for HAWQ components based on PORT. The below 
> components are covered.
> - Master
> - Standby
> - Segment
> 
> 
> Diffs
> -
> 
>   ambari-server/src/main/resources/common-services/HAWQ/2.0.0/alerts.json 
> 3119a0c 
> 
> Diff: https://reviews.apache.org/r/43748/diff/
> 
> 
> Testing
> ---
> 
> yes, manual.
> 
> 
> Thanks,
> 
> bhuvnesh chaudhary
> 
>

Re: Review Request 43731: Add Stack Advisor validations for hawq_global_rm_type property in HAWQ

[jun aoki]

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


Ship it!




Ship It!

- jun aoki


On Feb. 18, 2016, 7:23 p.m., bhuvnesh chaudhary wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/43731/
> ---
> 
> (Updated Feb. 18, 2016, 7:23 p.m.)
> 
> 
> Review request for Ambari, Alejandro Fernandez, Jaimin Jetly, jun aoki, 
> Jayush Luniya, Oleksandr Diachenko, Richard Zang, Sumit Mohanty, and Yusaku 
> Sako.
> 
> 
> Bugs: AMBARI-15083
> https://issues.apache.org/jira/browse/AMBARI-15083
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Add Stack Advisor validations for hawq_global_rm_type property in HAWQ. The 
> below 2 cases must be covered:
> # 1: If YARN service is not installed, and hawq_global_rm_type is set as 
> yarn, a validation error should be thrown
> # 2: If YARN service is installed, and hawq_gloabl_rm_type is set as yarn, no 
> validation error should be thrown
> 
> 
> Diffs
> -
> 
>   ambari-server/src/main/resources/stacks/HDP/2.3/services/stack_advisor.py 
> b354378 
>   ambari-server/src/test/python/stacks/2.3/common/test_stack_advisor.py 
> 545a2b5 
> 
> Diff: https://reviews.apache.org/r/43731/diff/
> 
> 
> Testing
> ---
> 
> yes, manual and stack advisor test run.
> 
> 
> Thanks,
> 
> bhuvnesh chaudhary
> 
>

Re: Review Request 43644: Ambari should show no. of HAWQ segments live on main dashboard

[Matt]

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

(Updated Feb. 18, 2016, 5:52 p.m.)


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


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


Repository: ambari


Description
---

The no. of HAWQ segments alive should be displayed as a widget on Ambari's main 
dashboard.


Diffs (updated)
-

  ambari-web/app/assets/test/tests.js 25c3f43 
  ambari-web/app/mappers/components_state_mapper.js 0f2b627 
  ambari-web/app/messages.js a7e4ff3 
  ambari-web/app/views.js 7e461f9 
  ambari-web/app/views/main/dashboard/widgets.js b99d881 
  ambari-web/app/views/main/dashboard/widgets/hawqsegment_live.js PRE-CREATION 
  ambari-web/test/views/main/dashboard/widgets/hawqsegment_live_test.js 
PRE-CREATION 

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


Testing (updated)
---

Manually Test: results pending. 
Images attached to JIRA.

Added additional unit test.
  10416 tests complete (10 seconds)
  121 tests pending

[INFO] 
[INFO] BUILD SUCCESS
[INFO] 
[INFO] Total time: 37.827 s
[INFO] Finished at: 2016-02-18T17:51:42-08:00
[INFO] Final Memory: 12M/310M
[INFO] 


Thanks,

Matt

[jira] [Commented] (AMBARI-15101) Remove the dependency between ZK start and Ranger user sync start

[Hudson (JIRA)]

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

Hudson commented on AMBARI-15101:
-

SUCCESS: Integrated in Ambari-branch-2.2 #359 (See 
[https://builds.apache.org/job/Ambari-branch-2.2/359/])
AMBARI-15101. Remove the dependency between ZK start and Ranger user (smohanty: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=86d9c1187a7918c3ae25759642655755b7cfdffe])
* ambari-server/src/main/resources/stacks/HDP/2.2/role_command_order.json


> Remove the dependency between ZK start and Ranger user sync start
> -
>
> Key: AMBARI-15101
> URL: https://issues.apache.org/jira/browse/AMBARI-15101
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.2.2
>Reporter: Sumit Mohanty
>Assignee: Sumit Mohanty
> Fix For: 2.2.2
>
> Attachments: AMBARI-15101.patch
>
>
> ZK start should not depend on Ranger user sync start. We should remove the 
> dependency.



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

[jira] [Commented] (AMBARI-15099) Ambari missing metrics in UI with Vip settings enabled.

[Hudson (JIRA)]

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

Hudson commented on AMBARI-15099:
-

SUCCESS: Integrated in Ambari-branch-2.2 #359 (See 
[https://builds.apache.org/job/Ambari-branch-2.2/359/])
AMBARI-15099 : Ambari missing metrics in UI with Vip settings enabled 
(avijayan: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=1210d0bd5077fa8358cd9af6107df30f2c074aae])
* 
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/AbstractProviderModule.java


> Ambari missing metrics in UI with Vip settings enabled.
> ---
>
> Key: AMBARI-15099
> URL: https://issues.apache.org/jira/browse/AMBARI-15099
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.2.1
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15099.patch
>
>
> When using a vip settings for a cluster with 2 Collectors (1 active at a 
> time), no metrics are seen unless Ambari Server is restarted.



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

[jira] [Commented] (AMBARI-15090) [Ambari tarballs] ambari-server python scripts should support running from custom root

[Hudson (JIRA)]

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

Hudson commented on AMBARI-15090:
-

ABORTED: Integrated in Ambari-trunk-Commit #4354 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/4354/])
AMBARI-15090. [Ambari tarballs] ambari-server python scripts should (aonishuk: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=6d121dd6e361b36a144134cd6f89c72e7cc17f27])
* ambari-server/src/test/python/TestOSCheck.py


> [Ambari tarballs] ambari-server python scripts should support running from 
> custom root
> --
>
> Key: AMBARI-15090
> URL: https://issues.apache.org/jira/browse/AMBARI-15090
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.4.0
>
> Attachments: AMBARI-15090.patch
>
>




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

[jira] [Commented] (AMBARI-15077) Auto-start services: Backend API and DB changes for component auto start

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-15077:


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

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

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

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

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

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

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

This message is automatically generated.

> Auto-start services: Backend API and DB changes for component auto start
> 
>
> Key: AMBARI-15077
> URL: https://issues.apache.org/jira/browse/AMBARI-15077
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
>  Labels: ambari-server
> Fix For: 2.4.0
>
> Attachments: rb43671.patch
>
>
> Add a new field *recovery_enabled* in *servicecomponentdesiredstate* and 
> provide API support for PUT and GET.
> *Type: PUT*
> Request 1: 
> api/v1/clusters//components?ServiceComponentInfo/component_name.in()
> Request Params: application/json
> {
>   ServiceComponentInfo: {
>   “recovery_enabled”: “true”
>   }
> }
> Request 2:
> api/v1/clusters//components?ServiceComponentInfo/component_name.in()
> Request Params: application/json
> {
>   ServiceComponentInfo: {
>   recovery_enabled: “false”
>   }
> }
> Request 3:
> api/v1/clusters/testcluster/components/ 
> Request Params: application/json
> '{"ServiceComponentInfo" : {"recovery_enabled":"false"}}'
> *Type:GET*
> Request: 
> api/v1/clusters//components?fields=ServiceComponentInfo/component_name,ServiceComponentInfo/service_name,ServiceComponentInfo/category,ServiceComponentInfo/recovery_enabled



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

[jira] [Updated] (AMBARI-14472) Parameterize distro-specific stack information for OOZIE

[Juanjo Marron (JIRA)]

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

Juanjo Marron updated AMBARI-14472:
---
Attachment: AMBARI-14472.patch

Oozie has been parameterized according to the prototype:
/usr/hdp paths, specific stack versions, hdp variables (hdp_stack_version ), 
version-based conditions, HDP references in get_stack_component method...
The patch has been built against AMBARI-13364 branch, so it is cumulative with 
previous patches on this JIRA
Tested OOZIE fresh installation successfully

> Parameterize distro-specific stack information for OOZIE
> 
>
> Key: AMBARI-14472
> URL: https://issues.apache.org/jira/browse/AMBARI-14472
> Project: Ambari
>  Issue Type: Technical task
>  Components: ambari-server
>Affects Versions: 2.2.0, 2.2.1
>Reporter: Juanjo Marron
>Assignee: Juanjo Marron
> Fix For: 2.4.0
>
> Attachments: AMBARI-14472.patch
>
>
> Apply the prototype detailed on AMBARI-13364 to OOZIE service.
> Tokens such as: current version, upgrade version, stack name, install 
> path..., will be parameterized and distro-agnostic at service definition 
> level.



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

[jira] [Commented] (AMBARI-15067) Add custom commands for HAWQ to run check and clear cache

[jun aoki (JIRA)]

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

jun aoki commented on AMBARI-15067:
---

Committed to branch-2.2
1e93caf4f7ba92f0190433303b7920eaf54c57eb
Committed to trunk
0941997b0f68f1044242354c9f3f0f4b3a476c7d


> Add custom commands for HAWQ to run check and clear cache
> -
>
> Key: AMBARI-15067
> URL: https://issues.apache.org/jira/browse/AMBARI-15067
> Project: Ambari
>  Issue Type: Story
>  Components: ambari-web, stacks
>Reporter: Matt
>Assignee: Matt
>Priority: Minor
> Fix For: trunk, 2.2.2
>
> Attachments: AMBARI-15067-branch-2.2-orig.patch, 
> AMBARI-15067-trunk-orig.patch
>
>
> A HAWQ user should be able to run hawq check and clear HDFS Metadata cache 
> from the Ambari UI.



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

Re: Review Request 43733: Remove targeted orchestration for patches

[Jonathan Hurley]

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


Ship it!




Ship It!

- Jonathan Hurley


On Feb. 18, 2016, 5:09 p.m., Nate Cole wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/43733/
> ---
> 
> (Updated Feb. 18, 2016, 5:09 p.m.)
> 
> 
> Review request for Ambari, Dmitro Lisnichenko and Jonathan Hurley.
> 
> 
> Bugs: AMBARI-15097
> https://issues.apache.org/jira/browse/AMBARI-15097
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Remove targeted orchestration for patches.  This is to make sure that when a 
> patch-type repository is added that the full orchestration occurrs.
> 
> Also added a fix whereby if a Version Definition file defines no available 
> services, that it supplies versions for all the manifest services instead.  
> This way the UI doesn't have to decide to do work on an empty array.
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/java/org/apache/ambari/annotations/ExperimentalFeature.java
>  f29ed40 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ClusterStackVersionResourceProvider.java
>  ce5606e 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/internal/UpgradeResourceProvider.java
>  40565c5 
>   
> ambari-server/src/main/java/org/apache/ambari/server/state/UpgradeContext.java
>  49b2b45 
>   
> ambari-server/src/main/java/org/apache/ambari/server/state/repository/VersionDefinitionXml.java
>  a610bd0 
>   ambari-server/src/main/resources/version_definition.xsd 42035de 
>   
> ambari-server/src/test/java/org/apache/ambari/server/controller/internal/ClusterStackVersionResourceProviderTest.java
>  c6d0c57 
>   
> ambari-server/src/test/java/org/apache/ambari/server/state/repository/VersionDefinitionTest.java
>  4ba5967 
>   ambari-server/src/test/resources/version_definition_test_all_services.xml 
> PRE-CREATION 
> 
> Diff: https://reviews.apache.org/r/43733/diff/
> 
> 
> Testing
> ---
> 
> Manual.  Automated:
> 
> Tests run: 3840, Failures: 0, Errors: 0, Skipped: 34
> 
> [INFO] 
> 
> [INFO] BUILD SUCCESS
> [INFO] 
> 
> [INFO] Total time: 33:05.125s
> [INFO] Finished at: Thu Feb 18 16:27:14 EST 2016
> [INFO] Final Memory: 32M/658M
> [INFO] 
> 
> 
> 
> Thanks,
> 
> Nate Cole
> 
>

Re: Review Request 43703: Add custom commands for HAWQ to run check and clear cache

[jun aoki]

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


Ship it!




Ship It!

- jun aoki


On Feb. 18, 2016, 10:17 a.m., Matt wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/43703/
> ---
> 
> (Updated Feb. 18, 2016, 10:17 a.m.)
> 
> 
> Review request for Ambari, Alexander Denissov, Alejandro Fernandez, bhuvnesh 
> chaudhary, Goutam Tadi, jun aoki, Lav Jain, and Newton Alex.
> 
> 
> Bugs: AMBARI-15067
> https://issues.apache.org/jira/browse/AMBARI-15067
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> A HAWQ user should be able to run hawq check and clear HDFS Metadata cache 
> from the Ambari UI.
> 
> 
> Diffs
> -
> 
>   ambari-server/src/main/resources/common-services/HAWQ/2.0.0/metainfo.xml 
> 942b250 
>   
> ambari-server/src/main/resources/common-services/HAWQ/2.0.0/package/scripts/hawq_constants.py
>  9fdbde5 
>   
> ambari-server/src/main/resources/common-services/HAWQ/2.0.0/package/scripts/hawqmaster.py
>  d2f9ad0 
>   
> ambari-server/src/main/resources/common-services/HAWQ/2.0.0/package/scripts/master_helper.py
>  c5f891b 
>   
> ambari-server/src/main/resources/common-services/HAWQ/2.0.0/package/scripts/params.py
>  74c9813 
>   
> ambari-server/src/main/resources/common-services/HAWQ/2.0.0/package/templates/hawq-hosts.j2
>  e093375 
>   
> ambari-server/src/main/resources/common-services/HAWQ/2.0.0/package/templates/slaves.j2
>  0435b3e 
>   ambari-web/app/messages.js a7e4ff3 
>   ambari-web/app/models/host_component.js 5d919b9 
>   ambari-web/app/utils/helper.js 8ac754a 
>   ambari-web/app/views/main/service/item.js 145b64b 
> 
> Diff: https://reviews.apache.org/r/43703/diff/
> 
> 
> Testing
> ---
> 
> Tested functionality manually.
> 
> No additional unit tests were added.
> 
> Ambari Web unit tests passed:
> 10409 tests complete (9 seconds)
>   121 tests pending
> 
> 
> [INFO] 
> 
> [INFO] BUILD SUCCESS
> [INFO] 
> 
> [INFO] Total time: 46.008 s
> [INFO] Finished at: 2016-02-18T02:14:25-08:00
> [INFO] Final Memory: 12M/311M
> [INFO] 
> 
> 
> 
> Thanks,
> 
> Matt
> 
>

Re: Review Request 43740: Hostname substitution in HAWQ add standby popup

[jun aoki]

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


Ship it!




Ship It!

- jun aoki


On Feb. 18, 2016, 10:45 p.m., Newton Alex wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/43740/
> ---
> 
> (Updated Feb. 18, 2016, 10:45 p.m.)
> 
> 
> Review request for Ambari.
> 
> 
> Bugs: AMBARI-15076
> https://issues.apache.org/jira/browse/AMBARI-15076
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Hostname substitution in HAWQ add standby popup
> 
> 
> Diffs
> -
> 
>   
> ambari-web/app/controllers/main/admin/highAvailability/hawq/addStandby/step3_controller.js
>  513a519 
> 
> Diff: https://reviews.apache.org/r/43740/diff/
> 
> 
> Testing
> ---
> 
> Manual testing done.
> 
> 
> Thanks,
> 
> Newton Alex
> 
>

Re: Review Request 43644: Ambari should show no. of HAWQ segments live on main dashboard

[Matt]

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




ambari-web/app/views/main/dashboard/widgets/hawqsegment_live.js (line 51)


It is being used for stopped. You'll see it when you hover over the widget.

Installed refers to that the component is in actual stopped state. It is 
better than doing the difference between total and started. A possible state is 
'starting'.


- Matt


On Feb. 17, 2016, 11:57 a.m., Matt wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/43644/
> ---
> 
> (Updated Feb. 17, 2016, 11:57 a.m.)
> 
> 
> Review request for Ambari, Alexander Denissov, Alejandro Fernandez, bhuvnesh 
> chaudhary, Goutam Tadi, Jaimin Jetly, jun aoki, Lav Jain, Newton Alex, and 
> Oleksandr Diachenko.
> 
> 
> Bugs: AMBARI-15060
> https://issues.apache.org/jira/browse/AMBARI-15060
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> The no. of HAWQ segments alive should be displayed as a widget on Ambari's 
> main dashboard.
> 
> 
> Diffs
> -
> 
>   ambari-web/app/assets/test/tests.js 25c3f43 
>   ambari-web/app/mappers/components_state_mapper.js 0f2b627 
>   ambari-web/app/messages.js a7e4ff3 
>   ambari-web/app/models.js b607bee 
>   ambari-web/app/models/service/hawq.js PRE-CREATION 
>   ambari-web/app/views.js 7e461f9 
>   ambari-web/app/views/main/dashboard/widgets.js b99d881 
>   ambari-web/app/views/main/dashboard/widgets/hawqsegment_live.js 
> PRE-CREATION 
>   ambari-web/test/views/main/dashboard/widgets/hawqsegment_live_test.js 
> PRE-CREATION 
> 
> Diff: https://reviews.apache.org/r/43644/diff/
> 
> 
> Testing
> ---
> 
> Manually Tested. Images attached to JIRA.
> 
> Added additional unit test.
>   10416 tests complete (10 seconds)
>   121 tests pending
> 
> [INFO] 
> 
> [INFO] BUILD SUCCESS
> [INFO] 
> 
> [INFO] Total time: 53.572 s
> [INFO] Finished at: 2016-02-17T11:55:29-08:00
> [INFO] Final Memory: 12M/311M
> [INFO] 
> 
> 
> 
> Thanks,
> 
> Matt
> 
>

Re: Review Request 43663: PXF Service checks fails with timeout

[jun aoki]

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




ambari-server/src/main/resources/common-services/PXF/3.0.0/package/files/hbase-cleanup-data.sh
 (line 22)


Could this be InlineTemplate?



ambari-server/src/main/resources/common-services/PXF/3.0.0/package/files/hbase-populate-data.sh
 (line 22)


Could this be InlineTemplate?



ambari-server/src/main/resources/common-services/PXF/3.0.0/package/scripts/pxf_constants.py
 (line 27)


will be nice if we have more consistent naming ?
e.g.
```
hbase_populate_data_script = "hbase-populate-data.sh"
hbase_cleanup_data_script = "hbase-cleanup-data.sh"
```



ambari-server/src/main/resources/common-services/PXF/3.0.0/package/scripts/service_check.py
 (line 105)


this is nice!



ambari-server/src/main/resources/common-services/PXF/3.0.0/package/scripts/service_check.py
 (line 238)


how about 
```

def __create_hbase_script(self, script_name)
  File("{0}/{1}".format(params.exec_tmp_dir, script_name),
 content=StaticFile("{0}".format(script_name)),
 mode=0755)

...

# caller
__create_hbase_script(pxf_constants.hbase_load_script)
__create_hbase_script(pxf_constants.hbase_cleanup_script)
```



ambari-server/src/main/resources/common-services/PXF/3.0.0/package/scripts/service_check.py
 (line 298)


At this point, it is guaranteed the table does not exist?


- jun aoki


On Feb. 17, 2016, 10:46 p.m., bhuvnesh chaudhary wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/43663/
> ---
> 
> (Updated Feb. 17, 2016, 10:46 p.m.)
> 
> 
> Review request for Ambari, Alejandro Fernandez, jun aoki, Jayush Luniya, 
> Oleksandr Diachenko, Richard Zang, and Yusaku Sako.
> 
> 
> Bugs: AMBARI-15061
> https://issues.apache.org/jira/browse/AMBARI-15061
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> During PXF service check, in order to execute hbase / hive command, we do 
> initialize the shell everytime (hbase shell / hive) and then run the command. 
> Initializing the shell takes time and we do that around 3-4 times which 
> consumes majority of the time.
> We should initialize the shell once, and execute the commands using a file 
> instead of doing individually.
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/resources/common-services/PXF/3.0.0/package/files/hbase-cleanup-data.sh
>  PRE-CREATION 
>   
> ambari-server/src/main/resources/common-services/PXF/3.0.0/package/files/hbase-populate-data.sh
>  PRE-CREATION 
>   
> ambari-server/src/main/resources/common-services/PXF/3.0.0/package/scripts/params.py
>  b3e85e4 
>   
> ambari-server/src/main/resources/common-services/PXF/3.0.0/package/scripts/pxf_constants.py
>  9d93a38 
>   
> ambari-server/src/main/resources/common-services/PXF/3.0.0/package/scripts/service_check.py
>  21b7c5d 
> 
> Diff: https://reviews.apache.org/r/43663/diff/
> 
> 
> Testing
> ---
> 
> yes. manual.
> 
> 
> Thanks,
> 
> bhuvnesh chaudhary
> 
>

Re: Review Request 43644: Ambari should show no. of HAWQ segments live on main dashboard

[jun aoki]

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




ambari-web/app/models/service/hawq.js (line 1)


Is this required?



ambari-web/app/views/main/dashboard/widgets/hawqsegment_live.js (line 51)


This may not be used as it is about started vs total?


- jun aoki


On Feb. 17, 2016, 7:57 p.m., Matt wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/43644/
> ---
> 
> (Updated Feb. 17, 2016, 7:57 p.m.)
> 
> 
> Review request for Ambari, Alexander Denissov, Alejandro Fernandez, bhuvnesh 
> chaudhary, Goutam Tadi, Jaimin Jetly, jun aoki, Lav Jain, Newton Alex, and 
> Oleksandr Diachenko.
> 
> 
> Bugs: AMBARI-15060
> https://issues.apache.org/jira/browse/AMBARI-15060
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> The no. of HAWQ segments alive should be displayed as a widget on Ambari's 
> main dashboard.
> 
> 
> Diffs
> -
> 
>   ambari-web/app/assets/test/tests.js 25c3f43 
>   ambari-web/app/mappers/components_state_mapper.js 0f2b627 
>   ambari-web/app/messages.js a7e4ff3 
>   ambari-web/app/models.js b607bee 
>   ambari-web/app/models/service/hawq.js PRE-CREATION 
>   ambari-web/app/views.js 7e461f9 
>   ambari-web/app/views/main/dashboard/widgets.js b99d881 
>   ambari-web/app/views/main/dashboard/widgets/hawqsegment_live.js 
> PRE-CREATION 
>   ambari-web/test/views/main/dashboard/widgets/hawqsegment_live_test.js 
> PRE-CREATION 
> 
> Diff: https://reviews.apache.org/r/43644/diff/
> 
> 
> Testing
> ---
> 
> Manually Tested. Images attached to JIRA.
> 
> Added additional unit test.
>   10416 tests complete (10 seconds)
>   121 tests pending
> 
> [INFO] 
> 
> [INFO] BUILD SUCCESS
> [INFO] 
> 
> [INFO] Total time: 53.572 s
> [INFO] Finished at: 2016-02-17T11:55:29-08:00
> [INFO] Final Memory: 12M/311M
> [INFO] 
> 
> 
> 
> Thanks,
> 
> Matt
> 
>

[jira] [Updated] (AMBARI-15105) Add alerts for HAWQ components status

[bhuvnesh chaudhary (JIRA)]

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

bhuvnesh chaudhary updated AMBARI-15105:

Attachment: AMBARI-15105.patch

> Add alerts for HAWQ components status
> -
>
> Key: AMBARI-15105
> URL: https://issues.apache.org/jira/browse/AMBARI-15105
> Project: Ambari
>  Issue Type: New Feature
>  Components: alerts
>Affects Versions: trunk, 2.2.0
>Reporter: bhuvnesh chaudhary
>Assignee: bhuvnesh chaudhary
> Fix For: trunk, 2.2.0
>
> Attachments: AMBARI-15105.patch
>
>
> Add alerts for HAWQ components based on PORT. The below components are 
> covered.
> - Master
> - Standby
> - Segment



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

[jira] [Updated] (AMBARI-15105) Add alerts for HAWQ components status

[bhuvnesh chaudhary (JIRA)]

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

bhuvnesh chaudhary updated AMBARI-15105:

Fix Version/s: 2.2.0
   trunk

> Add alerts for HAWQ components status
> -
>
> Key: AMBARI-15105
> URL: https://issues.apache.org/jira/browse/AMBARI-15105
> Project: Ambari
>  Issue Type: New Feature
>  Components: alerts
>Affects Versions: trunk, 2.2.0
>Reporter: bhuvnesh chaudhary
>Assignee: bhuvnesh chaudhary
> Fix For: trunk, 2.2.0
>
> Attachments: AMBARI-15105.patch
>
>
> Add alerts for HAWQ components based on PORT. The below components are 
> covered.
> - Master
> - Standby
> - Segment



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

Re: sync LDAP behavior

[Keta Patel]

Adding more detail to my question:

The following is what I see when I perform sync-ldap consecutively.
*The very 1st call:*
>>ambari-server sync-ldap --all

*Result:*
Using python  /usr/bin/python2
Syncing with LDAP...
Enter Ambari Admin login: admin
Enter Ambari Admin password:
Syncing all...

Completed LDAP Sync.
Summary:
  memberships:
removed = 0
created = 0
  users:
updated = 0
removed = 0
created = 0
  groups:
updated = 0
removed = 0
created = 2

Ambari Server 'sync-ldap' completed successfully.




*The 2nd time I call:*
>>ambari-server sync-ldap --all

*Result:*
Using python  /usr/bin/python2
Syncing with LDAP...
Enter Ambari Admin login: admin
Enter Ambari Admin password:
Syncing all...ERROR: Exiting with exit code 1.
REASON: Caught exception running LDAP sync. Exception [EclipseLink-4002]
(Eclipse Persistence Services - 2.5.2.v20140319-9ad6abd):
org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: java.sql.BatchUpdateException: Batch entry 0 INSERT
INTO groups (group_id, group_name, ldap_group, principal_id) VALUES (524,
'sheetsg9', 1, 5527) was aborted.  Call getNextException to see the cause.
Error Code: 0
Call: INSERT INTO groups (group_id, group_name, ldap_group, principal_id)
VALUES (?, ?, ?, ?)
bind => [4 parameters bound]



The only difference I found with the LDAP group "sheetsg9" when compared to
the other LDAP groups was that *it had no users associated with it.*
The workaround involves deleting that group from the "groups" table in the
DB and syncing again. The sync goes through fine after that.

Is this the expected behavior of "sync-ldap --all" or is the case of
handling groups with no users not handled properly?

On Thu, Feb 18, 2016 at 3:27 PM, Keta Patel <
keta.mahendrakumar.pa...@gmail.com> wrote:

> Hello all,
> What is the expected behavior of "ambari-server sync-ldap --all" on the
> 2nd or later calls?
>
> Thank you!
> Keta
>

Review Request 43748: Add alerts for HAWQ components status

[bhuvnesh chaudhary]

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

Review request for Ambari, Alejandro Fernandez, Jaimin Jetly, jun aoki, 
Jonathan Hurley, Jayush Luniya, Oleksandr Diachenko, Richard Zang, Sumit 
Mohanty, and Yusaku Sako.


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


Repository: ambari


Description
---

This patch introduces alerts for HAWQ components based on PORT. The below 
components are covered.
- Master
- Standby
- Segment


Diffs
-

  ambari-server/src/main/resources/common-services/HAWQ/2.0.0/alerts.json 
3119a0c 

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


Testing
---

yes, manual.


Thanks,

bhuvnesh chaudhary

[jira] [Created] (AMBARI-15105) Add alerts for HAWQ components status

[bhuvnesh chaudhary (JIRA)]

bhuvnesh chaudhary created AMBARI-15105:
---

 Summary: Add alerts for HAWQ components status
 Key: AMBARI-15105
 URL: https://issues.apache.org/jira/browse/AMBARI-15105
 Project: Ambari
  Issue Type: New Feature
  Components: alerts
Affects Versions: trunk, 2.2.0
Reporter: bhuvnesh chaudhary
Assignee: bhuvnesh chaudhary


Add alerts for HAWQ components based on PORT. The below components are covered.
- Master
- Standby
- Segment



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

Re: Review Request 43736: AMBARI-15096 Edit WEB Alert should show Critical for Connection Timeout

[Zhe (Joe) Wang]

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

(Updated Feb. 19, 2016, 12:42 a.m.)


Review request for Ambari, Richard Zang, Srimanth Gunturi, and Yusaku Sako.


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


Repository: ambari


Description
---

For WEB alerts, the Connection Timeout fields should show CRITICAL badge since 
if the connection times out, it is a critical situation.


Diffs (updated)
-

  ambari-web/app/controllers/main/alerts/definition_configs_controller.js 
130434f 
  ambari-web/app/models/alerts/alert_config.js 867b45a 
  ambari-web/app/styles/alerts.less 1b8d5f4 
  ambari-web/app/templates/main/alerts/configs/alert_config_parameter.hbs 
fffa7bd 

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


Testing
---

Local ambari-web test passed.
24271 tests complete (21 seconds)
156 tests pending
Manual testing done.


Thanks,

Zhe (Joe) Wang

[jira] [Updated] (AMBARI-15096) Edit WEB Alert should show Critical for Connection Timeout

[Zhe (Joe) Wang (JIRA)]

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

Zhe (Joe) Wang updated AMBARI-15096:

Attachment: AMBARI-15096_trunk.1.patch

Local ambari-web test passed.
24271 tests complete (21 seconds)
  156 tests pending
Manual testing done.

> Edit WEB Alert should show Critical for Connection Timeout
> --
>
> Key: AMBARI-15096
> URL: https://issues.apache.org/jira/browse/AMBARI-15096
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.2.2
>Reporter: Zhe (Joe) Wang
>Assignee: Zhe (Joe) Wang
> Fix For: 2.2.2
>
> Attachments: AMBARI-15096_branch_2_2.0.patch, 
> AMBARI-15096_trunk.0.patch, AMBARI-15096_trunk.1.patch
>
>
> For WEB alerts, the Connection Timeout fields should show CRITICAL badge 
> since if the connection times out, it is a critical situation.



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

Re: Review Request 43663: PXF Service checks fails with timeout

[bhuvnesh chaudhary]

> On Feb. 17, 2016, 7:52 p.m., Matt wrote:
> > ambari-server/src/main/resources/common-services/PXF/3.0.0/package/scripts/service_check.py,
> >  line 329
> > 
> >
> > May be str(hive_load_commands) ?

Its a string, so using str is not required. either use directly 
hive_load_commands or in the current way.


- bhuvnesh


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


On Feb. 17, 2016, 10:46 p.m., bhuvnesh chaudhary wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/43663/
> ---
> 
> (Updated Feb. 17, 2016, 10:46 p.m.)
> 
> 
> Review request for Ambari, Alejandro Fernandez, jun aoki, Jayush Luniya, 
> Oleksandr Diachenko, Richard Zang, and Yusaku Sako.
> 
> 
> Bugs: AMBARI-15061
> https://issues.apache.org/jira/browse/AMBARI-15061
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> During PXF service check, in order to execute hbase / hive command, we do 
> initialize the shell everytime (hbase shell / hive) and then run the command. 
> Initializing the shell takes time and we do that around 3-4 times which 
> consumes majority of the time.
> We should initialize the shell once, and execute the commands using a file 
> instead of doing individually.
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/resources/common-services/PXF/3.0.0/package/files/hbase-cleanup-data.sh
>  PRE-CREATION 
>   
> ambari-server/src/main/resources/common-services/PXF/3.0.0/package/files/hbase-populate-data.sh
>  PRE-CREATION 
>   
> ambari-server/src/main/resources/common-services/PXF/3.0.0/package/scripts/params.py
>  b3e85e4 
>   
> ambari-server/src/main/resources/common-services/PXF/3.0.0/package/scripts/pxf_constants.py
>  9d93a38 
>   
> ambari-server/src/main/resources/common-services/PXF/3.0.0/package/scripts/service_check.py
>  21b7c5d 
> 
> Diff: https://reviews.apache.org/r/43663/diff/
> 
> 
> Testing
> ---
> 
> yes. manual.
> 
> 
> Thanks,
> 
> bhuvnesh chaudhary
> 
>

[jira] [Commented] (AMBARI-15082) HAWQ fails to install

[Hudson (JIRA)]

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

Hudson commented on AMBARI-15082:
-

FAILURE: Integrated in Ambari-branch-2.2 #358 (See 
[https://builds.apache.org/job/Ambari-branch-2.2/358/])
AMBARI-15082: HAWQ fails to install (mithmatt via jaoki) (jaoki: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=620daba7cad89af4d2531ca74baddcf334502379])
* 
ambari-server/src/main/resources/common-services/HAWQ/2.0.0/package/scripts/common.py


> HAWQ fails to install
> -
>
> Key: AMBARI-15082
> URL: https://issues.apache.org/jira/browse/AMBARI-15082
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Reporter: Matt
>Assignee: Matt
> Fix For: trunk, 2.2.2
>
> Attachments: AMBARI-15082-branch-2.2-orig.patch, 
> AMBARI-15082-trunk-orig.patch
>
>
> HAWQ fails to install while deploying HAWQ service.
> {code}stderr: 
> Traceback (most recent call last):
>   File 
> "/var/lib/ambari-agent/cache/common-services/HAWQ/2.0.0/package/scripts/hawqmaster.py",
>  line 77, in 
> HawqMaster().execute()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 219, in execute
> method(env)
>   File 
> "/var/lib/ambari-agent/cache/common-services/HAWQ/2.0.0/package/scripts/hawqmaster.py",
>  line 40, in install
> self.configure(env)
>   File 
> "/var/lib/ambari-agent/cache/common-services/HAWQ/2.0.0/package/scripts/hawqmaster.py",
>  line 46, in configure
> master_helper.configure_master()
>   File 
> "/var/lib/ambari-agent/cache/common-services/HAWQ/2.0.0/package/scripts/master_helper.py",
>  line 60, in configure_master
> common.setup_common_configurations()
>   File 
> "/var/lib/ambari-agent/cache/common-services/HAWQ/2.0.0/package/scripts/common.py",
>  line 72, in setup_common_configurations
> configuration_attributes=params.config_attrs['hdfs-client'])
> TypeError: __new__() takes at least 2 non-keyword arguments (1 given)
> {code}



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

[jira] [Commented] (AMBARI-15064) RU/EU can't start if hosts have name in MixedCASE in configs for NameNode, HBASE Master, ResourceManager

[Hudson (JIRA)]

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

Hudson commented on AMBARI-15064:
-

FAILURE: Integrated in Ambari-branch-2.2 #358 (See 
[https://builds.apache.org/job/Ambari-branch-2.2/358/])
AMBARI-15064. RU/EU can't start if hosts have name in MixedCASE in (afernandez: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=67c9e81317547a34a65d6bfe480e665473e47849])
* 
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/UpgradeResourceProvider.java
* 
ambari-server/src/main/java/org/apache/ambari/server/stack/MasterHostResolver.java
* 
ambari-server/src/test/java/org/apache/ambari/server/state/UpgradeHelperTest.java
* ambari-server/src/main/java/org/apache/ambari/server/stack/JmxQuery.java
* 
ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariActionExecutionHelper.java
* 
ambari-server/src/test/java/org/apache/ambari/server/controller/AmbariManagementControllerTest.java


> RU/EU can't start if hosts have name in MixedCASE in configs for NameNode, 
> HBASE Master, ResourceManager
> 
>
> Key: AMBARI-15064
> URL: https://issues.apache.org/jira/browse/AMBARI-15064
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.2.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 2.2.2
>
> Attachments: AMBARI-15064.branch-2.2.patch, AMBARI-15064.trunk.patch
>
>
> RU/EU tries to resolve the hostnames for NameNode, HBASE Master, and 
> ResourceManager by using MasterHostResolver.java, which queries configs and 
> then JMX.
> Ambari DB stores the hostnames in all lowercase, so if the configs or JMX 
> store the hostnames in a different case, then Ambari will throw an exception 
> that the host could not be found.
> To fix this, convert all hostnames to lowercase.



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

[jira] [Commented] (AMBARI-15075) Edit Widget Wizard still open even though it was closed/saved in the previous step

[Hudson (JIRA)]

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

Hudson commented on AMBARI-15075:
-

FAILURE: Integrated in Ambari-branch-2.2 #358 (See 
[https://builds.apache.org/job/Ambari-branch-2.2/358/])
AMBARI-15075. Edit Widget Wizard still open even though it was (jaimin: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=2b1f7496e87741836691de9b22ba7511014c64e8])
* ambari-web/app/controllers/main/service/widgets/create/wizard_controller.js


> Edit Widget Wizard still open even though it was closed/saved in the previous 
> step
> --
>
> Key: AMBARI-15075
> URL: https://issues.apache.org/jira/browse/AMBARI-15075
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.1.0
>Reporter: Jaimin D Jetly
>Assignee: Jaimin D Jetly
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15075.2.patch, AMBARI-15075.patch
>
>




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

[jira] [Commented] (AMBARI-15087) Add log level for check database logs

[Hudson (JIRA)]

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

Hudson commented on AMBARI-15087:
-

FAILURE: Integrated in Ambari-branch-2.2 #358 (See 
[https://builds.apache.org/job/Ambari-branch-2.2/358/])
AMBARI-15087. Add log level for check database logs.(vbrodetskyi) (vbrodetskyi: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=e5521f3798a49b273392afc07de0c24fbb808d01])
* ambari-server/src/main/conf/log4j.properties
* ambari-server/conf/unix/log4j.properties
* ambari-server/conf/windows/log4j.properties


> Add log level for check database logs
> -
>
> Key: AMBARI-15087
> URL: https://issues.apache.org/jira/browse/AMBARI-15087
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
> Fix For: 2.2.2
>
> Attachments: AMBARI-15087.patch
>
>




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

[jira] [Commented] (AMBARI-15066) Spark History server does not start after downgrade due to missing spark-events directory

[Hudson (JIRA)]

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

Hudson commented on AMBARI-15066:
-

FAILURE: Integrated in Ambari-branch-2.2 #358 (See 
[https://builds.apache.org/job/Ambari-branch-2.2/358/])
AMBARI-15066. Spark History server does not start after downgrade due to 
(afernandez: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=53bf270657ae268c0ffd806f623da1a5650bbd09])
* 
ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/nonrolling-upgrade-2.4.xml
* ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.4.xml


> Spark History server does not start after downgrade due to missing 
> spark-events directory
> -
>
> Key: AMBARI-15066
> URL: https://issues.apache.org/jira/browse/AMBARI-15066
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.2.0
>Reporter: Jeff Zhang
>Assignee: Jeff Zhang
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15066.branch-2.2.patch, AMBARI-15066.trunk.patch
>
>




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

[jira] [Commented] (AMBARI-15098) Ambari Schema Version should ignore patch number from version number

[Hudson (JIRA)]

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

Hudson commented on AMBARI-15098:
-

FAILURE: Integrated in Ambari-branch-2.2 #358 (See 
[https://builds.apache.org/job/Ambari-branch-2.2/358/])
AMBARI-15098: Ambari Schema Version should ignore patch number from (jluniya: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=d12e14c90c7b22034a39ec7b0872ff67445bb010])
* ambari-server/src/main/resources/Ambari-DDL-SQLAnywhere-CREATE.sql
* 
ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariServer.java
* ambari-server/src/main/resources/Ambari-DDL-Oracle-CREATE.sql
* 
ambari-server/src/main/java/org/apache/ambari/server/controller/utilities/DatabaseChecker.java
* ambari-server/src/main/resources/Ambari-DDL-SQLServer-CREATE.sql
* ambari-server/src/main/resources/Ambari-DDL-Postgres-EMBEDDED-CREATE.sql
* ambari-server/pom.xml
* ambari-server/src/main/resources/Ambari-DDL-Postgres-CREATE.sql
* ambari-server/src/main/resources/Ambari-DDL-MySQL-CREATE.sql
* 
ambari-server/src/test/java/org/apache/ambari/server/utils/TestVersionUtils.java


> Ambari Schema Version should ignore patch number from version number
> 
>
> Key: AMBARI-15098
> URL: https://issues.apache.org/jira/browse/AMBARI-15098
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.2.1
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15098.patch
>
>
> # On ambari-server upgrade to a patch release version (2.0.2 -> 2.2.1.2), 
> ambari server fails to start. 
> # This is because the schema version set in the DB on ambari-server upgrade 
> is 2.2.1 whereas ambari-server version is 2.2.1.2. 
> # This incosistency leads to DB check failure. DB check should ignore patch 
> release number from the ambari version. 
> # Further a clean install on 2.2.1.2 will set the DB schema version to 
> 2.2.1.2 whereas an upgrade to 2.2.1.2 will set the DB schema version to 2.2.1
> # We should fix this inconsistency by always setting DB schema version to 
> 3-digit and ignoring the patch release version during DB check. 
> # We will not be supporting DB schema changes in patch releases.  



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

[jira] [Updated] (AMBARI-15061) PXF Service checks fails with timeout

[bhuvnesh chaudhary (JIRA)]

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

bhuvnesh chaudhary updated AMBARI-15061:

Fix Version/s: 2.2.0
   trunk

> PXF Service checks fails with timeout
> -
>
> Key: AMBARI-15061
> URL: https://issues.apache.org/jira/browse/AMBARI-15061
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: trunk, 2.2.0
>Reporter: bhuvnesh chaudhary
>Assignee: bhuvnesh chaudhary
> Fix For: trunk, 2.2.0
>
> Attachments: AMBARI-15061-1.patch, AMBARI-15061-branch-2.2.patch
>
>
> During PXF service check, in order to execute hbase / hive command, we do 
> initialize the shell everytime (hbase shell / hive) and then run the command. 
> Initializing the shell takes time and we do that around 3-4 times which 
> consumes majority of the time.
> We should initialize the shell once, and execute the commands using a file 
> instead of doing individually.



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

[jira] [Updated] (AMBARI-15083) Add Stack Advisor validations for hawq_global_rm_type property in HAWQ

[bhuvnesh chaudhary (JIRA)]

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

bhuvnesh chaudhary updated AMBARI-15083:

Attachment: AMBARI-15083-branch-2.2.patch

> Add Stack Advisor validations for hawq_global_rm_type property in HAWQ
> --
>
> Key: AMBARI-15083
> URL: https://issues.apache.org/jira/browse/AMBARI-15083
> Project: Ambari
>  Issue Type: Improvement
>  Components: stacks
>Affects Versions: trunk, 2.2.0
>Reporter: bhuvnesh chaudhary
>Assignee: bhuvnesh chaudhary
>Priority: Minor
> Fix For: trunk, 2.2.0
>
> Attachments: AMBARI-15083-branch-2.2.patch, AMBARI-15083.patch
>
>
> Add Stack Advisor validations for hawq_global_rm_type property in HAWQ. The 
> below 2 cases must be covered:
> #1:
> If YARN service is not installed, and hawq_global_rm_type is set as yarn, a 
> validation error should be thrown
> #2:
> If YARN service is installed, and hawq_gloabl_rm_type is set as yarn, no 
> validation error should be thrown



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

[jira] [Commented] (AMBARI-15061) PXF Service checks fails with timeout

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-15061:


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

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

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

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

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

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

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

This message is automatically generated.

> PXF Service checks fails with timeout
> -
>
> Key: AMBARI-15061
> URL: https://issues.apache.org/jira/browse/AMBARI-15061
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: trunk, 2.2.0
>Reporter: bhuvnesh chaudhary
>Assignee: bhuvnesh chaudhary
> Attachments: AMBARI-15061-1.patch, AMBARI-15061-branch-2.2.patch
>
>
> During PXF service check, in order to execute hbase / hive command, we do 
> initialize the shell everytime (hbase shell / hive) and then run the command. 
> Initializing the shell takes time and we do that around 3-4 times which 
> consumes majority of the time.
> We should initialize the shell once, and execute the commands using a file 
> instead of doing individually.



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

Re: Review Request 43736: AMBARI-15096 Edit WEB Alert should show Critical for Connection Timeout

[Richard Zang]

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



Instead of creating a new AlertConfigConnectionTimeoutView, we can add a 
parameter based badge section for currently used AlertConfigTextFieldView.

- Richard Zang


On Feb. 18, 2016, 9:01 p.m., Zhe (Joe) Wang wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/43736/
> ---
> 
> (Updated Feb. 18, 2016, 9:01 p.m.)
> 
> 
> Review request for Ambari, Richard Zang, Srimanth Gunturi, and Yusaku Sako.
> 
> 
> Bugs: AMBARI-15096
> https://issues.apache.org/jira/browse/AMBARI-15096
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> For WEB alerts, the Connection Timeout fields should show CRITICAL badge 
> since if the connection times out, it is a critical situation.
> 
> 
> Diffs
> -
> 
>   ambari-web/app/models/alerts/alert_config.js 867b45a 
>   
> ambari-web/app/templates/main/alerts/configs/alert_config_connection_timeout.hbs
>  PRE-CREATION 
>   ambari-web/app/views/main/alerts/definition_configs_view.js 00e26d4 
> 
> Diff: https://reviews.apache.org/r/43736/diff/
> 
> 
> Testing
> ---
> 
> Local ambari-web test passed.
> 24271 tests complete (21 seconds)
> 156 tests pending
> Manual testing done.
> 
> 
> Thanks,
> 
> Zhe (Joe) Wang
> 
>

sync LDAP behavior

[Keta Patel]

Hello all,
What is the expected behavior of "ambari-server sync-ldap --all" on the 2nd
or later calls?

Thank you!
Keta

[jira] [Commented] (AMBARI-14627) Ability to automate setup-security and setup-ldap/sync-ldap

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-14627:


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

This message is automatically generated.

> Ability to automate setup-security and setup-ldap/sync-ldap
> ---
>
> Key: AMBARI-14627
> URL: https://issues.apache.org/jira/browse/AMBARI-14627
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.2.1
>Reporter: Krisztian Horvath
>Assignee: Olivér Szabó
> Attachments: AMBARI-14627.patch
>
>
> Currently the ambari-server setup-security command does not have any options 
> thus it's interactive. This makes it really hard to automate this process. 
> For kerberos 1 option should be enough for setting the master key.
> Same for setup-ldap and sync-ldap



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

[jira] [Commented] (AMBARI-15101) Remove the dependency between ZK start and Ranger user sync start

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-15101:


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

This message is automatically generated.

> Remove the dependency between ZK start and Ranger user sync start
> -
>
> Key: AMBARI-15101
> URL: https://issues.apache.org/jira/browse/AMBARI-15101
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.2.2
>Reporter: Sumit Mohanty
>Assignee: Sumit Mohanty
> Fix For: 2.2.2
>
> Attachments: AMBARI-15101.patch
>
>
> ZK start should not depend on Ranger user sync start. We should remove the 
> dependency.



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

[jira] [Updated] (AMBARI-15077) Auto-start services: Backend API and DB changes for component auto start

[Nahappan Somasundaram (JIRA)]

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

Nahappan Somasundaram updated AMBARI-15077:
---
Attachment: rb43671.patch

> Auto-start services: Backend API and DB changes for component auto start
> 
>
> Key: AMBARI-15077
> URL: https://issues.apache.org/jira/browse/AMBARI-15077
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
>  Labels: ambari-server
> Fix For: 2.4.0
>
> Attachments: rb43671.patch
>
>
> Add a new field *recovery_enabled* in *servicecomponentdesiredstate* and 
> provide API support for PUT and GET.
> *Type: PUT*
> Request 1: 
> api/v1/clusters//components?ServiceComponentInfo/component_name.in()
> Request Params: application/json
> {
>   ServiceComponentInfo: {
>   “recovery_enabled”: “true”
>   }
> }
> Request 2:
> api/v1/clusters//components?ServiceComponentInfo/component_name.in()
> Request Params: application/json
> {
>   ServiceComponentInfo: {
>   recovery_enabled: “false”
>   }
> }
> Request 3:
> api/v1/clusters/testcluster/components/ 
> Request Params: application/json
> '{"ServiceComponentInfo" : {"recovery_enabled":"false"}}'
> *Type:GET*
> Request: 
> api/v1/clusters//components?fields=ServiceComponentInfo/component_name,ServiceComponentInfo/service_name,ServiceComponentInfo/category,ServiceComponentInfo/recovery_enabled



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

[jira] [Updated] (AMBARI-15077) Auto-start services: Backend API and DB changes for component auto start

[Nahappan Somasundaram (JIRA)]

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

Nahappan Somasundaram updated AMBARI-15077:
---
Attachment: (was: rb43671.patch)

> Auto-start services: Backend API and DB changes for component auto start
> 
>
> Key: AMBARI-15077
> URL: https://issues.apache.org/jira/browse/AMBARI-15077
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
>  Labels: ambari-server
> Fix For: 2.4.0
>
> Attachments: rb43671.patch
>
>
> Add a new field *recovery_enabled* in *servicecomponentdesiredstate* and 
> provide API support for PUT and GET.
> *Type: PUT*
> Request 1: 
> api/v1/clusters//components?ServiceComponentInfo/component_name.in()
> Request Params: application/json
> {
>   ServiceComponentInfo: {
>   “recovery_enabled”: “true”
>   }
> }
> Request 2:
> api/v1/clusters//components?ServiceComponentInfo/component_name.in()
> Request Params: application/json
> {
>   ServiceComponentInfo: {
>   recovery_enabled: “false”
>   }
> }
> Request 3:
> api/v1/clusters/testcluster/components/ 
> Request Params: application/json
> '{"ServiceComponentInfo" : {"recovery_enabled":"false"}}'
> *Type:GET*
> Request: 
> api/v1/clusters//components?fields=ServiceComponentInfo/component_name,ServiceComponentInfo/service_name,ServiceComponentInfo/category,ServiceComponentInfo/recovery_enabled



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

[jira] [Commented] (AMBARI-15098) Ambari Schema Version should ignore patch number from version number

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-15098:


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

This message is automatically generated.

> Ambari Schema Version should ignore patch number from version number
> 
>
> Key: AMBARI-15098
> URL: https://issues.apache.org/jira/browse/AMBARI-15098
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.2.1
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15098.patch
>
>
> # On ambari-server upgrade to a patch release version (2.0.2 -> 2.2.1.2), 
> ambari server fails to start. 
> # This is because the schema version set in the DB on ambari-server upgrade 
> is 2.2.1 whereas ambari-server version is 2.2.1.2. 
> # This incosistency leads to DB check failure. DB check should ignore patch 
> release number from the ambari version. 
> # Further a clean install on 2.2.1.2 will set the DB schema version to 
> 2.2.1.2 whereas an upgrade to 2.2.1.2 will set the DB schema version to 2.2.1
> # We should fix this inconsistency by always setting DB schema version to 
> 3-digit and ignoring the patch release version during DB check. 
> # We will not be supporting DB schema changes in patch releases.  



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

[jira] [Commented] (AMBARI-15096) Edit WEB Alert should show Critical for Connection Timeout

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-15096:


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

This message is automatically generated.

> Edit WEB Alert should show Critical for Connection Timeout
> --
>
> Key: AMBARI-15096
> URL: https://issues.apache.org/jira/browse/AMBARI-15096
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.2.2
>Reporter: Zhe (Joe) Wang
>Assignee: Zhe (Joe) Wang
> Fix For: 2.2.2
>
> Attachments: AMBARI-15096_branch_2_2.0.patch, 
> AMBARI-15096_trunk.0.patch
>
>
> For WEB alerts, the Connection Timeout fields should show CRITICAL badge 
> since if the connection times out, it is a critical situation.



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

[jira] [Commented] (AMBARI-15099) Ambari missing metrics in UI with Vip settings enabled.

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-15099:


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

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

This message is automatically generated.

> Ambari missing metrics in UI with Vip settings enabled.
> ---
>
> Key: AMBARI-15099
> URL: https://issues.apache.org/jira/browse/AMBARI-15099
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.2.1
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15099.patch
>
>
> When using a vip settings for a cluster with 2 Collectors (1 active at a 
> time), no metrics are seen unless Ambari Server is restarted.



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

[jira] [Created] (AMBARI-15104) Change description for HAWQ Sync standby alert

[Matt (JIRA)]

Matt created AMBARI-15104:
-

 Summary: Change description for HAWQ Sync standby alert
 Key: AMBARI-15104
 URL: https://issues.apache.org/jira/browse/AMBARI-15104
 Project: Ambari
  Issue Type: Sub-task
  Components: stacks
Reporter: Matt
Assignee: Matt
Priority: Minor
 Fix For: trunk, 2.2.2






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

Re: Review Request 43743: AMBARI-13424. Allow disabling RU/EU PreChecks

[Alejandro Fernandez]

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




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


New prop to control the prechecks.



ambari-server/src/main/java/org/apache/ambari/server/state/CheckHelper.java 
(line 69)


BYPASS implies failed but can be skipped.



ambari-web/app/controllers/main/admin/stack_and_upgrade_controller.js (line 889)


I should probably put these in messages.js



ambari-web/app/styles/stack_versions.less (line 320)


Removed the fixed height since it is now dynamic based on the additional 
error message that can show up.


- Alejandro Fernandez


On Feb. 18, 2016, 11:10 p.m., Alejandro Fernandez wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/43743/
> ---
> 
> (Updated Feb. 18, 2016, 11:10 p.m.)
> 
> 
> Review request for Ambari, Dmitro Lisnichenko, Jonathan Hurley, Nate Cole, 
> Richard Zang, and Xi Wang.
> 
> 
> Bugs: AMBARI-13424
> https://issues.apache.org/jira/browse/AMBARI-13424
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> In some environments, the customer still wants to proceed with RU & EU even 
> if PreChecks fail. E.g.,
> NameNode HA doesn't actually exist if they have their own distribution of HDFS
> Hosts be down at the time the upgrade is starting, but will come online 
> during the upgrade.
> 
> Today, they are unable to start RU/EU if any of the PreChecks fail.
> Introduce a config in ambari.properties file called 
> "stack.upgrade.bypass.prechecks" whose default value is "false"
> 
> 
> Diffs
> -
> 
>   ambari-server/conf/unix/ambari.properties 81ef446 
>   
> ambari-server/src/main/java/org/apache/ambari/server/checks/AbstractCheckDescriptor.java
>  8a81aa9 
>   
> ambari-server/src/main/java/org/apache/ambari/server/configuration/Configuration.java
>  cfc2f51 
>   ambari-server/src/main/java/org/apache/ambari/server/state/CheckHelper.java 
> 5a8d4fd 
>   
> ambari-server/src/main/java/org/apache/ambari/server/state/stack/PrereqCheckStatus.java
>  f8009e3 
>   ambari-web/app/controllers/main/admin/stack_and_upgrade_controller.js 
> c226059 
>   ambari-web/app/messages.js 9d24b4f 
>   ambari-web/app/styles/stack_versions.less ab27a84 
>   ambari-web/app/templates/common/modal_popups/cluster_check_dialog.hbs 
> 8fd2746 
>   ambari-web/app/templates/main/admin/stack_upgrade/upgrade_options.hbs 
> 268ea1d 
>   ambari-web/app/views/common/modal_popups/cluster_check_popup.js 54f20ba 
> 
> Diff: https://reviews.apache.org/r/43743/diff/
> 
> 
> Testing
> ---
> 
> Verified on PreChecks for RU/EU when put hosts in maintenance mode and tested 
> with/without the config "stack.upgrade.bypass.prechecks"
> See screenshots in Apache Jira.
> 
> Waiting for unit test results.
> 
> 
> Thanks,
> 
> Alejandro Fernandez
> 
>

[jira] [Updated] (AMBARI-15102) Remodel HAWQ configurations and message descriptions

[Matt (JIRA)]

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

Matt updated AMBARI-15102:
--
Summary: Remodel HAWQ configurations and message descriptions  (was: 
Remodel HAWQ configurations)

> Remodel HAWQ configurations and message descriptions
> 
>
> Key: AMBARI-15102
> URL: https://issues.apache.org/jira/browse/AMBARI-15102
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-web, stacks
>Reporter: Matt
>Assignee: Matt
>Priority: Minor
> Fix For: trunk, 2.2.2
>
>




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

Re: Review Request 43743: AMBARI-13424. Allow disabling RU/EU PreChecks

[Alejandro Fernandez]

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

(Updated Feb. 18, 2016, 11:10 p.m.)


Review request for Ambari, Dmitro Lisnichenko, Jonathan Hurley, Nate Cole, 
Richard Zang, and Xi Wang.


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


Repository: ambari


Description
---

In some environments, the customer still wants to proceed with RU & EU even if 
PreChecks fail. E.g.,
NameNode HA doesn't actually exist if they have their own distribution of HDFS
Hosts be down at the time the upgrade is starting, but will come online during 
the upgrade.

Today, they are unable to start RU/EU if any of the PreChecks fail.
Introduce a config in ambari.properties file called 
"stack.upgrade.bypass.prechecks" whose default value is "false"


Diffs
-

  ambari-server/conf/unix/ambari.properties 81ef446 
  
ambari-server/src/main/java/org/apache/ambari/server/checks/AbstractCheckDescriptor.java
 8a81aa9 
  
ambari-server/src/main/java/org/apache/ambari/server/configuration/Configuration.java
 cfc2f51 
  ambari-server/src/main/java/org/apache/ambari/server/state/CheckHelper.java 
5a8d4fd 
  
ambari-server/src/main/java/org/apache/ambari/server/state/stack/PrereqCheckStatus.java
 f8009e3 
  ambari-web/app/controllers/main/admin/stack_and_upgrade_controller.js c226059 
  ambari-web/app/messages.js 9d24b4f 
  ambari-web/app/styles/stack_versions.less ab27a84 
  ambari-web/app/templates/common/modal_popups/cluster_check_dialog.hbs 8fd2746 
  ambari-web/app/templates/main/admin/stack_upgrade/upgrade_options.hbs 268ea1d 
  ambari-web/app/views/common/modal_popups/cluster_check_popup.js 54f20ba 

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


Testing (updated)
---

Verified on PreChecks for RU/EU when put hosts in maintenance mode and tested 
with/without the config "stack.upgrade.bypass.prechecks"
See screenshots in Apache Jira.

Waiting for unit test results.


Thanks,

Alejandro Fernandez

Review Request 43743: AMBARI-13424. Allow disabling RU/EU PreChecks

[Alejandro Fernandez]

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

Review request for Ambari, Dmitro Lisnichenko, Jonathan Hurley, Nate Cole, 
Richard Zang, and Xi Wang.


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


Repository: ambari


Description
---

In some environments, the customer still wants to proceed with RU & EU even if 
PreChecks fail. E.g.,
NameNode HA doesn't actually exist if they have their own distribution of HDFS
Hosts be down at the time the upgrade is starting, but will come online during 
the upgrade.

Today, they are unable to start RU/EU if any of the PreChecks fail.
Introduce a config in ambari.properties file called 
"stack.upgrade.bypass.prechecks" whose default value is "false"


Diffs
-

  ambari-server/conf/unix/ambari.properties 81ef446 
  
ambari-server/src/main/java/org/apache/ambari/server/checks/AbstractCheckDescriptor.java
 8a81aa9 
  
ambari-server/src/main/java/org/apache/ambari/server/configuration/Configuration.java
 cfc2f51 
  ambari-server/src/main/java/org/apache/ambari/server/state/CheckHelper.java 
5a8d4fd 
  
ambari-server/src/main/java/org/apache/ambari/server/state/stack/PrereqCheckStatus.java
 f8009e3 
  ambari-web/app/controllers/main/admin/stack_and_upgrade_controller.js c226059 
  ambari-web/app/messages.js 9d24b4f 
  ambari-web/app/styles/stack_versions.less ab27a84 
  ambari-web/app/templates/common/modal_popups/cluster_check_dialog.hbs 8fd2746 
  ambari-web/app/templates/main/admin/stack_upgrade/upgrade_options.hbs 268ea1d 
  ambari-web/app/views/common/modal_popups/cluster_check_popup.js 54f20ba 

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


Testing
---

Verified on PreChecks for RU/EU when put hosts in maintenance mode and tested 
with/without the config "stack.upgrade.bypass.prechecks"
Waiting for unit test results.


Thanks,

Alejandro Fernandez