[jira] [Commented] (AMBARI-18946) Ambari Integration for Zeppelin and Spark 2.0

[Hudson (JIRA)]

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

Hudson commented on AMBARI-18946:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6099 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6099/])
AMBARI-18946 Ambari Integration for Zeppelin and Spark 2.0 (r-kamath) 
(renjith.kamath: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=69390ee4897699a94542e946e2f03d31ee4a626b])
* (edit) 
ambari-server/src/main/resources/common-services/ZEPPELIN/0.6.0.2.5/package/scripts/params.py
* (edit) 
ambari-server/src/main/resources/common-services/ZEPPELIN/0.6.0.2.5/package/scripts/master.py


> Ambari Integration for Zeppelin and Spark 2.0
> -
>
> Key: AMBARI-18946
> URL: https://issues.apache.org/jira/browse/AMBARI-18946
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Reporter: Renjith Kamath
>Assignee: Renjith Kamath
> Fix For: 2.5.0
>
> Attachments: AMBARI-18946-branch-2.5-v1.patch, 
> AMBARI-18946-branch-2.5-v2.patch
>
>




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

[jira] [Commented] (AMBARI-18946) Ambari Integration for Zeppelin and Spark 2.0

[Hudson (JIRA)]

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

Hudson commented on AMBARI-18946:
-

FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #398 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/398/])
AMBARI-18946 Ambari Integration for Zeppelin and Spark 2.0 (r-kamath) 
(renjith.kamath: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=182479d3ce0324422379ca87ec369b7025dfe91f])
* (edit) 
ambari-server/src/main/resources/common-services/ZEPPELIN/0.6.0.2.5/package/scripts/master.py
* (edit) 
ambari-server/src/main/resources/common-services/ZEPPELIN/0.6.0.2.5/package/scripts/params.py


> Ambari Integration for Zeppelin and Spark 2.0
> -
>
> Key: AMBARI-18946
> URL: https://issues.apache.org/jira/browse/AMBARI-18946
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Reporter: Renjith Kamath
>Assignee: Renjith Kamath
> Fix For: 2.5.0
>
> Attachments: AMBARI-18946-branch-2.5-v1.patch, 
> AMBARI-18946-branch-2.5-v2.patch
>
>




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

[jira] [Updated] (AMBARI-18946) Ambari Integration for Zeppelin and Spark 2.0

[Renjith Kamath (JIRA)]

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

Renjith Kamath updated AMBARI-18946:

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

Committed to trunk and branch-2.5

> Ambari Integration for Zeppelin and Spark 2.0
> -
>
> Key: AMBARI-18946
> URL: https://issues.apache.org/jira/browse/AMBARI-18946
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Reporter: Renjith Kamath
>Assignee: Renjith Kamath
> Fix For: 2.5.0
>
> Attachments: AMBARI-18946-branch-2.5-v1.patch, 
> AMBARI-18946-branch-2.5-v2.patch
>
>




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

[jira] [Commented] (AMBARI-19003) Perf: Fix deploy-gce-perf-cluster.py to deploy separate server onto own cluster with different settings for more cores and MySQL DB

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-19003:


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

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

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

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

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

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

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

This message is automatically generated.

> Perf: Fix deploy-gce-perf-cluster.py to deploy separate server onto own 
> cluster with different settings for more cores and MySQL DB
> ---
>
> Key: AMBARI-19003
> URL: https://issues.apache.org/jira/browse/AMBARI-19003
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.5.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 2.5.0
>
> Attachments: AMBARI-19003.patch
>
>
> Right now, deploy-gce-perf-cluster.py puts Ambari Server on the same 4 core 
> VM where it puts 50 agents. Instead, we need to create a separate 16-core VM 
> for the server without any agents.
> Next, Ambari Server should be installed with MySQL database instead since it 
> has more configuration options that the default postgres.
> Further, the sorting of the VMs is not numeric since "perf-9" comes after 
> "perf-42". The incorrect sorting means that VM #i isn't getting the agents 
> starting with number (i-1)*50+1



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

[jira] [Commented] (AMBARI-19005) 'conf.server' dir for HIVE1 and HIVE2 should have 700 permission and files in it should have 600 permission.

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-19005:


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

This message is automatically generated.

> 'conf.server' dir for HIVE1 and HIVE2 should have 700 permission and files in 
> it should have 600 permission.
> 
>
> Key: AMBARI-19005
> URL: https://issues.apache.org/jira/browse/AMBARI-19005
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.1
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19005.patch
>
>
> **Existing permissions for Hive1 and Hive2's 'conf.server' and files in it 
> were :**
> **hive1:**
> -
> $ ls -ltr /usr/hdp/current/hive-server2/conf/ | grep conf.server
> drwxr-xr-x. 2 hive hadoop   4096 Nov 22 00:17 conf.server
> $ ls -ltr /usr/hdp/current/hive-server2/conf/conf.server/
> total 56
> -rw-r--r--. 1 hive hadoop  6784 Nov 16 00:16 mapred-site.xml
> -rw-r--r--. 1 hive hadoop 0 Nov 16 00:16 hive-default.xml.template
> -rw-r--r--. 1 hive hadoop 0 Nov 16 00:16 hive-env.sh.template
> -rw-r--r--. 1 hive hadoop  2652 Nov 16 00:16 hive-exec-log4j.properties
> -rw-r--r--. 1 hive hadoop  3050 Nov 16 00:16 hive-log4j.properties
> -rw-r--r--. 1 hive hadoop   563 Nov 16 00:16 hivemetastore-site.xml
> -rw-r--r--. 1 hive hadoop   898 Nov 16 00:16 
> hadoop-metrics2-hivemetastore.properties
> -rw-r--r--. 1 hive hadoop   677 Nov 16 00:17 hiveserver2-site.xml
> -rw-r--r--. 1 hive hadoop   898 Nov 16 00:17 
> hadoop-metrics2-hiveserver2.properties
> -rw-r--r--. 1 hive hadoop 19625 Nov 16 09:22 hive-site.xml
> -rw-r--r--. 1 hive hadoop  2163 Nov 16 10:08 hive-env.sh
> -
> **hive2:**
> -
> $ ls -ltr /usr/hdp/current/hive-server2-hive2/conf/ | grep conf.server
> drwxr-xr-x. 2 hive hadoop   4096 Nov 22 08:10 conf.server
> $ ls -ltr /etc/hive2/conf/conf.server/
> total 76
> -rw-r--r--. 1 hive hadoop  6784 Nov 16 08:10 mapred-site.xml
> -rw-r--r--. 1 hive hadoop 0 Nov 16 08:10 hive-default.xml.template
> -rw-r--r--. 1 hive hadoop 0 Nov 16 08:10 hive-env.sh.template
> -rw-r--r--. 1 hive hadoop   793 Nov 16 08:10 hiveserver2-site.xml
> -rw-r--r--. 1 hive hadoop  1675 Nov 16 08:10 hive-env.sh
> -rw-r--r--. 1 hive hadoop  6378 Nov 16 08:10 llap-daemon-log4j2.properties
> -rw-r--r--. 1 hive hadoop  2715 Nov 16 08:10 llap-cli-log4j2.properties
> -rw-r--r--. 1 hive hadoop  2757 Nov 16 08:10 hive-log4j2.properties
> -rw-r--r--. 1 hive hadoop  2287 Nov 16 08:10 hive-exec-log4j2.properties
> -rw-r--r--. 1 hive hadoop  1596 Nov 16 08:10 beeline-log4j2.properties
> -rw-r--r--. 1 hive hadoop   898 Nov 16 08:10 
> hadoop-metrics2-hiveserver2.properties
> -rw-r--r--. 1 hive hadoop   898 Nov 16 08:10 
> hadoop-metrics2-llapdaemon.properties
> -rw-r--r--. 1 hive hadoop   898 Nov 16 08:10 
> hadoop-metrics2-llaptaskscheduler.properties
> -rw-r--r--. 1 hive hadoop 23688 Nov 22 20:27 hive-site.xml
> -
> **New updated permissions for Hive1 and Hive2's 'conf.server' and files in it 
> are :**
> **hive1:**
> -
> $ ls -ltr /usr/hdp/current/hive-server2/conf/ | grep conf.server
> drwx--. 2 hive hadoop   4096 Nov 16 00:17 conf.server
> $ ls -ltr /usr/hdp/current/hive-server2/conf/conf.server
> total 56
> -rw---. 1 hive hadoop 0 Nov 16 00:16 hive-default.xml.template
> -rw---. 1 hive hadoop 0 Nov 16 00:16 hive-env.sh.template
> -rw---. 1 hive hadoop  2652 Nov 16 00:16 hive-exec-log4j.properties
> -rw---. 1 hive hadoop  3050 Nov 16 00:16 hive-log4j.properties
> -rw---. 1 hive hadoop   563 Nov 16 00:16 hivemetastore-site.xml
> -rw---. 1 hive hadoop   898 Nov 16 00:16 
> hadoop-metrics2-hivemetastore.properties
> -rw---. 1 hive hadoop   677 Nov 16 00:17 hiveserver2-site.xml
> -rw---. 1 hive hadoop   898 Nov 16 00:17 
> hadoop-metrics2-hiveserver2.properties
> -rw---. 1 hive hadoop 19625 Nov 16 

[jira] [Commented] (AMBARI-19006) EU to message users to start YARN queues if work preserving recovery is disabled

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-19006:


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

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

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

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

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

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

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

This message is automatically generated.

> EU to message users to start YARN queues if work preserving recovery is 
> disabled
> 
>
> Key: AMBARI-19006
> URL: https://issues.apache.org/jira/browse/AMBARI-19006
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 2.5.0
>
> Attachments: AMBARI-19006.patch
>
>
> Today, the Express Upgrade packs message users to stop YARN queues if they do 
> not have work preserving recovery enabled.
> However, there's no message reminding users to enable it again.
> E.g.,
> {code}
> 
>   false
>   true
>   
>   
>  property="yarn.resourcemanager.work-preserving-recovery.enabled" value="true" 
> comparison="not-equal"/>
> 
>   Before continuing, please start all YARN queues if you 
> stopped them in a previous step.
> 
>   
> 
> {code}



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

[jira] [Commented] (AMBARI-18834) Add Ranger proxy user under Ranger KMS config during stack upgrade

[Hudson (JIRA)]

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

Hudson commented on AMBARI-18834:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6098 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6098/])
AMBARI-18834 Add Ranger proxy user under Ranger KMS config during stack 
(mugdha: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=b5b73d20274a8bbffcebbd9f099e30949220])
* (add) 
ambari-server/src/test/java/org/apache/ambari/server/serveraction/upgrades/RangerKmsProxyConfigTest.java
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/nonrolling-upgrade-2.5.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/nonrolling-upgrade-2.6.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/upgrade-2.6.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.5.xml
* (add) 
ambari-server/src/main/java/org/apache/ambari/server/serveraction/upgrades/RangerKmsProxyConfig.java
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/nonrolling-upgrade-2.5.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.6.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/upgrade-2.5.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/nonrolling-upgrade-2.6.xml


> Add Ranger proxy user under Ranger KMS config during stack upgrade
> --
>
> Key: AMBARI-18834
> URL: https://issues.apache.org/jira/browse/AMBARI-18834
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.4.0
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18834.1.patch, AMBARI-18834.2.patch, 
> AMBARI-18834.2.trunk.patch, AMBARI-18834.patch
>
>
> Add below properties during stack upgrade to 2.5 in kerberos environment 
> under kms-site.xml
> {code}
> hadoop.kms.proxyuser.[ranger].groups=*
> hadoop.kms.proxyuser.[ranger].hosts=*
> hadoop.kms.proxyuser.[ranger].users=*
> {code}



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

[jira] [Commented] (AMBARI-18929) Yarn service check fails when either resource manager is down in HA enabled cluster

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-18929:


{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12840793/AMBARI-18929_trunk.02.patch
  against trunk revision .

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

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

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

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

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

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

This message is automatically generated.

> Yarn service check fails when either resource manager is down in HA enabled 
> cluster
> ---
>
> Key: AMBARI-18929
> URL: https://issues.apache.org/jira/browse/AMBARI-18929
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Weiwei Yang
> Attachments: AMBARI-18929_trunk.02.patch, AMBARI-18929_trunk.patch
>
>
> When HA is enabled, yarn service_check.py fails if one of RM is down, even 
> the other one is active. This gives user the wrong impression the yarn 
> cluster is not healthy. Instead, service check should pass, or at least pass 
> with warning that lets user know there is one RM down.



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

[jira] [Commented] (AMBARI-18834) Add Ranger proxy user under Ranger KMS config during stack upgrade

[Hudson (JIRA)]

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

Hudson commented on AMBARI-18834:
-

FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #397 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/397/])
AMBARI-18834 Add Ranger proxy user under Ranger KMS config during stack 
(mugdha: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=d3c75557ec7bc20fa9b2782137a6412aa09a8afb])
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.5.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/nonrolling-upgrade-2.6.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.6.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/upgrade-2.5.xml
* (add) 
ambari-server/src/main/java/org/apache/ambari/server/serveraction/upgrades/RangerKmsProxyConfig.java
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/nonrolling-upgrade-2.6.xml
* (add) 
ambari-server/src/test/java/org/apache/ambari/server/serveraction/upgrades/RangerKmsProxyConfigTest.java
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/upgrade-2.6.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/nonrolling-upgrade-2.5.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/nonrolling-upgrade-2.5.xml


> Add Ranger proxy user under Ranger KMS config during stack upgrade
> --
>
> Key: AMBARI-18834
> URL: https://issues.apache.org/jira/browse/AMBARI-18834
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.4.0
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18834.1.patch, AMBARI-18834.2.patch, 
> AMBARI-18834.2.trunk.patch, AMBARI-18834.patch
>
>
> Add below properties during stack upgrade to 2.5 in kerberos environment 
> under kms-site.xml
> {code}
> hadoop.kms.proxyuser.[ranger].groups=*
> hadoop.kms.proxyuser.[ranger].hosts=*
> hadoop.kms.proxyuser.[ranger].users=*
> {code}



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

[jira] [Updated] (AMBARI-18834) Add Ranger proxy user under Ranger KMS config during stack upgrade

[Mugdha Varadkar (JIRA)]

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

Mugdha Varadkar updated AMBARI-18834:
-
Resolution: Fixed
Status: Resolved  (was: Patch Available)

Committed to branch-2.5: 
https://github.com/apache/ambari/commit/d3c75557ec7bc20fa9b2782137a6412aa09a8afb
trunk: 
https://github.com/apache/ambari/commit/b5b73d20274a8bbffcebbd9f099e30949220

> Add Ranger proxy user under Ranger KMS config during stack upgrade
> --
>
> Key: AMBARI-18834
> URL: https://issues.apache.org/jira/browse/AMBARI-18834
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.4.0
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18834.1.patch, AMBARI-18834.2.patch, 
> AMBARI-18834.2.trunk.patch, AMBARI-18834.patch
>
>
> Add below properties during stack upgrade to 2.5 in kerberos environment 
> under kms-site.xml
> {code}
> hadoop.kms.proxyuser.[ranger].groups=*
> hadoop.kms.proxyuser.[ranger].hosts=*
> hadoop.kms.proxyuser.[ranger].users=*
> {code}



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

[jira] [Updated] (AMBARI-18834) Add Ranger proxy user under Ranger KMS config during stack upgrade

[Mugdha Varadkar (JIRA)]

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

Mugdha Varadkar updated AMBARI-18834:
-
Status: Patch Available  (was: In Progress)

> Add Ranger proxy user under Ranger KMS config during stack upgrade
> --
>
> Key: AMBARI-18834
> URL: https://issues.apache.org/jira/browse/AMBARI-18834
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.4.0
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18834.1.patch, AMBARI-18834.2.patch, 
> AMBARI-18834.2.trunk.patch, AMBARI-18834.patch
>
>
> Add below properties during stack upgrade to 2.5 in kerberos environment 
> under kms-site.xml
> {code}
> hadoop.kms.proxyuser.[ranger].groups=*
> hadoop.kms.proxyuser.[ranger].hosts=*
> hadoop.kms.proxyuser.[ranger].users=*
> {code}



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

[jira] [Updated] (AMBARI-18834) Add Ranger proxy user under Ranger KMS config during stack upgrade

[Mugdha Varadkar (JIRA)]

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

Mugdha Varadkar updated AMBARI-18834:
-
Attachment: AMBARI-18834.2.trunk.patch

> Add Ranger proxy user under Ranger KMS config during stack upgrade
> --
>
> Key: AMBARI-18834
> URL: https://issues.apache.org/jira/browse/AMBARI-18834
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.4.0
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18834.1.patch, AMBARI-18834.2.patch, 
> AMBARI-18834.2.trunk.patch, AMBARI-18834.patch
>
>
> Add below properties during stack upgrade to 2.5 in kerberos environment 
> under kms-site.xml
> {code}
> hadoop.kms.proxyuser.[ranger].groups=*
> hadoop.kms.proxyuser.[ranger].hosts=*
> hadoop.kms.proxyuser.[ranger].users=*
> {code}



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

[jira] [Updated] (AMBARI-18834) Add Ranger proxy user under Ranger KMS config during stack upgrade

[Mugdha Varadkar (JIRA)]

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

Mugdha Varadkar updated AMBARI-18834:
-
Status: In Progress  (was: Patch Available)

> Add Ranger proxy user under Ranger KMS config during stack upgrade
> --
>
> Key: AMBARI-18834
> URL: https://issues.apache.org/jira/browse/AMBARI-18834
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.4.0
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18834.1.patch, AMBARI-18834.2.patch, 
> AMBARI-18834.patch
>
>
> Add below properties during stack upgrade to 2.5 in kerberos environment 
> under kms-site.xml
> {code}
> hadoop.kms.proxyuser.[ranger].groups=*
> hadoop.kms.proxyuser.[ranger].hosts=*
> hadoop.kms.proxyuser.[ranger].users=*
> {code}



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

[jira] [Updated] (AMBARI-18929) Yarn service check fails when either resource manager is down in HA enabled cluster

[Weiwei Yang (JIRA)]

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

Weiwei Yang updated AMBARI-18929:
-
Attachment: AMBARI-18929_trunk.02.patch

> Yarn service check fails when either resource manager is down in HA enabled 
> cluster
> ---
>
> Key: AMBARI-18929
> URL: https://issues.apache.org/jira/browse/AMBARI-18929
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Weiwei Yang
> Attachments: AMBARI-18929_trunk.02.patch, AMBARI-18929_trunk.patch
>
>
> When HA is enabled, yarn service_check.py fails if one of RM is down, even 
> the other one is active. This gives user the wrong impression the yarn 
> cluster is not healthy. Instead, service check should pass, or at least pass 
> with warning that lets user know there is one RM down.



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

[jira] [Updated] (AMBARI-19006) EU to message users to start YARN queues if work preserving recovery is disabled

[Alejandro Fernandez (JIRA)]

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

Alejandro Fernandez updated AMBARI-19006:
-
Attachment: AMBARI-19006.patch

> EU to message users to start YARN queues if work preserving recovery is 
> disabled
> 
>
> Key: AMBARI-19006
> URL: https://issues.apache.org/jira/browse/AMBARI-19006
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 2.5.0
>
> Attachments: AMBARI-19006.patch
>
>
> Today, the Express Upgrade packs message users to stop YARN queues if they do 
> not have work preserving recovery enabled.
> However, there's no message reminding users to enable it again.
> E.g.,
> {code}
> 
>   false
>   true
>   
>   
>  property="yarn.resourcemanager.work-preserving-recovery.enabled" value="true" 
> comparison="not-equal"/>
> 
>   Before continuing, please start all YARN queues if you 
> stopped them in a previous step.
> 
>   
> 
> {code}



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

[jira] [Updated] (AMBARI-19006) EU to message users to start YARN queues if work preserving recovery is disabled

[Alejandro Fernandez (JIRA)]

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

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

> EU to message users to start YARN queues if work preserving recovery is 
> disabled
> 
>
> Key: AMBARI-19006
> URL: https://issues.apache.org/jira/browse/AMBARI-19006
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 2.5.0
>
> Attachments: AMBARI-19006.patch
>
>
> Today, the Express Upgrade packs message users to stop YARN queues if they do 
> not have work preserving recovery enabled.
> However, there's no message reminding users to enable it again.
> E.g.,
> {code}
> 
>   false
>   true
>   
>   
>  property="yarn.resourcemanager.work-preserving-recovery.enabled" value="true" 
> comparison="not-equal"/>
> 
>   Before continuing, please start all YARN queues if you 
> stopped them in a previous step.
> 
>   
> 
> {code}



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

[jira] [Created] (AMBARI-19006) EU to message users to start YARN queues if work preserving recovery is disabled

[Alejandro Fernandez (JIRA)]

Alejandro Fernandez created AMBARI-19006:


 Summary: EU to message users to start YARN queues if work 
preserving recovery is disabled
 Key: AMBARI-19006
 URL: https://issues.apache.org/jira/browse/AMBARI-19006
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: 2.5.0
Reporter: Alejandro Fernandez
Assignee: Alejandro Fernandez
 Fix For: 2.5.0


Today, the Express Upgrade packs message users to stop YARN queues if they do 
not have work preserving recovery enabled.
However, there's no message reminding users to enable it again.

E.g.,
{code}

  false
  true
  

  


  Before continuing, please start all YARN queues if you 
stopped them in a previous step.

  

{code}



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

[jira] [Updated] (AMBARI-19005) 'conf.server' dir for HIVE1 and HIVE2 should have 700 permission and files in it should have 600 permission.

[Swapan Shridhar (JIRA)]

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

Swapan Shridhar updated AMBARI-19005:
-
Description: 
**Existing permissions for Hive1 and Hive2's 'conf.server' and files in it were 
:**


**hive1:**

-
$ ls -ltr /usr/hdp/current/hive-server2/conf/ | grep conf.server
drwxr-xr-x. 2 hive hadoop   4096 Nov 22 00:17 conf.server


$ ls -ltr /usr/hdp/current/hive-server2/conf/conf.server/
total 56
-rw-r--r--. 1 hive hadoop  6784 Nov 16 00:16 mapred-site.xml
-rw-r--r--. 1 hive hadoop 0 Nov 16 00:16 hive-default.xml.template
-rw-r--r--. 1 hive hadoop 0 Nov 16 00:16 hive-env.sh.template
-rw-r--r--. 1 hive hadoop  2652 Nov 16 00:16 hive-exec-log4j.properties
-rw-r--r--. 1 hive hadoop  3050 Nov 16 00:16 hive-log4j.properties
-rw-r--r--. 1 hive hadoop   563 Nov 16 00:16 hivemetastore-site.xml
-rw-r--r--. 1 hive hadoop   898 Nov 16 00:16 
hadoop-metrics2-hivemetastore.properties
-rw-r--r--. 1 hive hadoop   677 Nov 16 00:17 hiveserver2-site.xml
-rw-r--r--. 1 hive hadoop   898 Nov 16 00:17 
hadoop-metrics2-hiveserver2.properties
-rw-r--r--. 1 hive hadoop 19625 Nov 16 09:22 hive-site.xml
-rw-r--r--. 1 hive hadoop  2163 Nov 16 10:08 hive-env.sh

-


**hive2:**




-
$ ls -ltr /usr/hdp/current/hive-server2-hive2/conf/ | grep conf.server
drwxr-xr-x. 2 hive hadoop   4096 Nov 22 08:10 conf.server



$ ls -ltr /etc/hive2/conf/conf.server/
total 76
-rw-r--r--. 1 hive hadoop  6784 Nov 16 08:10 mapred-site.xml
-rw-r--r--. 1 hive hadoop 0 Nov 16 08:10 hive-default.xml.template
-rw-r--r--. 1 hive hadoop 0 Nov 16 08:10 hive-env.sh.template
-rw-r--r--. 1 hive hadoop   793 Nov 16 08:10 hiveserver2-site.xml
-rw-r--r--. 1 hive hadoop  1675 Nov 16 08:10 hive-env.sh
-rw-r--r--. 1 hive hadoop  6378 Nov 16 08:10 llap-daemon-log4j2.properties
-rw-r--r--. 1 hive hadoop  2715 Nov 16 08:10 llap-cli-log4j2.properties
-rw-r--r--. 1 hive hadoop  2757 Nov 16 08:10 hive-log4j2.properties
-rw-r--r--. 1 hive hadoop  2287 Nov 16 08:10 hive-exec-log4j2.properties
-rw-r--r--. 1 hive hadoop  1596 Nov 16 08:10 beeline-log4j2.properties
-rw-r--r--. 1 hive hadoop   898 Nov 16 08:10 
hadoop-metrics2-hiveserver2.properties
-rw-r--r--. 1 hive hadoop   898 Nov 16 08:10 
hadoop-metrics2-llapdaemon.properties
-rw-r--r--. 1 hive hadoop   898 Nov 16 08:10 
hadoop-metrics2-llaptaskscheduler.properties
-rw-r--r--. 1 hive hadoop 23688 Nov 22 20:27 hive-site.xml

-



**New updated permissions for Hive1 and Hive2's 'conf.server' and files in it 
are :**



**hive1:**



-
$ ls -ltr /usr/hdp/current/hive-server2/conf/ | grep conf.server
drwx--. 2 hive hadoop   4096 Nov 16 00:17 conf.server


$ ls -ltr /usr/hdp/current/hive-server2/conf/conf.server
total 56
-rw---. 1 hive hadoop 0 Nov 16 00:16 hive-default.xml.template
-rw---. 1 hive hadoop 0 Nov 16 00:16 hive-env.sh.template
-rw---. 1 hive hadoop  2652 Nov 16 00:16 hive-exec-log4j.properties
-rw---. 1 hive hadoop  3050 Nov 16 00:16 hive-log4j.properties
-rw---. 1 hive hadoop   563 Nov 16 00:16 hivemetastore-site.xml
-rw---. 1 hive hadoop   898 Nov 16 00:16 
hadoop-metrics2-hivemetastore.properties
-rw---. 1 hive hadoop   677 Nov 16 00:17 hiveserver2-site.xml
-rw---. 1 hive hadoop   898 Nov 16 00:17 
hadoop-metrics2-hiveserver2.properties
-rw---. 1 hive hadoop 19625 Nov 16 09:22 hive-site.xml
-rw---. 1 hive hadoop  6781 Nov 23 22:54 mapred-site.xml
-rw---. 1 hive hadoop  2163 Nov 28 23:31 hive-env.sh

-

**hive2:**



-
$ ls -ltr /usr/hdp/current/hive-server2-hive2/conf/ | grep conf.server
drwx--. 2 hive hadoop   4096 Nov 23 21:18 conf.server

$ ls -ltr /usr/hdp/current/hive-server2-hive2/conf/conf.server/
total 76
-rw---. 1 hive hadoop 0 Nov 16 08:10 hive-default.xml.template
-rw---. 1 hive hadoop 0 Nov 16 08:10 hive-env.sh.template
-rw---. 1 hive hadoop   793 Nov 16 08:10 hiveserver2-site.xml
-rw---. 1 hive hadoop  1675 Nov 16 08:10 hive-env.sh
-rw---. 1 hive hadoop  6378 Nov 16 08:10 llap-daemon-log4j2.properties
-rw---. 1 hive hadoop  2715 Nov 16 08:10 llap-cli-log4j2.properties
-rw---. 1 hive hadoop  2757 Nov 16 08:10 hive-log4j2.properties
-rw---. 1 hive hadoop  2287 Nov 16 08:10 hive-exec-log4j2.properties
-rw---. 1 hive hadoop  1596 Nov 16 08:10 beeline-log4j2.properties
-rw---. 1 hive hadoop   89

[jira] [Updated] (AMBARI-19005) 'conf.server' dir for HIVE1 and HIVE2 should have 700 permission and files in it should have 600 permission.

[Swapan Shridhar (JIRA)]

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

Swapan Shridhar updated AMBARI-19005:
-
Description: 
**Existing permissions for Hive1 and Hive2's 'conf.server' and files in it were 
:**
**hive1:**

-
$ ls -ltr /usr/hdp/current/hive-server2/conf/ | grep conf.server
drwxr-xr-x. 2 hive hadoop   4096 Nov 22 00:17 conf.server


$ ls -ltr /usr/hdp/current/hive-server2/conf/conf.server/
total 56
-rw-r--r--. 1 hive hadoop  6784 Nov 16 00:16 mapred-site.xml
-rw-r--r--. 1 hive hadoop 0 Nov 16 00:16 hive-default.xml.template
-rw-r--r--. 1 hive hadoop 0 Nov 16 00:16 hive-env.sh.template
-rw-r--r--. 1 hive hadoop  2652 Nov 16 00:16 hive-exec-log4j.properties
-rw-r--r--. 1 hive hadoop  3050 Nov 16 00:16 hive-log4j.properties
-rw-r--r--. 1 hive hadoop   563 Nov 16 00:16 hivemetastore-site.xml
-rw-r--r--. 1 hive hadoop   898 Nov 16 00:16 
hadoop-metrics2-hivemetastore.properties
-rw-r--r--. 1 hive hadoop   677 Nov 16 00:17 hiveserver2-site.xml
-rw-r--r--. 1 hive hadoop   898 Nov 16 00:17 
hadoop-metrics2-hiveserver2.properties
-rw-r--r--. 1 hive hadoop 19625 Nov 16 09:22 hive-site.xml
-rw-r--r--. 1 hive hadoop  2163 Nov 16 10:08 hive-env.sh

-


**hive2:**




-
$ ls -ltr /usr/hdp/current/hive-server2-hive2/conf/ | grep conf.server
drwxr-xr-x. 2 hive hadoop   4096 Nov 22 08:10 conf.server



$ ls -ltr /etc/hive2/conf/conf.server/
total 76
-rw-r--r--. 1 hive hadoop  6784 Nov 16 08:10 mapred-site.xml
-rw-r--r--. 1 hive hadoop 0 Nov 16 08:10 hive-default.xml.template
-rw-r--r--. 1 hive hadoop 0 Nov 16 08:10 hive-env.sh.template
-rw-r--r--. 1 hive hadoop   793 Nov 16 08:10 hiveserver2-site.xml
-rw-r--r--. 1 hive hadoop  1675 Nov 16 08:10 hive-env.sh
-rw-r--r--. 1 hive hadoop  6378 Nov 16 08:10 llap-daemon-log4j2.properties
-rw-r--r--. 1 hive hadoop  2715 Nov 16 08:10 llap-cli-log4j2.properties
-rw-r--r--. 1 hive hadoop  2757 Nov 16 08:10 hive-log4j2.properties
-rw-r--r--. 1 hive hadoop  2287 Nov 16 08:10 hive-exec-log4j2.properties
-rw-r--r--. 1 hive hadoop  1596 Nov 16 08:10 beeline-log4j2.properties
-rw-r--r--. 1 hive hadoop   898 Nov 16 08:10 
hadoop-metrics2-hiveserver2.properties
-rw-r--r--. 1 hive hadoop   898 Nov 16 08:10 
hadoop-metrics2-llapdaemon.properties
-rw-r--r--. 1 hive hadoop   898 Nov 16 08:10 
hadoop-metrics2-llaptaskscheduler.properties
-rw-r--r--. 1 hive hadoop 23688 Nov 22 20:27 hive-site.xml

-


#===
New updated permissions for Hive1 and Hive2's 'conf.server' and files in it are 
:
#===



**hive1:**



-
$ ls -ltr /usr/hdp/current/hive-server2/conf/ | grep conf.server
drwx--. 2 hive hadoop   4096 Nov 16 00:17 conf.server


$ ls -ltr /usr/hdp/current/hive-server2/conf/conf.server
total 56
-rw---. 1 hive hadoop 0 Nov 16 00:16 hive-default.xml.template
-rw---. 1 hive hadoop 0 Nov 16 00:16 hive-env.sh.template
-rw---. 1 hive hadoop  2652 Nov 16 00:16 hive-exec-log4j.properties
-rw---. 1 hive hadoop  3050 Nov 16 00:16 hive-log4j.properties
-rw---. 1 hive hadoop   563 Nov 16 00:16 hivemetastore-site.xml
-rw---. 1 hive hadoop   898 Nov 16 00:16 
hadoop-metrics2-hivemetastore.properties
-rw---. 1 hive hadoop   677 Nov 16 00:17 hiveserver2-site.xml
-rw---. 1 hive hadoop   898 Nov 16 00:17 
hadoop-metrics2-hiveserver2.properties
-rw---. 1 hive hadoop 19625 Nov 16 09:22 hive-site.xml
-rw---. 1 hive hadoop  6781 Nov 23 22:54 mapred-site.xml
-rw---. 1 hive hadoop  2163 Nov 28 23:31 hive-env.sh

-

**hive2:**



-
$ ls -ltr /usr/hdp/current/hive-server2-hive2/conf/ | grep conf.server
drwx--. 2 hive hadoop   4096 Nov 23 21:18 conf.server

$ ls -ltr /usr/hdp/current/hive-server2-hive2/conf/conf.server/
total 76
-rw---. 1 hive hadoop 0 Nov 16 08:10 hive-default.xml.template
-rw---. 1 hive hadoop 0 Nov 16 08:10 hive-env.sh.template
-rw---. 1 hive hadoop   793 Nov 16 08:10 hiveserver2-site.xml
-rw---. 1 hive hadoop  1675 Nov 16 08:10 hive-env.sh
-rw---. 1 hive hadoop  6378 Nov 16 08:10 llap-daemon-log4j2.properties
-rw---. 1 hive hadoop  2715 Nov 16 08:10 llap-cli-log4j2.properties
-rw---. 1 hive hadoop  2757 Nov 16 08:10 hive-log4j2.properties
-rw---. 1 hive 

[jira] [Updated] (AMBARI-19005) 'conf.server' dir for HIVE1 and HIVE2 should have 700 permission and files in it should have 600 permission.

[Swapan Shridhar (JIRA)]

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

Swapan Shridhar updated AMBARI-19005:
-
Status: Patch Available  (was: In Progress)

> 'conf.server' dir for HIVE1 and HIVE2 should have 700 permission and files in 
> it should have 600 permission.
> 
>
> Key: AMBARI-19005
> URL: https://issues.apache.org/jira/browse/AMBARI-19005
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.1
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19005.patch
>
>




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

[jira] [Updated] (AMBARI-19005) 'conf.server' dir for HIVE1 and HIVE2 should have 700 permission and files in it should have 600 permission.

[Swapan Shridhar (JIRA)]

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

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

> 'conf.server' dir for HIVE1 and HIVE2 should have 700 permission and files in 
> it should have 600 permission.
> 
>
> Key: AMBARI-19005
> URL: https://issues.apache.org/jira/browse/AMBARI-19005
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.1
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19005.patch
>
>




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

[jira] [Commented] (AMBARI-18987) A general preupgrade check on if services cannot be upgrade are installed

[Hudson (JIRA)]

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

Hudson commented on AMBARI-18987:
-

FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #396 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/396/])
AMBARI-18987 A general preupgrade check on if services cannot be upgrade (dili: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=68a881ef1d713c0764c8546eff2007c4630a933e])
* (add) 
ambari-server/src/main/java/org/apache/ambari/server/checks/ServicePresenceCheck.java
* (add) 
ambari-server/src/test/java/org/apache/ambari/server/checks/ServicePresenceCheckTest.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/checks/CheckDescription.java


> A general preupgrade check on if services cannot be upgrade are installed
> -
>
> Key: AMBARI-18987
> URL: https://issues.apache.org/jira/browse/AMBARI-18987
> Project: Ambari
>  Issue Type: New Feature
>  Components: ambari-server
>Affects Versions: trunk, 2.5.0
>Reporter: Di Li
>Assignee: Di Li
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-18987.patch
>
>
> A general check that takes list of services defined in upgrade XML and check 
> if they are installed, fail the check if there is at least one hit.
> Displaying different error messages depending on if a service does not 
> support upgrade or if a service is removed in the new release ( the two types 
> are specified via different properties in the upgrade XML files.



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

[jira] [Commented] (AMBARI-18841) Grafana fails to start

[Hudson (JIRA)]

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

Hudson commented on AMBARI-18841:
-

ABORTED: Integrated in Jenkins build Ambari-branch-2.5 #395 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/395/])
AMBARI-18841 : Grafana fails to start (Commit 2) (avijayan) (avijayan: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=1b63b9094f28b04fa361d8ad3c7ab122716d544d])
* (edit) ambari-metrics/ambari-metrics-grafana/conf/unix/ambari-metrics-grafana


> Grafana fails to start
> --
>
> Key: AMBARI-18841
> URL: https://issues.apache.org/jira/browse/AMBARI-18841
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics
>Affects Versions: 2.5.0
> Environment: Fresh install of 2.5.0 cluster.
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-18841-2.patch, AMBARI-18841.patch
>
>
> Grafana fails to start with the below error
> {code}
> Traceback (most recent call last):
>   File 
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py",
>  line 69, in 
> AmsGrafana().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/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py",
>  line 47, in start
> not_if = params.grafana_process_exists_cmd,
>   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 262, 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 72, in inner
> result = function(command, **kwargs)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 102, in checked_call
> tries=tries, try_sleep=try_sleep, 
> timeout_kill_strategy=timeout_kill_strategy)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 150, in _call_wrapper
> result = _call(command, **kwargs_copy)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 303, in _call
> raise ExecutionFailed(err_msg, code, out, err)
> resource_management.core.exceptions.ExecutionFailed: Execution of 
> '/usr/sbin/ambari-metrics-grafana start' returned 1.  Hortonworks 
> #
> This is MOTD message, added for testing in qe infra
> Starting Ambari Metrics Grafana:  FAILED
> {code}



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

[jira] [Commented] (AMBARI-18992) Stack version input text field on Register Version page should align properly even when resizing the page

[Hudson (JIRA)]

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

Hudson commented on AMBARI-18992:
-

ABORTED: Integrated in Jenkins build Ambari-branch-2.5 #395 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/395/])
AMBARI-18992: Stack version input text field on Register Version page (dili: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=17d2ab1f9b0086d12b6be49167606e43741ae702])
* (edit) 
ambari-admin/src/main/resources/ui/admin-web/app/views/stackVersions/stackVersionPage.html


> Stack version input text field on Register Version page should align properly 
> even when resizing the page
> -
>
> Key: AMBARI-18992
> URL: https://issues.apache.org/jira/browse/AMBARI-18992
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-admin
>Affects Versions: trunk
>Reporter: Di Li
>Assignee: Di Li
> Attachments: AMBARI-18992.patch, 
> stack_version_input_misaligned_1.png, stack_version_input_misaligned_2.png
>
>
> When the page is maximized to full size, the input field left boarder goes 
> beyond the outer boarder. 
> when the page is resized, the input field may tuck under the HDP x.x word and 
> overlaps with the Name: label.



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

[jira] [Commented] (AMBARI-18951) Force InnoDB usage for MySQL

[Hudson (JIRA)]

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

Hudson commented on AMBARI-18951:
-

ABORTED: Integrated in Jenkins build Ambari-branch-2.5 #395 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/395/])
AMBARI-18951. Force InnoDB usage for MySQL. (mpapirkovskyy) (mpapyrkovskyy: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=98e41c677b2e22e694eda27ee6217d560ac4dbe2])
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/upgrade/SchemaUpgradeHelper.java
* (edit) ambari-server/src/main/resources/Ambari-DDL-MySQL-CREATE.sql
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/orm/helpers/dbms/MySqlHelper.java


> Force InnoDB usage for MySQL
> 
>
> Key: AMBARI-18951
> URL: https://issues.apache.org/jira/browse/AMBARI-18951
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.2
>Reporter: Myroslav Papirkovskyi
>Assignee: Myroslav Papirkovskyi
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18951.patch
>
>
> We should always use InnoDB as database engine for MySQL as database with 
> MyISAM engine cannot be upgraded properly.
> Key reason is that MyISAM doesn't store foreign keys information, but do 
> store indexes with same name which lead to conflicts during upgrade.



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

[jira] [Created] (AMBARI-19005) 'conf.server' dir for HIVE1 and HIVE2 should have 700 permission and files in it should have 600 permission.

[Swapan Shridhar (JIRA)]

Swapan Shridhar created AMBARI-19005:


 Summary: 'conf.server' dir for HIVE1 and HIVE2 should have 700 
permission and files in it should have 600 permission.
 Key: AMBARI-19005
 URL: https://issues.apache.org/jira/browse/AMBARI-19005
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: 2.4.1
Reporter: Swapan Shridhar
Assignee: Swapan Shridhar
Priority: Critical
 Fix For: 2.5.0






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

[jira] [Updated] (AMBARI-18841) Grafana fails to start

[Aravindan Vijayan (JIRA)]

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

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

Pushed to branch-2.5 and trunk.

> Grafana fails to start
> --
>
> Key: AMBARI-18841
> URL: https://issues.apache.org/jira/browse/AMBARI-18841
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics
>Affects Versions: 2.5.0
> Environment: Fresh install of 2.5.0 cluster.
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-18841-2.patch, AMBARI-18841.patch
>
>
> Grafana fails to start with the below error
> {code}
> Traceback (most recent call last):
>   File 
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py",
>  line 69, in 
> AmsGrafana().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/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py",
>  line 47, in start
> not_if = params.grafana_process_exists_cmd,
>   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 262, 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 72, in inner
> result = function(command, **kwargs)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 102, in checked_call
> tries=tries, try_sleep=try_sleep, 
> timeout_kill_strategy=timeout_kill_strategy)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 150, in _call_wrapper
> result = _call(command, **kwargs_copy)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 303, in _call
> raise ExecutionFailed(err_msg, code, out, err)
> resource_management.core.exceptions.ExecutionFailed: Execution of 
> '/usr/sbin/ambari-metrics-grafana start' returned 1.  Hortonworks 
> #
> This is MOTD message, added for testing in qe infra
> Starting Ambari Metrics Grafana:  FAILED
> {code}



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

[jira] [Created] (AMBARI-19004) Logs tab in host details page not populating any logs

[Kishor Ramakrishnan (JIRA)]

Kishor Ramakrishnan created AMBARI-19004:


 Summary: Logs tab in host details page not populating any logs
 Key: AMBARI-19004
 URL: https://issues.apache.org/jira/browse/AMBARI-19004
 Project: Ambari
  Issue Type: Bug
  Components: ambari-web
Affects Versions: 2.5.0
Reporter: Kishor Ramakrishnan
Priority: Critical
 Fix For: 2.5.0


Logs tab in host details page not populating any logs.

STR:
Navigate to Ambari dashboard > Hosts page
Select any host and navigate to host details page
Navigate to Logs Tab
Expected: Logs of the components available on the host selected should be 
displayed according to the filters enabled
Actual : No log entries displayed.



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

[jira] [Updated] (AMBARI-19003) Perf: Fix deploy-gce-perf-cluster.py to deploy separate server onto own cluster with different settings for more cores and MySQL DB

[Alejandro Fernandez (JIRA)]

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

Alejandro Fernandez updated AMBARI-19003:
-
Attachment: AMBARI-19003.patch

> Perf: Fix deploy-gce-perf-cluster.py to deploy separate server onto own 
> cluster with different settings for more cores and MySQL DB
> ---
>
> Key: AMBARI-19003
> URL: https://issues.apache.org/jira/browse/AMBARI-19003
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.5.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 2.5.0
>
> Attachments: AMBARI-19003.patch
>
>
> Right now, deploy-gce-perf-cluster.py puts Ambari Server on the same 4 core 
> VM where it puts 50 agents. Instead, we need to create a separate 16-core VM 
> for the server without any agents.
> Next, Ambari Server should be installed with MySQL database instead since it 
> has more configuration options that the default postgres.
> Further, the sorting of the VMs is not numeric since "perf-9" comes after 
> "perf-42". The incorrect sorting means that VM #i isn't getting the agents 
> starting with number (i-1)*50+1



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

[jira] [Updated] (AMBARI-19003) Perf: Fix deploy-gce-perf-cluster.py to deploy separate server onto own cluster with different settings for more cores and MySQL DB

[Alejandro Fernandez (JIRA)]

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

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

> Perf: Fix deploy-gce-perf-cluster.py to deploy separate server onto own 
> cluster with different settings for more cores and MySQL DB
> ---
>
> Key: AMBARI-19003
> URL: https://issues.apache.org/jira/browse/AMBARI-19003
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.5.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 2.5.0
>
> Attachments: AMBARI-19003.patch
>
>
> Right now, deploy-gce-perf-cluster.py puts Ambari Server on the same 4 core 
> VM where it puts 50 agents. Instead, we need to create a separate 16-core VM 
> for the server without any agents.
> Next, Ambari Server should be installed with MySQL database instead since it 
> has more configuration options that the default postgres.
> Further, the sorting of the VMs is not numeric since "perf-9" comes after 
> "perf-42". The incorrect sorting means that VM #i isn't getting the agents 
> starting with number (i-1)*50+1



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

[jira] [Updated] (AMBARI-19003) Perf: Fix deploy-gce-perf-cluster.py to deploy separate server onto own cluster with different settings

[Alejandro Fernandez (JIRA)]

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

Alejandro Fernandez updated AMBARI-19003:
-
Description: 
Right now, deploy-gce-perf-cluster.py puts Ambari Server on the same 4 core VM 
where it puts 50 agents. Instead, we need to create a separate 16-core VM for 
the server without any agents.
Next, Ambari Server should be installed with MySQL database instead since it 
has more configuration options that the default postgres.

Further, the sorting of the VMs is not numeric since "perf-9" comes after 
"perf-42". The incorrect sorting means that VM #i isn't getting the agents 
starting with number (i-1)*50+1

  was:
Right now, deploy-gce-perf-cluster.py puts Ambari Server on the same 4 core VM 
where it puts 50 agents. Instead, we need to create a separate 16-core VM for 
the server without any agents.

Further, the sorting of the VMs is not numeric since "perf-9" comes after 
"perf-42". The incorrect sorting means that VM #i isn't getting the agents 
starting with number (i-1)*50+1


> Perf: Fix deploy-gce-perf-cluster.py to deploy separate server onto own 
> cluster with different settings
> ---
>
> Key: AMBARI-19003
> URL: https://issues.apache.org/jira/browse/AMBARI-19003
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.5.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 2.5.0
>
>
> Right now, deploy-gce-perf-cluster.py puts Ambari Server on the same 4 core 
> VM where it puts 50 agents. Instead, we need to create a separate 16-core VM 
> for the server without any agents.
> Next, Ambari Server should be installed with MySQL database instead since it 
> has more configuration options that the default postgres.
> Further, the sorting of the VMs is not numeric since "perf-9" comes after 
> "perf-42". The incorrect sorting means that VM #i isn't getting the agents 
> starting with number (i-1)*50+1



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

[jira] [Updated] (AMBARI-19003) Perf: Fix deploy-gce-perf-cluster.py to deploy separate server onto own cluster with different settings for more cores and MySQL DB

[Alejandro Fernandez (JIRA)]

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

Alejandro Fernandez updated AMBARI-19003:
-
Summary: Perf: Fix deploy-gce-perf-cluster.py to deploy separate server 
onto own cluster with different settings for more cores and MySQL DB  (was: 
Perf: Fix deploy-gce-perf-cluster.py to deploy separate server onto own cluster 
with different settings)

> Perf: Fix deploy-gce-perf-cluster.py to deploy separate server onto own 
> cluster with different settings for more cores and MySQL DB
> ---
>
> Key: AMBARI-19003
> URL: https://issues.apache.org/jira/browse/AMBARI-19003
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.5.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 2.5.0
>
>
> Right now, deploy-gce-perf-cluster.py puts Ambari Server on the same 4 core 
> VM where it puts 50 agents. Instead, we need to create a separate 16-core VM 
> for the server without any agents.
> Next, Ambari Server should be installed with MySQL database instead since it 
> has more configuration options that the default postgres.
> Further, the sorting of the VMs is not numeric since "perf-9" comes after 
> "perf-42". The incorrect sorting means that VM #i isn't getting the agents 
> starting with number (i-1)*50+1



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

[jira] [Created] (AMBARI-19003) Perf: Fix deploy-gce-perf-cluster.py to deploy separate server onto own cluster with different settings

[Alejandro Fernandez (JIRA)]

Alejandro Fernandez created AMBARI-19003:


 Summary: Perf: Fix deploy-gce-perf-cluster.py to deploy separate 
server onto own cluster with different settings
 Key: AMBARI-19003
 URL: https://issues.apache.org/jira/browse/AMBARI-19003
 Project: Ambari
  Issue Type: Bug
  Components: stacks
Affects Versions: 2.5.0
Reporter: Alejandro Fernandez
Assignee: Alejandro Fernandez
 Fix For: 2.5.0


Right now, deploy-gce-perf-cluster.py puts Ambari Server on the same 4 core VM 
where it puts 50 agents. Instead, we need to create a separate 16-core VM for 
the server without any agents.

Further, the sorting of the VMs is not numeric since "perf-9" comes after 
"perf-42". The incorrect sorting means that VM #i isn't getting the agents 
starting with number (i-1)*50+1



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

[jira] [Commented] (AMBARI-18987) A general preupgrade check on if services cannot be upgrade are installed

[Di Li (JIRA)]

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

Di Li commented on AMBARI-18987:


Test failures had existed since: 
https://builds.apache.org/job/Ambari-trunk-Commit/6094/
Test Result (2 failures / ±0)
org.apache.ambari.server.controller.metrics.JMXPropertyProviderTest.testJMXPropertyProviderAsAdministrator
org.apache.ambari.server.controller.metrics.JMXPropertyProviderTest.testJMXPropertyProviderAsServiceAdministrator

Code introduced in this JIRA does not impact JMXPropertyProviderTest


> A general preupgrade check on if services cannot be upgrade are installed
> -
>
> Key: AMBARI-18987
> URL: https://issues.apache.org/jira/browse/AMBARI-18987
> Project: Ambari
>  Issue Type: New Feature
>  Components: ambari-server
>Affects Versions: trunk, 2.5.0
>Reporter: Di Li
>Assignee: Di Li
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-18987.patch
>
>
> A general check that takes list of services defined in upgrade XML and check 
> if they are installed, fail the check if there is at least one hit.
> Displaying different error messages depending on if a service does not 
> support upgrade or if a service is removed in the new release ( the two types 
> are specified via different properties in the upgrade XML files.



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

[jira] [Commented] (AMBARI-18987) A general preupgrade check on if services cannot be upgrade are installed

[Hudson (JIRA)]

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

Hudson commented on AMBARI-18987:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6097 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6097/])
AMBARI-18987 A general preupgrade check on if services cannot be upgrade (dili: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=bb803fb332d8d247e236b5e1b29fe97acfd7a7ec])
* (add) 
ambari-server/src/test/java/org/apache/ambari/server/checks/ServicePresenceCheckTest.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/checks/CheckDescription.java
* (add) 
ambari-server/src/main/java/org/apache/ambari/server/checks/ServicePresenceCheck.java


> A general preupgrade check on if services cannot be upgrade are installed
> -
>
> Key: AMBARI-18987
> URL: https://issues.apache.org/jira/browse/AMBARI-18987
> Project: Ambari
>  Issue Type: New Feature
>  Components: ambari-server
>Affects Versions: trunk, 2.5.0
>Reporter: Di Li
>Assignee: Di Li
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-18987.patch
>
>
> A general check that takes list of services defined in upgrade XML and check 
> if they are installed, fail the check if there is at least one hit.
> Displaying different error messages depending on if a service does not 
> support upgrade or if a service is removed in the new release ( the two types 
> are specified via different properties in the upgrade XML files.



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

[jira] [Commented] (AMBARI-18987) A general preupgrade check on if services cannot be upgrade are installed

[Di Li (JIRA)]

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

Di Li commented on AMBARI-18987:


Pushed to Trunk as
https://git-wip-us.apache.org/repos/asf?p=ambari.git;a=commit;h=bb803fb332d8d247e236b5e1b29fe97acfd7a7ec

Pushed to Branch-2.5 as
https://git-wip-us.apache.org/repos/asf?p=ambari.git;a=commit;h=68a881ef1d713c0764c8546eff2007c4630a933e


> A general preupgrade check on if services cannot be upgrade are installed
> -
>
> Key: AMBARI-18987
> URL: https://issues.apache.org/jira/browse/AMBARI-18987
> Project: Ambari
>  Issue Type: New Feature
>  Components: ambari-server
>Affects Versions: trunk, 2.5.0
>Reporter: Di Li
>Assignee: Di Li
> Attachments: AMBARI-18987.patch
>
>
> A general check that takes list of services defined in upgrade XML and check 
> if they are installed, fail the check if there is at least one hit.
> Displaying different error messages depending on if a service does not 
> support upgrade or if a service is removed in the new release ( the two types 
> are specified via different properties in the upgrade XML files.



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

[jira] [Updated] (AMBARI-18987) A general preupgrade check on if services cannot be upgrade are installed

[Di Li (JIRA)]

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

Di Li updated AMBARI-18987:
---
Fix Version/s: 2.5.0
   trunk

> A general preupgrade check on if services cannot be upgrade are installed
> -
>
> Key: AMBARI-18987
> URL: https://issues.apache.org/jira/browse/AMBARI-18987
> Project: Ambari
>  Issue Type: New Feature
>  Components: ambari-server
>Affects Versions: trunk, 2.5.0
>Reporter: Di Li
>Assignee: Di Li
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-18987.patch
>
>
> A general check that takes list of services defined in upgrade XML and check 
> if they are installed, fail the check if there is at least one hit.
> Displaying different error messages depending on if a service does not 
> support upgrade or if a service is removed in the new release ( the two types 
> are specified via different properties in the upgrade XML files.



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

[jira] [Updated] (AMBARI-18987) A general preupgrade check on if services cannot be upgrade are installed

[Di Li (JIRA)]

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

Di Li updated AMBARI-18987:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> A general preupgrade check on if services cannot be upgrade are installed
> -
>
> Key: AMBARI-18987
> URL: https://issues.apache.org/jira/browse/AMBARI-18987
> Project: Ambari
>  Issue Type: New Feature
>  Components: ambari-server
>Affects Versions: trunk, 2.5.0
>Reporter: Di Li
>Assignee: Di Li
> Attachments: AMBARI-18987.patch
>
>
> A general check that takes list of services defined in upgrade XML and check 
> if they are installed, fail the check if there is at least one hit.
> Displaying different error messages depending on if a service does not 
> support upgrade or if a service is removed in the new release ( the two types 
> are specified via different properties in the upgrade XML files.



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

[jira] [Commented] (AMBARI-19002) Ambari widgets and service checks to honor LLAP clusters with 100% allocation to LLAP daemons

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-19002:


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

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

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

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

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

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

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

This message is automatically generated.

> Ambari widgets and service checks to honor LLAP clusters with 100% allocation 
> to LLAP daemons
> -
>
> Key: AMBARI-19002
> URL: https://issues.apache.org/jira/browse/AMBARI-19002
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19002.patch
>
>
> As part of this ticket
> When a new config which needs to be introduced as part of this ticket 
> "cluster-env/hide_yarn_memory_widget" is marked to be true then ambari-web 
> should not show "YARN Memory" widget by default on the dashboard. Widget can 
> be made hidden by default when any user logs in for the first time. Then if 
> some specific user explicitly adds the widget back, then user should be able 
> to see it



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

[jira] [Commented] (AMBARI-18992) Stack version input text field on Register Version page should align properly even when resizing the page

[Di Li (JIRA)]

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

Di Li commented on AMBARI-18992:


The build failed on the following two tests that neither is related to the UI 
change pushed in via this JIRA.
  Test Result (2 failures / -1)

org.apache.ambari.server.agent.TestHeartbeatHandler.testRegistrationRecoveryConfig

org.apache.ambari.server.state.cluster.ClusterDeadlockTest.testDeadlockWithConfigsUpdate


> Stack version input text field on Register Version page should align properly 
> even when resizing the page
> -
>
> Key: AMBARI-18992
> URL: https://issues.apache.org/jira/browse/AMBARI-18992
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-admin
>Affects Versions: trunk
>Reporter: Di Li
>Assignee: Di Li
> Attachments: AMBARI-18992.patch, 
> stack_version_input_misaligned_1.png, stack_version_input_misaligned_2.png
>
>
> When the page is maximized to full size, the input field left boarder goes 
> beyond the outer boarder. 
> when the page is resized, the input field may tuck under the HDP x.x word and 
> overlaps with the Name: label.



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

[jira] [Commented] (AMBARI-18976) Config History request execution time depends on config versions count

[Hudson (JIRA)]

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

Hudson commented on AMBARI-18976:
-

ABORTED: Integrated in Jenkins build Ambari-branch-2.5 #394 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/394/])
AMBARI-18976. Config History request execution time depends on config 
(mpapyrkovskyy: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=ce4d4fa768375aac631703dbfceac44fd8faa151])
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/state/cluster/ClusterImpl.java
Revert "AMBARI-18976. Config History request execution time depends on 
(mpapyrkovskyy: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=568d1e656b1f1c651e594a54f3b3744f62984653])
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/state/cluster/ClusterImpl.java
AMBARI-18976. Config History request execution time depends on config 
(mpapyrkovskyy: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=911b917783d66a44958e791e49d76b755d943f85])
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/logging/LoggingSearchPropertyProvider.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/orm/dao/ServiceConfigDAO.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/state/cluster/ClusterImpl.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/orm/dao/ClusterDAO.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/orm/entities/ClusterConfigMappingEntity.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ClusterControllerImpl.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ServiceConfigVersionResourceProvider.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/orm/entities/ClusterConfigEntity.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/orm/entities/ServiceConfigEntity.java


> Config History request execution time depends on config versions count
> --
>
> Key: AMBARI-18976
> URL: https://issues.apache.org/jira/browse/AMBARI-18976
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Myroslav Papirkovskyi
>Assignee: Myroslav Papirkovskyi
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18976.patch
>
>
> Request: 
> {{/api/v1/clusters/tdk/configurations/service_config_versions?fields=group_id,user&minimal_response=true&from=0&page_size=10}}
>  
> Response always contains 10 records or less (if there are less than 10 
> service configs versions). Each record has only two fields ({{group_id}}, 
> {{user}}).
> Request execution time depends on overall count of service config versions in 
> the DB.
> Example:
> || Items Total in the DB || Response Time ||
> |2|~140 ms|
> |100  |900+ ms|
> |290  |3+ s|
> |750  |9+ s|
> |1000 |15+ s|
> |3000 |30+ s|



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

[jira] [Commented] (AMBARI-18992) Stack version input text field on Register Version page should align properly even when resizing the page

[Hudson (JIRA)]

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

Hudson commented on AMBARI-18992:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6096 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6096/])
AMBARI-18992: Stack version input text field on Register Version page (dili: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=640d85a501e5dbc2b7422bf49f2f94a31aa391b6])
* (edit) 
ambari-admin/src/main/resources/ui/admin-web/app/views/stackVersions/stackVersionPage.html


> Stack version input text field on Register Version page should align properly 
> even when resizing the page
> -
>
> Key: AMBARI-18992
> URL: https://issues.apache.org/jira/browse/AMBARI-18992
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-admin
>Affects Versions: trunk
>Reporter: Di Li
>Assignee: Di Li
> Attachments: AMBARI-18992.patch, 
> stack_version_input_misaligned_1.png, stack_version_input_misaligned_2.png
>
>
> When the page is maximized to full size, the input field left boarder goes 
> beyond the outer boarder. 
> when the page is resized, the input field may tuck under the HDP x.x word and 
> overlaps with the Name: label.



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

[jira] [Updated] (AMBARI-18992) Stack version input text field on Register Version page should align properly even when resizing the page

[Di Li (JIRA)]

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

Di Li updated AMBARI-18992:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Stack version input text field on Register Version page should align properly 
> even when resizing the page
> -
>
> Key: AMBARI-18992
> URL: https://issues.apache.org/jira/browse/AMBARI-18992
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-admin
>Affects Versions: trunk
>Reporter: Di Li
>Assignee: Di Li
> Attachments: AMBARI-18992.patch, 
> stack_version_input_misaligned_1.png, stack_version_input_misaligned_2.png
>
>
> When the page is maximized to full size, the input field left boarder goes 
> beyond the outer boarder. 
> when the page is resized, the input field may tuck under the HDP x.x word and 
> overlaps with the Name: label.



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

[jira] [Commented] (AMBARI-18992) Stack version input text field on Register Version page should align properly even when resizing the page

[Di Li (JIRA)]

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

Di Li commented on AMBARI-18992:


Pushed to Trunk as
https://git-wip-us.apache.org/repos/asf?p=ambari.git;a=commit;h=640d85a501e5dbc2b7422bf49f2f94a31aa391b6

Pushed to Branch-2.5 as
https://git-wip-us.apache.org/repos/asf?p=ambari.git;a=commit;h=17d2ab1f9b0086d12b6be49167606e43741ae702


> Stack version input text field on Register Version page should align properly 
> even when resizing the page
> -
>
> Key: AMBARI-18992
> URL: https://issues.apache.org/jira/browse/AMBARI-18992
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-admin
>Affects Versions: trunk
>Reporter: Di Li
>Assignee: Di Li
> Attachments: AMBARI-18992.patch, 
> stack_version_input_misaligned_1.png, stack_version_input_misaligned_2.png
>
>
> When the page is maximized to full size, the input field left boarder goes 
> beyond the outer boarder. 
> when the page is resized, the input field may tuck under the HDP x.x word and 
> overlaps with the Name: label.



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

[jira] [Commented] (AMBARI-18999) Unable to Start Multiple Flume Agents Due to Missing Import

[Hudson (JIRA)]

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

Hudson commented on AMBARI-18999:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6095 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6095/])
AMBARI-18999 - Unable to Start Multiple Flume Agents Due to Missing (jhurley: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=80d09892d685a8179e6ece33a41f59de1b7d580b])
* (edit) 
ambari-server/src/main/resources/common-services/FLUME/1.4.0.2.0/package/scripts/flume.py


> Unable to Start Multiple Flume Agents Due to Missing Import
> ---
>
> Key: AMBARI-18999
> URL: https://issues.apache.org/jira/browse/AMBARI-18999
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 3.0.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: AMBARI-18999.patch
>
>
> Note that this issue does not affect Ambari 2.5, only {{trunk}}. 
> When creating multiple flume agents on the same host, the following exception 
> is thrown because of a missing import for {{shell}}:
> {code}
> Traceback (most recent call last):
>   File 
> "/var/lib/ambari-agent/cache/common-services/FLUME/1.4.0.2.0/package/scripts/flume_handler.py",
>  line 130, in 
> FlumeHandler().execute()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 283, in execute
> method(env)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 707, in restart
> self.stop(env, upgrade_type=upgrade_type)
>   File 
> "/var/lib/ambari-agent/cache/common-services/FLUME/1.4.0.2.0/package/scripts/flume_handler.py",
>  line 60, in stop
> flume(action='stop')
>   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/FLUME/1.4.0.2.0/package/scripts/flume.py",
>  line 228, in flume
> pid = shell.checked_call(("cat", pid_file), sudo=True)[1].strip()
> NameError: global name 'shell' is not defined
> {code}



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

[jira] [Commented] (AMBARI-18980) Add manual confirm task before finalizing host-ordered upgrade

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-18980:


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

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

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

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

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

{color:red}-1 core tests{color}.  The test build failed in ambari-server 

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

This message is automatically generated.

> Add manual confirm task before finalizing host-ordered upgrade
> --
>
> Key: AMBARI-18980
> URL: https://issues.apache.org/jira/browse/AMBARI-18980
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Duc Anh Le
>Assignee: Duc Anh Le
> Fix For: 2.5.0
>
> Attachments: AMBARI-18980.patch
>
>
> We need to users' confirmation before finalizing upgrade.



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

[jira] [Commented] (AMBARI-18973) Service Auto Start: discard popup appears even when no changes were made

[Hudson (JIRA)]

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

Hudson commented on AMBARI-18973:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6094 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6094/])
AMBARI-18973 Service Auto Start: discard popup appears even when no (atkach: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=3c8b1582c2f0aa65289b762fd0162049916e9140])
* (edit) ambari-web/app/controllers/main/admin/service_auto_start.js
* (edit) ambari-web/app/templates/main/admin/service_auto_start.hbs


> Service Auto Start: discard popup appears even when no changes were made
> 
>
> Key: AMBARI-18973
> URL: https://issues.apache.org/jira/browse/AMBARI-18973
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
> Fix For: 3.0.0
>
> Attachments: AMBARI-18973.patch, AMBARI-18973_2.patch
>
>
> Discard popup appears even when no changes were made.



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

[jira] [Updated] (AMBARI-19002) Ambari widgets and service checks to honor LLAP clusters with 100% allocation to LLAP daemons

[Andrii Tkach (JIRA)]

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

Andrii Tkach updated AMBARI-19002:
--
Status: Patch Available  (was: Open)

> Ambari widgets and service checks to honor LLAP clusters with 100% allocation 
> to LLAP daemons
> -
>
> Key: AMBARI-19002
> URL: https://issues.apache.org/jira/browse/AMBARI-19002
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19002.patch
>
>
> As part of this ticket
> When a new config which needs to be introduced as part of this ticket 
> "cluster-env/hide_yarn_memory_widget" is marked to be true then ambari-web 
> should not show "YARN Memory" widget by default on the dashboard. Widget can 
> be made hidden by default when any user logs in for the first time. Then if 
> some specific user explicitly adds the widget back, then user should be able 
> to see it



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

[jira] [Updated] (AMBARI-19002) Ambari widgets and service checks to honor LLAP clusters with 100% allocation to LLAP daemons

[Andrii Tkach (JIRA)]

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

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

> Ambari widgets and service checks to honor LLAP clusters with 100% allocation 
> to LLAP daemons
> -
>
> Key: AMBARI-19002
> URL: https://issues.apache.org/jira/browse/AMBARI-19002
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19002.patch
>
>
> As part of this ticket
> When a new config which needs to be introduced as part of this ticket 
> "cluster-env/hide_yarn_memory_widget" is marked to be true then ambari-web 
> should not show "YARN Memory" widget by default on the dashboard. Widget can 
> be made hidden by default when any user logs in for the first time. Then if 
> some specific user explicitly adds the widget back, then user should be able 
> to see it



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

[jira] [Commented] (AMBARI-19002) Ambari widgets and service checks to honor LLAP clusters with 100% allocation to LLAP daemons

[Andrii Tkach (JIRA)]

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

Andrii Tkach commented on AMBARI-19002:
---

 19935 tests complete (25 seconds)
  154 tests pending

> Ambari widgets and service checks to honor LLAP clusters with 100% allocation 
> to LLAP daemons
> -
>
> Key: AMBARI-19002
> URL: https://issues.apache.org/jira/browse/AMBARI-19002
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19002.patch
>
>
> As part of this ticket
> When a new config which needs to be introduced as part of this ticket 
> "cluster-env/hide_yarn_memory_widget" is marked to be true then ambari-web 
> should not show "YARN Memory" widget by default on the dashboard. Widget can 
> be made hidden by default when any user logs in for the first time. Then if 
> some specific user explicitly adds the widget back, then user should be able 
> to see it



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

[jira] [Updated] (AMBARI-18999) Unable to Start Multiple Flume Agents Due to Missing Import

[Jonathan Hurley (JIRA)]

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

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

> Unable to Start Multiple Flume Agents Due to Missing Import
> ---
>
> Key: AMBARI-18999
> URL: https://issues.apache.org/jira/browse/AMBARI-18999
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 3.0.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: AMBARI-18999.patch
>
>
> Note that this issue does not affect Ambari 2.5, only {{trunk}}. 
> When creating multiple flume agents on the same host, the following exception 
> is thrown because of a missing import for {{shell}}:
> {code}
> Traceback (most recent call last):
>   File 
> "/var/lib/ambari-agent/cache/common-services/FLUME/1.4.0.2.0/package/scripts/flume_handler.py",
>  line 130, in 
> FlumeHandler().execute()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 283, in execute
> method(env)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 707, in restart
> self.stop(env, upgrade_type=upgrade_type)
>   File 
> "/var/lib/ambari-agent/cache/common-services/FLUME/1.4.0.2.0/package/scripts/flume_handler.py",
>  line 60, in stop
> flume(action='stop')
>   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/FLUME/1.4.0.2.0/package/scripts/flume.py",
>  line 228, in flume
> pid = shell.checked_call(("cat", pid_file), sudo=True)[1].strip()
> NameError: global name 'shell' is not defined
> {code}



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

[jira] [Commented] (AMBARI-18841) Grafana fails to start

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-18841:


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

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

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

This message is automatically generated.

> Grafana fails to start
> --
>
> Key: AMBARI-18841
> URL: https://issues.apache.org/jira/browse/AMBARI-18841
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics
>Affects Versions: 2.5.0
> Environment: Fresh install of 2.5.0 cluster.
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-18841-2.patch, AMBARI-18841.patch
>
>
> Grafana fails to start with the below error
> {code}
> Traceback (most recent call last):
>   File 
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py",
>  line 69, in 
> AmsGrafana().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/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py",
>  line 47, in start
> not_if = params.grafana_process_exists_cmd,
>   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 262, 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 72, in inner
> result = function(command, **kwargs)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 102, in checked_call
> tries=tries, try_sleep=try_sleep, 
> timeout_kill_strategy=timeout_kill_strategy)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 150, in _call_wrapper
> result = _call(command, **kwargs_copy)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 303, in _call
> raise ExecutionFailed(err_msg, code, out, err)
> resource_management.core.exceptions.ExecutionFailed: Execution of 
> '/usr/sbin/ambari-metrics-grafana start' returned 1.  Hortonworks 
> #
> This is MOTD message, added for testing in qe infra
> Starting Ambari Metrics Grafana:  FAILED
> {code}



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

[jira] [Commented] (AMBARI-19000) Ambari-server fails to restart with --debug if it is already running

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-19000:


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

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

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

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

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

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

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

This message is automatically generated.

> Ambari-server fails to restart with --debug if it is already running
> 
>
> Key: AMBARI-19000
> URL: https://issues.apache.org/jira/browse/AMBARI-19000
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.5.0
>
> Attachments: AMBARI-19000.patch
>
>
> Using python  /usr/bin/python
> Restarting ambari-server
> Ambari Server stopped
> Ambari Server running with administrator privileges.
> Organizing resource files at /var/lib/ambari-server/resources...
> Ambari database consistency check started...
> Server PID at: /var/run/ambari-server/ambari-server.pid
> Server out at: /var/log/ambari-server/ambari-server.out
> Server log at: /var/log/ambari-server/ambari-server.log
> Waiting for server start.
> DB configs consistency check: no errors and warnings were found.
> ERROR: Exiting with exit code -1. 
> REASON: Ambari Server java process died with exitcode 134. Check 
> /var/log/ambari-server/ambari-server.out for more information.



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

[jira] [Commented] (AMBARI-18998) Create smart config tab for Hive and Oozie Database settings

[Hudson (JIRA)]

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

Hudson commented on AMBARI-18998:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6093 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6093/])
AMBARI-18998. Create smart config tab for Hive and Oozie Database (hiveww: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=cf82cf248a2e5178ea3fa35a76df338e7d258eb9])
* (edit) 
ambari-server/src/main/resources/common-services/OOZIE/4.0.0.2.0/configuration/oozie-env.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.5/services/OOZIE/metainfo.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.3/services/OOZIE/configuration/oozie-env.xml
* (edit) ambari-web/app/data/configs/services/oozie_properties.js
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.2/services/HIVE/themes/theme.json
* (add) 
ambari-server/src/main/resources/stacks/HDP/2.3/services/OOZIE/themes/theme.json
* (add) 
ambari-server/src/main/resources/stacks/HDP/2.5/services/OOZIE/themes/theme.json
* (edit) ambari-web/app/app.js
* (edit) ambari-web/app/data/configs/services/hive_properties.js
* (edit) 
ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/configuration/hive-env.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.3/services/OOZIE/metainfo.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.3/services/HIVE/configuration/hive-env.xml


> Create smart config tab for Hive and Oozie Database settings
> 
>
> Key: AMBARI-18998
> URL: https://issues.apache.org/jira/browse/AMBARI-18998
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.4.2
>Reporter: Denys Buzhor
>Assignee: Denys Buzhor
> Fix For: 3.0.0
>
> Attachments: AMBARI-18998.patch
>
>




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

[jira] [Commented] (AMBARI-18841) Grafana fails to start

[Hudson (JIRA)]

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

Hudson commented on AMBARI-18841:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6093 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6093/])
AMBARI-18841 : Grafana fails to start (Commit 2) (avijayan) (avijayan: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=8de17fadfd00912b9bc7801011905f6c90bc8a97])
* (edit) ambari-metrics/ambari-metrics-grafana/conf/unix/ambari-metrics-grafana


> Grafana fails to start
> --
>
> Key: AMBARI-18841
> URL: https://issues.apache.org/jira/browse/AMBARI-18841
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics
>Affects Versions: 2.5.0
> Environment: Fresh install of 2.5.0 cluster.
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-18841-2.patch, AMBARI-18841.patch
>
>
> Grafana fails to start with the below error
> {code}
> Traceback (most recent call last):
>   File 
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py",
>  line 69, in 
> AmsGrafana().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/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py",
>  line 47, in start
> not_if = params.grafana_process_exists_cmd,
>   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 262, 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 72, in inner
> result = function(command, **kwargs)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 102, in checked_call
> tries=tries, try_sleep=try_sleep, 
> timeout_kill_strategy=timeout_kill_strategy)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 150, in _call_wrapper
> result = _call(command, **kwargs_copy)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 303, in _call
> raise ExecutionFailed(err_msg, code, out, err)
> resource_management.core.exceptions.ExecutionFailed: Execution of 
> '/usr/sbin/ambari-metrics-grafana start' returned 1.  Hortonworks 
> #
> This is MOTD message, added for testing in qe infra
> Starting Ambari Metrics Grafana:  FAILED
> {code}



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

[jira] [Updated] (AMBARI-18836) Remove group readable from hdfs headless keytab

[Shi Wang (JIRA)]

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

Shi Wang updated AMBARI-18836:
--
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Remove group readable from hdfs headless keytab
> ---
>
> Key: AMBARI-18836
> URL: https://issues.apache.org/jira/browse/AMBARI-18836
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: trunk
>Reporter: Shi Wang
>Assignee: Shi Wang
> Fix For: trunk
>
> Attachments: 
> 0001-AMBARI-18836-Remove-group-readable-from-hdfs-headles.patch, 
> AMBARI-18836-test_failure.patch
>
>
> The Smoke and “Headless” Service users are used by Ambari to perform service 
> “smoke” checks and run alert health checks. 
> The permission for hdfs.headless.keytab is 440. But it will cause security 
> concern to allow other service user in hadoop group to kinit hdfs headless 
> principal using hdfs.headless.keytab. In this way, other service user could 
> "pretend" to be hdfs user and be granted hdfs user's authorities.



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

[jira] [Commented] (AMBARI-18836) Remove group readable from hdfs headless keytab

[Shi Wang (JIRA)]

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

Shi Wang commented on AMBARI-18836:
---

Thanks Robert.

> Remove group readable from hdfs headless keytab
> ---
>
> Key: AMBARI-18836
> URL: https://issues.apache.org/jira/browse/AMBARI-18836
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: trunk
>Reporter: Shi Wang
>Assignee: Shi Wang
> Fix For: trunk
>
> Attachments: 
> 0001-AMBARI-18836-Remove-group-readable-from-hdfs-headles.patch, 
> AMBARI-18836-test_failure.patch
>
>
> The Smoke and “Headless” Service users are used by Ambari to perform service 
> “smoke” checks and run alert health checks. 
> The permission for hdfs.headless.keytab is 440. But it will cause security 
> concern to allow other service user in hadoop group to kinit hdfs headless 
> principal using hdfs.headless.keytab. In this way, other service user could 
> "pretend" to be hdfs user and be granted hdfs user's authorities.



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

[jira] [Created] (AMBARI-19002) Ambari widgets and service checks to honor LLAP clusters with 100% allocation to LLAP daemons

[Andrii Tkach (JIRA)]

Andrii Tkach created AMBARI-19002:
-

 Summary: Ambari widgets and service checks to honor LLAP clusters 
with 100% allocation to LLAP daemons
 Key: AMBARI-19002
 URL: https://issues.apache.org/jira/browse/AMBARI-19002
 Project: Ambari
  Issue Type: Bug
  Components: ambari-web
Affects Versions: 2.4.0
Reporter: Andrii Tkach
Assignee: Andrii Tkach
Priority: Critical
 Fix For: 2.5.0


As part of this ticket
When a new config which needs to be introduced as part of this ticket 
"cluster-env/hide_yarn_memory_widget" is marked to be true then ambari-web 
should not show "YARN Memory" widget by default on the dashboard. Widget can be 
made hidden by default when any user logs in for the first time. Then if some 
specific user explicitly adds the widget back, then user should be able to see 
it



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

[jira] [Updated] (AMBARI-18973) Service Auto Start: discard popup appears even when no changes were made

[Andrii Tkach (JIRA)]

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

Andrii Tkach updated AMBARI-18973:
--
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Service Auto Start: discard popup appears even when no changes were made
> 
>
> Key: AMBARI-18973
> URL: https://issues.apache.org/jira/browse/AMBARI-18973
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
> Fix For: 3.0.0
>
> Attachments: AMBARI-18973.patch, AMBARI-18973_2.patch
>
>
> Discard popup appears even when no changes were made.



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

[jira] [Commented] (AMBARI-18973) Service Auto Start: discard popup appears even when no changes were made

[Andrii Tkach (JIRA)]

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

Andrii Tkach commented on AMBARI-18973:
---

the second patch committed to trunk.

> Service Auto Start: discard popup appears even when no changes were made
> 
>
> Key: AMBARI-18973
> URL: https://issues.apache.org/jira/browse/AMBARI-18973
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
> Fix For: 3.0.0
>
> Attachments: AMBARI-18973.patch, AMBARI-18973_2.patch
>
>
> Discard popup appears even when no changes were made.



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

[jira] [Commented] (AMBARI-18999) Unable to Start Multiple Flume Agents Due to Missing Import

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-18999:


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

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

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

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

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

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

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

This message is automatically generated.

> Unable to Start Multiple Flume Agents Due to Missing Import
> ---
>
> Key: AMBARI-18999
> URL: https://issues.apache.org/jira/browse/AMBARI-18999
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 3.0.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: AMBARI-18999.patch
>
>
> Note that this issue does not affect Ambari 2.5, only {{trunk}}. 
> When creating multiple flume agents on the same host, the following exception 
> is thrown because of a missing import for {{shell}}:
> {code}
> Traceback (most recent call last):
>   File 
> "/var/lib/ambari-agent/cache/common-services/FLUME/1.4.0.2.0/package/scripts/flume_handler.py",
>  line 130, in 
> FlumeHandler().execute()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 283, in execute
> method(env)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 707, in restart
> self.stop(env, upgrade_type=upgrade_type)
>   File 
> "/var/lib/ambari-agent/cache/common-services/FLUME/1.4.0.2.0/package/scripts/flume_handler.py",
>  line 60, in stop
> flume(action='stop')
>   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/FLUME/1.4.0.2.0/package/scripts/flume.py",
>  line 228, in flume
> pid = shell.checked_call(("cat", pid_file), sudo=True)[1].strip()
> NameError: global name 'shell' is not defined
> {code}



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

[jira] [Updated] (AMBARI-18980) Add manual confirm task before finalizing host-ordered upgrade

[Duc Anh Le (JIRA)]

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

Duc Anh Le updated AMBARI-18980:

Status: Patch Available  (was: Open)

> Add manual confirm task before finalizing host-ordered upgrade
> --
>
> Key: AMBARI-18980
> URL: https://issues.apache.org/jira/browse/AMBARI-18980
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Duc Anh Le
>Assignee: Duc Anh Le
> Fix For: 2.5.0
>
> Attachments: AMBARI-18980.patch
>
>
> We need to users' confirmation before finalizing upgrade.



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

[jira] [Updated] (AMBARI-18980) Add manual confirm task before finalizing host-ordered upgrade

[Duc Anh Le (JIRA)]

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

Duc Anh Le updated AMBARI-18980:

Attachment: AMBARI-18980.patch

> Add manual confirm task before finalizing host-ordered upgrade
> --
>
> Key: AMBARI-18980
> URL: https://issues.apache.org/jira/browse/AMBARI-18980
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Duc Anh Le
>Assignee: Duc Anh Le
> Fix For: 2.5.0
>
> Attachments: AMBARI-18980.patch
>
>
> We need to users' confirmation before finalizing upgrade.



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

[jira] [Commented] (AMBARI-18836) Remove group readable from hdfs headless keytab

[Hudson (JIRA)]

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

Hudson commented on AMBARI-18836:
-

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6092 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6092/])
AMBARI-18836. Remove group readable from hdfs headless keytab (Shi Wang 
(rlevas: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=cad0130d9d4a64a6bda1992758c5c7c05e06b39e])
* (edit) 
ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/webhcat.py
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.5/services/HDFS/kerberos.json
* (edit) 
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/kerberos.json
* (edit) ambari-server/src/test/python/stacks/2.0.6/HIVE/test_webhcat_server.py


> Remove group readable from hdfs headless keytab
> ---
>
> Key: AMBARI-18836
> URL: https://issues.apache.org/jira/browse/AMBARI-18836
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: trunk
>Reporter: Shi Wang
>Assignee: Shi Wang
> Fix For: trunk
>
> Attachments: 
> 0001-AMBARI-18836-Remove-group-readable-from-hdfs-headles.patch, 
> AMBARI-18836-test_failure.patch
>
>
> The Smoke and “Headless” Service users are used by Ambari to perform service 
> “smoke” checks and run alert health checks. 
> The permission for hdfs.headless.keytab is 440. But it will cause security 
> concern to allow other service user in hadoop group to kinit hdfs headless 
> principal using hdfs.headless.keytab. In this way, other service user could 
> "pretend" to be hdfs user and be granted hdfs user's authorities.



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

[jira] [Updated] (AMBARI-18841) Grafana fails to start

[Aravindan Vijayan (JIRA)]

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

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

> Grafana fails to start
> --
>
> Key: AMBARI-18841
> URL: https://issues.apache.org/jira/browse/AMBARI-18841
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics
>Affects Versions: 2.5.0
> Environment: Fresh install of 2.5.0 cluster.
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-18841-2.patch, AMBARI-18841.patch
>
>
> Grafana fails to start with the below error
> {code}
> Traceback (most recent call last):
>   File 
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py",
>  line 69, in 
> AmsGrafana().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/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py",
>  line 47, in start
> not_if = params.grafana_process_exists_cmd,
>   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 262, 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 72, in inner
> result = function(command, **kwargs)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 102, in checked_call
> tries=tries, try_sleep=try_sleep, 
> timeout_kill_strategy=timeout_kill_strategy)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 150, in _call_wrapper
> result = _call(command, **kwargs_copy)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 303, in _call
> raise ExecutionFailed(err_msg, code, out, err)
> resource_management.core.exceptions.ExecutionFailed: Execution of 
> '/usr/sbin/ambari-metrics-grafana start' returned 1.  Hortonworks 
> #
> This is MOTD message, added for testing in qe infra
> Starting Ambari Metrics Grafana:  FAILED
> {code}



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

[jira] [Commented] (AMBARI-18973) Service Auto Start: discard popup appears even when no changes were made

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-18973:


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

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

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

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

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

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

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

This message is automatically generated.

> Service Auto Start: discard popup appears even when no changes were made
> 
>
> Key: AMBARI-18973
> URL: https://issues.apache.org/jira/browse/AMBARI-18973
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
> Fix For: 3.0.0
>
> Attachments: AMBARI-18973.patch, AMBARI-18973_2.patch
>
>
> Discard popup appears even when no changes were made.



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

[jira] [Updated] (AMBARI-18998) Create smart config tab for Hive and Oozie Database settings

[Antonenko Alexander (JIRA)]

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

Antonenko Alexander updated AMBARI-18998:
-
Resolution: Fixed
Status: Resolved  (was: Patch Available)

Committed to trunk


> Create smart config tab for Hive and Oozie Database settings
> 
>
> Key: AMBARI-18998
> URL: https://issues.apache.org/jira/browse/AMBARI-18998
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.4.2
>Reporter: Denys Buzhor
>Assignee: Denys Buzhor
> Fix For: 3.0.0
>
> Attachments: AMBARI-18998.patch
>
>




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

[jira] [Commented] (AMBARI-19000) Ambari-server fails to restart with --debug if it is already running

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-19000:


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

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

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

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

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

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

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

This message is automatically generated.

> Ambari-server fails to restart with --debug if it is already running
> 
>
> Key: AMBARI-19000
> URL: https://issues.apache.org/jira/browse/AMBARI-19000
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.5.0
>
> Attachments: AMBARI-19000.patch
>
>
> Using python  /usr/bin/python
> Restarting ambari-server
> Ambari Server stopped
> Ambari Server running with administrator privileges.
> Organizing resource files at /var/lib/ambari-server/resources...
> Ambari database consistency check started...
> Server PID at: /var/run/ambari-server/ambari-server.pid
> Server out at: /var/log/ambari-server/ambari-server.out
> Server log at: /var/log/ambari-server/ambari-server.log
> Waiting for server start.
> DB configs consistency check: no errors and warnings were found.
> ERROR: Exiting with exit code -1. 
> REASON: Ambari Server java process died with exitcode 134. Check 
> /var/log/ambari-server/ambari-server.out for more information.



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

[jira] [Commented] (AMBARI-18836) Remove group readable from hdfs headless keytab

[Robert Levas (JIRA)]

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

Robert Levas commented on AMBARI-18836:
---

[~Wancy]..

I commit the update to the trunk:

{noformat}
commit cad0130d9d4a64a6bda1992758c5c7c05e06b39e
Author: Shi Wang 
Date:   Mon Nov 28 12:39:05 2016 -0500
{noformat}


> Remove group readable from hdfs headless keytab
> ---
>
> Key: AMBARI-18836
> URL: https://issues.apache.org/jira/browse/AMBARI-18836
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: trunk
>Reporter: Shi Wang
>Assignee: Shi Wang
> Fix For: trunk
>
> Attachments: 
> 0001-AMBARI-18836-Remove-group-readable-from-hdfs-headles.patch, 
> AMBARI-18836-test_failure.patch
>
>
> The Smoke and “Headless” Service users are used by Ambari to perform service 
> “smoke” checks and run alert health checks. 
> The permission for hdfs.headless.keytab is 440. But it will cause security 
> concern to allow other service user in hadoop group to kinit hdfs headless 
> principal using hdfs.headless.keytab. In this way, other service user could 
> "pretend" to be hdfs user and be granted hdfs user's authorities.



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

[jira] [Comment Edited] (AMBARI-18836) Remove group readable from hdfs headless keytab

[Robert Levas (JIRA)]

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

Robert Levas edited comment on AMBARI-18836 at 11/28/16 5:41 PM:
-

[~Wancy]..

I commited the update to the trunk:

{noformat}
commit cad0130d9d4a64a6bda1992758c5c7c05e06b39e
Author: Shi Wang 
Date:   Mon Nov 28 12:39:05 2016 -0500
{noformat}



was (Author: rlevas):
[~Wancy]..

I commit the update to the trunk:

{noformat}
commit cad0130d9d4a64a6bda1992758c5c7c05e06b39e
Author: Shi Wang 
Date:   Mon Nov 28 12:39:05 2016 -0500
{noformat}


> Remove group readable from hdfs headless keytab
> ---
>
> Key: AMBARI-18836
> URL: https://issues.apache.org/jira/browse/AMBARI-18836
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: trunk
>Reporter: Shi Wang
>Assignee: Shi Wang
> Fix For: trunk
>
> Attachments: 
> 0001-AMBARI-18836-Remove-group-readable-from-hdfs-headles.patch, 
> AMBARI-18836-test_failure.patch
>
>
> The Smoke and “Headless” Service users are used by Ambari to perform service 
> “smoke” checks and run alert health checks. 
> The permission for hdfs.headless.keytab is 440. But it will cause security 
> concern to allow other service user in hadoop group to kinit hdfs headless 
> principal using hdfs.headless.keytab. In this way, other service user could 
> "pretend" to be hdfs user and be granted hdfs user's authorities.



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

[jira] [Commented] (AMBARI-18951) Force InnoDB usage for MySQL

[Hudson (JIRA)]

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

Hudson commented on AMBARI-18951:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6091 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6091/])
AMBARI-18951. Force InnoDB usage for MySQL. (mpapirkovskyy) (mpapyrkovskyy: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=255725dfc07a4a4fd7fc8b3f6cdbd7cced1c375a])
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/upgrade/SchemaUpgradeHelper.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/orm/helpers/dbms/MySqlHelper.java
* (edit) ambari-server/src/main/resources/Ambari-DDL-MySQL-CREATE.sql


> Force InnoDB usage for MySQL
> 
>
> Key: AMBARI-18951
> URL: https://issues.apache.org/jira/browse/AMBARI-18951
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.2
>Reporter: Myroslav Papirkovskyi
>Assignee: Myroslav Papirkovskyi
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18951.patch
>
>
> We should always use InnoDB as database engine for MySQL as database with 
> MyISAM engine cannot be upgraded properly.
> Key reason is that MyISAM doesn't store foreign keys information, but do 
> store indexes with same name which lead to conflicts during upgrade.



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

[jira] [Commented] (AMBARI-18976) Config History request execution time depends on config versions count

[Hudson (JIRA)]

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

Hudson commented on AMBARI-18976:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6091 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6091/])
AMBARI-18976. Config History request execution time depends on config 
(mpapyrkovskyy: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=abf9882276d2ed73cd5dcf12a088d16492c9490d])
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/orm/entities/ClusterConfigMappingEntity.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ClusterControllerImpl.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/state/cluster/ClusterImpl.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/orm/dao/ClusterDAO.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/orm/dao/ServiceConfigDAO.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ServiceConfigVersionResourceProvider.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/orm/entities/ClusterConfigEntity.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/logging/LoggingSearchPropertyProvider.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/orm/entities/ServiceConfigEntity.java


> Config History request execution time depends on config versions count
> --
>
> Key: AMBARI-18976
> URL: https://issues.apache.org/jira/browse/AMBARI-18976
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Myroslav Papirkovskyi
>Assignee: Myroslav Papirkovskyi
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18976.patch
>
>
> Request: 
> {{/api/v1/clusters/tdk/configurations/service_config_versions?fields=group_id,user&minimal_response=true&from=0&page_size=10}}
>  
> Response always contains 10 records or less (if there are less than 10 
> service configs versions). Each record has only two fields ({{group_id}}, 
> {{user}}).
> Request execution time depends on overall count of service config versions in 
> the DB.
> Example:
> || Items Total in the DB || Response Time ||
> |2|~140 ms|
> |100  |900+ ms|
> |290  |3+ s|
> |750  |9+ s|
> |1000 |15+ s|
> |3000 |30+ s|



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

[jira] [Commented] (AMBARI-18998) Create smart config tab for Hive and Oozie Database settings

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-18998:


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

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

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

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

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

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

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

This message is automatically generated.

> Create smart config tab for Hive and Oozie Database settings
> 
>
> Key: AMBARI-18998
> URL: https://issues.apache.org/jira/browse/AMBARI-18998
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.4.2
>Reporter: Denys Buzhor
>Assignee: Denys Buzhor
> Fix For: 3.0.0
>
> Attachments: AMBARI-18998.patch
>
>




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

[jira] [Updated] (AMBARI-19001) Support configurable grok filters (output + ambari)

[JIRA]

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

Olivér Szabó updated AMBARI-19001:
--
Attachment: AMBARI-19001.patch

> Support configurable grok filters (output + ambari)
> ---
>
> Key: AMBARI-19001
> URL: https://issues.apache.org/jira/browse/AMBARI-19001
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-logsearch, ambari-server
>Affects Versions: 2.4.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
> Fix For: 2.5.0
>
> Attachments: AMBARI-19001.patch
>
>
> Support configurable output and ambari grok filter configs from ambari.
> Ambari log patterns can change, so its a good idea to make it editable.
> Also with a configurable output, we can extend the logfeeder output to use 
> e.g. kafka



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

[jira] [Updated] (AMBARI-19001) Support configurable grok filters (output + ambari)

[JIRA]

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

Olivér Szabó updated AMBARI-19001:
--
Attachment: (was: AMBARI-19001.patch)

> Support configurable grok filters (output + ambari)
> ---
>
> Key: AMBARI-19001
> URL: https://issues.apache.org/jira/browse/AMBARI-19001
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-logsearch, ambari-server
>Affects Versions: 2.4.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
> Fix For: 2.5.0
>
> Attachments: AMBARI-19001.patch
>
>
> Support configurable output and ambari grok filter configs from ambari.
> Ambari log patterns can change, so its a good idea to make it editable.
> Also with a configurable output, we can extend the logfeeder output to use 
> e.g. kafka



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

[jira] [Updated] (AMBARI-19001) Support configurable grok filters (output + ambari)

[JIRA]

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

Olivér Szabó updated AMBARI-19001:
--
Attachment: (was: AMBARI-19001.patch)

> Support configurable grok filters (output + ambari)
> ---
>
> Key: AMBARI-19001
> URL: https://issues.apache.org/jira/browse/AMBARI-19001
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-logsearch, ambari-server
>Affects Versions: 2.4.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
> Fix For: 2.5.0
>
> Attachments: AMBARI-19001.patch
>
>
> Support configurable output and ambari grok filter configs from ambari.
> Ambari log patterns can change, so its a good idea to make it editable.
> Also with a configurable output, we can extend the logfeeder output to use 
> e.g. kafka



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

[jira] [Updated] (AMBARI-19001) Support configurable grok filters (output + ambari)

[JIRA]

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

Olivér Szabó updated AMBARI-19001:
--
Attachment: AMBARI-19001.patch

> Support configurable grok filters (output + ambari)
> ---
>
> Key: AMBARI-19001
> URL: https://issues.apache.org/jira/browse/AMBARI-19001
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-logsearch, ambari-server
>Affects Versions: 2.4.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
> Fix For: 2.5.0
>
> Attachments: AMBARI-19001.patch
>
>
> Support configurable output and ambari grok filter configs from ambari.
> Ambari log patterns can change, so its a good idea to make it editable.
> Also with a configurable output, we can extend the logfeeder output to use 
> e.g. kafka



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

[jira] [Updated] (AMBARI-19001) Support configurable grok filters (output + ambari)

[JIRA]

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

Olivér Szabó updated AMBARI-19001:
--
Attachment: AMBARI-19001.patch

> Support configurable grok filters (output + ambari)
> ---
>
> Key: AMBARI-19001
> URL: https://issues.apache.org/jira/browse/AMBARI-19001
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-logsearch, ambari-server
>Affects Versions: 2.4.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
> Fix For: 2.5.0
>
> Attachments: AMBARI-19001.patch
>
>
> Support configurable output and ambari grok filter configs from ambari.
> Ambari log patterns can change, so its a good idea to make it editable.
> Also with a configurable output, we can extend the logfeeder output to use 
> e.g. kafka



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

[jira] [Updated] (AMBARI-19001) Support configurable grok filters (output + ambari)

[JIRA]

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

Olivér Szabó updated AMBARI-19001:
--
Summary: Support configurable grok filters (output + ambari)  (was: Support 
configurable grok filters)

> Support configurable grok filters (output + ambari)
> ---
>
> Key: AMBARI-19001
> URL: https://issues.apache.org/jira/browse/AMBARI-19001
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-logsearch, ambari-server
>Affects Versions: 2.4.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
> Fix For: 2.5.0
>
> Attachments: AMBARI-19001.patch
>
>
> Support configurable output and ambari grok filter configs from ambari.
> Ambari log patterns can change, so its a good idea to make it editable.
> Also with a configurable output, we can extend the logfeeder output to use 
> e.g. kafka



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

[jira] [Created] (AMBARI-19001) Support configurable grok filters

[JIRA]

Olivér Szabó created AMBARI-19001:
-

 Summary: Support configurable grok filters
 Key: AMBARI-19001
 URL: https://issues.apache.org/jira/browse/AMBARI-19001
 Project: Ambari
  Issue Type: Bug
  Components: ambari-logsearch, ambari-server
Affects Versions: 2.4.0
Reporter: Olivér Szabó
Assignee: Olivér Szabó
 Fix For: 2.5.0


Support configurable output and ambari grok filter configs from ambari.
Ambari log patterns can change, so its a good idea to make it editable.
Also with a configurable output, we can extend the logfeeder output to use e.g. 
kafka



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

[jira] [Commented] (AMBARI-18973) Service Auto Start: discard popup appears even when no changes were made

[Aleksandr Kovalenko (JIRA)]

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

Aleksandr Kovalenko commented on AMBARI-18973:
--

+1 for second patch

> Service Auto Start: discard popup appears even when no changes were made
> 
>
> Key: AMBARI-18973
> URL: https://issues.apache.org/jira/browse/AMBARI-18973
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
> Fix For: 3.0.0
>
> Attachments: AMBARI-18973.patch, AMBARI-18973_2.patch
>
>
> Discard popup appears even when no changes were made.



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

[jira] [Resolved] (AMBARI-18951) Force InnoDB usage for MySQL

[Myroslav Papirkovskyi (JIRA)]

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

Myroslav Papirkovskyi resolved AMBARI-18951.

Resolution: Fixed

Pushed to trunk and branch-2.5

> Force InnoDB usage for MySQL
> 
>
> Key: AMBARI-18951
> URL: https://issues.apache.org/jira/browse/AMBARI-18951
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.2
>Reporter: Myroslav Papirkovskyi
>Assignee: Myroslav Papirkovskyi
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18951.patch
>
>
> We should always use InnoDB as database engine for MySQL as database with 
> MyISAM engine cannot be upgraded properly.
> Key reason is that MyISAM doesn't store foreign keys information, but do 
> store indexes with same name which lead to conflicts during upgrade.



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

[jira] [Updated] (AMBARI-18951) Force InnoDB usage for MySQL

[Myroslav Papirkovskyi (JIRA)]

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

Myroslav Papirkovskyi updated AMBARI-18951:
---
Attachment: AMBARI-18951.patch

> Force InnoDB usage for MySQL
> 
>
> Key: AMBARI-18951
> URL: https://issues.apache.org/jira/browse/AMBARI-18951
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.2
>Reporter: Myroslav Papirkovskyi
>Assignee: Myroslav Papirkovskyi
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18951.patch
>
>
> We should always use InnoDB as database engine for MySQL as database with 
> MyISAM engine cannot be upgraded properly.
> Key reason is that MyISAM doesn't store foreign keys information, but do 
> store indexes with same name which lead to conflicts during upgrade.



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

[jira] [Updated] (AMBARI-18951) Force InnoDB usage for MySQL

[Myroslav Papirkovskyi (JIRA)]

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

Myroslav Papirkovskyi updated AMBARI-18951:
---
Attachment: (was: AMBARI-18951.patch)

> Force InnoDB usage for MySQL
> 
>
> Key: AMBARI-18951
> URL: https://issues.apache.org/jira/browse/AMBARI-18951
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.2
>Reporter: Myroslav Papirkovskyi
>Assignee: Myroslav Papirkovskyi
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18951.patch
>
>
> We should always use InnoDB as database engine for MySQL as database with 
> MyISAM engine cannot be upgraded properly.
> Key reason is that MyISAM doesn't store foreign keys information, but do 
> store indexes with same name which lead to conflicts during upgrade.



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

[jira] [Commented] (AMBARI-18994) In HA cluster copy the hdfs-site.xml and hbase-site.xml to Ranger conf directory

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-18994:


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

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

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

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

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

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

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

This message is automatically generated.

> In HA cluster copy the hdfs-site.xml and hbase-site.xml to Ranger conf 
> directory
> 
>
> Key: AMBARI-18994
> URL: https://issues.apache.org/jira/browse/AMBARI-18994
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.4.0, 2.5.0
>Reporter: Deepak Sharma
>Assignee: Mugdha Varadkar
> Fix For: 2.5.0
>
> Attachments: AMBARI-18994.patch
>
>
> in present , for HA cluster we have to symlink hbase-site.xml and 
> hdfs-site.xml to the /etc/ranger/admin/conf to Test connection be successful 
> in HDFS and HBASE Repo.
> Actually the better approach is copying these files to /etc/ranger/admin/conf 
> as all the services might be running in different nodes.
> and it is better if it done while enabling corresponding plugin itself.



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

[jira] [Resolved] (AMBARI-18976) Config History request execution time depends on config versions count

[Myroslav Papirkovskyi (JIRA)]

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

Myroslav Papirkovskyi resolved AMBARI-18976.

Resolution: Fixed

Pushed to trunk and branch-2.5

> Config History request execution time depends on config versions count
> --
>
> Key: AMBARI-18976
> URL: https://issues.apache.org/jira/browse/AMBARI-18976
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Myroslav Papirkovskyi
>Assignee: Myroslav Papirkovskyi
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18976.patch
>
>
> Request: 
> {{/api/v1/clusters/tdk/configurations/service_config_versions?fields=group_id,user&minimal_response=true&from=0&page_size=10}}
>  
> Response always contains 10 records or less (if there are less than 10 
> service configs versions). Each record has only two fields ({{group_id}}, 
> {{user}}).
> Request execution time depends on overall count of service config versions in 
> the DB.
> Example:
> || Items Total in the DB || Response Time ||
> |2|~140 ms|
> |100  |900+ ms|
> |290  |3+ s|
> |750  |9+ s|
> |1000 |15+ s|
> |3000 |30+ s|



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

[jira] [Updated] (AMBARI-18973) Service Auto Start: discard popup appears even when no changes were made

[Andrii Tkach (JIRA)]

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

Andrii Tkach updated AMBARI-18973:
--
Status: Patch Available  (was: Reopened)

> Service Auto Start: discard popup appears even when no changes were made
> 
>
> Key: AMBARI-18973
> URL: https://issues.apache.org/jira/browse/AMBARI-18973
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
> Fix For: 3.0.0
>
> Attachments: AMBARI-18973.patch, AMBARI-18973_2.patch
>
>
> Discard popup appears even when no changes were made.



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

[jira] [Updated] (AMBARI-18976) Config History request execution time depends on config versions count

[Myroslav Papirkovskyi (JIRA)]

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

Myroslav Papirkovskyi updated AMBARI-18976:
---
Attachment: AMBARI-18976.patch

> Config History request execution time depends on config versions count
> --
>
> Key: AMBARI-18976
> URL: https://issues.apache.org/jira/browse/AMBARI-18976
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Myroslav Papirkovskyi
>Assignee: Myroslav Papirkovskyi
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18976.patch
>
>
> Request: 
> {{/api/v1/clusters/tdk/configurations/service_config_versions?fields=group_id,user&minimal_response=true&from=0&page_size=10}}
>  
> Response always contains 10 records or less (if there are less than 10 
> service configs versions). Each record has only two fields ({{group_id}}, 
> {{user}}).
> Request execution time depends on overall count of service config versions in 
> the DB.
> Example:
> || Items Total in the DB || Response Time ||
> |2|~140 ms|
> |100  |900+ ms|
> |290  |3+ s|
> |750  |9+ s|
> |1000 |15+ s|
> |3000 |30+ s|



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

[jira] [Updated] (AMBARI-18973) Service Auto Start: discard popup appears even when no changes were made

[Andrii Tkach (JIRA)]

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

Andrii Tkach updated AMBARI-18973:
--
Attachment: AMBARI-18973_2.patch

> Service Auto Start: discard popup appears even when no changes were made
> 
>
> Key: AMBARI-18973
> URL: https://issues.apache.org/jira/browse/AMBARI-18973
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
> Fix For: 3.0.0
>
> Attachments: AMBARI-18973.patch, AMBARI-18973_2.patch
>
>
> Discard popup appears even when no changes were made.



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

[jira] [Reopened] (AMBARI-18973) Service Auto Start: discard popup appears even when no changes were made

[Andrii Tkach (JIRA)]

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

Andrii Tkach reopened AMBARI-18973:
---

Component name not displayed.

> Service Auto Start: discard popup appears even when no changes were made
> 
>
> Key: AMBARI-18973
> URL: https://issues.apache.org/jira/browse/AMBARI-18973
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
> Fix For: 3.0.0
>
> Attachments: AMBARI-18973.patch
>
>
> Discard popup appears even when no changes were made.



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

[jira] [Updated] (AMBARI-18999) Unable to Start Multiple Flume Agents Due to Missing Import

[Jonathan Hurley (JIRA)]

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

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

> Unable to Start Multiple Flume Agents Due to Missing Import
> ---
>
> Key: AMBARI-18999
> URL: https://issues.apache.org/jira/browse/AMBARI-18999
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 3.0.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: AMBARI-18999.patch
>
>
> Note that this issue does not affect Ambari 2.5, only {{trunk}}. 
> When creating multiple flume agents on the same host, the following exception 
> is thrown because of a missing import for {{shell}}:
> {code}
> Traceback (most recent call last):
>   File 
> "/var/lib/ambari-agent/cache/common-services/FLUME/1.4.0.2.0/package/scripts/flume_handler.py",
>  line 130, in 
> FlumeHandler().execute()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 283, in execute
> method(env)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 707, in restart
> self.stop(env, upgrade_type=upgrade_type)
>   File 
> "/var/lib/ambari-agent/cache/common-services/FLUME/1.4.0.2.0/package/scripts/flume_handler.py",
>  line 60, in stop
> flume(action='stop')
>   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/FLUME/1.4.0.2.0/package/scripts/flume.py",
>  line 228, in flume
> pid = shell.checked_call(("cat", pid_file), sudo=True)[1].strip()
> NameError: global name 'shell' is not defined
> {code}



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

[jira] [Updated] (AMBARI-18999) Unable to Start Multiple Flume Agents Due to Missing Import

[Jonathan Hurley (JIRA)]

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

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

> Unable to Start Multiple Flume Agents Due to Missing Import
> ---
>
> Key: AMBARI-18999
> URL: https://issues.apache.org/jira/browse/AMBARI-18999
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 3.0.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 3.0.0
>
>
> Note that this issue does not affect Ambari 2.5, only {{trunk}}. 
> When creating multiple flume agents on the same host, the following exception 
> is thrown because of a missing import for {{shell}}:
> {code}
> Traceback (most recent call last):
>   File 
> "/var/lib/ambari-agent/cache/common-services/FLUME/1.4.0.2.0/package/scripts/flume_handler.py",
>  line 130, in 
> FlumeHandler().execute()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 283, in execute
> method(env)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 707, in restart
> self.stop(env, upgrade_type=upgrade_type)
>   File 
> "/var/lib/ambari-agent/cache/common-services/FLUME/1.4.0.2.0/package/scripts/flume_handler.py",
>  line 60, in stop
> flume(action='stop')
>   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/FLUME/1.4.0.2.0/package/scripts/flume.py",
>  line 228, in flume
> pid = shell.checked_call(("cat", pid_file), sudo=True)[1].strip()
> NameError: global name 'shell' is not defined
> {code}



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

[jira] [Updated] (AMBARI-19000) Ambari-server fails to restart with --debug if it is already running

[Andrew Onischuk (JIRA)]

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

Andrew Onischuk updated AMBARI-19000:
-
Description: 
Using python  /usr/bin/python
Restarting ambari-server
Ambari Server stopped
Ambari Server running with administrator privileges.
Organizing resource files at /var/lib/ambari-server/resources...
Ambari database consistency check started...
Server PID at: /var/run/ambari-server/ambari-server.pid
Server out at: /var/log/ambari-server/ambari-server.out
Server log at: /var/log/ambari-server/ambari-server.log
Waiting for server start.
DB configs consistency check: no errors and warnings were found.
ERROR: Exiting with exit code -1. 
REASON: Ambari Server java process died with exitcode 134. Check 
/var/log/ambari-server/ambari-server.out for more information.

> Ambari-server fails to restart with --debug if it is already running
> 
>
> Key: AMBARI-19000
> URL: https://issues.apache.org/jira/browse/AMBARI-19000
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.5.0
>
> Attachments: AMBARI-19000.patch
>
>
> Using python  /usr/bin/python
> Restarting ambari-server
> Ambari Server stopped
> Ambari Server running with administrator privileges.
> Organizing resource files at /var/lib/ambari-server/resources...
> Ambari database consistency check started...
> Server PID at: /var/run/ambari-server/ambari-server.pid
> Server out at: /var/log/ambari-server/ambari-server.out
> Server log at: /var/log/ambari-server/ambari-server.log
> Waiting for server start.
> DB configs consistency check: no errors and warnings were found.
> ERROR: Exiting with exit code -1. 
> REASON: Ambari Server java process died with exitcode 134. Check 
> /var/log/ambari-server/ambari-server.out for more information.



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

[jira] [Updated] (AMBARI-18951) Force InnoDB usage for MySQL

[Myroslav Papirkovskyi (JIRA)]

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

Myroslav Papirkovskyi updated AMBARI-18951:
---
Summary: Force InnoDB usage for MySQL  (was: Forse InnoDB usage for MySQL)

> Force InnoDB usage for MySQL
> 
>
> Key: AMBARI-18951
> URL: https://issues.apache.org/jira/browse/AMBARI-18951
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.2
>Reporter: Myroslav Papirkovskyi
>Assignee: Myroslav Papirkovskyi
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18951.patch
>
>
> We should always use InnoDB as database engine for MySQL as database with 
> MyISAM engine cannot be upgraded properly.
> Key reason is that MyISAM doesn't store foreign keys information, but do 
> store indexes with same name which lead to conflicts during upgrade.



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

[jira] [Updated] (AMBARI-19000) Ambari-server fails to restart with --debug if it is already running

[Andrew Onischuk (JIRA)]

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

Andrew Onischuk updated AMBARI-19000:
-
Description: (was: After enabling WireEncyption For HDFS, ambari server 
goes down, I tried
restart again, it came up. but all hosts in HEARTBEAT_LOST state.

cluster: 

logs:  


Steps test executes to enable swebHDFS:  


)

> Ambari-server fails to restart with --debug if it is already running
> 
>
> Key: AMBARI-19000
> URL: https://issues.apache.org/jira/browse/AMBARI-19000
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.5.0
>
> Attachments: AMBARI-19000.patch
>
>




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

[jira] [Created] (AMBARI-19000) Ambari-server fails to restart with --debug if it is already running

[Andrew Onischuk (JIRA)]

Andrew Onischuk created AMBARI-19000:


 Summary: Ambari-server fails to restart with --debug if it is 
already running
 Key: AMBARI-19000
 URL: https://issues.apache.org/jira/browse/AMBARI-19000
 Project: Ambari
  Issue Type: Bug
Reporter: Andrew Onischuk
Assignee: Andrew Onischuk
 Fix For: 2.5.0
 Attachments: AMBARI-19000.patch

After enabling WireEncyption For HDFS, ambari server goes down, I tried
restart again, it came up. but all hosts in HEARTBEAT_LOST state.

cluster: 

logs:  


Steps test executes to enable swebHDFS:  






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

[jira] [Updated] (AMBARI-19000) Ambari-server fails to restart with --debug if it is already running

[Andrew Onischuk (JIRA)]

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

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

> Ambari-server fails to restart with --debug if it is already running
> 
>
> Key: AMBARI-19000
> URL: https://issues.apache.org/jira/browse/AMBARI-19000
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.5.0
>
> Attachments: AMBARI-19000.patch
>
>
> After enabling WireEncyption For HDFS, ambari server goes down, I tried
> restart again, it came up. but all hosts in HEARTBEAT_LOST state.
> cluster: 
> logs:  
>  /ambari-stackviews-we/artifacts/screenshots/com.hw.ambari.view.conf.ViewConfig
> uration/UndefinedMethod/_25_5_54_37_Element_has_not_been_found_within_60_secon
> ds__/logs/>
> Steps test executes to enable swebHDFS:  
>  /src/test/java/com/hw/ambari/view/conf/ViewConfiguration.java#L101>



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

[jira] [Updated] (AMBARI-19000) Ambari-server fails to restart with --debug if it is already running

[Andrew Onischuk (JIRA)]

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

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

> Ambari-server fails to restart with --debug if it is already running
> 
>
> Key: AMBARI-19000
> URL: https://issues.apache.org/jira/browse/AMBARI-19000
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.5.0
>
> Attachments: AMBARI-19000.patch
>
>
> After enabling WireEncyption For HDFS, ambari server goes down, I tried
> restart again, it came up. but all hosts in HEARTBEAT_LOST state.
> cluster: 
> logs:  
>  /ambari-stackviews-we/artifacts/screenshots/com.hw.ambari.view.conf.ViewConfig
> uration/UndefinedMethod/_25_5_54_37_Element_has_not_been_found_within_60_secon
> ds__/logs/>
> Steps test executes to enable swebHDFS:  
>  /src/test/java/com/hw/ambari/view/conf/ViewConfiguration.java#L101>



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

[jira] [Commented] (AMBARI-18989) Log level filter labels not getting updated with host name filter

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-18989:


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

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

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

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

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

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

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

This message is automatically generated.

>  Log level filter labels not getting updated with host name filter
> --
>
> Key: AMBARI-18989
> URL: https://issues.apache.org/jira/browse/AMBARI-18989
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-logsearch
>Affects Versions: 2.4.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
> Fix For: 2.5.0
>
> Attachments: AMBARI-18989.patch
>
>




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

[jira] [Created] (AMBARI-18999) Unable to Start Multiple Flume Agents Due to Missing Import

[Jonathan Hurley (JIRA)]

Jonathan Hurley created AMBARI-18999:


 Summary: Unable to Start Multiple Flume Agents Due to Missing 
Import
 Key: AMBARI-18999
 URL: https://issues.apache.org/jira/browse/AMBARI-18999
 Project: Ambari
  Issue Type: Bug
Affects Versions: 3.0.0
Reporter: Jonathan Hurley
Assignee: Jonathan Hurley
Priority: Critical
 Fix For: 3.0.0


Note that this issue does not affect Ambari 2.5, only {{trunk}}. 

When creating multiple flume agents on the same host, the following exception 
is thrown because of a missing import for {{shell}}:

{code}
Traceback (most recent call last):
  File 
"/var/lib/ambari-agent/cache/common-services/FLUME/1.4.0.2.0/package/scripts/flume_handler.py",
 line 130, in 
FlumeHandler().execute()
  File 
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
 line 283, in execute
method(env)
  File 
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
 line 707, in restart
self.stop(env, upgrade_type=upgrade_type)
  File 
"/var/lib/ambari-agent/cache/common-services/FLUME/1.4.0.2.0/package/scripts/flume_handler.py",
 line 60, in stop
flume(action='stop')
  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/FLUME/1.4.0.2.0/package/scripts/flume.py",
 line 228, in flume
pid = shell.checked_call(("cat", pid_file), sudo=True)[1].strip()
NameError: global name 'shell' is not defined
{code}



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