[jira] [Updated] (AMBARI-18140) Avoid hardcoded values in blueprint for hive and oozie

[Amruta Borkar (JIRA)]

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

Amruta Borkar updated AMBARI-18140:
---
Status: Patch Available  (was: In Progress)

> Avoid hardcoded values in blueprint for hive and oozie
> --
>
> Key: AMBARI-18140
> URL: https://issues.apache.org/jira/browse/AMBARI-18140
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server, blueprints
>Affects Versions: 2.2.0
>Reporter: Amruta Borkar
>Assignee: Amruta Borkar
> Fix For: trunk
>
> Attachments: AMBARI-18140.patch
>
>
> There are a lot of hardcoded values in blueprint for hive.
> {
>   "hive-env" : {
> "properties_attributes" : { },
> "properties" : {
>   "hive_security_authorization" : "None",
>   "hive_log_dir" : "/var/log/hive",
>   "hive_existing_oracle_host" : "hardcodedhostname
> com",
>   "hive_user" : "hive",
>   "hive_existing_mssql_server_2_host" : "hardcodedhostname.com",
>   "hive.heapsize" : "1024",
>   "hcat_log_dir" : "/var/log/webhcat",
>   "hive_hostname" : "%HOSTGROUP::host_group_1%",
>   "hive_database" : "New MySQL Database",
>   "hive_exec_orc_storage_strategy" : "SPEED",
>   "hive_database_name" : "hive",
>   "webhcat_user" : "hcat",
>   "hive_txn_acid" : "off",
>   "hcat_pid_dir" : "/var/run/webhcat",
>   "hive.metastore.heapsize" : "1024",
>   "hive.client.heapsize" : "512",
>   "hive_existing_mssql_server_host" : "hardcodedhostname.com",
>   "hcat_user" : "hcat",
>   "hive_ambari_database" : "MySQL",
>   "content" : "\n if [ \"$SERVICE\" = \"cli\" ]; then\n   {%...}
>   "hive_pid_dir" : "/var/run/hive",
>   "hive_existing_postgresql_host" : "hardcodedhostname.com",
>   "hive_database_type" : "mysql",
>   "hive_existing_mysql_host" : "hardcodedhostname.
> com"
> }



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

[jira] [Updated] (AMBARI-18140) Avoid hardcoded values in blueprint for hive and oozie

[Amruta Borkar (JIRA)]

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

Amruta Borkar updated AMBARI-18140:
---
Attachment: AMBARI-18140.patch

> Avoid hardcoded values in blueprint for hive and oozie
> --
>
> Key: AMBARI-18140
> URL: https://issues.apache.org/jira/browse/AMBARI-18140
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server, blueprints
>Affects Versions: 2.2.0
>Reporter: Amruta Borkar
>Assignee: Amruta Borkar
> Fix For: trunk
>
> Attachments: AMBARI-18140.patch
>
>
> There are a lot of hardcoded values in blueprint for hive.
> {
>   "hive-env" : {
> "properties_attributes" : { },
> "properties" : {
>   "hive_security_authorization" : "None",
>   "hive_log_dir" : "/var/log/hive",
>   "hive_existing_oracle_host" : "hardcodedhostname
> com",
>   "hive_user" : "hive",
>   "hive_existing_mssql_server_2_host" : "hardcodedhostname.com",
>   "hive.heapsize" : "1024",
>   "hcat_log_dir" : "/var/log/webhcat",
>   "hive_hostname" : "%HOSTGROUP::host_group_1%",
>   "hive_database" : "New MySQL Database",
>   "hive_exec_orc_storage_strategy" : "SPEED",
>   "hive_database_name" : "hive",
>   "webhcat_user" : "hcat",
>   "hive_txn_acid" : "off",
>   "hcat_pid_dir" : "/var/run/webhcat",
>   "hive.metastore.heapsize" : "1024",
>   "hive.client.heapsize" : "512",
>   "hive_existing_mssql_server_host" : "hardcodedhostname.com",
>   "hcat_user" : "hcat",
>   "hive_ambari_database" : "MySQL",
>   "content" : "\n if [ \"$SERVICE\" = \"cli\" ]; then\n   {%...}
>   "hive_pid_dir" : "/var/run/hive",
>   "hive_existing_postgresql_host" : "hardcodedhostname.com",
>   "hive_database_type" : "mysql",
>   "hive_existing_mysql_host" : "hardcodedhostname.
> com"
> }



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

[jira] [Updated] (AMBARI-18140) Avoid hardcoded values in blueprint for hive and oozie

[Amruta Borkar (JIRA)]

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

Amruta Borkar updated AMBARI-18140:
---
Attachment: (was: AMBARI-18140.patch)

> Avoid hardcoded values in blueprint for hive and oozie
> --
>
> Key: AMBARI-18140
> URL: https://issues.apache.org/jira/browse/AMBARI-18140
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server, blueprints
>Affects Versions: 2.2.0
>Reporter: Amruta Borkar
>Assignee: Amruta Borkar
> Fix For: trunk
>
> Attachments: AMBARI-18140.patch
>
>
> There are a lot of hardcoded values in blueprint for hive.
> {
>   "hive-env" : {
> "properties_attributes" : { },
> "properties" : {
>   "hive_security_authorization" : "None",
>   "hive_log_dir" : "/var/log/hive",
>   "hive_existing_oracle_host" : "hardcodedhostname
> com",
>   "hive_user" : "hive",
>   "hive_existing_mssql_server_2_host" : "hardcodedhostname.com",
>   "hive.heapsize" : "1024",
>   "hcat_log_dir" : "/var/log/webhcat",
>   "hive_hostname" : "%HOSTGROUP::host_group_1%",
>   "hive_database" : "New MySQL Database",
>   "hive_exec_orc_storage_strategy" : "SPEED",
>   "hive_database_name" : "hive",
>   "webhcat_user" : "hcat",
>   "hive_txn_acid" : "off",
>   "hcat_pid_dir" : "/var/run/webhcat",
>   "hive.metastore.heapsize" : "1024",
>   "hive.client.heapsize" : "512",
>   "hive_existing_mssql_server_host" : "hardcodedhostname.com",
>   "hcat_user" : "hcat",
>   "hive_ambari_database" : "MySQL",
>   "content" : "\n if [ \"$SERVICE\" = \"cli\" ]; then\n   {%...}
>   "hive_pid_dir" : "/var/run/hive",
>   "hive_existing_postgresql_host" : "hardcodedhostname.com",
>   "hive_database_type" : "mysql",
>   "hive_existing_mysql_host" : "hardcodedhostname.
> com"
> }



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

[jira] [Updated] (AMBARI-18140) Avoid hardcoded values in blueprint for hive and oozie

[Amruta Borkar (JIRA)]

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

Amruta Borkar updated AMBARI-18140:
---
Status: Open  (was: Patch Available)

> Avoid hardcoded values in blueprint for hive and oozie
> --
>
> Key: AMBARI-18140
> URL: https://issues.apache.org/jira/browse/AMBARI-18140
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server, blueprints
>Affects Versions: 2.2.0
>Reporter: Amruta Borkar
>Assignee: Amruta Borkar
> Fix For: trunk
>
> Attachments: AMBARI-18140.patch
>
>
> There are a lot of hardcoded values in blueprint for hive.
> {
>   "hive-env" : {
> "properties_attributes" : { },
> "properties" : {
>   "hive_security_authorization" : "None",
>   "hive_log_dir" : "/var/log/hive",
>   "hive_existing_oracle_host" : "hardcodedhostname
> com",
>   "hive_user" : "hive",
>   "hive_existing_mssql_server_2_host" : "hardcodedhostname.com",
>   "hive.heapsize" : "1024",
>   "hcat_log_dir" : "/var/log/webhcat",
>   "hive_hostname" : "%HOSTGROUP::host_group_1%",
>   "hive_database" : "New MySQL Database",
>   "hive_exec_orc_storage_strategy" : "SPEED",
>   "hive_database_name" : "hive",
>   "webhcat_user" : "hcat",
>   "hive_txn_acid" : "off",
>   "hcat_pid_dir" : "/var/run/webhcat",
>   "hive.metastore.heapsize" : "1024",
>   "hive.client.heapsize" : "512",
>   "hive_existing_mssql_server_host" : "hardcodedhostname.com",
>   "hcat_user" : "hcat",
>   "hive_ambari_database" : "MySQL",
>   "content" : "\n if [ \"$SERVICE\" = \"cli\" ]; then\n   {%...}
>   "hive_pid_dir" : "/var/run/hive",
>   "hive_existing_postgresql_host" : "hardcodedhostname.com",
>   "hive_database_type" : "mysql",
>   "hive_existing_mysql_host" : "hardcodedhostname.
> com"
> }



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

[jira] [Commented] (AMBARI-18110) Ambari unit tests for HAWQ are not being called

[Hudson (JIRA)]

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

Hudson commented on AMBARI-18110:
-

FAILURE: Integrated in Ambari-trunk-Commit #5518 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5518/])
AMBARI-18110: Ambari unit tests for HAWQ are not being called (lavjain) (ljain: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=5676cd0c946dc34468037b4996d5f1ce7fac20e0])
* ambari-server/src/test/python/common-services/PXF/test_pxf.py
* 
ambari-server/src/test/python/common-services/HAWQ/test_alert_component_status.py
* ambari-server/src/test/python/common-services/HAWQ/test_alert_sync_status.py
* ambari-server/src/test/python/common-services/PXF/test_service_advisor.py
* ambari-server/src/test/python/common-services/HAWQ/test_hawqsegment.py
* ambari-server/src/test/python/common-services/HAWQ/test_hawqstandby.py
* ambari-server/src/test/python/common-services/HAWQ/hawq_base_test_case.py
* ambari-server/src/test/python/common-services/HAWQ/test_hawqmaster.py
* ambari-server/src/test/python/common-services/PXF/test_alerts_api_status.py
* ambari-server/src/test/python/common-services/HAWQ/test_utils.py
* ambari-server/src/test/python/unitTests.py
* 
ambari-server/src/main/resources/common-services/HAWQ/2.0.0/package/scripts/common.py
* 
ambari-server/src/test/python/common-services/HAWQ/test_alert_segment_registration_status.py
* ambari-server/src/test/python/common-services/HAWQ/test_service_advisor.py


> Ambari unit tests for HAWQ are not being called
> ---
>
> Key: AMBARI-18110
> URL: https://issues.apache.org/jira/browse/AMBARI-18110
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk, 2.4.0
>Reporter: Lav Jain
>Assignee: Lav Jain
> Fix For: trunk, 2.4.0
>
> Attachments: AMBARI-18110.patch, AMBARI-18110.v2.patch, 
> AMBARI-18110.v3.patch
>
>
> Ambari build jobs are not running the unit tests for HAWQ.
> HAWQ (and PXF) unit tests in the new common-services directory under test is 
> being ignored during maven's test phase.



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

[jira] [Created] (AMBARI-18142) Define keytab/principal for Spark Thrift Server

[Jeff Zhang (JIRA)]

Jeff Zhang created AMBARI-18142:
---

 Summary: Define keytab/principal for Spark Thrift Server
 Key: AMBARI-18142
 URL: https://issues.apache.org/jira/browse/AMBARI-18142
 Project: Ambari
  Issue Type: Bug
Affects Versions: 2.4.0
Reporter: Jeff Zhang
Assignee: Jeff Zhang






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

[jira] [Commented] (AMBARI-18141) Display and export current cluster's blueprint from Ambari Admin view UI

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-18141:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12823521/blueprint%20sidebar%20item.png
  against trunk revision .

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

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

This message is automatically generated.

> Display and export current cluster's blueprint from Ambari Admin view UI
> 
>
> Key: AMBARI-18141
> URL: https://issues.apache.org/jira/browse/AMBARI-18141
> Project: Ambari
>  Issue Type: New Feature
>  Components: ambari-admin
>Affects Versions: trunk
>Reporter: Di Li
>Assignee: Di Li
> Fix For: trunk
>
> Attachments: AMBARI-18141.patch, blueprint sidebar item.png, view and 
> download blueprint.png
>
>
> This jira proposes a read-only view of the blueprint used by the current 
> cluster so that if user wants to deploy a cluster with the same (or similar) 
> configurations, they can save the blueprint directly from the Ambari admin 
> view UI instead of issuing rest api calls via command line.



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

[jira] [Commented] (AMBARI-18140) Avoid hardcoded values in blueprint for hive and oozie

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-18140:


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

{color:red}-1 patch{color}.  Top-level trunk compilation may be broken.

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

This message is automatically generated.

> Avoid hardcoded values in blueprint for hive and oozie
> --
>
> Key: AMBARI-18140
> URL: https://issues.apache.org/jira/browse/AMBARI-18140
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server, blueprints
>Affects Versions: 2.2.0
>Reporter: Amruta Borkar
>Assignee: Amruta Borkar
> Fix For: trunk
>
> Attachments: AMBARI-18140.patch
>
>
> There are a lot of hardcoded values in blueprint for hive.
> {
>   "hive-env" : {
> "properties_attributes" : { },
> "properties" : {
>   "hive_security_authorization" : "None",
>   "hive_log_dir" : "/var/log/hive",
>   "hive_existing_oracle_host" : "hardcodedhostname
> com",
>   "hive_user" : "hive",
>   "hive_existing_mssql_server_2_host" : "hardcodedhostname.com",
>   "hive.heapsize" : "1024",
>   "hcat_log_dir" : "/var/log/webhcat",
>   "hive_hostname" : "%HOSTGROUP::host_group_1%",
>   "hive_database" : "New MySQL Database",
>   "hive_exec_orc_storage_strategy" : "SPEED",
>   "hive_database_name" : "hive",
>   "webhcat_user" : "hcat",
>   "hive_txn_acid" : "off",
>   "hcat_pid_dir" : "/var/run/webhcat",
>   "hive.metastore.heapsize" : "1024",
>   "hive.client.heapsize" : "512",
>   "hive_existing_mssql_server_host" : "hardcodedhostname.com",
>   "hcat_user" : "hcat",
>   "hive_ambari_database" : "MySQL",
>   "content" : "\n if [ \"$SERVICE\" = \"cli\" ]; then\n   {%...}
>   "hive_pid_dir" : "/var/run/hive",
>   "hive_existing_postgresql_host" : "hardcodedhostname.com",
>   "hive_database_type" : "mysql",
>   "hive_existing_mysql_host" : "hardcodedhostname.
> com"
> }



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

[jira] [Updated] (AMBARI-18140) Avoid hardcoded values in blueprint for hive and oozie

[Amruta Borkar (JIRA)]

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

Amruta Borkar updated AMBARI-18140:
---
Status: Patch Available  (was: In Progress)

The given patch replaces host name with host_name reference, if the external 
host is not assigned, there by avoiding harcoded hostnames

> Avoid hardcoded values in blueprint for hive and oozie
> --
>
> Key: AMBARI-18140
> URL: https://issues.apache.org/jira/browse/AMBARI-18140
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server, blueprints
>Affects Versions: 2.2.0
>Reporter: Amruta Borkar
>Assignee: Amruta Borkar
> Fix For: trunk
>
> Attachments: AMBARI-18140.patch
>
>
> There are a lot of hardcoded values in blueprint for hive.
> {
>   "hive-env" : {
> "properties_attributes" : { },
> "properties" : {
>   "hive_security_authorization" : "None",
>   "hive_log_dir" : "/var/log/hive",
>   "hive_existing_oracle_host" : "hardcodedhostname
> com",
>   "hive_user" : "hive",
>   "hive_existing_mssql_server_2_host" : "hardcodedhostname.com",
>   "hive.heapsize" : "1024",
>   "hcat_log_dir" : "/var/log/webhcat",
>   "hive_hostname" : "%HOSTGROUP::host_group_1%",
>   "hive_database" : "New MySQL Database",
>   "hive_exec_orc_storage_strategy" : "SPEED",
>   "hive_database_name" : "hive",
>   "webhcat_user" : "hcat",
>   "hive_txn_acid" : "off",
>   "hcat_pid_dir" : "/var/run/webhcat",
>   "hive.metastore.heapsize" : "1024",
>   "hive.client.heapsize" : "512",
>   "hive_existing_mssql_server_host" : "hardcodedhostname.com",
>   "hcat_user" : "hcat",
>   "hive_ambari_database" : "MySQL",
>   "content" : "\n if [ \"$SERVICE\" = \"cli\" ]; then\n   {%...}
>   "hive_pid_dir" : "/var/run/hive",
>   "hive_existing_postgresql_host" : "hardcodedhostname.com",
>   "hive_database_type" : "mysql",
>   "hive_existing_mysql_host" : "hardcodedhostname.
> com"
> }



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

[jira] [Updated] (AMBARI-18140) Avoid hardcoded values in blueprint for hive and oozie

[Amruta Borkar (JIRA)]

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

Amruta Borkar updated AMBARI-18140:
---
Attachment: AMBARI-18140.patch

> Avoid hardcoded values in blueprint for hive and oozie
> --
>
> Key: AMBARI-18140
> URL: https://issues.apache.org/jira/browse/AMBARI-18140
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server, blueprints
>Affects Versions: 2.2.0
>Reporter: Amruta Borkar
>Assignee: Amruta Borkar
> Fix For: trunk
>
> Attachments: AMBARI-18140.patch
>
>
> There are a lot of hardcoded values in blueprint for hive.
> {
>   "hive-env" : {
> "properties_attributes" : { },
> "properties" : {
>   "hive_security_authorization" : "None",
>   "hive_log_dir" : "/var/log/hive",
>   "hive_existing_oracle_host" : "hardcodedhostname
> com",
>   "hive_user" : "hive",
>   "hive_existing_mssql_server_2_host" : "hardcodedhostname.com",
>   "hive.heapsize" : "1024",
>   "hcat_log_dir" : "/var/log/webhcat",
>   "hive_hostname" : "%HOSTGROUP::host_group_1%",
>   "hive_database" : "New MySQL Database",
>   "hive_exec_orc_storage_strategy" : "SPEED",
>   "hive_database_name" : "hive",
>   "webhcat_user" : "hcat",
>   "hive_txn_acid" : "off",
>   "hcat_pid_dir" : "/var/run/webhcat",
>   "hive.metastore.heapsize" : "1024",
>   "hive.client.heapsize" : "512",
>   "hive_existing_mssql_server_host" : "hardcodedhostname.com",
>   "hcat_user" : "hcat",
>   "hive_ambari_database" : "MySQL",
>   "content" : "\n if [ \"$SERVICE\" = \"cli\" ]; then\n   {%...}
>   "hive_pid_dir" : "/var/run/hive",
>   "hive_existing_postgresql_host" : "hardcodedhostname.com",
>   "hive_database_type" : "mysql",
>   "hive_existing_mysql_host" : "hardcodedhostname.
> com"
> }



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

[jira] [Updated] (AMBARI-18140) Avoid hardcoded values in blueprint for hive and oozie

[Amruta Borkar (JIRA)]

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

Amruta Borkar updated AMBARI-18140:
---
Fix Version/s: (was: 2.2.0)

> Avoid hardcoded values in blueprint for hive and oozie
> --
>
> Key: AMBARI-18140
> URL: https://issues.apache.org/jira/browse/AMBARI-18140
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server, blueprints
>Affects Versions: 2.2.0
>Reporter: Amruta Borkar
>Assignee: Amruta Borkar
> Fix For: trunk
>
>
> There are a lot of hardcoded values in blueprint for hive.
> {
>   "hive-env" : {
> "properties_attributes" : { },
> "properties" : {
>   "hive_security_authorization" : "None",
>   "hive_log_dir" : "/var/log/hive",
>   "hive_existing_oracle_host" : "hardcodedhostname
> com",
>   "hive_user" : "hive",
>   "hive_existing_mssql_server_2_host" : "hardcodedhostname.com",
>   "hive.heapsize" : "1024",
>   "hcat_log_dir" : "/var/log/webhcat",
>   "hive_hostname" : "%HOSTGROUP::host_group_1%",
>   "hive_database" : "New MySQL Database",
>   "hive_exec_orc_storage_strategy" : "SPEED",
>   "hive_database_name" : "hive",
>   "webhcat_user" : "hcat",
>   "hive_txn_acid" : "off",
>   "hcat_pid_dir" : "/var/run/webhcat",
>   "hive.metastore.heapsize" : "1024",
>   "hive.client.heapsize" : "512",
>   "hive_existing_mssql_server_host" : "hardcodedhostname.com",
>   "hcat_user" : "hcat",
>   "hive_ambari_database" : "MySQL",
>   "content" : "\n if [ \"$SERVICE\" = \"cli\" ]; then\n   {%...}
>   "hive_pid_dir" : "/var/run/hive",
>   "hive_existing_postgresql_host" : "hardcodedhostname.com",
>   "hive_database_type" : "mysql",
>   "hive_existing_mysql_host" : "hardcodedhostname.
> com"
> }



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

[jira] [Resolved] (AMBARI-18094) Oozie server failed to start with NoClassDefFoundError: org/apache/oozie/cli/CLIParser

[Vivek Rathod (JIRA)]

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

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

> Oozie server failed to start with NoClassDefFoundError: 
> org/apache/oozie/cli/CLIParser
> --
>
> Key: AMBARI-18094
> URL: https://issues.apache.org/jira/browse/AMBARI-18094
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.4.0
> Environment: ambari-server-2.4.0.0-1121.x86_64
> ambari-agent-2.4.0.0-1121.x86_64
> Ambari DB: :MariaDB
> Oozie/Hive DB: MariaDB/MariaDB
> Security:no
> Security Type:MIT/MIT
> Blueprints: false
> Umask: 
> JDK: OracleJDK7
> OS: CentOS 7
>Reporter: Vivek Rathod
>Priority: Critical
> Fix For: 2.4.0
>
>
> Install cluster with HDFS, Yarn, MR and ZK, and then add
> {hive,tez,piz}
> and then
> {oozie,hbase,sqoop}
> Oozie server fails to start on adding oozie. 
> {code}
> Traceback (most recent call last):
>   File 
> "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_server.py",
>  line 215, in 
> OozieServer().execute()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 280, in execute
> method(env)
>   File 
> "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_server.py",
>  line 95, in start
> oozie_service(action='start', upgrade_type=upgrade_type)
>   File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py", 
> line 89, in thunk
> return fn(*args, **kwargs)
>   File 
> "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_service.py",
>  line 131, in oozie_service
> path = params.execute_path 
>   File "/usr/lib/python2.6/site-packages/resource_management/core/base.py", 
> line 155, in __init__
> self.env.run()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
> line 160, in run
> self.run_action(resource, action)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
> line 124, in run_action
> provider_action()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
>  line 273, in action_run
> tries=self.resource.tries, try_sleep=self.resource.try_sleep)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 71, in inner
> result = function(command, **kwargs)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 93, in checked_call
> tries=tries, try_sleep=try_sleep)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 141, in _call_wrapper
> result = _call(command, **kwargs_copy)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 294, in _call
> raise Fail(err_msg)
> resource_management.core.exceptions.Fail: Execution of 
> '/usr/hdp/current/oozie-server/bin/oozie-setup.sh sharelib create -fs 
> hdfs://nat-r7-ifu-ambari-serv-2-1.openstacklocal:8020 -locallib 
> /usr/hdp/current/oozie-server/share' returned 1.  Hortonworks 
> #
> This is MOTD message, added for testing in qe infra
>   setting OOZIE_CONFIG=${OOZIE_CONFIG:-/usr/hdp/current/oozie-server/conf}
>   setting 
> CATALINA_BASE=${CATALINA_BASE:-/usr/hdp/current/oozie-server/oozie-server}
>   setting CATALINA_TMPDIR=${CATALINA_TMPDIR:-/var/tmp/oozie}
>   setting OOZIE_CATALINA_HOME=/usr/lib/bigtop-tomcat
>   setting JAVA_HOME=/usr/jdk64/jdk1.8.0_60
>   setting JRE_HOME=${JAVA_HOME}
>   setting CATALINA_OPTS="$CATALINA_OPTS -Xmx2048m"
>   setting OOZIE_LOG=/grid/0/log/oozie
>   setting CATALINA_PID=/var/run/oozie/oozie.pid
>   setting OOZIE_DATA=/grid/0/hadoop/oozie/data
>   setting OOZIE_HTTP_PORT=11000
>   setting OOZIE_ADMIN_PORT=11001
>   setting 
> JAVA_LIBRARY_PATH=/usr/hdp/current/hadoop-client/lib/native/Linux-amd64-64
>   setting OOZIE_CLIENT_OPTS="${OOZIE_CLIENT_OPTS} 
> -Doozie.connection.retry.count=5 "
>   setting OOZIE_CONFIG=${OOZIE_CONFIG:-/usr/hdp/current/oozie-server/conf}
>   setting 
> CATALINA_BASE=${CATALINA_BASE:-/usr/hdp/current/oozie-server/oozie-server}
>   setting CATALINA_TMPDIR=${CATALINA_TMPDIR:-/var/tmp/oozie}
>   setting OOZIE_CATALINA_HOME=/usr/lib/bigtop-tomcat
>   setting JAVA_HOME=/usr/jdk64/jdk1.8.0_60
>   setting JRE_HOME=${JAVA_HOME}
>   setting CATALINA_OPTS="$CATALINA_OPTS -Xmx2048m"
>   setting OOZIE_LOG=/grid/0/log/oozie
>   setting CATALINA_PID=/var/run/oozie/oozie.pid
>   setting OOZIE_DATA=/grid/0/hadoop/oozie/data
>   setting OOZIE_HTTP_PORT=11000
>   setting OOZIE_ADMIN_PORT=11001
>   setting 
> JAVA_LIBRARY_PATH=/usr/hdp/current/hadoop-client/lib/native/Linux-amd64-64
>   setting 

[jira] [Commented] (AMBARI-18110) Ambari unit tests for HAWQ are not being called

[Lav Jain (JIRA)]

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

Lav Jain commented on AMBARI-18110:
---

BRANCH-2.4
commit 85c97e3a7f3db4d85fc01a82e7286c4c45fdb99a
Author: Lav Jain 
Fri, 12 Aug 2016 14:34:47 -0700 (14:34 -0700)

TRUNK
commit 5676cd0c946dc34468037b4996d5f1ce7fac20e0
Author: Lav Jain 
Fri, 12 Aug 2016 14:36:04 -0700 (14:36 -0700)

> Ambari unit tests for HAWQ are not being called
> ---
>
> Key: AMBARI-18110
> URL: https://issues.apache.org/jira/browse/AMBARI-18110
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk, 2.4.0
>Reporter: Lav Jain
>Assignee: Lav Jain
> Fix For: trunk, 2.4.0
>
> Attachments: AMBARI-18110.patch, AMBARI-18110.v2.patch, 
> AMBARI-18110.v3.patch
>
>
> Ambari build jobs are not running the unit tests for HAWQ.
> HAWQ (and PXF) unit tests in the new common-services directory under test is 
> being ignored during maven's test phase.



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

[jira] [Updated] (AMBARI-18110) Ambari unit tests for HAWQ are not being called

[Lav Jain (JIRA)]

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

Lav Jain updated AMBARI-18110:
--
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Ambari unit tests for HAWQ are not being called
> ---
>
> Key: AMBARI-18110
> URL: https://issues.apache.org/jira/browse/AMBARI-18110
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk, 2.4.0
>Reporter: Lav Jain
>Assignee: Lav Jain
> Fix For: trunk, 2.4.0
>
> Attachments: AMBARI-18110.patch, AMBARI-18110.v2.patch, 
> AMBARI-18110.v3.patch
>
>
> Ambari build jobs are not running the unit tests for HAWQ.
> HAWQ (and PXF) unit tests in the new common-services directory under test is 
> being ignored during maven's test phase.



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

[jira] [Updated] (AMBARI-18110) Ambari unit tests for HAWQ are not being called

[Lav Jain (JIRA)]

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

Lav Jain updated AMBARI-18110:
--
Attachment: AMBARI-18110.v3.patch

> Ambari unit tests for HAWQ are not being called
> ---
>
> Key: AMBARI-18110
> URL: https://issues.apache.org/jira/browse/AMBARI-18110
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk, 2.4.0
>Reporter: Lav Jain
>Assignee: Lav Jain
> Fix For: trunk, 2.4.0
>
> Attachments: AMBARI-18110.patch, AMBARI-18110.v2.patch, 
> AMBARI-18110.v3.patch
>
>
> Ambari build jobs are not running the unit tests for HAWQ.
> HAWQ (and PXF) unit tests in the new common-services directory under test is 
> being ignored during maven's test phase.



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

[jira] [Commented] (AMBARI-17984) Integrate Cassandra with Ambari

[Amey (JIRA)]

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

Amey commented on AMBARI-17984:
---

working on it
assign this to me whoever can.

> Integrate Cassandra with Ambari
> ---
>
> Key: AMBARI-17984
> URL: https://issues.apache.org/jira/browse/AMBARI-17984
> Project: Ambari
>  Issue Type: New Feature
>  Components: ambari-server
>Reporter: saurabh mishra
>  Labels: cassandra
>
> Integrate Cassandra with Ambari
> Custom service for Cassandra already exists which can be integrated into 
> ambari.
> https://github.com/Symantec/ambari-cassandra-service



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

[jira] [Commented] (AMBARI-18130) Atlas hooks to include atlas.rest.address config, allow editing in the UI, and compute value using all Atlas Servers

[Hudson (JIRA)]

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

Hudson commented on AMBARI-18130:
-

FAILURE: Integrated in Ambari-trunk-Commit #5517 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5517/])
AMBARI-18130. Atlas hooks to include atlas.rest.address config, allow 
(afernandez: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=c08cbff6ee1e734620472d8edc1c659e4938c01b])
* 
ambari-common/src/main/python/resource_management/libraries/functions/setup_atlas_hook.py
* 
ambari-server/src/main/resources/common-services/ATLAS/0.7.0.2.5/configuration/application-properties.xml
* ambari-server/src/main/resources/stacks/HDP/2.5/services/stack_advisor.py


> Atlas hooks to include atlas.rest.address config, allow editing in the UI, 
> and compute value using all Atlas Servers
> 
>
> Key: AMBARI-18130
> URL: https://issues.apache.org/jira/browse/AMBARI-18130
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.4.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 2.4.0
>
> Attachments: AMBARI-18130.patch
>
>
> For all of the Atlas hook files (atlas-application.properties), the config 
> atlas.rest.address needs to be added.
> Further, whenever Atlas topology changes (add/move/delete a server), the 
> atlas.rest.address will need to change. However, we have no mechanism of 
> recalculating this from the UI, so instead, allow the property to be editable 
> from the UI for the time being.
> Lastly, the current value of atlas.rest.address is incorrect; it should be 
> csv of http(s):$server:$port from all of the servers.



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

[jira] [Commented] (AMBARI-18136) Falcon service checks fail after RU from build to build upgrade for stack HDP-2.5

[Hudson (JIRA)]

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

Hudson commented on AMBARI-18136:
-

FAILURE: Integrated in Ambari-trunk-Commit #5517 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5517/])
AMBARI-18136. Falcon service checks fail after RU from build to build 
(smohanty: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=ba6482fadb5dbb4d193a326e1a9ac3d8485b0d43])
* ambari-server/src/main/resources/common-services/FALCON/0.5.0.2.1/metainfo.xml


> Falcon service checks fail after RU from build to build upgrade for stack 
> HDP-2.5
> -
>
> Key: AMBARI-18136
> URL: https://issues.apache.org/jira/browse/AMBARI-18136
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Shreya Bhat
>Assignee: Sumit Mohanty
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-18136.patch
>
>
> Stderr : 
> {code}
> "stderr" : "Traceback (most recent call last):\n  File 
> \"/var/lib/ambari-agent/cache/common-services/FALCON/0.5.0.2.1/package/scripts/service_check.py\",
>  line 53, in \nFalconServiceCheck().execute()\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\",
>  line 280, in execute\nmethod(env)\n  File 
> \"/var/lib/ambari-agent/cache/common-services/FALCON/0.5.0.2.1/package/scripts/service_check.py\",
>  line 40, in service_check\ntry_sleep = 20\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/base.py\", line 
> 155, in __init__\nself.env.run()\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\", 
> line 160, in run\nself.run_action(resource, action)\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\", 
> line 124, in run_action\nprovider_action()\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py\",
>  line 273, in action_run\ntries=self.resource.tries, 
> try_sleep=self.resource.try_sleep)\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line 
> 71, in inner\nresult = function(command, **kwargs)\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line 
> 93, in checked_call\ntries=tries, try_sleep=try_sleep)\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line 
> 141, in _call_wrapper\nresult = _call(command, **kwargs_copy)\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line 
> 294, in _call\nraise 
> Fail(err_msg)\nresource_management.core.exceptions.Fail: Execution of 
> '/usr/hdp/current/falcon-client/bin/falcon admin -version' returned 255. 
> ERROR: Unable to initialize Falcon Client object. Cause : Could not 
> authenticate, Authentication failed, URL: 
> http://natr66-reos-erietoerienxtsec-r6-11.openstacklocal:15000/api/options?user.name=ambari-qa=ambari-qa,
>  status: 503, message: Service Unavailable",
> {code}



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

[jira] [Commented] (AMBARI-18128) Receiving Error "Cannot save settings" when trying to edit view settings.

[Hudson (JIRA)]

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

Hudson commented on AMBARI-18128:
-

FAILURE: Integrated in Ambari-trunk-Commit #5517 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5517/])
AMBARI-18128. Receiving Error 'Cannot save settings' when trying to edit 
(dipayan.bhowmick: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=9a4d1b1076ec7adbddde6ad82062755b271df106])
* 
contrib/views/capacity-scheduler/src/test/java/org/apache/ambari/view/capacityscheduler/PropertyValidatorTest.java
* contrib/views/capacity-scheduler/src/main/resources/view.xml
* 
contrib/views/hive-next/src/test/java/org/apache/ambari/view/hive2/JobExecutionTest.java
* 
contrib/views/hive-next/src/main/java/org/apache/ambari/view/hive2/PropertyValidator.java
* 
contrib/views/files/src/main/java/org/apache/ambari/view/filebrowser/PropertyValidator.java
* 
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog240.java
* 
contrib/views/hive-next/src/test/java/org/apache/ambari/view/hive2/ConnectionFailuresTest.java
* 
contrib/views/pig/src/main/java/org/apache/ambari/view/pig/PropertyValidator.java
* 
contrib/views/hive/src/main/java/org/apache/ambari/view/hive/PropertyValidator.java
* 
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ViewInstanceResourceProvider.java
* 
contrib/views/capacity-scheduler/src/main/java/org/apache/ambari/view/capacityscheduler/PropertyValidator.java


> Receiving Error "Cannot save settings" when trying to edit view settings.
> -
>
> Key: AMBARI-18128
> URL: https://issues.apache.org/jira/browse/AMBARI-18128
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.4.0
>Reporter: DIPAYAN BHOWMICK
>Assignee: DIPAYAN BHOWMICK
> Fix For: 2.4.0
>
> Attachments: AMBARI-18128.2.branch-2.4.patch
>
>
> PROBLEM: Receiving Error "Cannot save settings" when trying to edit view 
> settings. 
> IMPACT:  Customer not able to edit view after the fact. 
> STEPS TO REPRODUCE: 
> 1.  Create a new instance of a view and save
> 2. try to edit a the instance such as display name. 
> 3.  You should get stack like: 
> {code}
> Cannot save settings
> java.lang.IllegalArgumentException: 
> {"propertyResults":{"webhdfs.url":{"valid":false,"detail":"Must be valid 
> URL"},"hdfs.auth_to_local":{"valid":true,"detail":"OK"},"hdfs.umask-mode":{"valid":true,"detail":"OK"},"webhdfs.nameservices":{"valid":true,"detail":"OK"},"hive.transport.mode":{"valid":true,"detail":"OK"},"jobs.dir":{"valid":true,"detail":"OK"},"hive.http.port":{"valid":true,"detail":"OK"},"webhdfs.auth":{"valid":true,"detail":"OK"},"webhdfs.ha.namenode.rpc-address.nn2":{"valid":true,"detail":"OK"},"webhdfs.ha.namenode.rpc-address.nn1":{"valid":true,"detail":"OK"},"views.tez.instance":{"valid":true,"detail":"OK"},"yarn.resourcemanager.url":{"valid":true,"detail":"OK"},"scripts.settings.defaults-file":{"valid":true,"detail":"OK"},"webhdfs.ha.namenode.http-address.nn2":{"valid":true,"detail":"OK"},"webhdfs.client.failover.proxy.provider":{"valid":true,"detail":"OK"},"webhdfs.ha.namenode.http-address.nn1":{"valid":true,"detail":"OK"},"webhdfs.ha.namenodes.list":{"valid":true,"detail":"OK"},"hive.metastore.warehouse.dir":{"valid":true,"detail":"OK"},"hive.port":{"valid":true,"detail":"OK"},"hive.http.path":{"valid":true,"detail":"OK"},"scripts.dir":{"valid":true,"detail":"OK"},"webhdfs.
> {code}



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

[jira] [Updated] (AMBARI-18141) Display and export current cluster's blueprint from Ambari Admin view UI

[Di Li (JIRA)]

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

Di Li updated AMBARI-18141:
---
Attachment: blueprint sidebar item.png

> Display and export current cluster's blueprint from Ambari Admin view UI
> 
>
> Key: AMBARI-18141
> URL: https://issues.apache.org/jira/browse/AMBARI-18141
> Project: Ambari
>  Issue Type: New Feature
>  Components: ambari-admin
>Affects Versions: trunk
>Reporter: Di Li
>Assignee: Di Li
> Fix For: trunk
>
> Attachments: AMBARI-18141.patch, blueprint sidebar item.png, view and 
> download blueprint.png
>
>
> This jira proposes a read-only view of the blueprint used by the current 
> cluster so that if user wants to deploy a cluster with the same (or similar) 
> configurations, they can save the blueprint directly from the Ambari admin 
> view UI instead of issuing rest api calls via command line.



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

[jira] [Updated] (AMBARI-18141) Display and export current cluster's blueprint from Ambari Admin view UI

[Di Li (JIRA)]

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

Di Li updated AMBARI-18141:
---
Attachment: view and download blueprint.png

> Display and export current cluster's blueprint from Ambari Admin view UI
> 
>
> Key: AMBARI-18141
> URL: https://issues.apache.org/jira/browse/AMBARI-18141
> Project: Ambari
>  Issue Type: New Feature
>  Components: ambari-admin
>Affects Versions: trunk
>Reporter: Di Li
>Assignee: Di Li
> Fix For: trunk
>
> Attachments: AMBARI-18141.patch, view and download blueprint.png
>
>
> This jira proposes a read-only view of the blueprint used by the current 
> cluster so that if user wants to deploy a cluster with the same (or similar) 
> configurations, they can save the blueprint directly from the Ambari admin 
> view UI instead of issuing rest api calls via command line.



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

[jira] [Commented] (AMBARI-18141) Display and export current cluster's blueprint from Ambari Admin view UI

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-18141:


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

{color:red}-1 patch{color}.  Top-level trunk compilation may be broken.

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

This message is automatically generated.

> Display and export current cluster's blueprint from Ambari Admin view UI
> 
>
> Key: AMBARI-18141
> URL: https://issues.apache.org/jira/browse/AMBARI-18141
> Project: Ambari
>  Issue Type: New Feature
>  Components: ambari-admin
>Affects Versions: trunk
>Reporter: Di Li
>Assignee: Di Li
> Fix For: trunk
>
> Attachments: AMBARI-18141.patch
>
>
> This jira proposes a read-only view of the blueprint used by the current 
> cluster so that if user wants to deploy a cluster with the same (or similar) 
> configurations, they can save the blueprint directly from the Ambari admin 
> view UI instead of issuing rest api calls via command line.



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

[jira] [Updated] (AMBARI-18141) Display and export current cluster's blueprint from Ambari Admin view UI

[Di Li (JIRA)]

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

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

> Display and export current cluster's blueprint from Ambari Admin view UI
> 
>
> Key: AMBARI-18141
> URL: https://issues.apache.org/jira/browse/AMBARI-18141
> Project: Ambari
>  Issue Type: New Feature
>  Components: ambari-admin
>Affects Versions: trunk
>Reporter: Di Li
>Assignee: Di Li
> Fix For: trunk
>
> Attachments: AMBARI-18141.patch
>
>
> This jira proposes a read-only view of the blueprint used by the current 
> cluster so that if user wants to deploy a cluster with the same (or similar) 
> configurations, they can save the blueprint directly from the Ambari admin 
> view UI instead of issuing rest api calls via command line.



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

[jira] [Updated] (AMBARI-18141) Display and export current cluster's blueprint from Ambari Admin view UI

[Di Li (JIRA)]

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

Di Li updated AMBARI-18141:
---
Status: Patch Available  (was: Open)

> Display and export current cluster's blueprint from Ambari Admin view UI
> 
>
> Key: AMBARI-18141
> URL: https://issues.apache.org/jira/browse/AMBARI-18141
> Project: Ambari
>  Issue Type: New Feature
>  Components: ambari-admin
>Affects Versions: trunk
>Reporter: Di Li
>Assignee: Di Li
> Fix For: trunk
>
> Attachments: AMBARI-18141.patch
>
>
> This jira proposes a read-only view of the blueprint used by the current 
> cluster so that if user wants to deploy a cluster with the same (or similar) 
> configurations, they can save the blueprint directly from the Ambari admin 
> view UI instead of issuing rest api calls via command line.



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

[jira] [Commented] (AMBARI-18139) Oozie service check fails if set yarn.resourcemanager.address to the default from yarn-default.xml

[Hudson (JIRA)]

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

Hudson commented on AMBARI-18139:
-

FAILURE: Integrated in Ambari-trunk-Commit #5516 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5516/])
AMBARI-18139. Oozie service check fails if set (dlysnichenko: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=755c5eabc8eee9f8bd051efa340d8b56789984e8])
* 
ambari-server/src/main/resources/common-services/OOZIE/4.0.0.2.0/package/scripts/service_check.py
* ambari-server/src/test/python/stacks/2.0.6/OOZIE/test_oozie_service_check.py
* ambari-server/src/test/python/stacks/2.0.6/OOZIE/test_service_check.py


> Oozie service check fails if set yarn.resourcemanager.address to the default 
> from yarn-default.xml
> --
>
> Key: AMBARI-18139
> URL: https://issues.apache.org/jira/browse/AMBARI-18139
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Fix For: 2.4.0
>
> Attachments: AMBARI-18139.patch
>
>
> yarn-default.xml suggests to use $\{yarn.resourcemanager.hostname\}:8032 as 
> yarn.resourcemanager.address.
> But Oozie service check fails if value contains a substitution placeholder 
> '$\{yarn.resourcemanager.hostname\}'
> {noformat}
> resource_management.core.exceptions.Fail: Execution of 
> '/var/lib/ambari-agent/tmp/prepareOozieHdfsDirectories.sh 
> /usr/hdp/current/oozie-client/conf /usr/hdp/current/oozie-client/doc 
> /usr/hdp/current/hadoop-client/conf ${yarn.resourcemanager.hostname}:8050 
> hdfs://nameservice default' returned 1. /bin/bash: 
> ${yarn.resourcemanager.hostname}:8050: bad substitution
> {noformat}



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

[jira] [Updated] (AMBARI-18136) Falcon service checks fail after RU from build to build upgrade for stack HDP-2.5

[Sumit Mohanty (JIRA)]

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

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

committed to trunk and branch-2.4

> Falcon service checks fail after RU from build to build upgrade for stack 
> HDP-2.5
> -
>
> Key: AMBARI-18136
> URL: https://issues.apache.org/jira/browse/AMBARI-18136
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Shreya Bhat
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-18136.patch
>
>
> Stderr : 
> {code}
> "stderr" : "Traceback (most recent call last):\n  File 
> \"/var/lib/ambari-agent/cache/common-services/FALCON/0.5.0.2.1/package/scripts/service_check.py\",
>  line 53, in \nFalconServiceCheck().execute()\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\",
>  line 280, in execute\nmethod(env)\n  File 
> \"/var/lib/ambari-agent/cache/common-services/FALCON/0.5.0.2.1/package/scripts/service_check.py\",
>  line 40, in service_check\ntry_sleep = 20\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/base.py\", line 
> 155, in __init__\nself.env.run()\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\", 
> line 160, in run\nself.run_action(resource, action)\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\", 
> line 124, in run_action\nprovider_action()\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py\",
>  line 273, in action_run\ntries=self.resource.tries, 
> try_sleep=self.resource.try_sleep)\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line 
> 71, in inner\nresult = function(command, **kwargs)\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line 
> 93, in checked_call\ntries=tries, try_sleep=try_sleep)\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line 
> 141, in _call_wrapper\nresult = _call(command, **kwargs_copy)\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line 
> 294, in _call\nraise 
> Fail(err_msg)\nresource_management.core.exceptions.Fail: Execution of 
> '/usr/hdp/current/falcon-client/bin/falcon admin -version' returned 255. 
> ERROR: Unable to initialize Falcon Client object. Cause : Could not 
> authenticate, Authentication failed, URL: 
> http://natr66-reos-erietoerienxtsec-r6-11.openstacklocal:15000/api/options?user.name=ambari-qa=ambari-qa,
>  status: 503, message: Service Unavailable",
> {code}



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

[jira] [Updated] (AMBARI-18136) Falcon service checks fail after RU from build to build upgrade for stack HDP-2.5

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty updated AMBARI-18136:
---
Assignee: Sumit Mohanty

> Falcon service checks fail after RU from build to build upgrade for stack 
> HDP-2.5
> -
>
> Key: AMBARI-18136
> URL: https://issues.apache.org/jira/browse/AMBARI-18136
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Shreya Bhat
>Assignee: Sumit Mohanty
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-18136.patch
>
>
> Stderr : 
> {code}
> "stderr" : "Traceback (most recent call last):\n  File 
> \"/var/lib/ambari-agent/cache/common-services/FALCON/0.5.0.2.1/package/scripts/service_check.py\",
>  line 53, in \nFalconServiceCheck().execute()\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\",
>  line 280, in execute\nmethod(env)\n  File 
> \"/var/lib/ambari-agent/cache/common-services/FALCON/0.5.0.2.1/package/scripts/service_check.py\",
>  line 40, in service_check\ntry_sleep = 20\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/base.py\", line 
> 155, in __init__\nself.env.run()\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\", 
> line 160, in run\nself.run_action(resource, action)\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\", 
> line 124, in run_action\nprovider_action()\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py\",
>  line 273, in action_run\ntries=self.resource.tries, 
> try_sleep=self.resource.try_sleep)\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line 
> 71, in inner\nresult = function(command, **kwargs)\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line 
> 93, in checked_call\ntries=tries, try_sleep=try_sleep)\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line 
> 141, in _call_wrapper\nresult = _call(command, **kwargs_copy)\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line 
> 294, in _call\nraise 
> Fail(err_msg)\nresource_management.core.exceptions.Fail: Execution of 
> '/usr/hdp/current/falcon-client/bin/falcon admin -version' returned 255. 
> ERROR: Unable to initialize Falcon Client object. Cause : Could not 
> authenticate, Authentication failed, URL: 
> http://natr66-reos-erietoerienxtsec-r6-11.openstacklocal:15000/api/options?user.name=ambari-qa=ambari-qa,
>  status: 503, message: Service Unavailable",
> {code}



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

[jira] [Updated] (AMBARI-18136) Falcon service checks fail after RU from build to build upgrade for stack HDP-2.5

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty updated AMBARI-18136:
---
Status: Patch Available  (was: Open)

> Falcon service checks fail after RU from build to build upgrade for stack 
> HDP-2.5
> -
>
> Key: AMBARI-18136
> URL: https://issues.apache.org/jira/browse/AMBARI-18136
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Shreya Bhat
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-18136.patch
>
>
> Stderr : 
> {code}
> "stderr" : "Traceback (most recent call last):\n  File 
> \"/var/lib/ambari-agent/cache/common-services/FALCON/0.5.0.2.1/package/scripts/service_check.py\",
>  line 53, in \nFalconServiceCheck().execute()\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\",
>  line 280, in execute\nmethod(env)\n  File 
> \"/var/lib/ambari-agent/cache/common-services/FALCON/0.5.0.2.1/package/scripts/service_check.py\",
>  line 40, in service_check\ntry_sleep = 20\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/base.py\", line 
> 155, in __init__\nself.env.run()\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\", 
> line 160, in run\nself.run_action(resource, action)\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\", 
> line 124, in run_action\nprovider_action()\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py\",
>  line 273, in action_run\ntries=self.resource.tries, 
> try_sleep=self.resource.try_sleep)\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line 
> 71, in inner\nresult = function(command, **kwargs)\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line 
> 93, in checked_call\ntries=tries, try_sleep=try_sleep)\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line 
> 141, in _call_wrapper\nresult = _call(command, **kwargs_copy)\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line 
> 294, in _call\nraise 
> Fail(err_msg)\nresource_management.core.exceptions.Fail: Execution of 
> '/usr/hdp/current/falcon-client/bin/falcon admin -version' returned 255. 
> ERROR: Unable to initialize Falcon Client object. Cause : Could not 
> authenticate, Authentication failed, URL: 
> http://natr66-reos-erietoerienxtsec-r6-11.openstacklocal:15000/api/options?user.name=ambari-qa=ambari-qa,
>  status: 503, message: Service Unavailable",
> {code}



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

[jira] [Commented] (AMBARI-18136) Falcon service checks fail after RU from build to build upgrade for stack HDP-2.5

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty commented on AMBARI-18136:


mvn test -pl ambari-server -Dtest=PropertyConfigTest

Running org.apache.ambari.server.view.configuration.PropertyConfigTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.428 sec - in 
org.apache.ambari.server.view.configuration.PropertyConfigTest
Results :
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0

mvn clean test -pl ambari-agent,ambari-server -Dmaven.test.skip=true

[INFO] Rat check: Summary of files. Unapproved: 0 unknown: 0 generated: 0 
approved: 148 licence.
[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] Ambari Server . SUCCESS [1:32.543s]
[INFO] Ambari Agent .. SUCCESS [18.884s]
[INFO] 
[INFO] BUILD SUCCESS
[INFO] 

> Falcon service checks fail after RU from build to build upgrade for stack 
> HDP-2.5
> -
>
> Key: AMBARI-18136
> URL: https://issues.apache.org/jira/browse/AMBARI-18136
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Shreya Bhat
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-18136.patch
>
>
> Stderr : 
> {code}
> "stderr" : "Traceback (most recent call last):\n  File 
> \"/var/lib/ambari-agent/cache/common-services/FALCON/0.5.0.2.1/package/scripts/service_check.py\",
>  line 53, in \nFalconServiceCheck().execute()\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\",
>  line 280, in execute\nmethod(env)\n  File 
> \"/var/lib/ambari-agent/cache/common-services/FALCON/0.5.0.2.1/package/scripts/service_check.py\",
>  line 40, in service_check\ntry_sleep = 20\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/base.py\", line 
> 155, in __init__\nself.env.run()\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\", 
> line 160, in run\nself.run_action(resource, action)\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\", 
> line 124, in run_action\nprovider_action()\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py\",
>  line 273, in action_run\ntries=self.resource.tries, 
> try_sleep=self.resource.try_sleep)\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line 
> 71, in inner\nresult = function(command, **kwargs)\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line 
> 93, in checked_call\ntries=tries, try_sleep=try_sleep)\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line 
> 141, in _call_wrapper\nresult = _call(command, **kwargs_copy)\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line 
> 294, in _call\nraise 
> Fail(err_msg)\nresource_management.core.exceptions.Fail: Execution of 
> '/usr/hdp/current/falcon-client/bin/falcon admin -version' returned 255. 
> ERROR: Unable to initialize Falcon Client object. Cause : Could not 
> authenticate, Authentication failed, URL: 
> http://natr66-reos-erietoerienxtsec-r6-11.openstacklocal:15000/api/options?user.name=ambari-qa=ambari-qa,
>  status: 503, message: Service Unavailable",
> {code}



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

[jira] [Updated] (AMBARI-18128) Receiving Error "Cannot save settings" when trying to edit view settings.

[DIPAYAN BHOWMICK (JIRA)]

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

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

Committed to branch-2.4, trunk.

> Receiving Error "Cannot save settings" when trying to edit view settings.
> -
>
> Key: AMBARI-18128
> URL: https://issues.apache.org/jira/browse/AMBARI-18128
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.4.0
>Reporter: DIPAYAN BHOWMICK
>Assignee: DIPAYAN BHOWMICK
> Fix For: 2.4.0
>
> Attachments: AMBARI-18128.2.branch-2.4.patch
>
>
> PROBLEM: Receiving Error "Cannot save settings" when trying to edit view 
> settings. 
> IMPACT:  Customer not able to edit view after the fact. 
> STEPS TO REPRODUCE: 
> 1.  Create a new instance of a view and save
> 2. try to edit a the instance such as display name. 
> 3.  You should get stack like: 
> {code}
> Cannot save settings
> java.lang.IllegalArgumentException: 
> {"propertyResults":{"webhdfs.url":{"valid":false,"detail":"Must be valid 
> URL"},"hdfs.auth_to_local":{"valid":true,"detail":"OK"},"hdfs.umask-mode":{"valid":true,"detail":"OK"},"webhdfs.nameservices":{"valid":true,"detail":"OK"},"hive.transport.mode":{"valid":true,"detail":"OK"},"jobs.dir":{"valid":true,"detail":"OK"},"hive.http.port":{"valid":true,"detail":"OK"},"webhdfs.auth":{"valid":true,"detail":"OK"},"webhdfs.ha.namenode.rpc-address.nn2":{"valid":true,"detail":"OK"},"webhdfs.ha.namenode.rpc-address.nn1":{"valid":true,"detail":"OK"},"views.tez.instance":{"valid":true,"detail":"OK"},"yarn.resourcemanager.url":{"valid":true,"detail":"OK"},"scripts.settings.defaults-file":{"valid":true,"detail":"OK"},"webhdfs.ha.namenode.http-address.nn2":{"valid":true,"detail":"OK"},"webhdfs.client.failover.proxy.provider":{"valid":true,"detail":"OK"},"webhdfs.ha.namenode.http-address.nn1":{"valid":true,"detail":"OK"},"webhdfs.ha.namenodes.list":{"valid":true,"detail":"OK"},"hive.metastore.warehouse.dir":{"valid":true,"detail":"OK"},"hive.port":{"valid":true,"detail":"OK"},"hive.http.path":{"valid":true,"detail":"OK"},"scripts.dir":{"valid":true,"detail":"OK"},"webhdfs.
> {code}



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

[jira] [Updated] (AMBARI-18136) Falcon service checks fail after RU from build to build upgrade for stack HDP-2.5

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty updated AMBARI-18136:
---
Attachment: AMBARI-18136.patch

> Falcon service checks fail after RU from build to build upgrade for stack 
> HDP-2.5
> -
>
> Key: AMBARI-18136
> URL: https://issues.apache.org/jira/browse/AMBARI-18136
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Shreya Bhat
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-18136.patch
>
>
> Stderr : 
> {code}
> "stderr" : "Traceback (most recent call last):\n  File 
> \"/var/lib/ambari-agent/cache/common-services/FALCON/0.5.0.2.1/package/scripts/service_check.py\",
>  line 53, in \nFalconServiceCheck().execute()\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\",
>  line 280, in execute\nmethod(env)\n  File 
> \"/var/lib/ambari-agent/cache/common-services/FALCON/0.5.0.2.1/package/scripts/service_check.py\",
>  line 40, in service_check\ntry_sleep = 20\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/base.py\", line 
> 155, in __init__\nself.env.run()\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\", 
> line 160, in run\nself.run_action(resource, action)\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\", 
> line 124, in run_action\nprovider_action()\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py\",
>  line 273, in action_run\ntries=self.resource.tries, 
> try_sleep=self.resource.try_sleep)\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line 
> 71, in inner\nresult = function(command, **kwargs)\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line 
> 93, in checked_call\ntries=tries, try_sleep=try_sleep)\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line 
> 141, in _call_wrapper\nresult = _call(command, **kwargs_copy)\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line 
> 294, in _call\nraise 
> Fail(err_msg)\nresource_management.core.exceptions.Fail: Execution of 
> '/usr/hdp/current/falcon-client/bin/falcon admin -version' returned 255. 
> ERROR: Unable to initialize Falcon Client object. Cause : Could not 
> authenticate, Authentication failed, URL: 
> http://natr66-reos-erietoerienxtsec-r6-11.openstacklocal:15000/api/options?user.name=ambari-qa=ambari-qa,
>  status: 503, message: Service Unavailable",
> {code}



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

[jira] [Created] (AMBARI-18141) Display and export current cluster's blueprint from Ambari Admin view UI

[Di Li (JIRA)]

Di Li created AMBARI-18141:
--

 Summary: Display and export current cluster's blueprint from 
Ambari Admin view UI
 Key: AMBARI-18141
 URL: https://issues.apache.org/jira/browse/AMBARI-18141
 Project: Ambari
  Issue Type: New Feature
  Components: ambari-admin
Affects Versions: trunk
Reporter: Di Li
Assignee: Di Li
 Fix For: trunk


This jira proposes a read-only view of the blueprint used by the current 
cluster so that if user wants to deploy a cluster with the same (or similar) 
configurations, they can save the blueprint directly from the Ambari admin view 
UI instead of issuing rest api calls via command line.



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

[jira] [Commented] (AMBARI-18136) Falcon service checks fail after RU from build to build upgrade for stack HDP-2.5

[Swapan Shridhar (JIRA)]

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

Swapan Shridhar commented on AMBARI-18136:
--

+1 for the patch .

> Falcon service checks fail after RU from build to build upgrade for stack 
> HDP-2.5
> -
>
> Key: AMBARI-18136
> URL: https://issues.apache.org/jira/browse/AMBARI-18136
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Shreya Bhat
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-18136.patch
>
>
> Stderr : 
> {code}
> "stderr" : "Traceback (most recent call last):\n  File 
> \"/var/lib/ambari-agent/cache/common-services/FALCON/0.5.0.2.1/package/scripts/service_check.py\",
>  line 53, in \nFalconServiceCheck().execute()\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\",
>  line 280, in execute\nmethod(env)\n  File 
> \"/var/lib/ambari-agent/cache/common-services/FALCON/0.5.0.2.1/package/scripts/service_check.py\",
>  line 40, in service_check\ntry_sleep = 20\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/base.py\", line 
> 155, in __init__\nself.env.run()\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\", 
> line 160, in run\nself.run_action(resource, action)\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\", 
> line 124, in run_action\nprovider_action()\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py\",
>  line 273, in action_run\ntries=self.resource.tries, 
> try_sleep=self.resource.try_sleep)\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line 
> 71, in inner\nresult = function(command, **kwargs)\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line 
> 93, in checked_call\ntries=tries, try_sleep=try_sleep)\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line 
> 141, in _call_wrapper\nresult = _call(command, **kwargs_copy)\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line 
> 294, in _call\nraise 
> Fail(err_msg)\nresource_management.core.exceptions.Fail: Execution of 
> '/usr/hdp/current/falcon-client/bin/falcon admin -version' returned 255. 
> ERROR: Unable to initialize Falcon Client object. Cause : Could not 
> authenticate, Authentication failed, URL: 
> http://natr66-reos-erietoerienxtsec-r6-11.openstacklocal:15000/api/options?user.name=ambari-qa=ambari-qa,
>  status: 503, message: Service Unavailable",
> {code}



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

[jira] [Updated] (AMBARI-18136) Falcon service checks fail after RU from build to build upgrade for stack HDP-2.5

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty updated AMBARI-18136:
---
Summary: Falcon service checks fail after RU from build to build upgrade 
for stack HDP-2.5  (was: Falcon service checks fail after RU from erie to erie)

> Falcon service checks fail after RU from build to build upgrade for stack 
> HDP-2.5
> -
>
> Key: AMBARI-18136
> URL: https://issues.apache.org/jira/browse/AMBARI-18136
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Shreya Bhat
>Priority: Critical
> Fix For: 2.4.0
>
>
> Stderr : 
> {code}
> "stderr" : "Traceback (most recent call last):\n  File 
> \"/var/lib/ambari-agent/cache/common-services/FALCON/0.5.0.2.1/package/scripts/service_check.py\",
>  line 53, in \nFalconServiceCheck().execute()\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\",
>  line 280, in execute\nmethod(env)\n  File 
> \"/var/lib/ambari-agent/cache/common-services/FALCON/0.5.0.2.1/package/scripts/service_check.py\",
>  line 40, in service_check\ntry_sleep = 20\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/base.py\", line 
> 155, in __init__\nself.env.run()\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\", 
> line 160, in run\nself.run_action(resource, action)\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\", 
> line 124, in run_action\nprovider_action()\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py\",
>  line 273, in action_run\ntries=self.resource.tries, 
> try_sleep=self.resource.try_sleep)\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line 
> 71, in inner\nresult = function(command, **kwargs)\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line 
> 93, in checked_call\ntries=tries, try_sleep=try_sleep)\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line 
> 141, in _call_wrapper\nresult = _call(command, **kwargs_copy)\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line 
> 294, in _call\nraise 
> Fail(err_msg)\nresource_management.core.exceptions.Fail: Execution of 
> '/usr/hdp/current/falcon-client/bin/falcon admin -version' returned 255. 
> ERROR: Unable to initialize Falcon Client object. Cause : Could not 
> authenticate, Authentication failed, URL: 
> http://natr66-reos-erietoerienxtsec-r6-11.openstacklocal:15000/api/options?user.name=ambari-qa=ambari-qa,
>  status: 503, message: Service Unavailable",
> {code}



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

[jira] [Resolved] (AMBARI-18129) Mask trust-store password returned in plain-text by API call

[Sangeeta Ravindran (JIRA)]

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

Sangeeta Ravindran resolved AMBARI-18129.
-
Resolution: Invalid

Specifying ambari-server setup-security option 2 encrypts passwords in the 
ambari.properties file

> Mask trust-store password returned in plain-text by API call
> 
>
> Key: AMBARI-18129
> URL: https://issues.apache.org/jira/browse/AMBARI-18129
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk
>Reporter: Sangeeta Ravindran
>Assignee: Sangeeta Ravindran
>
> If a trustore has been configured for Ambari Server, the SSL truststore 
> password is returned in plain text by the following api call:
> https:///api/v1/services/AMBARI/components/AMBARI_SERVER
> Sample output:
> {
>   "href" : 
> "https://:/api/v1/services/AMBARI/components/AMBARI_SERVER",
>   "RootServiceComponents" : {
> "component_name" : "AMBARI_SERVER",
> "component_version" : "2.4.0.0",
> "server_clock" : 1470943672,
> "service_name" : "AMBARI",
> "properties" : {
>   "agent.package.install.task.timeout" : "1800",
>   "agent.stack.retry.on_repo_unavailability" : "false",
>   "agent.stack.retry.tries" : "5",
>   "agent.task.timeout" : "900",
>   "agent.threadpool.size.max" : "25",
>   "ambari-server.user" : "root",
>   "ambari.python.wrap" : "ambari-python-wrap",
>   "api.ssl" : "true",
>   "bootstrap.dir" : "/var/run/ambari-server/bootstrap",
>   "bootstrap.script" : 
> "/usr/lib/python2.6/site-packages/ambari_server/bootstrap.py",
>   "bootstrap.setup_agent.script" : 
> "/usr/lib/python2.6/site-packages/ambari_server/setupAgent.py",
>   "check_database_skipped" : "false",
>   "client.api.port" : "8081",
>   "client.api.ssl.cert_name" : "https.crt",
>   "client.api.ssl.key_name" : "https.key",
>   "client.api.ssl.port" : "",
>   "client.threadpool.size.max" : "25",
>   "common.services.path" : 
> "/var/lib/ambari-server/resources/common-services",
>   "custom.action.definitions" : 
> "/var/lib/ambari-server/resources/custom_action_definitions",
>   "extensions.path" : "/var/lib/ambari-server/resources/extensions",
>   "http.strict-transport-security" : "max-age=31536000",
>   "http.x-frame-options" : "DENY",
>   "http.x-xss-protection" : "1; mode=block",
>   "java.home" : "/usr/jdk64/jdk1.8.0_60",
>   "java.releases" : "jdk1.8,jdk1.7",
>   "java.version" : "1.8",
>   "jce.download.supported" : "true",
>   "jce.name" : "jce_policy-8.zip",
>   "jdk.download.supported" : "true",
>   "jdk.name" : "jdk-8u60-linux-x64.tar.gz",
>   "jdk1.7.desc" : "Oracle JDK 1.7 + Java Cryptography Extension (JCE) 
> Policy Files 7",
>   "jdk1.7.dest-file" : "jdk-7u67-linux-x64.tar.gz",
>   "jdk1.7.home" : "/usr/jdk64/",
>   "jdk1.7.jcpol-file" : "UnlimitedJCEPolicyJDK7.zip",
>   "jdk1.7.jcpol-url" : 
> "http://public-repo-1.hortonworks.com/ARTIFACTS/UnlimitedJCEPolicyJDK7.zip;,
>   "jdk1.7.re" : "(jdk.*)/jre",
>   "jdk1.7.url" : 
> "http://public-repo-1.hortonworks.com/ARTIFACTS/jdk-7u67-linux-x64.tar.gz;,
>   "jdk1.8.desc" : "Oracle JDK 1.8 + Java Cryptography Extension (JCE) 
> Policy Files 8",
>   "jdk1.8.dest-file" : "jdk-8u60-linux-x64.tar.gz",
>   "jdk1.8.home" : "/usr/jdk64/",
>   "jdk1.8.jcpol-file" : "jce_policy-8.zip",
>   "jdk1.8.jcpol-url" : 
> "http://public-repo-1.hortonworks.com/ARTIFACTS/jce_policy-8.zip;,
>   "jdk1.8.re" : "(jdk.*)/jre",
>   "jdk1.8.url" : 
> "http://public-repo-1.hortonworks.com/ARTIFACTS/jdk-8u60-linux-x64.tar.gz;,
>   "jdk_location" : "https://:/resources/",
>   "kerberos.keytab.cache.dir" : "/var/lib/ambari-server/data/cache",
>   "metadata.path" : "/var/lib/ambari-server/resources/stacks",
>   "mpacks.staging.path" : "/var/lib/ambari-server/resources/mpacks",
>   "pid.dir" : "/var/run/ambari-server",
>   "recommendations.artifacts.lifetime" : "1w",
>   "recommendations.dir" : "/var/run/ambari-server/stack-recommendations",
>   "resources.dir" : "/var/lib/ambari-server/resources",
>   "rolling.upgrade.skip.packages.prefixes" : "",
>   "security.server.disabled.ciphers" : 
> 

[jira] [Updated] (AMBARI-18130) Atlas hooks to include atlas.rest.address config, allow editing in the UI, and compute value using all Atlas Servers

[Alejandro Fernandez (JIRA)]

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

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

Pushed to trunk, commit c08cbff6ee1e734620472d8edc1c659e4938c01b
branch-2.4, commit 1719c9034bfd448932b9905c083d260281865aaf

> Atlas hooks to include atlas.rest.address config, allow editing in the UI, 
> and compute value using all Atlas Servers
> 
>
> Key: AMBARI-18130
> URL: https://issues.apache.org/jira/browse/AMBARI-18130
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.4.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 2.4.0
>
> Attachments: AMBARI-18130.patch
>
>
> For all of the Atlas hook files (atlas-application.properties), the config 
> atlas.rest.address needs to be added.
> Further, whenever Atlas topology changes (add/move/delete a server), the 
> atlas.rest.address will need to change. However, we have no mechanism of 
> recalculating this from the UI, so instead, allow the property to be editable 
> from the UI for the time being.
> Lastly, the current value of atlas.rest.address is incorrect; it should be 
> csv of http(s):$server:$port from all of the servers.



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

[jira] [Commented] (AMBARI-18012) Metrics Sink unable to connect to zookeeper to locate collector host.

[Hudson (JIRA)]

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

Hudson commented on AMBARI-18012:
-

FAILURE: Integrated in Ambari-trunk-Commit #5515 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5515/])
AMBARI-18012 : Metrics Sink unable to connect to zookeeper to locate (avijayan: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=9696b62afb98a7e94815e9aec26692d533cad12a])
* 
ambari-metrics/ambari-metrics-common/src/main/java/org/apache/hadoop/metrics2/sink/timeline/availability/MetricCollectorHAHelper.java
Revert "AMBARI-18012 : Metrics Sink unable to connect to zookeeper to 
(avijayan: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=212927a416c3edec6e20c25217b6f28fc1f7e55b])
* 
ambari-metrics/ambari-metrics-common/src/main/java/org/apache/hadoop/metrics2/sink/timeline/availability/MetricCollectorHAHelper.java


> Metrics Sink unable to connect to zookeeper to locate collector host.
> -
>
> Key: AMBARI-18012
> URL: https://issues.apache.org/jira/browse/AMBARI-18012
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18012.patch
>
>
> Test and validate sink fallback connect to ZK for finding collector
> {code}
> 2016-07-14 20:37:01,212 INFO  timeline.HadoopTimelineMetricsSink 
> (AbstractTimelineMetricsSink.java:findPreferredCollectHost(353)) - Collector 
> ambari-sid-5.c.pramod-thangali.internal is not longer live. Removing it from 
> list of know live collector hosts : []
> 2016-07-14 20:37:03,213 WARN  availability.MetricCollectorHAHelper 
> (MetricCollectorHAHelper.java:findLiveCollectorHostsFromZNode(83)) - Unable 
> to connect to zookeeper.
> java.lang.IllegalStateException: Client is not started
> at 
> org.apache.hadoop.metrics2.sink.relocated.google.common.base.Preconditions.checkState(Preconditions.java:149)
> at 
> org.apache.hadoop.metrics2.sink.relocated.curator.CuratorZookeeperClient.getZooKeeper(CuratorZookeeperClient.java:113)
> at 
> org.apache.hadoop.metrics2.sink.timeline.availability.MetricCollectorHAHelper$1.call(MetricCollectorHAHelper.java:77)
> at 
> org.apache.hadoop.metrics2.sink.timeline.availability.MetricCollectorHAHelper$1.call(MetricCollectorHAHelper.java:74)
> at 
> org.apache.hadoop.metrics2.sink.relocated.curator.RetryLoop.callWithRetry(RetryLoop.java:107)
> at 
> org.apache.hadoop.metrics2.sink.timeline.availability.MetricCollectorHAHelper.findLiveCollectorHostsFromZNode(MetricCollectorHAHelper.java:74)
> at 
> org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink.findPreferredCollectHost(AbstractTimelineMetricsSink.java:363)
> at 
> org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink.emitMetrics(AbstractTimelineMetricsSink.java:209)
> at 
> org.apache.hadoop.metrics2.sink.timeline.HadoopTimelineMetricsSink.putMetrics(HadoopTimelineMetricsSink.java:315)
> at 
> org.apache.hadoop.metrics2.impl.MetricsSinkAdapter.consume(MetricsSinkAdapter.java:186)
> at 
> org.apache.hadoop.metrics2.impl.MetricsSinkAdapter.consume(MetricsSinkAdapter.java:43)
> at 
> org.apache.hadoop.metrics2.impl.SinkQueue.consumeAll(SinkQueue.java:87)
> at 
> org.apache.hadoop.metrics2.impl.MetricsSinkAdapter.publishMetricsFromQueue(MetricsSinkAdapter.java:134)
> at 
> org.apache.hadoop.metrics2.impl.MetricsSinkAdapter$1.run(MetricsSinkAdapter.java:88)
> 2016-07-14 20:37:03,245 WARN  timeline.HadoopTimelineMetricsSink 
> (AbstractTimelineMetricsSink.java:findLiveCollectorHostsFromKnownCollector(433))
>  - Unable to conne
> {code}



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

[jira] [Commented] (AMBARI-18138) Overriding a config in a Config group and then saving it transitions the screen to default group with configs in non-editable state

[Hudson (JIRA)]

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

Hudson commented on AMBARI-18138:
-

FAILURE: Integrated in Ambari-trunk-Commit #5515 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5515/])
AMBARI-18138. Overriding a config in a Config group and then saving it 
(akovalenko: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=25506aeb53123cde7cca6f1aa1056ab9cdc06f8d])
* ambari-web/test/mixins/common/configs/configs_loader_test.js
* ambari-web/app/mixins/common/configs/configs_loader.js
* ambari-web/app/controllers/main/service/info/configs.js


> Overriding a config in a Config group and then saving it transitions the 
> screen to default group with configs in non-editable state
> ---
>
> Key: AMBARI-18138
> URL: https://issues.apache.org/jira/browse/AMBARI-18138
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-18138.patch, AMBARI-18138_branch-2.4.patch
>
>
> *STR:*
> # On a deployed cluster, Create a config group for any servce
> # Select the config group. All configs will show up in non-editable state
> # Override any config, change the overridden value and save configurations.
> *Actual Result:* After saving, Default group appears with non-editable state.
> *Expected Result:* Either Default group should appear in editable state or 
> config group should appear in non-editable state.



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

[jira] [Commented] (AMBARI-18093) Reduce TTL for high precision tables for AMS.

[Hudson (JIRA)]

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

Hudson commented on AMBARI-18093:
-

FAILURE: Integrated in Ambari-trunk-Commit #5515 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5515/])
AMBARI-18093 : Reduce TTL for high precision tables in AMS. (avijayan) 
(avijayan: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=fd7dbd3b26449182a37bea924b619cfa728452c8])
* ambari-server/src/main/resources/stacks/HDP/2.0.6/services/stack_advisor.py
* ambari-server/src/test/python/stacks/2.2/common/test_stack_advisor.py
* 
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog240Test.java
* 
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog240.java
* 
ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/configuration/ams-site.xml


>  Reduce TTL for high precision tables for AMS.
> --
>
> Key: AMBARI-18093
> URL: https://issues.apache.org/jira/browse/AMBARI-18093
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics
>Affects Versions: 2.4.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
> Fix For: 2.4.0
>
> Attachments: AMBARI-18093-2.4.patch
>
>
> TTL changes
> {code}
> timeline.metrics.host.aggregator.ttl : 1 day
> timeline.metrics.cluster.aggregator.second.ttl : 3 days
> {code}



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

[jira] [Commented] (AMBARI-18132) Remove FIFO and Normalizer in ams-env config.

[Hudson (JIRA)]

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

Hudson commented on AMBARI-18132:
-

FAILURE: Integrated in Ambari-trunk-Commit #5515 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5515/])
AMBARI-18132 : Remove FIFO and Normalizer in ams-env config. (avijayan) 
(avijayan: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=95754ab10e978bb74f3527f0d1a03b088dcc7a83])
* 
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog250Test.java
* 
ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/params.py
* 
ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/configuration/ams-env.xml
* 
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog250.java
* 
ambari-server/src/main/java/org/apache/ambari/server/upgrade/SchemaUpgradeHelper.java
Revert "AMBARI-18132 : Remove FIFO and Normalizer in ams-env config. (avijayan: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=7a6f710e223a78d40a7bfa0c21d45686c8aa8fb5])
* 
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog250Test.java
* 
ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/params.py
* 
ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/configuration/ams-env.xml
* 
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog250.java
* 
ambari-server/src/main/java/org/apache/ambari/server/upgrade/SchemaUpgradeHelper.java


> Remove FIFO and Normalizer in ams-env config.
> -
>
> Key: AMBARI-18132
> URL: https://issues.apache.org/jira/browse/AMBARI-18132
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-metrics
>Affects Versions: 2.4.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
> Fix For: 2.5.0
>
> Attachments: AMBARI-18132.patch
>
>
> It is currently
> {code}
> # HBase compaction policy enabled
> export HBASE_NORMALIZATION_ENABLED=True
> # HBase compaction policy enabled
> export HBASE_FIFO_COMPACTION_POLICY_ENABLED=
> {code}



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

[jira] [Commented] (AMBARI-18121) Cover utils/config with unit tests

[Hudson (JIRA)]

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

Hudson commented on AMBARI-18121:
-

FAILURE: Integrated in Ambari-trunk-Commit #5515 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5515/])
AMBARI-18121 Cover utils/config with unit tests. (ababiichuk) (ababiichuk: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=b9d61f7d7e91a5d057d9bfa4a650d621cde8be00])
* ambari-web/app/utils/helper.js
* ambari-web/test/mappers/stack_service_mapper_test.js
* ambari-web/app/controllers/main/admin/stack_upgrade_history_controller.js
* ambari-web/test/utils/config_test.js
* ambari-web/app/utils/config.js
* ambari-web/app/views/main/alerts/manage_alert_notifications_view.js
* ambari-web/app/utils/string_utils.js
* ambari-web/test/utils/ajax/ajax_test.js


> Cover utils/config with unit tests
> --
>
> Key: AMBARI-18121
> URL: https://issues.apache.org/jira/browse/AMBARI-18121
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
> Fix For: 3.0.0
>
> Attachments: AMBARI-18121.patch
>
>




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

[jira] [Commented] (AMBARI-18126) Refactor Configuration To Allow For Generation Of Documentation

[Hudson (JIRA)]

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

Hudson commented on AMBARI-18126:
-

FAILURE: Integrated in Ambari-trunk-Commit #5515 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5515/])
AMBARI-18126 - Refactor Configuration To Allow For Generation Of (jhurley: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=b1a63404a0efb7fabce77f7a87df1033f8cf2fe0])
* 
ambari-server/src/test/java/org/apache/ambari/server/security/CertGenerationTest.java
* 
ambari-server/src/main/java/org/apache/ambari/server/checks/DatabaseConsistencyCheckHelper.java
* 
ambari-server/src/test/java/org/apache/ambari/server/state/stack/ConfigUpgradeValidityTest.java
* 
ambari-server/src/main/java/org/apache/ambari/server/resources/ResourceManager.java
* ambari-server/src/test/java/org/apache/ambari/server/orm/JdbcPropertyTest.java
* 
ambari-server/src/test/java/org/apache/ambari/server/security/AmbariServerSecurityHeaderFilterTest.java
* 
ambari-server/src/test/java/org/apache/ambari/server/security/authorization/AmbariLdapAuthenticationProviderTest.java
* 
ambari-server/src/main/java/org/apache/ambari/server/api/services/HostComponentService.java
* 
ambari-server/src/test/java/org/apache/ambari/server/security/authorization/AmbariLdapAuthenticationProviderForDuplicateUserTest.java
* 
ambari-server/src/test/java/org/apache/ambari/server/security/encryption/CredentialStoreServiceImplTest.java
* ambari-server/src/main/java/org/apache/ambari/annotations/Markdown.java
* 
ambari-server/src/test/java/org/apache/ambari/server/api/services/AmbariMetaInfoTest.java
* 
ambari-server/src/test/java/org/apache/ambari/server/orm/InMemoryDefaultTestModule.java
* 
ambari-server/src/main/java/org/apache/ambari/server/configuration/ComponentSSLConfiguration.java
* 
ambari-server/src/test/java/org/apache/ambari/server/notifications/DispatchFactoryTest.java
* 
ambari-server/src/test/java/org/apache/ambari/server/security/authorization/AuthorizationTestModule.java
* 
ambari-server/src/main/java/org/apache/ambari/server/security/CertificateManager.java
* 
ambari-server/src/test/java/org/apache/ambari/server/security/SslExecutionTest.java
* 
ambari-server/src/main/java/org/apache/ambari/server/api/services/ComponentService.java
* 
ambari-server/src/main/java/org/apache/ambari/server/configuration/Configuration.java
* 
ambari-server/src/test/java/org/apache/ambari/server/controller/AmbariManagementControllerTest.java
* 
ambari-server/src/test/java/org/apache/ambari/server/resources/TestResources.java
* 
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/CredentialResourceProviderTest.java
* 
ambari-server/src/main/java/org/apache/ambari/server/security/AbstractSecurityHeaderFilter.java
* 
ambari-server/src/test/java/org/apache/ambari/server/actionmanager/TestActionScheduler.java
* 
ambari-server/src/test/java/org/apache/ambari/server/security/authorization/AuthorizationTestModuleForLdapDNWithSpace.java
* 
ambari-server/src/test/java/org/apache/ambari/server/security/authorization/AmbariLdapBindAuthenticatorTest.java
* 
ambari-server/src/main/java/org/apache/ambari/server/view/ViewURLStreamProvider.java
* 
ambari-server/src/test/java/org/apache/ambari/server/view/ViewURLStreamProviderTest.java
* 
ambari-server/src/main/java/org/apache/ambari/server/security/unsecured/rest/ConnectionInfo.java
* 
ambari-server/src/test/java/org/apache/ambari/server/controller/BackgroundCustomCommandExecutionTest.java
* 
ambari-server/src/test/java/org/apache/ambari/server/security/encryption/MasterKeyServiceTest.java
* 
ambari-server/src/test/java/org/apache/ambari/server/cleanup/CleanupServiceFunctionalTest.java
* 
ambari-server/src/test/java/org/apache/ambari/server/scheduler/ExecutionScheduleManagerTest.java
* 
ambari-server/src/test/java/org/apache/ambari/server/bootstrap/BootStrapTest.java
* 
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ClientConfigResourceProvider.java
* 
ambari-server/src/test/java/org/apache/ambari/server/security/encryption/CredentialProviderTest.java
* 
ambari-server/src/test/java/org/apache/ambari/server/security/AbstractSecurityHeaderFilterTest.java
* 
ambari-server/src/test/java/org/apache/ambari/server/security/AmbariViewsSecurityHeaderFilterTest.java
* 
ambari-server/src/main/java/org/apache/ambari/server/controller/KerberosHelperImpl.java
* 
ambari-server/src/main/java/org/apache/ambari/server/state/services/RetryUpgradeActionService.java
* 
ambari-server/src/test/java/org/apache/ambari/server/controller/utilities/DatabaseCheckerTest.java
* 
ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariServer.java
* 
ambari-server/src/main/java/org/apache/ambari/server/controller/utilities/DatabaseChecker.java
* 
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/ClientConfigResourceProviderTest.java
* 

[jira] [Updated] (AMBARI-18139) Oozie service check fails if set yarn.resourcemanager.address to the default from yarn-default.xml

[Dmitry Lysnichenko (JIRA)]

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

Dmitry Lysnichenko updated AMBARI-18139:

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

Committed
To https://git-wip-us.apache.org/repos/asf/ambari.git
   427dccb..8071c36  branch-2.4 -> branch-2.4
   7a6f710..755c5ea  trunk -> trunk

> Oozie service check fails if set yarn.resourcemanager.address to the default 
> from yarn-default.xml
> --
>
> Key: AMBARI-18139
> URL: https://issues.apache.org/jira/browse/AMBARI-18139
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Fix For: 2.4.0
>
> Attachments: AMBARI-18139.patch
>
>
> yarn-default.xml suggests to use $\{yarn.resourcemanager.hostname\}:8032 as 
> yarn.resourcemanager.address.
> But Oozie service check fails if value contains a substitution placeholder 
> '$\{yarn.resourcemanager.hostname\}'
> {noformat}
> resource_management.core.exceptions.Fail: Execution of 
> '/var/lib/ambari-agent/tmp/prepareOozieHdfsDirectories.sh 
> /usr/hdp/current/oozie-client/conf /usr/hdp/current/oozie-client/doc 
> /usr/hdp/current/hadoop-client/conf ${yarn.resourcemanager.hostname}:8050 
> hdfs://nameservice default' returned 1. /bin/bash: 
> ${yarn.resourcemanager.hostname}:8050: bad substitution
> {noformat}



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

[jira] [Created] (AMBARI-18140) Avoid hardcoded values in blueprint for hive and oozie

[Amruta Borkar (JIRA)]

Amruta Borkar created AMBARI-18140:
--

 Summary: Avoid hardcoded values in blueprint for hive and oozie
 Key: AMBARI-18140
 URL: https://issues.apache.org/jira/browse/AMBARI-18140
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server, blueprints
Affects Versions: 2.2.0
Reporter: Amruta Borkar
Assignee: Amruta Borkar
 Fix For: trunk, 2.2.0


There are a lot of hardcoded values in blueprint for hive.

{
  "hive-env" : {
"properties_attributes" : { },
"properties" : {
  "hive_security_authorization" : "None",
  "hive_log_dir" : "/var/log/hive",
  "hive_existing_oracle_host" : "hardcodedhostname
com",
  "hive_user" : "hive",
  "hive_existing_mssql_server_2_host" : "hardcodedhostname.com",
  "hive.heapsize" : "1024",
  "hcat_log_dir" : "/var/log/webhcat",
  "hive_hostname" : "%HOSTGROUP::host_group_1%",
  "hive_database" : "New MySQL Database",
  "hive_exec_orc_storage_strategy" : "SPEED",
  "hive_database_name" : "hive",
  "webhcat_user" : "hcat",
  "hive_txn_acid" : "off",
  "hcat_pid_dir" : "/var/run/webhcat",
  "hive.metastore.heapsize" : "1024",
  "hive.client.heapsize" : "512",
  "hive_existing_mssql_server_host" : "hardcodedhostname.com",
  "hcat_user" : "hcat",
  "hive_ambari_database" : "MySQL",
  "content" : "\n if [ \"$SERVICE\" = \"cli\" ]; then\n   {%...}
  "hive_pid_dir" : "/var/run/hive",
  "hive_existing_postgresql_host" : "hardcodedhostname.com",
  "hive_database_type" : "mysql",
  "hive_existing_mysql_host" : "hardcodedhostname.
com"
}



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

[jira] [Updated] (AMBARI-18139) Oozie service check fails if set yarn.resourcemanager.address to the default from yarn-default.xml

[Dmitry Lysnichenko (JIRA)]

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

Dmitry Lysnichenko updated AMBARI-18139:

Affects Version/s: 2.4.0

> Oozie service check fails if set yarn.resourcemanager.address to the default 
> from yarn-default.xml
> --
>
> Key: AMBARI-18139
> URL: https://issues.apache.org/jira/browse/AMBARI-18139
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Fix For: 2.4.0
>
> Attachments: AMBARI-18139.patch
>
>
> yarn-default.xml suggests to use $\{yarn.resourcemanager.hostname\}:8032 as 
> yarn.resourcemanager.address.
> But Oozie service check fails if value contains a substitution placeholder 
> '$\{yarn.resourcemanager.hostname\}'
> {noformat}
> resource_management.core.exceptions.Fail: Execution of 
> '/var/lib/ambari-agent/tmp/prepareOozieHdfsDirectories.sh 
> /usr/hdp/current/oozie-client/conf /usr/hdp/current/oozie-client/doc 
> /usr/hdp/current/hadoop-client/conf ${yarn.resourcemanager.hostname}:8050 
> hdfs://nameservice default' returned 1. /bin/bash: 
> ${yarn.resourcemanager.hostname}:8050: bad substitution
> {noformat}



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

[jira] [Updated] (AMBARI-18139) Oozie service check fails if set yarn.resourcemanager.address to the default from yarn-default.xml

[Dmitry Lysnichenko (JIRA)]

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

Dmitry Lysnichenko updated AMBARI-18139:

Fix Version/s: 2.4.0

> Oozie service check fails if set yarn.resourcemanager.address to the default 
> from yarn-default.xml
> --
>
> Key: AMBARI-18139
> URL: https://issues.apache.org/jira/browse/AMBARI-18139
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Fix For: 2.4.0
>
> Attachments: AMBARI-18139.patch
>
>
> yarn-default.xml suggests to use $\{yarn.resourcemanager.hostname\}:8032 as 
> yarn.resourcemanager.address.
> But Oozie service check fails if value contains a substitution placeholder 
> '$\{yarn.resourcemanager.hostname\}'
> {noformat}
> resource_management.core.exceptions.Fail: Execution of 
> '/var/lib/ambari-agent/tmp/prepareOozieHdfsDirectories.sh 
> /usr/hdp/current/oozie-client/conf /usr/hdp/current/oozie-client/doc 
> /usr/hdp/current/hadoop-client/conf ${yarn.resourcemanager.hostname}:8050 
> hdfs://nameservice default' returned 1. /bin/bash: 
> ${yarn.resourcemanager.hostname}:8050: bad substitution
> {noformat}



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

[jira] [Updated] (AMBARI-18139) Oozie service check fails if set yarn.resourcemanager.address to the default from yarn-default.xml

[Dmitry Lysnichenko (JIRA)]

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

Dmitry Lysnichenko updated AMBARI-18139:

Component/s: ambari-server

> Oozie service check fails if set yarn.resourcemanager.address to the default 
> from yarn-default.xml
> --
>
> Key: AMBARI-18139
> URL: https://issues.apache.org/jira/browse/AMBARI-18139
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Attachments: AMBARI-18139.patch
>
>
> yarn-default.xml suggests to use $\{yarn.resourcemanager.hostname\}:8032 as 
> yarn.resourcemanager.address.
> But Oozie service check fails if value contains a substitution placeholder 
> '$\{yarn.resourcemanager.hostname\}'
> {noformat}
> resource_management.core.exceptions.Fail: Execution of 
> '/var/lib/ambari-agent/tmp/prepareOozieHdfsDirectories.sh 
> /usr/hdp/current/oozie-client/conf /usr/hdp/current/oozie-client/doc 
> /usr/hdp/current/hadoop-client/conf ${yarn.resourcemanager.hostname}:8050 
> hdfs://nameservice default' returned 1. /bin/bash: 
> ${yarn.resourcemanager.hostname}:8050: bad substitution
> {noformat}



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

[jira] [Updated] (AMBARI-18139) Oozie service check fails if set yarn.resourcemanager.address to the default from yarn-default.xml

[Dmitry Lysnichenko (JIRA)]

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

Dmitry Lysnichenko updated AMBARI-18139:

Attachment: AMBARI-18139.patch

> Oozie service check fails if set yarn.resourcemanager.address to the default 
> from yarn-default.xml
> --
>
> Key: AMBARI-18139
> URL: https://issues.apache.org/jira/browse/AMBARI-18139
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Attachments: AMBARI-18139.patch
>
>
> yarn-default.xml suggests to use $\{yarn.resourcemanager.hostname\}:8032 as 
> yarn.resourcemanager.address.
> But Oozie service check fails if value contains a substitution placeholder 
> '$\{yarn.resourcemanager.hostname\}'
> {noformat}
> resource_management.core.exceptions.Fail: Execution of 
> '/var/lib/ambari-agent/tmp/prepareOozieHdfsDirectories.sh 
> /usr/hdp/current/oozie-client/conf /usr/hdp/current/oozie-client/doc 
> /usr/hdp/current/hadoop-client/conf ${yarn.resourcemanager.hostname}:8050 
> hdfs://nameservice default' returned 1. /bin/bash: 
> ${yarn.resourcemanager.hostname}:8050: bad substitution
> {noformat}



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

[jira] [Updated] (AMBARI-18139) Oozie service check fails if set yarn.resourcemanager.address to the default from yarn-default.xml

[Dmitry Lysnichenko (JIRA)]

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

Dmitry Lysnichenko updated AMBARI-18139:

Status: Patch Available  (was: Open)

> Oozie service check fails if set yarn.resourcemanager.address to the default 
> from yarn-default.xml
> --
>
> Key: AMBARI-18139
> URL: https://issues.apache.org/jira/browse/AMBARI-18139
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Attachments: AMBARI-18139.patch
>
>
> yarn-default.xml suggests to use $\{yarn.resourcemanager.hostname\}:8032 as 
> yarn.resourcemanager.address.
> But Oozie service check fails if value contains a substitution placeholder 
> '$\{yarn.resourcemanager.hostname\}'
> {noformat}
> resource_management.core.exceptions.Fail: Execution of 
> '/var/lib/ambari-agent/tmp/prepareOozieHdfsDirectories.sh 
> /usr/hdp/current/oozie-client/conf /usr/hdp/current/oozie-client/doc 
> /usr/hdp/current/hadoop-client/conf ${yarn.resourcemanager.hostname}:8050 
> hdfs://nameservice default' returned 1. /bin/bash: 
> ${yarn.resourcemanager.hostname}:8050: bad substitution
> {noformat}



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

[jira] [Created] (AMBARI-18139) Oozie service check fails if set yarn.resourcemanager.address to the default from yarn-default.xml

[Dmitry Lysnichenko (JIRA)]

Dmitry Lysnichenko created AMBARI-18139:
---

 Summary: Oozie service check fails if set 
yarn.resourcemanager.address to the default from yarn-default.xml
 Key: AMBARI-18139
 URL: https://issues.apache.org/jira/browse/AMBARI-18139
 Project: Ambari
  Issue Type: Bug
Reporter: Dmitry Lysnichenko
Assignee: Dmitry Lysnichenko
 Attachments: AMBARI-18139.patch


yarn-default.xml suggests to use $\{yarn.resourcemanager.hostname\}:8032 as 
yarn.resourcemanager.address.

But Oozie service check fails if value contains a substitution placeholder 
'$\{yarn.resourcemanager.hostname\}'
{noformat}
resource_management.core.exceptions.Fail: Execution of 
'/var/lib/ambari-agent/tmp/prepareOozieHdfsDirectories.sh 
/usr/hdp/current/oozie-client/conf /usr/hdp/current/oozie-client/doc 
/usr/hdp/current/hadoop-client/conf ${yarn.resourcemanager.hostname}:8050 
hdfs://nameservice default' returned 1. /bin/bash: 
${yarn.resourcemanager.hostname}:8050: bad substitution
{noformat}




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

[jira] [Commented] (AMBARI-18132) Remove FIFO and Normalizer in ams-env config.

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-18132:


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

{color:red}-1 patch{color}.  Top-level trunk compilation may be broken.

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

This message is automatically generated.

> Remove FIFO and Normalizer in ams-env config.
> -
>
> Key: AMBARI-18132
> URL: https://issues.apache.org/jira/browse/AMBARI-18132
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-metrics
>Affects Versions: 2.4.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
> Fix For: 2.5.0
>
> Attachments: AMBARI-18132.patch
>
>
> It is currently
> {code}
> # HBase compaction policy enabled
> export HBASE_NORMALIZATION_ENABLED=True
> # HBase compaction policy enabled
> export HBASE_FIFO_COMPACTION_POLICY_ENABLED=
> {code}



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

[jira] [Commented] (AMBARI-18137) Regionserver failed to start after cluster installation

[Hudson (JIRA)]

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

Hudson commented on AMBARI-18137:
-

FAILURE: Integrated in Ambari-trunk-Commit #5514 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5514/])
AMBARI-18137. Regionserver failed to start after cluster installation  
(aonishuk: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=7ce06fc7ba4dccc4340db3cb986663a97b2b0c38])
* 
ambari-server/src/main/resources/stacks/HDP/2.5/services/HBASE/configuration/hbase-site.xml


> Regionserver failed to start after cluster installation 
> 
>
> Key: AMBARI-18137
> URL: https://issues.apache.org/jira/browse/AMBARI-18137
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.4.0
>
> Attachments: AMBARI-18137.patch
>
>
> Couple of tests failed in todays run as region server was not started
> in one of the hosts after cluster installation.
> Steps followed in the test :  
> 1) Install new ambari, ambari-2.4.0.0-1121 with older HDP version,
> HDP-2.4.2.0.  
> 2) Once installation is completed, check that all the services are up and
> running. Test is failing at this step as region server is not started in one
> of the host.
> Test does express upgrade after this and upgrade went through fine. So it
> appears as if regionserver was down immediately after the installation but
> came up after some time.
> This issue is observed only on OS suse-11+ postgres and with new
> ambari(ambari-2.4.0.0-1121) and older HDP version(HDP-2.4.2.0).  
> Though intermittent, this issue is observed over multiple runs and occurs only
> with this configuration.



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

[jira] [Updated] (AMBARI-18012) Metrics Sink unable to connect to zookeeper to locate collector host.

[Aravindan Vijayan (JIRA)]

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

Aravindan Vijayan updated AMBARI-18012:
---
Status: Patch Available  (was: Reopened)

> Metrics Sink unable to connect to zookeeper to locate collector host.
> -
>
> Key: AMBARI-18012
> URL: https://issues.apache.org/jira/browse/AMBARI-18012
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18012.patch
>
>
> Test and validate sink fallback connect to ZK for finding collector
> {code}
> 2016-07-14 20:37:01,212 INFO  timeline.HadoopTimelineMetricsSink 
> (AbstractTimelineMetricsSink.java:findPreferredCollectHost(353)) - Collector 
> ambari-sid-5.c.pramod-thangali.internal is not longer live. Removing it from 
> list of know live collector hosts : []
> 2016-07-14 20:37:03,213 WARN  availability.MetricCollectorHAHelper 
> (MetricCollectorHAHelper.java:findLiveCollectorHostsFromZNode(83)) - Unable 
> to connect to zookeeper.
> java.lang.IllegalStateException: Client is not started
> at 
> org.apache.hadoop.metrics2.sink.relocated.google.common.base.Preconditions.checkState(Preconditions.java:149)
> at 
> org.apache.hadoop.metrics2.sink.relocated.curator.CuratorZookeeperClient.getZooKeeper(CuratorZookeeperClient.java:113)
> at 
> org.apache.hadoop.metrics2.sink.timeline.availability.MetricCollectorHAHelper$1.call(MetricCollectorHAHelper.java:77)
> at 
> org.apache.hadoop.metrics2.sink.timeline.availability.MetricCollectorHAHelper$1.call(MetricCollectorHAHelper.java:74)
> at 
> org.apache.hadoop.metrics2.sink.relocated.curator.RetryLoop.callWithRetry(RetryLoop.java:107)
> at 
> org.apache.hadoop.metrics2.sink.timeline.availability.MetricCollectorHAHelper.findLiveCollectorHostsFromZNode(MetricCollectorHAHelper.java:74)
> at 
> org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink.findPreferredCollectHost(AbstractTimelineMetricsSink.java:363)
> at 
> org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink.emitMetrics(AbstractTimelineMetricsSink.java:209)
> at 
> org.apache.hadoop.metrics2.sink.timeline.HadoopTimelineMetricsSink.putMetrics(HadoopTimelineMetricsSink.java:315)
> at 
> org.apache.hadoop.metrics2.impl.MetricsSinkAdapter.consume(MetricsSinkAdapter.java:186)
> at 
> org.apache.hadoop.metrics2.impl.MetricsSinkAdapter.consume(MetricsSinkAdapter.java:43)
> at 
> org.apache.hadoop.metrics2.impl.SinkQueue.consumeAll(SinkQueue.java:87)
> at 
> org.apache.hadoop.metrics2.impl.MetricsSinkAdapter.publishMetricsFromQueue(MetricsSinkAdapter.java:134)
> at 
> org.apache.hadoop.metrics2.impl.MetricsSinkAdapter$1.run(MetricsSinkAdapter.java:88)
> 2016-07-14 20:37:03,245 WARN  timeline.HadoopTimelineMetricsSink 
> (AbstractTimelineMetricsSink.java:findLiveCollectorHostsFromKnownCollector(433))
>  - Unable to conne
> {code}



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

[jira] [Updated] (AMBARI-18132) Remove FIFO and Normalizer in ams-env config.

[Aravindan Vijayan (JIRA)]

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

Aravindan Vijayan updated AMBARI-18132:
---
Attachment: AMBARI-18132.patch

> Remove FIFO and Normalizer in ams-env config.
> -
>
> Key: AMBARI-18132
> URL: https://issues.apache.org/jira/browse/AMBARI-18132
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-metrics
>Affects Versions: 2.4.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
> Fix For: 2.5.0
>
> Attachments: AMBARI-18132.patch
>
>
> It is currently
> {code}
> # HBase compaction policy enabled
> export HBASE_NORMALIZATION_ENABLED=True
> # HBase compaction policy enabled
> export HBASE_FIFO_COMPACTION_POLICY_ENABLED=
> {code}



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

[jira] [Updated] (AMBARI-18132) Remove FIFO and Normalizer in ams-env config.

[Aravindan Vijayan (JIRA)]

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

Aravindan Vijayan updated AMBARI-18132:
---
Status: Patch Available  (was: Open)

> Remove FIFO and Normalizer in ams-env config.
> -
>
> Key: AMBARI-18132
> URL: https://issues.apache.org/jira/browse/AMBARI-18132
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-metrics
>Affects Versions: 2.4.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
> Fix For: 2.5.0
>
> Attachments: AMBARI-18132.patch
>
>
> It is currently
> {code}
> # HBase compaction policy enabled
> export HBASE_NORMALIZATION_ENABLED=True
> # HBase compaction policy enabled
> export HBASE_FIFO_COMPACTION_POLICY_ENABLED=
> {code}



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

[jira] [Reopened] (AMBARI-18012) Metrics Sink unable to connect to zookeeper to locate collector host.

[Aravindan Vijayan (JIRA)]

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

Aravindan Vijayan reopened AMBARI-18012:


> Metrics Sink unable to connect to zookeeper to locate collector host.
> -
>
> Key: AMBARI-18012
> URL: https://issues.apache.org/jira/browse/AMBARI-18012
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18012.patch
>
>
> Test and validate sink fallback connect to ZK for finding collector
> {code}
> 2016-07-14 20:37:01,212 INFO  timeline.HadoopTimelineMetricsSink 
> (AbstractTimelineMetricsSink.java:findPreferredCollectHost(353)) - Collector 
> ambari-sid-5.c.pramod-thangali.internal is not longer live. Removing it from 
> list of know live collector hosts : []
> 2016-07-14 20:37:03,213 WARN  availability.MetricCollectorHAHelper 
> (MetricCollectorHAHelper.java:findLiveCollectorHostsFromZNode(83)) - Unable 
> to connect to zookeeper.
> java.lang.IllegalStateException: Client is not started
> at 
> org.apache.hadoop.metrics2.sink.relocated.google.common.base.Preconditions.checkState(Preconditions.java:149)
> at 
> org.apache.hadoop.metrics2.sink.relocated.curator.CuratorZookeeperClient.getZooKeeper(CuratorZookeeperClient.java:113)
> at 
> org.apache.hadoop.metrics2.sink.timeline.availability.MetricCollectorHAHelper$1.call(MetricCollectorHAHelper.java:77)
> at 
> org.apache.hadoop.metrics2.sink.timeline.availability.MetricCollectorHAHelper$1.call(MetricCollectorHAHelper.java:74)
> at 
> org.apache.hadoop.metrics2.sink.relocated.curator.RetryLoop.callWithRetry(RetryLoop.java:107)
> at 
> org.apache.hadoop.metrics2.sink.timeline.availability.MetricCollectorHAHelper.findLiveCollectorHostsFromZNode(MetricCollectorHAHelper.java:74)
> at 
> org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink.findPreferredCollectHost(AbstractTimelineMetricsSink.java:363)
> at 
> org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink.emitMetrics(AbstractTimelineMetricsSink.java:209)
> at 
> org.apache.hadoop.metrics2.sink.timeline.HadoopTimelineMetricsSink.putMetrics(HadoopTimelineMetricsSink.java:315)
> at 
> org.apache.hadoop.metrics2.impl.MetricsSinkAdapter.consume(MetricsSinkAdapter.java:186)
> at 
> org.apache.hadoop.metrics2.impl.MetricsSinkAdapter.consume(MetricsSinkAdapter.java:43)
> at 
> org.apache.hadoop.metrics2.impl.SinkQueue.consumeAll(SinkQueue.java:87)
> at 
> org.apache.hadoop.metrics2.impl.MetricsSinkAdapter.publishMetricsFromQueue(MetricsSinkAdapter.java:134)
> at 
> org.apache.hadoop.metrics2.impl.MetricsSinkAdapter$1.run(MetricsSinkAdapter.java:88)
> 2016-07-14 20:37:03,245 WARN  timeline.HadoopTimelineMetricsSink 
> (AbstractTimelineMetricsSink.java:findLiveCollectorHostsFromKnownCollector(433))
>  - Unable to conne
> {code}



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

[jira] [Updated] (AMBARI-18012) Metrics Sink unable to connect to zookeeper to locate collector host.

[Aravindan Vijayan (JIRA)]

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

Aravindan Vijayan updated AMBARI-18012:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

Pushed to trunk.

> Metrics Sink unable to connect to zookeeper to locate collector host.
> -
>
> Key: AMBARI-18012
> URL: https://issues.apache.org/jira/browse/AMBARI-18012
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18012.patch
>
>
> Test and validate sink fallback connect to ZK for finding collector
> {code}
> 2016-07-14 20:37:01,212 INFO  timeline.HadoopTimelineMetricsSink 
> (AbstractTimelineMetricsSink.java:findPreferredCollectHost(353)) - Collector 
> ambari-sid-5.c.pramod-thangali.internal is not longer live. Removing it from 
> list of know live collector hosts : []
> 2016-07-14 20:37:03,213 WARN  availability.MetricCollectorHAHelper 
> (MetricCollectorHAHelper.java:findLiveCollectorHostsFromZNode(83)) - Unable 
> to connect to zookeeper.
> java.lang.IllegalStateException: Client is not started
> at 
> org.apache.hadoop.metrics2.sink.relocated.google.common.base.Preconditions.checkState(Preconditions.java:149)
> at 
> org.apache.hadoop.metrics2.sink.relocated.curator.CuratorZookeeperClient.getZooKeeper(CuratorZookeeperClient.java:113)
> at 
> org.apache.hadoop.metrics2.sink.timeline.availability.MetricCollectorHAHelper$1.call(MetricCollectorHAHelper.java:77)
> at 
> org.apache.hadoop.metrics2.sink.timeline.availability.MetricCollectorHAHelper$1.call(MetricCollectorHAHelper.java:74)
> at 
> org.apache.hadoop.metrics2.sink.relocated.curator.RetryLoop.callWithRetry(RetryLoop.java:107)
> at 
> org.apache.hadoop.metrics2.sink.timeline.availability.MetricCollectorHAHelper.findLiveCollectorHostsFromZNode(MetricCollectorHAHelper.java:74)
> at 
> org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink.findPreferredCollectHost(AbstractTimelineMetricsSink.java:363)
> at 
> org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink.emitMetrics(AbstractTimelineMetricsSink.java:209)
> at 
> org.apache.hadoop.metrics2.sink.timeline.HadoopTimelineMetricsSink.putMetrics(HadoopTimelineMetricsSink.java:315)
> at 
> org.apache.hadoop.metrics2.impl.MetricsSinkAdapter.consume(MetricsSinkAdapter.java:186)
> at 
> org.apache.hadoop.metrics2.impl.MetricsSinkAdapter.consume(MetricsSinkAdapter.java:43)
> at 
> org.apache.hadoop.metrics2.impl.SinkQueue.consumeAll(SinkQueue.java:87)
> at 
> org.apache.hadoop.metrics2.impl.MetricsSinkAdapter.publishMetricsFromQueue(MetricsSinkAdapter.java:134)
> at 
> org.apache.hadoop.metrics2.impl.MetricsSinkAdapter$1.run(MetricsSinkAdapter.java:88)
> 2016-07-14 20:37:03,245 WARN  timeline.HadoopTimelineMetricsSink 
> (AbstractTimelineMetricsSink.java:findLiveCollectorHostsFromKnownCollector(433))
>  - Unable to conne
> {code}



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

[jira] [Updated] (AMBARI-18093) Reduce TTL for high precision tables for AMS.

[Aravindan Vijayan (JIRA)]

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

Aravindan Vijayan updated AMBARI-18093:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

Pushed to branch-2.4 and trunk.

>  Reduce TTL for high precision tables for AMS.
> --
>
> Key: AMBARI-18093
> URL: https://issues.apache.org/jira/browse/AMBARI-18093
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics
>Affects Versions: 2.4.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
> Fix For: 2.4.0
>
> Attachments: AMBARI-18093-2.4.patch
>
>
> TTL changes
> {code}
> timeline.metrics.host.aggregator.ttl : 1 day
> timeline.metrics.cluster.aggregator.second.ttl : 3 days
> {code}



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

[jira] [Updated] (AMBARI-18138) Overriding a config in a Config group and then saving it transitions the screen to default group with configs in non-editable state

[Aleksandr Kovalenko (JIRA)]

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

Aleksandr Kovalenko updated AMBARI-18138:
-
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Overriding a config in a Config group and then saving it transitions the 
> screen to default group with configs in non-editable state
> ---
>
> Key: AMBARI-18138
> URL: https://issues.apache.org/jira/browse/AMBARI-18138
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-18138.patch, AMBARI-18138_branch-2.4.patch
>
>
> *STR:*
> # On a deployed cluster, Create a config group for any servce
> # Select the config group. All configs will show up in non-editable state
> # Override any config, change the overridden value and save configurations.
> *Actual Result:* After saving, Default group appears with non-editable state.
> *Expected Result:* Either Default group should appear in editable state or 
> config group should appear in non-editable state.



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

[jira] [Commented] (AMBARI-18138) Overriding a config in a Config group and then saving it transitions the screen to default group with configs in non-editable state

[Aleksandr Kovalenko (JIRA)]

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

Aleksandr Kovalenko commented on AMBARI-18138:
--

committed to trunk and branch-2.4

> Overriding a config in a Config group and then saving it transitions the 
> screen to default group with configs in non-editable state
> ---
>
> Key: AMBARI-18138
> URL: https://issues.apache.org/jira/browse/AMBARI-18138
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-18138.patch, AMBARI-18138_branch-2.4.patch
>
>
> *STR:*
> # On a deployed cluster, Create a config group for any servce
> # Select the config group. All configs will show up in non-editable state
> # Override any config, change the overridden value and save configurations.
> *Actual Result:* After saving, Default group appears with non-editable state.
> *Expected Result:* Either Default group should appear in editable state or 
> config group should appear in non-editable state.



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

[jira] [Commented] (AMBARI-18138) Overriding a config in a Config group and then saving it transitions the screen to default group with configs in non-editable state

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-18138:


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

{color:red}-1 patch{color}.  Top-level trunk compilation may be broken.

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

This message is automatically generated.

> Overriding a config in a Config group and then saving it transitions the 
> screen to default group with configs in non-editable state
> ---
>
> Key: AMBARI-18138
> URL: https://issues.apache.org/jira/browse/AMBARI-18138
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-18138.patch, AMBARI-18138_branch-2.4.patch
>
>
> *STR:*
> # On a deployed cluster, Create a config group for any servce
> # Select the config group. All configs will show up in non-editable state
> # Override any config, change the overridden value and save configurations.
> *Actual Result:* After saving, Default group appears with non-editable state.
> *Expected Result:* Either Default group should appear in editable state or 
> config group should appear in non-editable state.



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

[jira] [Updated] (AMBARI-18138) Overriding a config in a Config group and then saving it transitions the screen to default group with configs in non-editable state

[Aleksandr Kovalenko (JIRA)]

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

Aleksandr Kovalenko updated AMBARI-18138:
-
Attachment: AMBARI-18138.patch

> Overriding a config in a Config group and then saving it transitions the 
> screen to default group with configs in non-editable state
> ---
>
> Key: AMBARI-18138
> URL: https://issues.apache.org/jira/browse/AMBARI-18138
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-18138.patch
>
>
> *STR:*
> # On a deployed cluster, Create a config group for any servce
> # Select the config group. All configs will show up in non-editable state
> # Override any config, change the overridden value and save configurations.
> *Actual Result:* After saving, Default group appears with non-editable state.
> *Expected Result:* Either Default group should appear in editable state or 
> config group should appear in non-editable state.



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

[jira] [Commented] (AMBARI-18138) Overriding a config in a Config group and then saving it transitions the screen to default group with configs in non-editable state

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-18138:


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

{color:red}-1 patch{color}.  Top-level trunk compilation may be broken.

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

This message is automatically generated.

> Overriding a config in a Config group and then saving it transitions the 
> screen to default group with configs in non-editable state
> ---
>
> Key: AMBARI-18138
> URL: https://issues.apache.org/jira/browse/AMBARI-18138
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-18138.patch, AMBARI-18138_branch-2.4.patch
>
>
> *STR:*
> # On a deployed cluster, Create a config group for any servce
> # Select the config group. All configs will show up in non-editable state
> # Override any config, change the overridden value and save configurations.
> *Actual Result:* After saving, Default group appears with non-editable state.
> *Expected Result:* Either Default group should appear in editable state or 
> config group should appear in non-editable state.



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

[jira] [Commented] (AMBARI-18138) Overriding a config in a Config group and then saving it transitions the screen to default group with configs in non-editable state

[Andrii Babiichuk (JIRA)]

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

Andrii Babiichuk commented on AMBARI-18138:
---

+1 for the patch

> Overriding a config in a Config group and then saving it transitions the 
> screen to default group with configs in non-editable state
> ---
>
> Key: AMBARI-18138
> URL: https://issues.apache.org/jira/browse/AMBARI-18138
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-18138.patch, AMBARI-18138_branch-2.4.patch
>
>
> *STR:*
> # On a deployed cluster, Create a config group for any servce
> # Select the config group. All configs will show up in non-editable state
> # Override any config, change the overridden value and save configurations.
> *Actual Result:* After saving, Default group appears with non-editable state.
> *Expected Result:* Either Default group should appear in editable state or 
> config group should appear in non-editable state.



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

[jira] [Updated] (AMBARI-18138) Overriding a config in a Config group and then saving it transitions the screen to default group with configs in non-editable state

[Aleksandr Kovalenko (JIRA)]

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

Aleksandr Kovalenko updated AMBARI-18138:
-
Attachment: (was: AMBARI-18138.patch)

> Overriding a config in a Config group and then saving it transitions the 
> screen to default group with configs in non-editable state
> ---
>
> Key: AMBARI-18138
> URL: https://issues.apache.org/jira/browse/AMBARI-18138
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-18138.patch, AMBARI-18138_branch-2.4.patch
>
>
> *STR:*
> # On a deployed cluster, Create a config group for any servce
> # Select the config group. All configs will show up in non-editable state
> # Override any config, change the overridden value and save configurations.
> *Actual Result:* After saving, Default group appears with non-editable state.
> *Expected Result:* Either Default group should appear in editable state or 
> config group should appear in non-editable state.



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

[jira] [Updated] (AMBARI-18138) Overriding a config in a Config group and then saving it transitions the screen to default group with configs in non-editable state

[Aleksandr Kovalenko (JIRA)]

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

Aleksandr Kovalenko updated AMBARI-18138:
-
Attachment: AMBARI-18138.patch

> Overriding a config in a Config group and then saving it transitions the 
> screen to default group with configs in non-editable state
> ---
>
> Key: AMBARI-18138
> URL: https://issues.apache.org/jira/browse/AMBARI-18138
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-18138.patch, AMBARI-18138_branch-2.4.patch
>
>
> *STR:*
> # On a deployed cluster, Create a config group for any servce
> # Select the config group. All configs will show up in non-editable state
> # Override any config, change the overridden value and save configurations.
> *Actual Result:* After saving, Default group appears with non-editable state.
> *Expected Result:* Either Default group should appear in editable state or 
> config group should appear in non-editable state.



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

[jira] [Updated] (AMBARI-18138) Overriding a config in a Config group and then saving it transitions the screen to default group with configs in non-editable state

[Aleksandr Kovalenko (JIRA)]

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

Aleksandr Kovalenko updated AMBARI-18138:
-
Attachment: AMBARI-18138_branch-2.4.patch

> Overriding a config in a Config group and then saving it transitions the 
> screen to default group with configs in non-editable state
> ---
>
> Key: AMBARI-18138
> URL: https://issues.apache.org/jira/browse/AMBARI-18138
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-18138.patch, AMBARI-18138_branch-2.4.patch
>
>
> *STR:*
> # On a deployed cluster, Create a config group for any servce
> # Select the config group. All configs will show up in non-editable state
> # Override any config, change the overridden value and save configurations.
> *Actual Result:* After saving, Default group appears with non-editable state.
> *Expected Result:* Either Default group should appear in editable state or 
> config group should appear in non-editable state.



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

[jira] [Updated] (AMBARI-18138) Overriding a config in a Config group and then saving it transitions the screen to default group with configs in non-editable state

[Aleksandr Kovalenko (JIRA)]

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

Aleksandr Kovalenko updated AMBARI-18138:
-
Status: Patch Available  (was: Open)

> Overriding a config in a Config group and then saving it transitions the 
> screen to default group with configs in non-editable state
> ---
>
> Key: AMBARI-18138
> URL: https://issues.apache.org/jira/browse/AMBARI-18138
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-18138.patch, AMBARI-18138_branch-2.4.patch
>
>
> *STR:*
> # On a deployed cluster, Create a config group for any servce
> # Select the config group. All configs will show up in non-editable state
> # Override any config, change the overridden value and save configurations.
> *Actual Result:* After saving, Default group appears with non-editable state.
> *Expected Result:* Either Default group should appear in editable state or 
> config group should appear in non-editable state.



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

[jira] [Updated] (AMBARI-18121) Cover utils/config with unit tests

[Andrii Babiichuk (JIRA)]

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

Andrii Babiichuk updated AMBARI-18121:
--
Resolution: Fixed
Status: Resolved  (was: Patch Available)

committed to trunk

> Cover utils/config with unit tests
> --
>
> Key: AMBARI-18121
> URL: https://issues.apache.org/jira/browse/AMBARI-18121
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
> Fix For: 3.0.0
>
> Attachments: AMBARI-18121.patch
>
>




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

[jira] [Updated] (AMBARI-18126) Refactor Configuration To Allow For Generation Of Documentation

[Jonathan Hurley (JIRA)]

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

Jonathan Hurley updated AMBARI-18126:
-
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Refactor Configuration To Allow For Generation Of Documentation
> ---
>
> Key: AMBARI-18126
> URL: https://issues.apache.org/jira/browse/AMBARI-18126
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: trunk
>
> Attachments: AMBARI-18126.patch
>
>
> As part of the work for AMBARI-18089, all of the potential properties from 
> {{ambari.properties}} need a way to be organized and queried in order to 
> generate documentation. 
> This Jira proposes to change our disorganized String/String (key/default) 
> structure found in {{Configuration}}, and instead, have a strongly-coupled 
> relationship between key/default/type. 
> Additionally, expose a way to provide extra information in the markdown 
> (similar to JavaDoc, but geared more for users and not developers).



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

[jira] [Updated] (AMBARI-18137) Regionserver failed to start after cluster installation

[Andrew Onischuk (JIRA)]

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

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

Committed to trunk and branch-2.4

> Regionserver failed to start after cluster installation 
> 
>
> Key: AMBARI-18137
> URL: https://issues.apache.org/jira/browse/AMBARI-18137
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.4.0
>
> Attachments: AMBARI-18137.patch
>
>
> Couple of tests failed in todays run as region server was not started
> in one of the hosts after cluster installation.
> Steps followed in the test :  
> 1) Install new ambari, ambari-2.4.0.0-1121 with older HDP version,
> HDP-2.4.2.0.  
> 2) Once installation is completed, check that all the services are up and
> running. Test is failing at this step as region server is not started in one
> of the host.
> Test does express upgrade after this and upgrade went through fine. So it
> appears as if regionserver was down immediately after the installation but
> came up after some time.
> This issue is observed only on OS suse-11+ postgres and with new
> ambari(ambari-2.4.0.0-1121) and older HDP version(HDP-2.4.2.0).  
> Though intermittent, this issue is observed over multiple runs and occurs only
> with this configuration.



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

[jira] [Commented] (AMBARI-18137) Regionserver failed to start after cluster installation

[Andrew Onischuk (JIRA)]

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

Andrew Onischuk commented on AMBARI-18137:
--

{noformat}
[INFO] Rat check: Summary of files. Unapproved: 0 unknown: 0 generated: 0 
approved: 148 licence.
[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] Ambari Views .. SUCCESS [2.406s]
[INFO] Ambari Metrics Common . SUCCESS [1.114s]
[INFO] Ambari Server . SUCCESS [1:09.519s]
[INFO] Ambari Agent .. SUCCESS [12.750s]
[INFO] 
[INFO] BUILD SUCCESS
[INFO] 
[INFO] Total time: 1:26.634s
[INFO] Finished at: Fri Aug 12 16:19:49 EEST 2016
[INFO] Final Memory: 87M/1194M
[INFO] 
{noformat}

> Regionserver failed to start after cluster installation 
> 
>
> Key: AMBARI-18137
> URL: https://issues.apache.org/jira/browse/AMBARI-18137
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.4.0
>
> Attachments: AMBARI-18137.patch
>
>
> Couple of tests failed in todays run as region server was not started
> in one of the hosts after cluster installation.
> Steps followed in the test :  
> 1) Install new ambari, ambari-2.4.0.0-1121 with older HDP version,
> HDP-2.4.2.0.  
> 2) Once installation is completed, check that all the services are up and
> running. Test is failing at this step as region server is not started in one
> of the host.
> Test does express upgrade after this and upgrade went through fine. So it
> appears as if regionserver was down immediately after the installation but
> came up after some time.
> This issue is observed only on OS suse-11+ postgres and with new
> ambari(ambari-2.4.0.0-1121) and older HDP version(HDP-2.4.2.0).  
> Though intermittent, this issue is observed over multiple runs and occurs only
> with this configuration.



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

[jira] [Updated] (AMBARI-18089) Create Documentation Around All Options In ambari.properties

[Jonathan Hurley (JIRA)]

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

Jonathan Hurley updated AMBARI-18089:
-
Status: Open  (was: Patch Available)

> Create Documentation Around All Options In ambari.properties
> 
>
> Key: AMBARI-18089
> URL: https://issues.apache.org/jira/browse/AMBARI-18089
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.5.0
>
>
> Ambari Server has "sensible" defaults for many of the configurations in 
> {{ambari.properties}}. They may work for 5-, 10-, 50-, or even 100-host 
> clusters. However, they _must_ be properly tuned in any situation which has a 
> large, production-level topology. 
> There is currently sparse to no documentation on many of these properties. 
> For every property, we need to consider:
> - The context in which different cluster deployments could be affected by it
> -- Cluster Size
> -- Cluster History
> -- Concurrent Users
> - Provide recommendations that are grouped logically, such as (for example)
> -- Multiple Concurrent Users
> -- 50 to 100 Hosts
> -- Ambari Server Hardware



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

[jira] [Updated] (AMBARI-18126) Refactor Configuration To Allow For Generation Of Documentation

[Jonathan Hurley (JIRA)]

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

Jonathan Hurley updated AMBARI-18126:
-
Attachment: AMBARI-18126.patch

> Refactor Configuration To Allow For Generation Of Documentation
> ---
>
> Key: AMBARI-18126
> URL: https://issues.apache.org/jira/browse/AMBARI-18126
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: trunk
>
> Attachments: AMBARI-18126.patch
>
>
> As part of the work for AMBARI-18089, all of the potential properties from 
> {{ambari.properties}} need a way to be organized and queried in order to 
> generate documentation. 
> This Jira proposes to change our disorganized String/String (key/default) 
> structure found in {{Configuration}}, and instead, have a strongly-coupled 
> relationship between key/default/type. 
> Additionally, expose a way to provide extra information in the markdown 
> (similar to JavaDoc, but geared more for users and not developers).



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

[jira] [Updated] (AMBARI-18126) Refactor Configuration To Allow For Generation Of Documentation

[Jonathan Hurley (JIRA)]

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

Jonathan Hurley updated AMBARI-18126:
-
Status: Patch Available  (was: Open)

> Refactor Configuration To Allow For Generation Of Documentation
> ---
>
> Key: AMBARI-18126
> URL: https://issues.apache.org/jira/browse/AMBARI-18126
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: trunk
>
> Attachments: AMBARI-18126.patch
>
>
> As part of the work for AMBARI-18089, all of the potential properties from 
> {{ambari.properties}} need a way to be organized and queried in order to 
> generate documentation. 
> This Jira proposes to change our disorganized String/String (key/default) 
> structure found in {{Configuration}}, and instead, have a strongly-coupled 
> relationship between key/default/type. 
> Additionally, expose a way to provide extra information in the markdown 
> (similar to JavaDoc, but geared more for users and not developers).



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

[jira] [Updated] (AMBARI-18089) Create Documentation Around All Options In ambari.properties

[Jonathan Hurley (JIRA)]

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

Jonathan Hurley updated AMBARI-18089:
-
Status: Patch Available  (was: Open)

> Create Documentation Around All Options In ambari.properties
> 
>
> Key: AMBARI-18089
> URL: https://issues.apache.org/jira/browse/AMBARI-18089
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.5.0
>
>
> Ambari Server has "sensible" defaults for many of the configurations in 
> {{ambari.properties}}. They may work for 5-, 10-, 50-, or even 100-host 
> clusters. However, they _must_ be properly tuned in any situation which has a 
> large, production-level topology. 
> There is currently sparse to no documentation on many of these properties. 
> For every property, we need to consider:
> - The context in which different cluster deployments could be affected by it
> -- Cluster Size
> -- Cluster History
> -- Concurrent Users
> - Provide recommendations that are grouped logically, such as (for example)
> -- Multiple Concurrent Users
> -- 50 to 100 Hosts
> -- Ambari Server Hardware



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

[jira] [Created] (AMBARI-18138) Overriding a config in a Config group and then saving it transitions the screen to default group with configs in non-editable state

[Aleksandr Kovalenko (JIRA)]

Aleksandr Kovalenko created AMBARI-18138:


 Summary: Overriding a config in a Config group and then saving it 
transitions the screen to default group with configs in non-editable state
 Key: AMBARI-18138
 URL: https://issues.apache.org/jira/browse/AMBARI-18138
 Project: Ambari
  Issue Type: Bug
  Components: ambari-web
Affects Versions: 2.4.0
Reporter: Aleksandr Kovalenko
Assignee: Aleksandr Kovalenko
Priority: Blocker
 Fix For: 2.4.0


*STR:*
# On a deployed cluster, Create a config group for any servce
# Select the config group. All configs will show up in non-editable state
# Override any config, change the overridden value and save configurations.

*Actual Result:* After saving, Default group appears with non-editable state.
*Expected Result:* Either Default group should appear in editable state or 
config group should appear in non-editable state.



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

[jira] [Commented] (AMBARI-18137) Regionserver failed to start after cluster installation

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-18137:


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

{color:red}-1 patch{color}.  Top-level trunk compilation may be broken.

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

This message is automatically generated.

> Regionserver failed to start after cluster installation 
> 
>
> Key: AMBARI-18137
> URL: https://issues.apache.org/jira/browse/AMBARI-18137
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.4.0
>
> Attachments: AMBARI-18137.patch
>
>
> Couple of tests failed in todays run as region server was not started
> in one of the hosts after cluster installation.
> Steps followed in the test :  
> 1) Install new ambari, ambari-2.4.0.0-1121 with older HDP version,
> HDP-2.4.2.0.  
> 2) Once installation is completed, check that all the services are up and
> running. Test is failing at this step as region server is not started in one
> of the host.
> Test does express upgrade after this and upgrade went through fine. So it
> appears as if regionserver was down immediately after the installation but
> came up after some time.
> This issue is observed only on OS suse-11+ postgres and with new
> ambari(ambari-2.4.0.0-1121) and older HDP version(HDP-2.4.2.0).  
> Though intermittent, this issue is observed over multiple runs and occurs only
> with this configuration.



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

[jira] [Updated] (AMBARI-18137) Regionserver failed to start after cluster installation

[Andrew Onischuk (JIRA)]

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

Andrew Onischuk updated AMBARI-18137:
-
Description: 
Couple of tests failed in todays run as region server was not started
in one of the hosts after cluster installation.

Steps followed in the test :  
1) Install new ambari, ambari-2.4.0.0-1121 with older HDP version,
HDP-2.4.2.0.  
2) Once installation is completed, check that all the services are up and
running. Test is failing at this step as region server is not started in one
of the host.

Test does express upgrade after this and upgrade went through fine. So it
appears as if regionserver was down immediately after the installation but
came up after some time.

This issue is observed only on OS suse-11+ postgres and with new
ambari(ambari-2.4.0.0-1121) and older HDP version(HDP-2.4.2.0).  
Though intermittent, this issue is observed over multiple runs and occurs only
with this configuration.



  was:
Couple of system tests failed in todays run as region server was not started
in one of the hosts after cluster installation.

Steps followed in the test :  
1) Install new ambari, ambari-2.4.0.0-1121 with older HDP version,
HDP-2.4.2.0.  
2) Once installation is completed, check that all the services are up and
running. Test is failing at this step as region server is not started in one
of the host.

Test does express upgrade after this and upgrade went through fine. So it
appears as if regionserver was down immediately after the installation but
came up after some time.

This issue is observed only on OS suse-11+ postgres and with new
ambari(ambari-2.4.0.0-1121) and older HDP version(HDP-2.4.2.0).  
Though intermittent, this issue is observed over multiple runs and occurs only
with this configuration.




> Regionserver failed to start after cluster installation 
> 
>
> Key: AMBARI-18137
> URL: https://issues.apache.org/jira/browse/AMBARI-18137
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.4.0
>
> Attachments: AMBARI-18137.patch
>
>
> Couple of tests failed in todays run as region server was not started
> in one of the hosts after cluster installation.
> Steps followed in the test :  
> 1) Install new ambari, ambari-2.4.0.0-1121 with older HDP version,
> HDP-2.4.2.0.  
> 2) Once installation is completed, check that all the services are up and
> running. Test is failing at this step as region server is not started in one
> of the host.
> Test does express upgrade after this and upgrade went through fine. So it
> appears as if regionserver was down immediately after the installation but
> came up after some time.
> This issue is observed only on OS suse-11+ postgres and with new
> ambari(ambari-2.4.0.0-1121) and older HDP version(HDP-2.4.2.0).  
> Though intermittent, this issue is observed over multiple runs and occurs only
> with this configuration.



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

[jira] [Updated] (AMBARI-18137) Regionserver failed to start after cluster installation

[Andrew Onischuk (JIRA)]

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

Andrew Onischuk updated AMBARI-18137:
-
Status: Patch Available  (was: Open)

> Regionserver failed to start after cluster installation 
> 
>
> Key: AMBARI-18137
> URL: https://issues.apache.org/jira/browse/AMBARI-18137
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.4.0
>
> Attachments: AMBARI-18137.patch
>
>
> Couple of system tests failed in todays run as region server was not started
> in one of the hosts after cluster installation.
> Steps followed in the test :  
> 1) Install new ambari, ambari-2.4.0.0-1121 with older HDP version,
> HDP-2.4.2.0.  
> 2) Once installation is completed, check that all the services are up and
> running. Test is failing at this step as region server is not started in one
> of the host.
> Test does express upgrade after this and upgrade went through fine. So it
> appears as if regionserver was down immediately after the installation but
> came up after some time.
> This issue is observed only on OS suse-11+ postgres and with new
> ambari(ambari-2.4.0.0-1121) and older HDP version(HDP-2.4.2.0).  
> Though intermittent, this issue is observed over multiple runs and occurs only
> with this configuration.



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

[jira] [Updated] (AMBARI-18137) Regionserver failed to start after cluster installation

[Andrew Onischuk (JIRA)]

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

Andrew Onischuk updated AMBARI-18137:
-
Attachment: AMBARI-18137.patch

> Regionserver failed to start after cluster installation 
> 
>
> Key: AMBARI-18137
> URL: https://issues.apache.org/jira/browse/AMBARI-18137
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.4.0
>
> Attachments: AMBARI-18137.patch
>
>
> Couple of system tests failed in todays run as region server was not started
> in one of the hosts after cluster installation.
> Steps followed in the test :  
> 1) Install new ambari, ambari-2.4.0.0-1121 with older HDP version,
> HDP-2.4.2.0.  
> 2) Once installation is completed, check that all the services are up and
> running. Test is failing at this step as region server is not started in one
> of the host.
> Test does express upgrade after this and upgrade went through fine. So it
> appears as if regionserver was down immediately after the installation but
> came up after some time.
> This issue is observed only on OS suse-11+ postgres and with new
> ambari(ambari-2.4.0.0-1121) and older HDP version(HDP-2.4.2.0).  
> Though intermittent, this issue is observed over multiple runs and occurs only
> with this configuration.



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

[jira] [Created] (AMBARI-18137) Regionserver failed to start after cluster installation

[Andrew Onischuk (JIRA)]

Andrew Onischuk created AMBARI-18137:


 Summary: Regionserver failed to start after cluster installation 
 Key: AMBARI-18137
 URL: https://issues.apache.org/jira/browse/AMBARI-18137
 Project: Ambari
  Issue Type: Bug
Reporter: Andrew Onischuk
Assignee: Andrew Onischuk
 Fix For: 2.4.0
 Attachments: AMBARI-18137.patch

Couple of system tests failed in todays run as region server was not started
in one of the hosts after cluster installation.

Steps followed in the test :  
1) Install new ambari, ambari-2.4.0.0-1121 with older HDP version,
HDP-2.4.2.0.  
2) Once installation is completed, check that all the services are up and
running. Test is failing at this step as region server is not started in one
of the host.

Test does express upgrade after this and upgrade went through fine. So it
appears as if regionserver was down immediately after the installation but
came up after some time.

This issue is observed only on OS suse-11+ postgres and with new
ambari(ambari-2.4.0.0-1121) and older HDP version(HDP-2.4.2.0).  
Though intermittent, this issue is observed over multiple runs and occurs only
with this configuration.





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

[jira] [Commented] (AMBARI-18124) HDFS Finalize Upgrade alert shows up in Unknown state after EU to 2.3.6

[Hudson (JIRA)]

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

Hudson commented on AMBARI-18124:
-

FAILURE: Integrated in Ambari-trunk-Commit #5513 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5513/])
AMBARI-18124. HDFS Finalize Upgrade alert shows up in Unknown state 
(dlysnichenko: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=03457f1c9e261512fa5aa1e5fa59a402f5f2bc8c])
* 
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/alerts/alert_upgrade_finalized.py


> HDFS Finalize Upgrade alert shows up in Unknown state after EU to 2.3.6
> ---
>
> Key: AMBARI-18124
> URL: https://issues.apache.org/jira/browse/AMBARI-18124
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Fix For: 2.4.0
>
> Attachments: AMBARI-18124.patch
>
>
> *Steps*
> # Deploy HDP-2.2.6 cluster with Ambari 2.0.2
> # Upgrade Ambari to 2.4.0.0
> # Perform Express Upgrade to 2.3.6.0 and let it complete
> # Go to Alerts page and filter by "HDFS Upgrade Finalized State" Alert 
> definition
> *Result*
> The alert shows in UNKWN state
> {code}
> Traceback (most recent call last):
> File 
> "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/alerts/alert_upgrade_finalized.py",
>  line 132, in execute
> upgrade_finalized_response_json = json.loads(last_checkpoint_time_response)
> File "/usr/lib/python2.6/site-packages/ambari_simplejson/__init__.py", line 
> 307, in loads
> return _default_decoder.decode(s)
> File "/usr/lib/python2.6/site-packages/ambari_simplejson/decoder.py", line 
> 335, in decode
> obj, end = self.raw_decode(s, idx=_w(s, 0).end())
> File "/usr/lib/python2.6/site-packages/ambari_simplejson/decoder.py", line 
> 353, in raw_decode
> raise ValueError("No JSON object could be decoded")
> ValueError: No JSON object could be decoded
> {code}



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

[jira] [Commented] (AMBARI-18121) Cover utils/config with unit tests

[Aleksandr Kovalenko (JIRA)]

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

Aleksandr Kovalenko commented on AMBARI-18121:
--

+1 for the patch

> Cover utils/config with unit tests
> --
>
> Key: AMBARI-18121
> URL: https://issues.apache.org/jira/browse/AMBARI-18121
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
> Fix For: 3.0.0
>
> Attachments: AMBARI-18121.patch
>
>




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

[jira] [Updated] (AMBARI-18121) Cover utils/config with unit tests

[Andrii Babiichuk (JIRA)]

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

Andrii Babiichuk updated AMBARI-18121:
--
Status: Patch Available  (was: Open)

  29768 tests complete (23 seconds)
  154 tests pending


> Cover utils/config with unit tests
> --
>
> Key: AMBARI-18121
> URL: https://issues.apache.org/jira/browse/AMBARI-18121
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
> Fix For: 3.0.0
>
> Attachments: AMBARI-18121.patch
>
>




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

[jira] [Updated] (AMBARI-18121) Cover utils/config with unit tests

[Andrii Babiichuk (JIRA)]

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

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

> Cover utils/config with unit tests
> --
>
> Key: AMBARI-18121
> URL: https://issues.apache.org/jira/browse/AMBARI-18121
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
> Fix For: 3.0.0
>
> Attachments: AMBARI-18121.patch
>
>




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

[jira] [Commented] (AMBARI-18130) Atlas hooks to include atlas.rest.address config, allow editing in the UI, and compute value using all Atlas Servers

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-18130:


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

{color:red}-1 patch{color}.  Top-level trunk compilation may be broken.

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

This message is automatically generated.

> Atlas hooks to include atlas.rest.address config, allow editing in the UI, 
> and compute value using all Atlas Servers
> 
>
> Key: AMBARI-18130
> URL: https://issues.apache.org/jira/browse/AMBARI-18130
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.4.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 2.4.0
>
> Attachments: AMBARI-18130.patch
>
>
> For all of the Atlas hook files (atlas-application.properties), the config 
> atlas.rest.address needs to be added.
> Further, whenever Atlas topology changes (add/move/delete a server), the 
> atlas.rest.address will need to change. However, we have no mechanism of 
> recalculating this from the UI, so instead, allow the property to be editable 
> from the UI for the time being.
> Lastly, the current value of atlas.rest.address is incorrect; it should be 
> csv of http(s):$server:$port from all of the servers.



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

[jira] [Commented] (AMBARI-18093) Reduce TTL for high precision tables for AMS.

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-18093:


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

This message is automatically generated.

>  Reduce TTL for high precision tables for AMS.
> --
>
> Key: AMBARI-18093
> URL: https://issues.apache.org/jira/browse/AMBARI-18093
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics
>Affects Versions: 2.4.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
> Fix For: 2.4.0
>
> Attachments: AMBARI-18093-2.4.patch
>
>
> TTL changes
> {code}
> timeline.metrics.host.aggregator.ttl : 1 day
> timeline.metrics.cluster.aggregator.second.ttl : 3 days
> {code}



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

[jira] [Commented] (AMBARI-18133) Error message displays mesage key instead of actual message

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-18133:


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

{color:red}-1 patch{color}.  Top-level trunk compilation may be broken.

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

This message is automatically generated.

> Error message displays mesage key instead of actual message
> ---
>
> Key: AMBARI-18133
> URL: https://issues.apache.org/jira/browse/AMBARI-18133
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-admin
>Affects Versions: 2.4.0
>Reporter: Sangeeta Ravindran
>Assignee: Sangeeta Ravindran
>Priority: Minor
> Fix For: 2.4.0
>
> Attachments: AMBARI-18133.patch, ErrorMessageWithFix.jpg, 
> MessageKeyInsteadOfMessage.jpg
>
>
> 1. Click on a user in the Ambari Admin view -> Users.
> 2. Under Local Group Membership, add a group that does not exist.
> 3. The error message returns the message key instead of the actual message.



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

[jira] [Commented] (AMBARI-18125) AMS : Allow for certain metrics to skip aggregation determined by client

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-18125:


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

{color:red}-1 patch{color}.  Top-level trunk compilation may be broken.

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

This message is automatically generated.

> AMS : Allow for certain metrics to skip aggregation determined by client
> 
>
> Key: AMBARI-18125
> URL: https://issues.apache.org/jira/browse/AMBARI-18125
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-metrics
>Affects Versions: 2.4.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
> Fix For: 2.5.0
>
> Attachments: AMBARI-18125.patch
>
>
> _Example_: Per disk metrics / host static info (no aggregation across hosts)
> The client should be able to submit a request which dimension should be 
> skipped.
> The metadata can store this info and allow the SELECT query projection to 
> skip a chunk of these metrics based on what aggregation is working.
> For now only across host skipping makes sense and the client part can be put 
> in later.
> *Note*:
> Sub-task, de-normalize disk metrics so that user can find out disk per host.
> Grafana implication: The non-aggregated metrics can obviously be visualized 
> only on the templatized / host dashboard



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

[jira] [Commented] (AMBARI-17999) Typo in property name "yarn.nodemanager.log.retain-second", should be "seconds"

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-17999:


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

{color:red}-1 patch{color}.  Top-level trunk compilation may be broken.

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

This message is automatically generated.

> Typo in property name "yarn.nodemanager.log.retain-second", should be 
> "seconds"
> ---
>
> Key: AMBARI-17999
> URL: https://issues.apache.org/jira/browse/AMBARI-17999
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.2.0
>Reporter: Ying Zhang
>Assignee: Masahiro Tanaka
>Priority: Minor
> Attachments: AMBARI-17999.001.patch
>
>
> In yarn-site.xml, property name "yarn.nodemanager.log.retain-second" is 
> wrong, should be "yarn.nodemanager.log.retain-seconds" instead.



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

[jira] [Commented] (AMBARI-18074) umask value should less than 18 when check hosts in the step 3 of install ambari

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-18074:


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

{color:red}-1 patch{color}.  Top-level trunk compilation may be broken.

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

This message is automatically generated.

> umask value should less than 18 when check hosts in the step 3 of install 
> ambari
> 
>
> Key: AMBARI-18074
> URL: https://issues.apache.org/jira/browse/AMBARI-18074
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: wuhui
> Fix For: 2.4.0
>
> Attachments: AMBARI-18074.patch
>
>
> if umask value big than 18 ,some hdfs user may not have the privilege to 
> operate the hdfs system.
> so i suggest to notice people to revise the umask value when the umask value 
> it not narmal in the step 3 of host check.



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

[jira] [Commented] (AMBARI-17805) the history versions of config can't be showed in the screen fully

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-17805:


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

This message is automatically generated.

> the history versions of config can't be showed in the screen fully
> --
>
> Key: AMBARI-17805
> URL: https://issues.apache.org/jira/browse/AMBARI-17805
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.2.2
>Reporter: wuhui
> Fix For: 2.4.0
>
> Attachments: AMBARI-17805.patch, A_WQ6V3PP70}SPDU09QZG8P.jpg, 
> [Q{M}H{{3JVL%U(A8${UMWF.png, page_turn_1.png, page_turn_2.png
>
>
> when the number of config version is more than twenty-one，type the button 
> ‘show more config history’，the configs can't be show in the screen fully。
> if you want to show the detail of the bug，please see the picture of below！



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

[jira] [Commented] (AMBARI-18128) Receiving Error "Cannot save settings" when trying to edit view settings.

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-18128:


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

{color:red}-1 patch{color}.  Top-level trunk compilation may be broken.

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

This message is automatically generated.

> Receiving Error "Cannot save settings" when trying to edit view settings.
> -
>
> Key: AMBARI-18128
> URL: https://issues.apache.org/jira/browse/AMBARI-18128
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.4.0
>Reporter: DIPAYAN BHOWMICK
>Assignee: DIPAYAN BHOWMICK
> Fix For: 2.4.0
>
> Attachments: AMBARI-18128.2.branch-2.4.patch
>
>
> PROBLEM: Receiving Error "Cannot save settings" when trying to edit view 
> settings. 
> IMPACT:  Customer not able to edit view after the fact. 
> STEPS TO REPRODUCE: 
> 1.  Create a new instance of a view and save
> 2. try to edit a the instance such as display name. 
> 3.  You should get stack like: 
> {code}
> Cannot save settings
> java.lang.IllegalArgumentException: 
> {"propertyResults":{"webhdfs.url":{"valid":false,"detail":"Must be valid 
> URL"},"hdfs.auth_to_local":{"valid":true,"detail":"OK"},"hdfs.umask-mode":{"valid":true,"detail":"OK"},"webhdfs.nameservices":{"valid":true,"detail":"OK"},"hive.transport.mode":{"valid":true,"detail":"OK"},"jobs.dir":{"valid":true,"detail":"OK"},"hive.http.port":{"valid":true,"detail":"OK"},"webhdfs.auth":{"valid":true,"detail":"OK"},"webhdfs.ha.namenode.rpc-address.nn2":{"valid":true,"detail":"OK"},"webhdfs.ha.namenode.rpc-address.nn1":{"valid":true,"detail":"OK"},"views.tez.instance":{"valid":true,"detail":"OK"},"yarn.resourcemanager.url":{"valid":true,"detail":"OK"},"scripts.settings.defaults-file":{"valid":true,"detail":"OK"},"webhdfs.ha.namenode.http-address.nn2":{"valid":true,"detail":"OK"},"webhdfs.client.failover.proxy.provider":{"valid":true,"detail":"OK"},"webhdfs.ha.namenode.http-address.nn1":{"valid":true,"detail":"OK"},"webhdfs.ha.namenodes.list":{"valid":true,"detail":"OK"},"hive.metastore.warehouse.dir":{"valid":true,"detail":"OK"},"hive.port":{"valid":true,"detail":"OK"},"hive.http.path":{"valid":true,"detail":"OK"},"scripts.dir":{"valid":true,"detail":"OK"},"webhdfs.
> {code}



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

[jira] [Updated] (AMBARI-18136) Falcon service checks fail after RU from erie to erie

[Shreya Bhat (JIRA)]

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

Shreya Bhat updated AMBARI-18136:
-
Description: 
Stderr : 
{code}
"stderr" : "Traceback (most recent call last):\n  File 
\"/var/lib/ambari-agent/cache/common-services/FALCON/0.5.0.2.1/package/scripts/service_check.py\",
 line 53, in \nFalconServiceCheck().execute()\n  File 
\"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\",
 line 280, in execute\nmethod(env)\n  File 
\"/var/lib/ambari-agent/cache/common-services/FALCON/0.5.0.2.1/package/scripts/service_check.py\",
 line 40, in service_check\ntry_sleep = 20\n  File 
\"/usr/lib/python2.6/site-packages/resource_management/core/base.py\", line 
155, in __init__\nself.env.run()\n  File 
\"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\", 
line 160, in run\nself.run_action(resource, action)\n  File 
\"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\", 
line 124, in run_action\nprovider_action()\n  File 
\"/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py\",
 line 273, in action_run\ntries=self.resource.tries, 
try_sleep=self.resource.try_sleep)\n  File 
\"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line 
71, in inner\nresult = function(command, **kwargs)\n  File 
\"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line 
93, in checked_call\ntries=tries, try_sleep=try_sleep)\n  File 
\"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line 
141, in _call_wrapper\nresult = _call(command, **kwargs_copy)\n  File 
\"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line 
294, in _call\nraise 
Fail(err_msg)\nresource_management.core.exceptions.Fail: Execution of 
'/usr/hdp/current/falcon-client/bin/falcon admin -version' returned 255. ERROR: 
Unable to initialize Falcon Client object. Cause : Could not authenticate, 
Authentication failed, URL: 
http://natr66-reos-erietoerienxtsec-r6-11.openstacklocal:15000/api/options?user.name=ambari-qa=ambari-qa,
 status: 503, message: Service Unavailable",
{code}

  was:
Source HDP build :1154
Target HDP build :1189
Upgrade type : RU


> Falcon service checks fail after RU from erie to erie
> -
>
> Key: AMBARI-18136
> URL: https://issues.apache.org/jira/browse/AMBARI-18136
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Shreya Bhat
>Priority: Critical
> Fix For: 2.4.0
>
>
> Stderr : 
> {code}
> "stderr" : "Traceback (most recent call last):\n  File 
> \"/var/lib/ambari-agent/cache/common-services/FALCON/0.5.0.2.1/package/scripts/service_check.py\",
>  line 53, in \nFalconServiceCheck().execute()\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\",
>  line 280, in execute\nmethod(env)\n  File 
> \"/var/lib/ambari-agent/cache/common-services/FALCON/0.5.0.2.1/package/scripts/service_check.py\",
>  line 40, in service_check\ntry_sleep = 20\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/base.py\", line 
> 155, in __init__\nself.env.run()\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\", 
> line 160, in run\nself.run_action(resource, action)\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\", 
> line 124, in run_action\nprovider_action()\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py\",
>  line 273, in action_run\ntries=self.resource.tries, 
> try_sleep=self.resource.try_sleep)\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line 
> 71, in inner\nresult = function(command, **kwargs)\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line 
> 93, in checked_call\ntries=tries, try_sleep=try_sleep)\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line 
> 141, in _call_wrapper\nresult = _call(command, **kwargs_copy)\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line 
> 294, in _call\nraise 
> Fail(err_msg)\nresource_management.core.exceptions.Fail: Execution of 
> '/usr/hdp/current/falcon-client/bin/falcon admin -version' returned 255. 
> ERROR: Unable to initialize Falcon Client object. Cause : Could not 
> authenticate, Authentication failed, URL: 
> http://natr66-reos-erietoerienxtsec-r6-11.openstacklocal:15000/api/options?user.name=ambari-qa=ambari-qa,
>  status: 503, message: Service Unavailable",
> {code}



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

[jira] [Updated] (AMBARI-18124) HDFS Finalize Upgrade alert shows up in Unknown state after EU to 2.3.6

[Dmitry Lysnichenko (JIRA)]

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

Dmitry Lysnichenko updated AMBARI-18124:

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

Committed
To https://git-wip-us.apache.org/repos/asf/ambari.git
   56a60ab..d2ee285  branch-2.4 -> branch-2.4
   c803237..03457f1  trunk -> trunk


> HDFS Finalize Upgrade alert shows up in Unknown state after EU to 2.3.6
> ---
>
> Key: AMBARI-18124
> URL: https://issues.apache.org/jira/browse/AMBARI-18124
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Fix For: 2.4.0
>
> Attachments: AMBARI-18124.patch
>
>
> *Steps*
> # Deploy HDP-2.2.6 cluster with Ambari 2.0.2
> # Upgrade Ambari to 2.4.0.0
> # Perform Express Upgrade to 2.3.6.0 and let it complete
> # Go to Alerts page and filter by "HDFS Upgrade Finalized State" Alert 
> definition
> *Result*
> The alert shows in UNKWN state
> {code}
> Traceback (most recent call last):
> File 
> "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/alerts/alert_upgrade_finalized.py",
>  line 132, in execute
> upgrade_finalized_response_json = json.loads(last_checkpoint_time_response)
> File "/usr/lib/python2.6/site-packages/ambari_simplejson/__init__.py", line 
> 307, in loads
> return _default_decoder.decode(s)
> File "/usr/lib/python2.6/site-packages/ambari_simplejson/decoder.py", line 
> 335, in decode
> obj, end = self.raw_decode(s, idx=_w(s, 0).end())
> File "/usr/lib/python2.6/site-packages/ambari_simplejson/decoder.py", line 
> 353, in raw_decode
> raise ValueError("No JSON object could be decoded")
> ValueError: No JSON object could be decoded
> {code}



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

[jira] [Created] (AMBARI-18136) Falcon service checks fail after RU from erie to erie

[Shreya Bhat (JIRA)]

Shreya Bhat created AMBARI-18136:


 Summary: Falcon service checks fail after RU from erie to erie
 Key: AMBARI-18136
 URL: https://issues.apache.org/jira/browse/AMBARI-18136
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: 2.4.0
Reporter: Shreya Bhat
Priority: Critical
 Fix For: 2.4.0


Source HDP build :1154
Target HDP build :1189
Upgrade type : RU



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

[jira] [Created] (AMBARI-18135) Enable Namenode HA failing at install journal nodes with cluster operator user

[Shreya Bhat (JIRA)]

Shreya Bhat created AMBARI-18135:


 Summary: Enable Namenode HA failing at install journal nodes with 
cluster operator user
 Key: AMBARI-18135
 URL: https://issues.apache.org/jira/browse/AMBARI-18135
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: 2.4.0
Reporter: Shreya Bhat
Priority: Critical
 Fix For: 2.4.0


Enabling name node HA is failing at journal node install for cluster operator 
user. Looking at network from the chrome browser, looks like there is a 403.



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

[jira] [Commented] (AMBARI-18128) Receiving Error "Cannot save settings" when trying to edit view settings.

[DIPAYAN BHOWMICK (JIRA)]

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

DIPAYAN BHOWMICK commented on AMBARI-18128:
---

Added a new patch and removed the old ones. Updated review board.

> Receiving Error "Cannot save settings" when trying to edit view settings.
> -
>
> Key: AMBARI-18128
> URL: https://issues.apache.org/jira/browse/AMBARI-18128
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.4.0
>Reporter: DIPAYAN BHOWMICK
>Assignee: DIPAYAN BHOWMICK
> Fix For: 2.4.0
>
> Attachments: AMBARI-18128.2.branch-2.4.patch
>
>
> PROBLEM: Receiving Error "Cannot save settings" when trying to edit view 
> settings. 
> IMPACT:  Customer not able to edit view after the fact. 
> STEPS TO REPRODUCE: 
> 1.  Create a new instance of a view and save
> 2. try to edit a the instance such as display name. 
> 3.  You should get stack like: 
> {code}
> Cannot save settings
> java.lang.IllegalArgumentException: 
> {"propertyResults":{"webhdfs.url":{"valid":false,"detail":"Must be valid 
> URL"},"hdfs.auth_to_local":{"valid":true,"detail":"OK"},"hdfs.umask-mode":{"valid":true,"detail":"OK"},"webhdfs.nameservices":{"valid":true,"detail":"OK"},"hive.transport.mode":{"valid":true,"detail":"OK"},"jobs.dir":{"valid":true,"detail":"OK"},"hive.http.port":{"valid":true,"detail":"OK"},"webhdfs.auth":{"valid":true,"detail":"OK"},"webhdfs.ha.namenode.rpc-address.nn2":{"valid":true,"detail":"OK"},"webhdfs.ha.namenode.rpc-address.nn1":{"valid":true,"detail":"OK"},"views.tez.instance":{"valid":true,"detail":"OK"},"yarn.resourcemanager.url":{"valid":true,"detail":"OK"},"scripts.settings.defaults-file":{"valid":true,"detail":"OK"},"webhdfs.ha.namenode.http-address.nn2":{"valid":true,"detail":"OK"},"webhdfs.client.failover.proxy.provider":{"valid":true,"detail":"OK"},"webhdfs.ha.namenode.http-address.nn1":{"valid":true,"detail":"OK"},"webhdfs.ha.namenodes.list":{"valid":true,"detail":"OK"},"hive.metastore.warehouse.dir":{"valid":true,"detail":"OK"},"hive.port":{"valid":true,"detail":"OK"},"hive.http.path":{"valid":true,"detail":"OK"},"scripts.dir":{"valid":true,"detail":"OK"},"webhdfs.
> {code}



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

[jira] [Updated] (AMBARI-18128) Receiving Error "Cannot save settings" when trying to edit view settings.

[DIPAYAN BHOWMICK (JIRA)]

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

DIPAYAN BHOWMICK updated AMBARI-18128:
--
Attachment: (was: AMBARI-18128.1.branch-2.4.patch)

> Receiving Error "Cannot save settings" when trying to edit view settings.
> -
>
> Key: AMBARI-18128
> URL: https://issues.apache.org/jira/browse/AMBARI-18128
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.4.0
>Reporter: DIPAYAN BHOWMICK
>Assignee: DIPAYAN BHOWMICK
> Fix For: 2.4.0
>
> Attachments: AMBARI-18128.2.branch-2.4.patch
>
>
> PROBLEM: Receiving Error "Cannot save settings" when trying to edit view 
> settings. 
> IMPACT:  Customer not able to edit view after the fact. 
> STEPS TO REPRODUCE: 
> 1.  Create a new instance of a view and save
> 2. try to edit a the instance such as display name. 
> 3.  You should get stack like: 
> {code}
> Cannot save settings
> java.lang.IllegalArgumentException: 
> {"propertyResults":{"webhdfs.url":{"valid":false,"detail":"Must be valid 
> URL"},"hdfs.auth_to_local":{"valid":true,"detail":"OK"},"hdfs.umask-mode":{"valid":true,"detail":"OK"},"webhdfs.nameservices":{"valid":true,"detail":"OK"},"hive.transport.mode":{"valid":true,"detail":"OK"},"jobs.dir":{"valid":true,"detail":"OK"},"hive.http.port":{"valid":true,"detail":"OK"},"webhdfs.auth":{"valid":true,"detail":"OK"},"webhdfs.ha.namenode.rpc-address.nn2":{"valid":true,"detail":"OK"},"webhdfs.ha.namenode.rpc-address.nn1":{"valid":true,"detail":"OK"},"views.tez.instance":{"valid":true,"detail":"OK"},"yarn.resourcemanager.url":{"valid":true,"detail":"OK"},"scripts.settings.defaults-file":{"valid":true,"detail":"OK"},"webhdfs.ha.namenode.http-address.nn2":{"valid":true,"detail":"OK"},"webhdfs.client.failover.proxy.provider":{"valid":true,"detail":"OK"},"webhdfs.ha.namenode.http-address.nn1":{"valid":true,"detail":"OK"},"webhdfs.ha.namenodes.list":{"valid":true,"detail":"OK"},"hive.metastore.warehouse.dir":{"valid":true,"detail":"OK"},"hive.port":{"valid":true,"detail":"OK"},"hive.http.path":{"valid":true,"detail":"OK"},"scripts.dir":{"valid":true,"detail":"OK"},"webhdfs.
> {code}



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