[jira] [Commented] (AMBARI-20264) HiveServer2 Interactive start failed after WE enable

[Hudson (JIRA)]

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

Hudson commented on AMBARI-20264:
-

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6912 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6912/])
AMBARI-20264: HiveServer2 Interactive start failed after WE enable (jluniya: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=7cf7fcf556bed2ecc765828a9e2954908fdaf8a8])
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.5/services/HIVE/configuration/hive-interactive-env.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.6/services/HIVE/configuration/hive-interactive-env.xml


> HiveServer2 Interactive start failed after WE enable
> 
>
> Key: AMBARI-20264
> URL: https://issues.apache.org/jira/browse/AMBARI-20264
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.5.0
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
> Fix For: 2.5.0
>
> Attachments: AMBARI-20264.patch
>
>
> {code}
> hive --service llapstatus -w -r 0.8 -i 2 -t 200
>  Hortonworks #
> This is MOTD message, added for testing in qe infra
> SLF4J: Class path contains multiple SLF4J bindings.
> SLF4J: Found binding in 
> [jar:file:/grid/0/hdp/2.6.0.0-572/hive2/lib/log4j-slf4j-impl-2.6.2.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: Found binding in 
> [jar:file:/grid/0/hdp/2.6.0.0-572/hadoop/lib/slf4j-log4j12-1.7.10.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an 
> explanation.
> SLF4J: Actual binding is of type [org.apache.logging.slf4j.Log4jLoggerFactory]
> WARN conf.HiveConf: HiveConf hive.llap.daemon.vcpus.per.instance expects INT 
> type value
> LLAPSTATUS WatchMode with timeout=200 s
> 
> LLAP Starting up with AppId=application_1488363522091_0001.
> 
> LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
> instances
> 
> LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
> instances
> 
> LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
> instances
> 
> LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
> instances
> 
> LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
> instances
> 
> LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
> instances
> 
> LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
> instances
> 
> LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
> instances
> 
> LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
> instances
> 
> LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
> instances
> 
> LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
> instances
> 
> LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
> instances
> 
> LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
> instances
> 
> {
>   "amInfo" : {
> "appName" : "llap0",
> "appType" : "org-apache-slider",
> "appId" : "application_1488363522091_0001",
> "containerId" : "container_e01_1488363522091_0001_01_01",
> "hostname" : "ctr-e129-1487033772569-30632-01-04.hwx.site",
> "amWebUrl" : 
> "http://ctr-e129-1487033772569-30632-01-04.hwx.site:32864/;
>   },
>   "state" : "LAUNCHING",
>   "originalConfigurationPath" : 
> 

[jira] [Commented] (AMBARI-20264) HiveServer2 Interactive start failed after WE enable

[Hudson (JIRA)]

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

Hudson commented on AMBARI-20264:
-

SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1153 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/1153/])
AMBARI-20264: HiveServer2 Interactive start failed after WE enable (jluniya: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=eb8526d5fdab12616cc229874c5a1fa2f58f07c9])
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.5/services/HIVE/configuration/hive-interactive-env.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.6/services/HIVE/configuration/hive-interactive-env.xml


> HiveServer2 Interactive start failed after WE enable
> 
>
> Key: AMBARI-20264
> URL: https://issues.apache.org/jira/browse/AMBARI-20264
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.5.0
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
> Fix For: 2.5.0
>
> Attachments: AMBARI-20264.patch
>
>
> {code}
> hive --service llapstatus -w -r 0.8 -i 2 -t 200
>  Hortonworks #
> This is MOTD message, added for testing in qe infra
> SLF4J: Class path contains multiple SLF4J bindings.
> SLF4J: Found binding in 
> [jar:file:/grid/0/hdp/2.6.0.0-572/hive2/lib/log4j-slf4j-impl-2.6.2.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: Found binding in 
> [jar:file:/grid/0/hdp/2.6.0.0-572/hadoop/lib/slf4j-log4j12-1.7.10.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an 
> explanation.
> SLF4J: Actual binding is of type [org.apache.logging.slf4j.Log4jLoggerFactory]
> WARN conf.HiveConf: HiveConf hive.llap.daemon.vcpus.per.instance expects INT 
> type value
> LLAPSTATUS WatchMode with timeout=200 s
> 
> LLAP Starting up with AppId=application_1488363522091_0001.
> 
> LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
> instances
> 
> LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
> instances
> 
> LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
> instances
> 
> LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
> instances
> 
> LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
> instances
> 
> LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
> instances
> 
> LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
> instances
> 
> LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
> instances
> 
> LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
> instances
> 
> LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
> instances
> 
> LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
> instances
> 
> LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
> instances
> 
> LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
> instances
> 
> {
>   "amInfo" : {
> "appName" : "llap0",
> "appType" : "org-apache-slider",
> "appId" : "application_1488363522091_0001",
> "containerId" : "container_e01_1488363522091_0001_01_01",
> "hostname" : "ctr-e129-1487033772569-30632-01-04.hwx.site",
> "amWebUrl" : 
> "http://ctr-e129-1487033772569-30632-01-04.hwx.site:32864/;
>   },
>   "state" : "LAUNCHING",
>   "originalConfigurationPath" : 
> 

[jira] [Commented] (AMBARI-20265) Blueprint deployment with auto-restart settings enabled, auto-restart UI is incomplete.

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-20265:


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

This message is automatically generated.

> Blueprint deployment with auto-restart settings enabled, auto-restart UI is 
> incomplete.
> ---
>
> Key: AMBARI-20265
> URL: https://issues.apache.org/jira/browse/AMBARI-20265
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Richard Zang
>Assignee: Richard Zang
> Fix For: 2.5.0
>
> Attachments: AMBARI-20265.patch
>
>
> Attached screenshot of UI post blueprint deployment.
> Attached blueprint used for deployment.
> Here is a snipped of blueprint to enable the auto-restart feature:
> {noformat}
>  "settings" : [
> {
>   "recovery_settings" : [
> {
>   "recovery_enabled" : "true"
> }
>   ]
> },
> {
>   "service_settings" : [
> {
>   "recovery_enabled" : "true",
>   "name" : "YARN"
> }
>   ]
> },
> {
>   "component_settings" : [
> {
>   "recovery_enabled" : "true",
>   "name" : "APP_TIMELINE_SERVER"
> }
>   ]
> }
>   ],
> {noformat}
> The expectation is that only the YARN App_timeline_server should be 
> auto-restart enabled. The overall property would also show enabled.
> {noformat}
> {
>   "blueprint": "bugbash",
>   "default_password": "password",
>   "config_recommendation_strategy": 
> "ALWAYS_APPLY_DONT_OVERRIDE_CUSTOM_VALUES",
>   "host_groups": [
> {
>   "name": "host_group_1",
>   "hosts": [
> {
>   "fqdn": "c6401.apache.ambari.org",
>   "ip": "192.168.64.101"
> }
>   ]
> },
> {
>   "name": "host_group_2",
>   "hosts": [
> {
>   "fqdn": "c6402.apache.ambari.org",
>   "ip": "192.168.64.102"
> }
>   ]
> },
> {
>   "name": "host_group_3",
>   "hosts": [
> {
>   "fqdn": "c6403.apache.ambari.org",
>   "ip": "192.168.64.103"
> }
>   ]
> }
>   ]
> }
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-20264) HiveServer2 Interactive start failed after WE enable

[Jayush Luniya (JIRA)]

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

Jayush Luniya commented on AMBARI-20264:


Trunk
commit 7cf7fcf556bed2ecc765828a9e2954908fdaf8a8
Author: Jayush Luniya 
Date:   Wed Mar 1 22:52:51 2017 -0800

AMBARI-20264: HiveServer2 Interactive start failed after WE enable (jluniya)

branch-2.5
commit eb8526d5fdab12616cc229874c5a1fa2f58f07c9
Author: Jayush Luniya 
Date:   Wed Mar 1 22:52:51 2017 -0800

AMBARI-20264: HiveServer2 Interactive start failed after WE enable (jluniya)

> HiveServer2 Interactive start failed after WE enable
> 
>
> Key: AMBARI-20264
> URL: https://issues.apache.org/jira/browse/AMBARI-20264
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.5.0
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
> Fix For: 2.5.0
>
> Attachments: AMBARI-20264.patch
>
>
> {code}
> hive --service llapstatus -w -r 0.8 -i 2 -t 200
>  Hortonworks #
> This is MOTD message, added for testing in qe infra
> SLF4J: Class path contains multiple SLF4J bindings.
> SLF4J: Found binding in 
> [jar:file:/grid/0/hdp/2.6.0.0-572/hive2/lib/log4j-slf4j-impl-2.6.2.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: Found binding in 
> [jar:file:/grid/0/hdp/2.6.0.0-572/hadoop/lib/slf4j-log4j12-1.7.10.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an 
> explanation.
> SLF4J: Actual binding is of type [org.apache.logging.slf4j.Log4jLoggerFactory]
> WARN conf.HiveConf: HiveConf hive.llap.daemon.vcpus.per.instance expects INT 
> type value
> LLAPSTATUS WatchMode with timeout=200 s
> 
> LLAP Starting up with AppId=application_1488363522091_0001.
> 
> LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
> instances
> 
> LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
> instances
> 
> LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
> instances
> 
> LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
> instances
> 
> LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
> instances
> 
> LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
> instances
> 
> LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
> instances
> 
> LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
> instances
> 
> LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
> instances
> 
> LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
> instances
> 
> LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
> instances
> 
> LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
> instances
> 
> LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
> instances
> 
> {
>   "amInfo" : {
> "appName" : "llap0",
> "appType" : "org-apache-slider",
> "appId" : "application_1488363522091_0001",
> "containerId" : "container_e01_1488363522091_0001_01_01",
> "hostname" : "ctr-e129-1487033772569-30632-01-04.hwx.site",
> "amWebUrl" : 
> "http://ctr-e129-1487033772569-30632-01-04.hwx.site:32864/;
>   },
>   "state" : "LAUNCHING",
>   "originalConfigurationPath" : 
> "hdfs://ctr-e129-1487033772569-30632-01-02.hwx.site:8020/user/cstm-hive/.slider/cluster/llap0/snapshot",
>   "generatedConfigurationPath" : 
> 

[jira] [Updated] (AMBARI-20264) HiveServer2 Interactive start failed after WE enable

[Jayush Luniya (JIRA)]

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

Jayush Luniya updated AMBARI-20264:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> HiveServer2 Interactive start failed after WE enable
> 
>
> Key: AMBARI-20264
> URL: https://issues.apache.org/jira/browse/AMBARI-20264
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.5.0
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
> Fix For: 2.5.0
>
> Attachments: AMBARI-20264.patch
>
>
> {code}
> hive --service llapstatus -w -r 0.8 -i 2 -t 200
>  Hortonworks #
> This is MOTD message, added for testing in qe infra
> SLF4J: Class path contains multiple SLF4J bindings.
> SLF4J: Found binding in 
> [jar:file:/grid/0/hdp/2.6.0.0-572/hive2/lib/log4j-slf4j-impl-2.6.2.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: Found binding in 
> [jar:file:/grid/0/hdp/2.6.0.0-572/hadoop/lib/slf4j-log4j12-1.7.10.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an 
> explanation.
> SLF4J: Actual binding is of type [org.apache.logging.slf4j.Log4jLoggerFactory]
> WARN conf.HiveConf: HiveConf hive.llap.daemon.vcpus.per.instance expects INT 
> type value
> LLAPSTATUS WatchMode with timeout=200 s
> 
> LLAP Starting up with AppId=application_1488363522091_0001.
> 
> LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
> instances
> 
> LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
> instances
> 
> LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
> instances
> 
> LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
> instances
> 
> LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
> instances
> 
> LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
> instances
> 
> LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
> instances
> 
> LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
> instances
> 
> LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
> instances
> 
> LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
> instances
> 
> LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
> instances
> 
> LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
> instances
> 
> LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
> instances
> 
> {
>   "amInfo" : {
> "appName" : "llap0",
> "appType" : "org-apache-slider",
> "appId" : "application_1488363522091_0001",
> "containerId" : "container_e01_1488363522091_0001_01_01",
> "hostname" : "ctr-e129-1487033772569-30632-01-04.hwx.site",
> "amWebUrl" : 
> "http://ctr-e129-1487033772569-30632-01-04.hwx.site:32864/;
>   },
>   "state" : "LAUNCHING",
>   "originalConfigurationPath" : 
> "hdfs://ctr-e129-1487033772569-30632-01-02.hwx.site:8020/user/cstm-hive/.slider/cluster/llap0/snapshot",
>   "generatedConfigurationPath" : 
> "hdfs://ctr-e129-1487033772569-30632-01-02.hwx.site:8020/user/cstm-hive/.slider/cluster/llap0/generated",
>   "desiredInstances" : 1,
>   "liveInstances" : 0,
>   "appStartTime" : 1488363931836,
>   "runningThresholdAchieved" : false
> }
> WARN cli.LlapStatusServiceDriver: Watch timeout 200s exhausted before desired 
> state RUNNING is attained.
> 2017-03-01 10:28:51,909 - LLAP app 'llap0' current state is LAUNCHING.
> 

[jira] [Commented] (AMBARI-20091) Table statistics is not getting computed when 'include columns' is checked

[Hudson (JIRA)]

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

Hudson commented on AMBARI-20091:
-

SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1152 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/1152/])
AMBARI-20091 : hive20 view : executing analyze table explicitly with 
(nitiraj.rathore: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=8425eeb01427c43a4e25ab3403320ad6251b3e4b])
* (edit) 
contrib/views/hive20/src/main/java/org/apache/ambari/view/hive20/internal/query/generators/AnalyzeTableQueryGenerator.java
* (edit) 
contrib/views/hive20/src/test/java/org/apache/ambari/view/hive20/internal/query/generators/AnalyzeTableQueryGeneratorSpecTest.groovy


> Table statistics is not getting computed when 'include columns' is checked
> --
>
> Key: AMBARI-20091
> URL: https://issues.apache.org/jira/browse/AMBARI-20091
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Supreeth Sharma
>Assignee: Nitiraj Singh Rathore
>Priority: Critical
>  Labels: HiveView2.0
> Fix For: 2.5.0
>
> Attachments: AMBARI-20091_branch-2.5_2.patch
>
>
> Table statistics is not getting computed when 'include columns' is checked.
> Steps to reproduce :
> 1) Create a new table and load data into the table .
> 2) Navigate to the table and recompute the statistics with 'include columns' 
> being checked.
> 3) Table statistics is not computed by this action and 'Number of Rows' and 
> 'Raw Data Size' still coming as 0.
> If user runs the recompute without checking 'include columns' , then results 
> are appearing as expected.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-20091) Table statistics is not getting computed when 'include columns' is checked

[Hudson (JIRA)]

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

Hudson commented on AMBARI-20091:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6911 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6911/])
AMBARI-20091 : hive20 view : executing analyze table explicitly with 
(nitiraj.rathore: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=e90f7edf2e019b86ef194399115a33ab70c9643a])
* (edit) 
contrib/views/hive20/src/main/java/org/apache/ambari/view/hive20/internal/query/generators/AnalyzeTableQueryGenerator.java
* (edit) 
contrib/views/hive20/src/test/java/org/apache/ambari/view/hive20/internal/query/generators/AnalyzeTableQueryGeneratorSpecTest.groovy


> Table statistics is not getting computed when 'include columns' is checked
> --
>
> Key: AMBARI-20091
> URL: https://issues.apache.org/jira/browse/AMBARI-20091
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Supreeth Sharma
>Assignee: Nitiraj Singh Rathore
>Priority: Critical
>  Labels: HiveView2.0
> Fix For: 2.5.0
>
> Attachments: AMBARI-20091_branch-2.5_2.patch
>
>
> Table statistics is not getting computed when 'include columns' is checked.
> Steps to reproduce :
> 1) Create a new table and load data into the table .
> 2) Navigate to the table and recompute the statistics with 'include columns' 
> being checked.
> 3) Table statistics is not computed by this action and 'Number of Rows' and 
> 'Raw Data Size' still coming as 0.
> If user runs the recompute without checking 'include columns' , then results 
> are appearing as expected.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-20091) Table statistics is not getting computed when 'include columns' is checked

[Nitiraj Singh Rathore (JIRA)]

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

Nitiraj Singh Rathore updated AMBARI-20091:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

committed to branch-2.5 and trunk

> Table statistics is not getting computed when 'include columns' is checked
> --
>
> Key: AMBARI-20091
> URL: https://issues.apache.org/jira/browse/AMBARI-20091
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Supreeth Sharma
>Assignee: Nitiraj Singh Rathore
>Priority: Critical
>  Labels: HiveView2.0
> Fix For: 2.5.0
>
> Attachments: AMBARI-20091_branch-2.5_2.patch
>
>
> Table statistics is not getting computed when 'include columns' is checked.
> Steps to reproduce :
> 1) Create a new table and load data into the table .
> 2) Navigate to the table and recompute the statistics with 'include columns' 
> being checked.
> 3) Table statistics is not computed by this action and 'Number of Rows' and 
> 'Raw Data Size' still coming as 0.
> If user runs the recompute without checking 'include columns' , then results 
> are appearing as expected.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-20091) Table statistics is not getting computed when 'include columns' is checked

[Nitiraj Singh Rathore (JIRA)]

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

Nitiraj Singh Rathore updated AMBARI-20091:
---
Attachment: (was: AMBARI-20091_branch-2.5.patch)

> Table statistics is not getting computed when 'include columns' is checked
> --
>
> Key: AMBARI-20091
> URL: https://issues.apache.org/jira/browse/AMBARI-20091
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Supreeth Sharma
>Assignee: Nitiraj Singh Rathore
>Priority: Critical
>  Labels: HiveView2.0
> Fix For: 2.5.0
>
> Attachments: AMBARI-20091_branch-2.5_2.patch
>
>
> Table statistics is not getting computed when 'include columns' is checked.
> Steps to reproduce :
> 1) Create a new table and load data into the table .
> 2) Navigate to the table and recompute the statistics with 'include columns' 
> being checked.
> 3) Table statistics is not computed by this action and 'Number of Rows' and 
> 'Raw Data Size' still coming as 0.
> If user runs the recompute without checking 'include columns' , then results 
> are appearing as expected.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-20091) Table statistics is not getting computed when 'include columns' is checked

[Nitiraj Singh Rathore (JIRA)]

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

Nitiraj Singh Rathore updated AMBARI-20091:
---
Attachment: AMBARI-20091_branch-2.5_2.patch

updated patch after resolving conflicts.

> Table statistics is not getting computed when 'include columns' is checked
> --
>
> Key: AMBARI-20091
> URL: https://issues.apache.org/jira/browse/AMBARI-20091
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Supreeth Sharma
>Assignee: Nitiraj Singh Rathore
>Priority: Critical
>  Labels: HiveView2.0
> Fix For: 2.5.0
>
> Attachments: AMBARI-20091_branch-2.5_2.patch, 
> AMBARI-20091_branch-2.5.patch
>
>
> Table statistics is not getting computed when 'include columns' is checked.
> Steps to reproduce :
> 1) Create a new table and load data into the table .
> 2) Navigate to the table and recompute the statistics with 'include columns' 
> being checked.
> 3) Table statistics is not computed by this action and 'Number of Rows' and 
> 'Raw Data Size' still coming as 0.
> If user runs the recompute without checking 'include columns' , then results 
> are appearing as expected.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-20265) Blueprint deployment with auto-restart settings enabled, auto-restart UI is incomplete.

[Richard Zang (JIRA)]

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

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

> Blueprint deployment with auto-restart settings enabled, auto-restart UI is 
> incomplete.
> ---
>
> Key: AMBARI-20265
> URL: https://issues.apache.org/jira/browse/AMBARI-20265
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Richard Zang
>Assignee: Richard Zang
> Fix For: 2.5.0
>
> Attachments: AMBARI-20265.patch
>
>
> Attached screenshot of UI post blueprint deployment.
> Attached blueprint used for deployment.
> Here is a snipped of blueprint to enable the auto-restart feature:
> {noformat}
>  "settings" : [
> {
>   "recovery_settings" : [
> {
>   "recovery_enabled" : "true"
> }
>   ]
> },
> {
>   "service_settings" : [
> {
>   "recovery_enabled" : "true",
>   "name" : "YARN"
> }
>   ]
> },
> {
>   "component_settings" : [
> {
>   "recovery_enabled" : "true",
>   "name" : "APP_TIMELINE_SERVER"
> }
>   ]
> }
>   ],
> {noformat}
> The expectation is that only the YARN App_timeline_server should be 
> auto-restart enabled. The overall property would also show enabled.
> {noformat}
> {
>   "blueprint": "bugbash",
>   "default_password": "password",
>   "config_recommendation_strategy": 
> "ALWAYS_APPLY_DONT_OVERRIDE_CUSTOM_VALUES",
>   "host_groups": [
> {
>   "name": "host_group_1",
>   "hosts": [
> {
>   "fqdn": "c6401.apache.ambari.org",
>   "ip": "192.168.64.101"
> }
>   ]
> },
> {
>   "name": "host_group_2",
>   "hosts": [
> {
>   "fqdn": "c6402.apache.ambari.org",
>   "ip": "192.168.64.102"
> }
>   ]
> },
> {
>   "name": "host_group_3",
>   "hosts": [
> {
>   "fqdn": "c6403.apache.ambari.org",
>   "ip": "192.168.64.103"
> }
>   ]
> }
>   ]
> }
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-20265) Blueprint deployment with auto-restart settings enabled, auto-restart UI is incomplete.

[Richard Zang (JIRA)]

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

Richard Zang updated AMBARI-20265:
--
Status: Patch Available  (was: Open)

> Blueprint deployment with auto-restart settings enabled, auto-restart UI is 
> incomplete.
> ---
>
> Key: AMBARI-20265
> URL: https://issues.apache.org/jira/browse/AMBARI-20265
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Richard Zang
>Assignee: Richard Zang
> Fix For: 2.5.0
>
> Attachments: AMBARI-20265.patch
>
>
> Attached screenshot of UI post blueprint deployment.
> Attached blueprint used for deployment.
> Here is a snipped of blueprint to enable the auto-restart feature:
> {noformat}
>  "settings" : [
> {
>   "recovery_settings" : [
> {
>   "recovery_enabled" : "true"
> }
>   ]
> },
> {
>   "service_settings" : [
> {
>   "recovery_enabled" : "true",
>   "name" : "YARN"
> }
>   ]
> },
> {
>   "component_settings" : [
> {
>   "recovery_enabled" : "true",
>   "name" : "APP_TIMELINE_SERVER"
> }
>   ]
> }
>   ],
> {noformat}
> The expectation is that only the YARN App_timeline_server should be 
> auto-restart enabled. The overall property would also show enabled.
> {noformat}
> {
>   "blueprint": "bugbash",
>   "default_password": "password",
>   "config_recommendation_strategy": 
> "ALWAYS_APPLY_DONT_OVERRIDE_CUSTOM_VALUES",
>   "host_groups": [
> {
>   "name": "host_group_1",
>   "hosts": [
> {
>   "fqdn": "c6401.apache.ambari.org",
>   "ip": "192.168.64.101"
> }
>   ]
> },
> {
>   "name": "host_group_2",
>   "hosts": [
> {
>   "fqdn": "c6402.apache.ambari.org",
>   "ip": "192.168.64.102"
> }
>   ]
> },
> {
>   "name": "host_group_3",
>   "hosts": [
> {
>   "fqdn": "c6403.apache.ambari.org",
>   "ip": "192.168.64.103"
> }
>   ]
> }
>   ]
> }
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (AMBARI-20265) Blueprint deployment with auto-restart settings enabled, auto-restart UI is incomplete.

[Richard Zang (JIRA)]

Richard Zang created AMBARI-20265:
-

 Summary: Blueprint deployment with auto-restart settings enabled, 
auto-restart UI is incomplete.
 Key: AMBARI-20265
 URL: https://issues.apache.org/jira/browse/AMBARI-20265
 Project: Ambari
  Issue Type: Bug
  Components: ambari-web
Affects Versions: 2.5.0
Reporter: Richard Zang
Assignee: Richard Zang
 Fix For: 2.5.0


Attached screenshot of UI post blueprint deployment.
Attached blueprint used for deployment.

Here is a snipped of blueprint to enable the auto-restart feature:
{noformat}
 "settings" : [
{
  "recovery_settings" : [
{
  "recovery_enabled" : "true"
}
  ]
},
{
  "service_settings" : [
{
  "recovery_enabled" : "true",
  "name" : "YARN"
}
  ]
},
{
  "component_settings" : [
{
  "recovery_enabled" : "true",
  "name" : "APP_TIMELINE_SERVER"
}
  ]
}
  ],
{noformat}

The expectation is that only the YARN App_timeline_server should be 
auto-restart enabled. The overall property would also show enabled.

{noformat}
{
  "blueprint": "bugbash",
  "default_password": "password",
  "config_recommendation_strategy": "ALWAYS_APPLY_DONT_OVERRIDE_CUSTOM_VALUES",
  "host_groups": [
{
  "name": "host_group_1",
  "hosts": [
{
  "fqdn": "c6401.apache.ambari.org",
  "ip": "192.168.64.101"
}
  ]
},
{
  "name": "host_group_2",
  "hosts": [
{
  "fqdn": "c6402.apache.ambari.org",
  "ip": "192.168.64.102"
}
  ]
},
{
  "name": "host_group_3",
  "hosts": [
{
  "fqdn": "c6403.apache.ambari.org",
  "ip": "192.168.64.103"
}
  ]
}
  ]
}
{noformat}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-20243) Include option to filter out properties from APi that returns ambari.properties file

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-20243:


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

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

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

This message is automatically generated.

> Include option to filter out properties from APi that returns 
> ambari.properties file
> 
>
> Key: AMBARI-20243
> URL: https://issues.apache.org/jira/browse/AMBARI-20243
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-sever
>Affects Versions: trunk
>Reporter: Anita Gnanamalar Jebaraj
>Assignee: Anita Gnanamalar Jebaraj
> Fix For: trunk
>
> Attachments: AMBARI-20243-Mar1.patch, AMBARI-20243.patch
>
>
> Currently all the details from the ambari.properties file is being returned 
> by the API call.
> Some of those information may not be utilized and hence an option can be 
> provided to filter the properties.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-20264) HiveServer2 Interactive start failed after WE enable

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-20264:


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

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

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

This message is automatically generated.

> HiveServer2 Interactive start failed after WE enable
> 
>
> Key: AMBARI-20264
> URL: https://issues.apache.org/jira/browse/AMBARI-20264
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.5.0
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
> Fix For: 2.5.0
>
> Attachments: AMBARI-20264.patch
>
>
> {code}
> hive --service llapstatus -w -r 0.8 -i 2 -t 200
>  Hortonworks #
> This is MOTD message, added for testing in qe infra
> SLF4J: Class path contains multiple SLF4J bindings.
> SLF4J: Found binding in 
> [jar:file:/grid/0/hdp/2.6.0.0-572/hive2/lib/log4j-slf4j-impl-2.6.2.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: Found binding in 
> [jar:file:/grid/0/hdp/2.6.0.0-572/hadoop/lib/slf4j-log4j12-1.7.10.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an 
> explanation.
> SLF4J: Actual binding is of type [org.apache.logging.slf4j.Log4jLoggerFactory]
> WARN conf.HiveConf: HiveConf hive.llap.daemon.vcpus.per.instance expects INT 
> type value
> LLAPSTATUS WatchMode with timeout=200 s
> 
> LLAP Starting up with AppId=application_1488363522091_0001.
> 
> LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
> instances
> 
> LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
> instances
> 
> LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
> instances
> 
> LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
> instances
> 
> LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
> instances
> 
> LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
> instances
> 
> LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
> instances
> 
> LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
> instances
> 
> LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
> instances
> 
> LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
> instances
> 
> LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
> instances
> 
> LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
> instances
> 
> LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
> instances
> 
> {
>   "amInfo" : {
> "appName" : "llap0",
> "appType" : "org-apache-slider",
> "appId" : "application_1488363522091_0001",
> "containerId" : "container_e01_1488363522091_0001_01_01",
> "hostname" : "ctr-e129-1487033772569-30632-01-04.hwx.site",
> "amWebUrl" : 
> "http://ctr-e129-1487033772569-30632-01-04.hwx.site:32864/;
>   },
>   "state" : "LAUNCHING",
>   "originalConfigurationPath" : 
> "hdfs://ctr-e129-1487033772569-30632-01-02.hwx.site:8020/user/cstm-hive/.slider/cluster/llap0/snapshot",
>   "generatedConfigurationPath" : 
> 

[jira] [Commented] (AMBARI-20245) Setup tez ats related parameters

[Hudson (JIRA)]

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

Hudson commented on AMBARI-20245:
-

SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1151 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/1151/])
"AMBARI-20245. Setup tez ats related parameters (smohanty)" (smohanty: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=986771179ab65b144a396ae17fa4c9d5ad7ba281])
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.6/services/HIVE/configuration/tez-interactive-site.xml
* (edit) ambari-server/pom.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.6/services/TEZ/configuration/tez-site.xml


> Setup tez ats related parameters
> 
>
> Key: AMBARI-20245
> URL: https://issues.apache.org/jira/browse/AMBARI-20245
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.5.0
>Reporter: Siddharth Seth
>Assignee: Sumit Mohanty
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20245.modified.patch, AMBARI-20245.patch
>
>
> Dags per group needs to be set to 5.
> TASK_ATTEMPT events to be ignored needs to be set to 
> |tez-interactive-site|tez.history.logging.timeline.num-dags-per-group|5|
> |tez-site|tez.history.logging.timeline-cache-plugin.old-num-dags-per-group|5|
> |tez-intearactive-site|tez.history.logging.taskattempt-filters|EXECUTOR_BUSY,EXTERNAL_PREEMPTION|



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-20245) Setup tez ats related parameters

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty updated AMBARI-20245:
---
Attachment: AMBARI-20245.modified.patch

> Setup tez ats related parameters
> 
>
> Key: AMBARI-20245
> URL: https://issues.apache.org/jira/browse/AMBARI-20245
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.5.0
>Reporter: Siddharth Seth
>Assignee: Sumit Mohanty
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20245.modified.patch, AMBARI-20245.patch
>
>
> Dags per group needs to be set to 5.
> TASK_ATTEMPT events to be ignored needs to be set to 
> |tez-interactive-site|tez.history.logging.timeline.num-dags-per-group|5|
> |tez-site|tez.history.logging.timeline-cache-plugin.old-num-dags-per-group|5|
> |tez-intearactive-site|tez.history.logging.taskattempt-filters|EXECUTOR_BUSY,EXTERNAL_PREEMPTION|



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-20245) Setup tez ats related parameters

[Hudson (JIRA)]

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

Hudson commented on AMBARI-20245:
-

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6910 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6910/])
Revert "AMBARI-20245. Setup tez ats related parameters (smohanty)" (smohanty: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=74233a1bf29418e820b0b85b70c8b024dfd9])
* (edit) pom.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.6/services/TEZ/configuration/tez-site.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.6/services/HIVE/configuration/tez-interactive-site.xml
AMBARI-20245. Setup tez ats related parameters (smohanty) (smohanty: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=1e8b7748323a43abd4e743dedd2708ceecb40386])
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.6/services/HIVE/configuration/tez-interactive-site.xml
* (edit) ambari-server/pom.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.6/services/TEZ/configuration/tez-site.xml


> Setup tez ats related parameters
> 
>
> Key: AMBARI-20245
> URL: https://issues.apache.org/jira/browse/AMBARI-20245
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.5.0
>Reporter: Siddharth Seth
>Assignee: Sumit Mohanty
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20245.patch
>
>
> Dags per group needs to be set to 5.
> TASK_ATTEMPT events to be ignored needs to be set to 
> |tez-interactive-site|tez.history.logging.timeline.num-dags-per-group|5|
> |tez-site|tez.history.logging.timeline-cache-plugin.old-num-dags-per-group|5|
> |tez-intearactive-site|tez.history.logging.taskattempt-filters|EXECUTOR_BUSY,EXTERNAL_PREEMPTION|



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-20245) Setup tez ats related parameters

[Hudson (JIRA)]

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

Hudson commented on AMBARI-20245:
-

SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1150 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/1150/])
Revert "AMBARI-20245. Setup tez ats related parameters (smohanty)" (smohanty: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=c323a94029565b76720549a3b950d653dd58ef84])
* (edit) pom.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.6/services/HIVE/configuration/tez-interactive-site.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.6/services/TEZ/configuration/tez-site.xml


> Setup tez ats related parameters
> 
>
> Key: AMBARI-20245
> URL: https://issues.apache.org/jira/browse/AMBARI-20245
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.5.0
>Reporter: Siddharth Seth
>Assignee: Sumit Mohanty
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20245.patch
>
>
> Dags per group needs to be set to 5.
> TASK_ATTEMPT events to be ignored needs to be set to 
> |tez-interactive-site|tez.history.logging.timeline.num-dags-per-group|5|
> |tez-site|tez.history.logging.timeline-cache-plugin.old-num-dags-per-group|5|
> |tez-intearactive-site|tez.history.logging.taskattempt-filters|EXECUTOR_BUSY,EXTERNAL_PREEMPTION|



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-20259) Superset not able to start on Ubuntu if ASCII encoding is set as default encoding

[Hudson (JIRA)]

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

Hudson commented on AMBARI-20259:
-

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6909 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6909/])
AMBARI-20259. Superset not able to start on Ubuntu if ASCII encoding is 
(sshridhar: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=2ceeae8503a6e051f9e7e69801ad4bd9d229ea78])
* (edit) 
ambari-server/src/main/resources/common-services/DRUID/0.9.2/configuration/druid-superset-env.xml


> Superset not able to start on Ubuntu if ASCII encoding is set as default 
> encoding
> -
>
> Key: AMBARI-20259
> URL: https://issues.apache.org/jira/browse/AMBARI-20259
> Project: Ambari
>  Issue Type: Bug
>Reporter: Nishant Bangarwa
>Assignee: Nishant Bangarwa
> Fix For: trunk, 2.5.0
>
> Attachments: ambari-20259.patch
>
>
> RuntimeError: Click will abort further execution because Python 3 was 
> configured to use ASCII as encoding for the environment.  Consult 
> http://click.pocoo.org/python3/for mitigation steps.
> This system supports the C.UTF-8 locale which is recommended.
> You might be able to resolve your issue by exporting the
> following environment variables:
> export LC_ALL=C.UTF-8
> export LANG=C.UTF-8



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-20264) HiveServer2 Interactive start failed after WE enable

[Jayush Luniya (JIRA)]

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

Jayush Luniya updated AMBARI-20264:
---
Attachment: AMBARI-20264.patch

> HiveServer2 Interactive start failed after WE enable
> 
>
> Key: AMBARI-20264
> URL: https://issues.apache.org/jira/browse/AMBARI-20264
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.5.0
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
> Fix For: 2.5.0
>
> Attachments: AMBARI-20264.patch
>
>
> {code}
> hive --service llapstatus -w -r 0.8 -i 2 -t 200
>  Hortonworks #
> This is MOTD message, added for testing in qe infra
> SLF4J: Class path contains multiple SLF4J bindings.
> SLF4J: Found binding in 
> [jar:file:/grid/0/hdp/2.6.0.0-572/hive2/lib/log4j-slf4j-impl-2.6.2.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: Found binding in 
> [jar:file:/grid/0/hdp/2.6.0.0-572/hadoop/lib/slf4j-log4j12-1.7.10.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an 
> explanation.
> SLF4J: Actual binding is of type [org.apache.logging.slf4j.Log4jLoggerFactory]
> WARN conf.HiveConf: HiveConf hive.llap.daemon.vcpus.per.instance expects INT 
> type value
> LLAPSTATUS WatchMode with timeout=200 s
> 
> LLAP Starting up with AppId=application_1488363522091_0001.
> 
> LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
> instances
> 
> LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
> instances
> 
> LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
> instances
> 
> LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
> instances
> 
> LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
> instances
> 
> LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
> instances
> 
> LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
> instances
> 
> LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
> instances
> 
> LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
> instances
> 
> LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
> instances
> 
> LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
> instances
> 
> LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
> instances
> 
> LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
> instances
> 
> {
>   "amInfo" : {
> "appName" : "llap0",
> "appType" : "org-apache-slider",
> "appId" : "application_1488363522091_0001",
> "containerId" : "container_e01_1488363522091_0001_01_01",
> "hostname" : "ctr-e129-1487033772569-30632-01-04.hwx.site",
> "amWebUrl" : 
> "http://ctr-e129-1487033772569-30632-01-04.hwx.site:32864/;
>   },
>   "state" : "LAUNCHING",
>   "originalConfigurationPath" : 
> "hdfs://ctr-e129-1487033772569-30632-01-02.hwx.site:8020/user/cstm-hive/.slider/cluster/llap0/snapshot",
>   "generatedConfigurationPath" : 
> "hdfs://ctr-e129-1487033772569-30632-01-02.hwx.site:8020/user/cstm-hive/.slider/cluster/llap0/generated",
>   "desiredInstances" : 1,
>   "liveInstances" : 0,
>   "appStartTime" : 1488363931836,
>   "runningThresholdAchieved" : false
> }
> WARN cli.LlapStatusServiceDriver: Watch timeout 200s exhausted before desired 
> state RUNNING is attained.
> 2017-03-01 10:28:51,909 - LLAP app 'llap0' current state is LAUNCHING.
> 2017-03-01 10:28:51,909 - LLAP app 

[jira] [Commented] (AMBARI-20259) Superset not able to start on Ubuntu if ASCII encoding is set as default encoding

[Hudson (JIRA)]

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

Hudson commented on AMBARI-20259:
-

SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1149 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/1149/])
AMBARI-20259. Superset not able to start on Ubuntu if ASCII encoding is 
(sshridhar: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=9edf3c9371132c5733155ca7b38616f5ae70ded2])
* (edit) 
ambari-server/src/main/resources/common-services/DRUID/0.9.2/configuration/druid-superset-env.xml


> Superset not able to start on Ubuntu if ASCII encoding is set as default 
> encoding
> -
>
> Key: AMBARI-20259
> URL: https://issues.apache.org/jira/browse/AMBARI-20259
> Project: Ambari
>  Issue Type: Bug
>Reporter: Nishant Bangarwa
>Assignee: Nishant Bangarwa
> Fix For: trunk, 2.5.0
>
> Attachments: ambari-20259.patch
>
>
> RuntimeError: Click will abort further execution because Python 3 was 
> configured to use ASCII as encoding for the environment.  Consult 
> http://click.pocoo.org/python3/for mitigation steps.
> This system supports the C.UTF-8 locale which is recommended.
> You might be able to resolve your issue by exporting the
> following environment variables:
> export LC_ALL=C.UTF-8
> export LANG=C.UTF-8



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-20264) HiveServer2 Interactive start failed after WE enable

[Jayush Luniya (JIRA)]

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

Jayush Luniya updated AMBARI-20264:
---
Status: Patch Available  (was: In Progress)

> HiveServer2 Interactive start failed after WE enable
> 
>
> Key: AMBARI-20264
> URL: https://issues.apache.org/jira/browse/AMBARI-20264
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.5.0
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
> Fix For: 2.5.0
>
> Attachments: AMBARI-20264.patch
>
>
> {code}
> hive --service llapstatus -w -r 0.8 -i 2 -t 200
>  Hortonworks #
> This is MOTD message, added for testing in qe infra
> SLF4J: Class path contains multiple SLF4J bindings.
> SLF4J: Found binding in 
> [jar:file:/grid/0/hdp/2.6.0.0-572/hive2/lib/log4j-slf4j-impl-2.6.2.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: Found binding in 
> [jar:file:/grid/0/hdp/2.6.0.0-572/hadoop/lib/slf4j-log4j12-1.7.10.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an 
> explanation.
> SLF4J: Actual binding is of type [org.apache.logging.slf4j.Log4jLoggerFactory]
> WARN conf.HiveConf: HiveConf hive.llap.daemon.vcpus.per.instance expects INT 
> type value
> LLAPSTATUS WatchMode with timeout=200 s
> 
> LLAP Starting up with AppId=application_1488363522091_0001.
> 
> LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
> instances
> 
> LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
> instances
> 
> LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
> instances
> 
> LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
> instances
> 
> LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
> instances
> 
> LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
> instances
> 
> LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
> instances
> 
> LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
> instances
> 
> LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
> instances
> 
> LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
> instances
> 
> LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
> instances
> 
> LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
> instances
> 
> LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
> instances
> 
> {
>   "amInfo" : {
> "appName" : "llap0",
> "appType" : "org-apache-slider",
> "appId" : "application_1488363522091_0001",
> "containerId" : "container_e01_1488363522091_0001_01_01",
> "hostname" : "ctr-e129-1487033772569-30632-01-04.hwx.site",
> "amWebUrl" : 
> "http://ctr-e129-1487033772569-30632-01-04.hwx.site:32864/;
>   },
>   "state" : "LAUNCHING",
>   "originalConfigurationPath" : 
> "hdfs://ctr-e129-1487033772569-30632-01-02.hwx.site:8020/user/cstm-hive/.slider/cluster/llap0/snapshot",
>   "generatedConfigurationPath" : 
> "hdfs://ctr-e129-1487033772569-30632-01-02.hwx.site:8020/user/cstm-hive/.slider/cluster/llap0/generated",
>   "desiredInstances" : 1,
>   "liveInstances" : 0,
>   "appStartTime" : 1488363931836,
>   "runningThresholdAchieved" : false
> }
> WARN cli.LlapStatusServiceDriver: Watch timeout 200s exhausted before desired 
> state RUNNING is attained.
> 2017-03-01 10:28:51,909 - LLAP app 'llap0' current state is LAUNCHING.
> 2017-03-01 10:28:51,909 - 

[jira] [Updated] (AMBARI-20264) HiveServer2 Interactive start failed after WE enable

[Jayush Luniya (JIRA)]

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

Jayush Luniya updated AMBARI-20264:
---
Description: 
{code}
hive --service llapstatus -w -r 0.8 -i 2 -t 200
 Hortonworks #
This is MOTD message, added for testing in qe infra
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in 
[jar:file:/grid/0/hdp/2.6.0.0-572/hive2/lib/log4j-slf4j-impl-2.6.2.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in 
[jar:file:/grid/0/hdp/2.6.0.0-572/hadoop/lib/slf4j-log4j12-1.7.10.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual binding is of type [org.apache.logging.slf4j.Log4jLoggerFactory]
WARN conf.HiveConf: HiveConf hive.llap.daemon.vcpus.per.instance expects INT 
type value

LLAPSTATUS WatchMode with timeout=200 s

LLAP Starting up with AppId=application_1488363522091_0001.

LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
instances

LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
instances

LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
instances

LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
instances

LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
instances

LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
instances

LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
instances

LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
instances

LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
instances

LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
instances

LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
instances

LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
instances

LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
instances





{
  "amInfo" : {
"appName" : "llap0",
"appType" : "org-apache-slider",
"appId" : "application_1488363522091_0001",
"containerId" : "container_e01_1488363522091_0001_01_01",
"hostname" : "ctr-e129-1487033772569-30632-01-04.hwx.site",
"amWebUrl" : "http://ctr-e129-1487033772569-30632-01-04.hwx.site:32864/;
  },
  "state" : "LAUNCHING",
  "originalConfigurationPath" : 
"hdfs://ctr-e129-1487033772569-30632-01-02.hwx.site:8020/user/cstm-hive/.slider/cluster/llap0/snapshot",
  "generatedConfigurationPath" : 
"hdfs://ctr-e129-1487033772569-30632-01-02.hwx.site:8020/user/cstm-hive/.slider/cluster/llap0/generated",
  "desiredInstances" : 1,
  "liveInstances" : 0,
  "appStartTime" : 1488363931836,
  "runningThresholdAchieved" : false
}
WARN cli.LlapStatusServiceDriver: Watch timeout 200s exhausted before desired 
state RUNNING is attained.
2017-03-01 10:28:51,909 - LLAP app 'llap0' current state is LAUNCHING.
2017-03-01 10:28:51,909 - LLAP app 'llap0' current state is LAUNCHING.
2017-03-01 10:28:51,909 - LLAP app 'llap0' deployment unsuccessful.

Command failed after 1 tries
{code}

Need to increase the retry count and hence the total_timeout value used for 
llapstatus check.


  was:
hive --service llapstatus -w -r 0.8 -i 2 -t 200
 Hortonworks #
This is MOTD message, added for testing in qe infra
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in 
[jar:file:/grid/0/hdp/2.6.0.0-572/hive2/lib/log4j-slf4j-impl-2.6.2.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in 

[jira] [Created] (AMBARI-20264) HiveServer2 Interactive start failed after WE enable

[Jayush Luniya (JIRA)]

Jayush Luniya created AMBARI-20264:
--

 Summary: HiveServer2 Interactive start failed after WE enable
 Key: AMBARI-20264
 URL: https://issues.apache.org/jira/browse/AMBARI-20264
 Project: Ambari
  Issue Type: Bug
  Components: stacks
Affects Versions: 2.5.0
Reporter: Jayush Luniya
Assignee: Jayush Luniya
 Fix For: 2.5.0


hive --service llapstatus -w -r 0.8 -i 2 -t 200
 Hortonworks #
This is MOTD message, added for testing in qe infra
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in 
[jar:file:/grid/0/hdp/2.6.0.0-572/hive2/lib/log4j-slf4j-impl-2.6.2.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in 
[jar:file:/grid/0/hdp/2.6.0.0-572/hadoop/lib/slf4j-log4j12-1.7.10.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual binding is of type [org.apache.logging.slf4j.Log4jLoggerFactory]
WARN conf.HiveConf: HiveConf hive.llap.daemon.vcpus.per.instance expects INT 
type value

LLAPSTATUS WatchMode with timeout=200 s

LLAP Starting up with AppId=application_1488363522091_0001.

LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
instances

LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
instances

LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
instances

LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
instances

LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
instances

LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
instances

LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
instances

LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
instances

LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
instances

LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
instances

LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
instances

LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
instances

LLAP Starting up with AppId=application_1488363522091_0001. Started 0/1 
instances





{
  "amInfo" : {
"appName" : "llap0",
"appType" : "org-apache-slider",
"appId" : "application_1488363522091_0001",
"containerId" : "container_e01_1488363522091_0001_01_01",
"hostname" : "ctr-e129-1487033772569-30632-01-04.hwx.site",
"amWebUrl" : "http://ctr-e129-1487033772569-30632-01-04.hwx.site:32864/;
  },
  "state" : "LAUNCHING",
  "originalConfigurationPath" : 
"hdfs://ctr-e129-1487033772569-30632-01-02.hwx.site:8020/user/cstm-hive/.slider/cluster/llap0/snapshot",
  "generatedConfigurationPath" : 
"hdfs://ctr-e129-1487033772569-30632-01-02.hwx.site:8020/user/cstm-hive/.slider/cluster/llap0/generated",
  "desiredInstances" : 1,
  "liveInstances" : 0,
  "appStartTime" : 1488363931836,
  "runningThresholdAchieved" : false
}
WARN cli.LlapStatusServiceDriver: Watch timeout 200s exhausted before desired 
state RUNNING is attained.
2017-03-01 10:28:51,909 - LLAP app 'llap0' current state is LAUNCHING.
2017-03-01 10:28:51,909 - LLAP app 'llap0' current state is LAUNCHING.
2017-03-01 10:28:51,909 - LLAP app 'llap0' deployment unsuccessful.

Command failed after 1 tries





--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-20243) Include option to filter out properties from APi that returns ambari.properties file

[Anita Gnanamalar Jebaraj (JIRA)]

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

Anita Gnanamalar Jebaraj updated AMBARI-20243:
--
Status: Patch Available  (was: Open)

> Include option to filter out properties from APi that returns 
> ambari.properties file
> 
>
> Key: AMBARI-20243
> URL: https://issues.apache.org/jira/browse/AMBARI-20243
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-sever
>Affects Versions: trunk
>Reporter: Anita Gnanamalar Jebaraj
>Assignee: Anita Gnanamalar Jebaraj
> Fix For: trunk
>
> Attachments: AMBARI-20243-Mar1.patch, AMBARI-20243.patch
>
>
> Currently all the details from the ambari.properties file is being returned 
> by the API call.
> Some of those information may not be utilized and hence an option can be 
> provided to filter the properties.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-20243) Include option to filter out properties from APi that returns ambari.properties file

[Anita Gnanamalar Jebaraj (JIRA)]

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

Anita Gnanamalar Jebaraj updated AMBARI-20243:
--
Status: Open  (was: Patch Available)

> Include option to filter out properties from APi that returns 
> ambari.properties file
> 
>
> Key: AMBARI-20243
> URL: https://issues.apache.org/jira/browse/AMBARI-20243
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-sever
>Affects Versions: trunk
>Reporter: Anita Gnanamalar Jebaraj
>Assignee: Anita Gnanamalar Jebaraj
> Fix For: trunk
>
> Attachments: AMBARI-20243-Mar1.patch, AMBARI-20243.patch
>
>
> Currently all the details from the ambari.properties file is being returned 
> by the API call.
> Some of those information may not be utilized and hence an option can be 
> provided to filter the properties.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-20243) Include option to filter out properties from APi that returns ambari.properties file

[Anita Gnanamalar Jebaraj (JIRA)]

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

Anita Gnanamalar Jebaraj updated AMBARI-20243:
--
Attachment: AMBARI-20243-Mar1.patch

> Include option to filter out properties from APi that returns 
> ambari.properties file
> 
>
> Key: AMBARI-20243
> URL: https://issues.apache.org/jira/browse/AMBARI-20243
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-sever
>Affects Versions: trunk
>Reporter: Anita Gnanamalar Jebaraj
>Assignee: Anita Gnanamalar Jebaraj
> Fix For: trunk
>
> Attachments: AMBARI-20243-Mar1.patch, AMBARI-20243.patch
>
>
> Currently all the details from the ambari.properties file is being returned 
> by the API call.
> Some of those information may not be utilized and hence an option can be 
> provided to filter the properties.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-20243) Include option to filter out properties from APi that returns ambari.properties file

[Anita Gnanamalar Jebaraj (JIRA)]

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

Anita Gnanamalar Jebaraj updated AMBARI-20243:
--
Attachment: AMBARI-20243-Mar1.patch

> Include option to filter out properties from APi that returns 
> ambari.properties file
> 
>
> Key: AMBARI-20243
> URL: https://issues.apache.org/jira/browse/AMBARI-20243
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-sever
>Affects Versions: trunk
>Reporter: Anita Gnanamalar Jebaraj
>Assignee: Anita Gnanamalar Jebaraj
> Fix For: trunk
>
> Attachments: AMBARI-20243-Mar1.patch, AMBARI-20243.patch
>
>
> Currently all the details from the ambari.properties file is being returned 
> by the API call.
> Some of those information may not be utilized and hence an option can be 
> provided to filter the properties.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-20243) Include option to filter out properties from APi that returns ambari.properties file

[Anita Gnanamalar Jebaraj (JIRA)]

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

Anita Gnanamalar Jebaraj updated AMBARI-20243:
--
Attachment: (was: AMBARI-20243-Mar1.patch)

> Include option to filter out properties from APi that returns 
> ambari.properties file
> 
>
> Key: AMBARI-20243
> URL: https://issues.apache.org/jira/browse/AMBARI-20243
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-sever
>Affects Versions: trunk
>Reporter: Anita Gnanamalar Jebaraj
>Assignee: Anita Gnanamalar Jebaraj
> Fix For: trunk
>
> Attachments: AMBARI-20243-Mar1.patch, AMBARI-20243.patch
>
>
> Currently all the details from the ambari.properties file is being returned 
> by the API call.
> Some of those information may not be utilized and hence an option can be 
> provided to filter the properties.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-20260) Misc errors in Ambari Server log that need to be cleaned up

[Hudson (JIRA)]

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

Hudson commented on AMBARI-20260:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6908 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6908/])
AMBARI-20260: Misc errors in Ambari Server log that need to be cleaned 
(jluniya: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=54374e9781e3d8cda52f36ecf328546f9fc9c69d])
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/events/listeners/upgrade/StackVersionListener.java


> Misc errors in Ambari Server log that need to be cleaned up
> ---
>
> Key: AMBARI-20260
> URL: https://issues.apache.org/jira/browse/AMBARI-20260
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
>Priority: Minor
> Fix For: 3.0.0
>
> Attachments: AMBARI-20260.patch
>
>
> Misc ERRORs in Ambari Server log:
> {noformat}
> 27 Feb 2017 21:06:07,574 ERROR [ambari-heartbeat-processor-0] 
> StackVersionListener:128 - ServiceComponent DRUID_BROKER doesn't advertise 
> version, however ServiceHostComponent DRUID_BROKER on host 
> alejandro-3.c.pramod-thangali.internal advertised version as 2.6.0.0-559. 
> Skipping version update
> 27 Feb 2017 21:06:09,568 ERROR [ambari-heartbeat-processor-0] 
> StackVersionListener:128 - ServiceComponent DRUID_COORDINATOR doesn't 
> advertise version, however ServiceHostComponent DRUID_COORDINATOR on host 
> alejandro-3.c.pramod-thangali.internal advertised version as 2.6.0.0-559. 
> Skipping version update
> 27 Feb 2017 21:06:10,570 ERROR [ambari-heartbeat-processor-0] 
> StackVersionListener:128 - ServiceComponent DRUID_HISTORICAL doesn't 
> advertise version, however ServiceHostComponent DRUID_HISTORICAL on host 
> alejandro-3.c.pramod-thangali.internal advertised version as 2.6.0.0-559. 
> Skipping version update
> 27 Feb 2017 21:06:11,580 ERROR [ambari-heartbeat-processor-0] 
> StackVersionListener:128 - ServiceComponent DRUID_MIDDLEMANAGER doesn't 
> advertise version, however ServiceHostComponent DRUID_MIDDLEMANAGER on host 
> alejandro-3.c.pramod-thangali.internal advertised version as 2.6.0.0-559. 
> Skipping version update
> 27 Feb 2017 21:06:13,570 ERROR [ambari-heartbeat-processor-0] 
> StackVersionListener:128 - ServiceComponent DRUID_OVERLORD doesn't advertise 
> version, however ServiceHostComponent DRUID_OVERLORD on host 
> alejandro-3.c.pramod-thangali.internal advertised version as 2.6.0.0-559. 
> Skipping version update
> 27 Feb 2017 21:06:14,611 ERROR [ambari-heartbeat-processor-0] 
> StackVersionListener:128 - ServiceComponent DRUID_ROUTER doesn't advertise 
> version, however ServiceHostComponent DRUID_ROUTER on host 
> alejandro-3.c.pramod-thangali.internal advertised version as 2.6.0.0-559. 
> Skipping version update
> 27 Feb 2017 21:06:15,589 ERROR [ambari-heartbeat-processor-0] 
> StackVersionListener:128 - ServiceComponent DRUID_SUPERSET doesn't advertise 
> version, however ServiceHostComponent DRUID_SUPERSET on host 
> alejandro-3.c.pramod-thangali.internal advertised version as 2.6.0.0-559. 
> Skipping version update
> ERROR [ambari-client-thread-33] ClusterImpl:2882 - No service found for 
> config types '[cluster-env]', service config version not created
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-20259) Superset not able to start on Ubuntu if ASCII encoding is set as default encoding

[Swapan Shridhar (JIRA)]

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

Swapan Shridhar updated AMBARI-20259:
-
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Superset not able to start on Ubuntu if ASCII encoding is set as default 
> encoding
> -
>
> Key: AMBARI-20259
> URL: https://issues.apache.org/jira/browse/AMBARI-20259
> Project: Ambari
>  Issue Type: Bug
>Reporter: Nishant Bangarwa
>Assignee: Nishant Bangarwa
> Fix For: trunk, 2.5.0
>
> Attachments: ambari-20259.patch
>
>
> RuntimeError: Click will abort further execution because Python 3 was 
> configured to use ASCII as encoding for the environment.  Consult 
> http://click.pocoo.org/python3/for mitigation steps.
> This system supports the C.UTF-8 locale which is recommended.
> You might be able to resolve your issue by exporting the
> following environment variables:
> export LC_ALL=C.UTF-8
> export LANG=C.UTF-8



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-20259) Superset not able to start on Ubuntu if ASCII encoding is set as default encoding

[Swapan Shridhar (JIRA)]

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

Swapan Shridhar commented on AMBARI-20259:
--

commit 

trunk:

{code}
commit 2ceeae8503a6e051f9e7e69801ad4bd9d229ea78
Author: Swapan Shridhar 
Date:   Wed Mar 1 15:07:38 2017 -0800

AMBARI-20259. Superset not able to start on Ubuntu if ASCII encoding is set 
as default encoding. (Nishant Bangarwa via Swapan Shridhar)
{code}



branch-2.5:

{code}
commit 9edf3c9371132c5733155ca7b38616f5ae70ded2
Author: Swapan Shridhar 
Date:   Wed Mar 1 15:07:38 2017 -0800

AMBARI-20259. Superset not able to start on Ubuntu if ASCII encoding is set 
as default encoding. (Nishant Bangarwa via Swapan Shridhar)
{code}

> Superset not able to start on Ubuntu if ASCII encoding is set as default 
> encoding
> -
>
> Key: AMBARI-20259
> URL: https://issues.apache.org/jira/browse/AMBARI-20259
> Project: Ambari
>  Issue Type: Bug
>Reporter: Nishant Bangarwa
>Assignee: Nishant Bangarwa
> Fix For: trunk, 2.5.0
>
> Attachments: ambari-20259.patch
>
>
> RuntimeError: Click will abort further execution because Python 3 was 
> configured to use ASCII as encoding for the environment.  Consult 
> http://click.pocoo.org/python3/for mitigation steps.
> This system supports the C.UTF-8 locale which is recommended.
> You might be able to resolve your issue by exporting the
> following environment variables:
> export LC_ALL=C.UTF-8
> export LANG=C.UTF-8



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-19429) Create an ODPi stack definition

[Jayush Luniya (JIRA)]

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

Jayush Luniya commented on AMBARI-19429:


[~rshaposhnik]
# Why are the ODPi service definitions not using common-services (ex: HIVE)? 
# Has anyone tested ODPi stack with latest Ambari? 
# Why not put ODPi as a management pack?

{code}
ls 
/Users/jluniya/trunk/ambari/ambari-server/src/main/resources/stacks/ODPi/2.0/services/HIVE/package/scripts
__init__.py hive_interactive.py 
hive_service_interactive.py params_linux.py 
webhcat.py
hcat.py hive_metastore.py   
mysql_server.py params_windows.py   
webhcat_server.py
hcat_client.py  hive_server.py  
mysql_service.pyservice_check.py
webhcat_service.py
hcat_service_check.py   hive_server_interactive.py  
mysql_users.py  setup_ranger_hive.py
webhcat_service_check.py
hive.py hive_server_upgrade.py  
mysql_utils.py  setup_ranger_hive_interactive.py
hive_client.py  hive_service.py 
params.py   status_params.py
{code}

> Create an ODPi stack definition
> ---
>
> Key: AMBARI-19429
> URL: https://issues.apache.org/jira/browse/AMBARI-19429
> Project: Ambari
>  Issue Type: Improvement
>  Components: stacks
>Affects Versions: 2.4.2
>Reporter: Roman Shaposhnik
>Assignee: Roman Shaposhnik
> Fix For: trunk
>
> Attachments: AMBARI-19429.patch2.gz, AMBARI-19429.patch.gz
>
>
> ODPi is a nonprofit organization committed to simplification & 
> standardization of the big data ecosystem with common reference 
> specifications and test suites. As part of its mission, ODPi has been 
> developing a series of specifications for how to integrate upstream Apache 
> projects into the coherent platform. Part of this standardization effort is 
> maintenance of the ODPi core stack definition which today includes:
>* Apache Zookeeper
>* Apache Hadoop
>* Apache Hive
> and has been maintained as a custom stack on ODPi side:
> 
> https://github.com/odpi/bigtop/tree/odpi-master/bigtop-packages/src/common/ambari/ODPi/1.0
> In conjunction with merge effort for Apache Bigtop BIGTOP-2666 I'd like to 
> propose that instead of migrating the stack definition to Bigtop, we should 
> actually migrate it to Ambari.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-20260) Misc errors in Ambari Server log that need to be cleaned up

[Jayush Luniya (JIRA)]

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

Jayush Luniya updated AMBARI-20260:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Misc errors in Ambari Server log that need to be cleaned up
> ---
>
> Key: AMBARI-20260
> URL: https://issues.apache.org/jira/browse/AMBARI-20260
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
>Priority: Minor
> Fix For: 3.0.0
>
> Attachments: AMBARI-20260.patch
>
>
> Misc ERRORs in Ambari Server log:
> {noformat}
> 27 Feb 2017 21:06:07,574 ERROR [ambari-heartbeat-processor-0] 
> StackVersionListener:128 - ServiceComponent DRUID_BROKER doesn't advertise 
> version, however ServiceHostComponent DRUID_BROKER on host 
> alejandro-3.c.pramod-thangali.internal advertised version as 2.6.0.0-559. 
> Skipping version update
> 27 Feb 2017 21:06:09,568 ERROR [ambari-heartbeat-processor-0] 
> StackVersionListener:128 - ServiceComponent DRUID_COORDINATOR doesn't 
> advertise version, however ServiceHostComponent DRUID_COORDINATOR on host 
> alejandro-3.c.pramod-thangali.internal advertised version as 2.6.0.0-559. 
> Skipping version update
> 27 Feb 2017 21:06:10,570 ERROR [ambari-heartbeat-processor-0] 
> StackVersionListener:128 - ServiceComponent DRUID_HISTORICAL doesn't 
> advertise version, however ServiceHostComponent DRUID_HISTORICAL on host 
> alejandro-3.c.pramod-thangali.internal advertised version as 2.6.0.0-559. 
> Skipping version update
> 27 Feb 2017 21:06:11,580 ERROR [ambari-heartbeat-processor-0] 
> StackVersionListener:128 - ServiceComponent DRUID_MIDDLEMANAGER doesn't 
> advertise version, however ServiceHostComponent DRUID_MIDDLEMANAGER on host 
> alejandro-3.c.pramod-thangali.internal advertised version as 2.6.0.0-559. 
> Skipping version update
> 27 Feb 2017 21:06:13,570 ERROR [ambari-heartbeat-processor-0] 
> StackVersionListener:128 - ServiceComponent DRUID_OVERLORD doesn't advertise 
> version, however ServiceHostComponent DRUID_OVERLORD on host 
> alejandro-3.c.pramod-thangali.internal advertised version as 2.6.0.0-559. 
> Skipping version update
> 27 Feb 2017 21:06:14,611 ERROR [ambari-heartbeat-processor-0] 
> StackVersionListener:128 - ServiceComponent DRUID_ROUTER doesn't advertise 
> version, however ServiceHostComponent DRUID_ROUTER on host 
> alejandro-3.c.pramod-thangali.internal advertised version as 2.6.0.0-559. 
> Skipping version update
> 27 Feb 2017 21:06:15,589 ERROR [ambari-heartbeat-processor-0] 
> StackVersionListener:128 - ServiceComponent DRUID_SUPERSET doesn't advertise 
> version, however ServiceHostComponent DRUID_SUPERSET on host 
> alejandro-3.c.pramod-thangali.internal advertised version as 2.6.0.0-559. 
> Skipping version update
> ERROR [ambari-client-thread-33] ClusterImpl:2882 - No service found for 
> config types '[cluster-env]', service config version not created
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-20260) Misc errors in Ambari Server log that need to be cleaned up

[Jayush Luniya (JIRA)]

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

Jayush Luniya updated AMBARI-20260:
---
Affects Version/s: 2.5.0

> Misc errors in Ambari Server log that need to be cleaned up
> ---
>
> Key: AMBARI-20260
> URL: https://issues.apache.org/jira/browse/AMBARI-20260
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
>Priority: Minor
> Fix For: 3.0.0
>
> Attachments: AMBARI-20260.patch
>
>
> Misc ERRORs in Ambari Server log:
> {noformat}
> 27 Feb 2017 21:06:07,574 ERROR [ambari-heartbeat-processor-0] 
> StackVersionListener:128 - ServiceComponent DRUID_BROKER doesn't advertise 
> version, however ServiceHostComponent DRUID_BROKER on host 
> alejandro-3.c.pramod-thangali.internal advertised version as 2.6.0.0-559. 
> Skipping version update
> 27 Feb 2017 21:06:09,568 ERROR [ambari-heartbeat-processor-0] 
> StackVersionListener:128 - ServiceComponent DRUID_COORDINATOR doesn't 
> advertise version, however ServiceHostComponent DRUID_COORDINATOR on host 
> alejandro-3.c.pramod-thangali.internal advertised version as 2.6.0.0-559. 
> Skipping version update
> 27 Feb 2017 21:06:10,570 ERROR [ambari-heartbeat-processor-0] 
> StackVersionListener:128 - ServiceComponent DRUID_HISTORICAL doesn't 
> advertise version, however ServiceHostComponent DRUID_HISTORICAL on host 
> alejandro-3.c.pramod-thangali.internal advertised version as 2.6.0.0-559. 
> Skipping version update
> 27 Feb 2017 21:06:11,580 ERROR [ambari-heartbeat-processor-0] 
> StackVersionListener:128 - ServiceComponent DRUID_MIDDLEMANAGER doesn't 
> advertise version, however ServiceHostComponent DRUID_MIDDLEMANAGER on host 
> alejandro-3.c.pramod-thangali.internal advertised version as 2.6.0.0-559. 
> Skipping version update
> 27 Feb 2017 21:06:13,570 ERROR [ambari-heartbeat-processor-0] 
> StackVersionListener:128 - ServiceComponent DRUID_OVERLORD doesn't advertise 
> version, however ServiceHostComponent DRUID_OVERLORD on host 
> alejandro-3.c.pramod-thangali.internal advertised version as 2.6.0.0-559. 
> Skipping version update
> 27 Feb 2017 21:06:14,611 ERROR [ambari-heartbeat-processor-0] 
> StackVersionListener:128 - ServiceComponent DRUID_ROUTER doesn't advertise 
> version, however ServiceHostComponent DRUID_ROUTER on host 
> alejandro-3.c.pramod-thangali.internal advertised version as 2.6.0.0-559. 
> Skipping version update
> 27 Feb 2017 21:06:15,589 ERROR [ambari-heartbeat-processor-0] 
> StackVersionListener:128 - ServiceComponent DRUID_SUPERSET doesn't advertise 
> version, however ServiceHostComponent DRUID_SUPERSET on host 
> alejandro-3.c.pramod-thangali.internal advertised version as 2.6.0.0-559. 
> Skipping version update
> ERROR [ambari-client-thread-33] ClusterImpl:2882 - No service found for 
> config types '[cluster-env]', service config version not created
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-20260) Misc errors in Ambari Server log that need to be cleaned up

[Jayush Luniya (JIRA)]

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

Jayush Luniya updated AMBARI-20260:
---
Fix Version/s: 3.0.0

> Misc errors in Ambari Server log that need to be cleaned up
> ---
>
> Key: AMBARI-20260
> URL: https://issues.apache.org/jira/browse/AMBARI-20260
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
>Priority: Minor
> Fix For: 3.0.0
>
> Attachments: AMBARI-20260.patch
>
>
> Misc ERRORs in Ambari Server log:
> {noformat}
> 27 Feb 2017 21:06:07,574 ERROR [ambari-heartbeat-processor-0] 
> StackVersionListener:128 - ServiceComponent DRUID_BROKER doesn't advertise 
> version, however ServiceHostComponent DRUID_BROKER on host 
> alejandro-3.c.pramod-thangali.internal advertised version as 2.6.0.0-559. 
> Skipping version update
> 27 Feb 2017 21:06:09,568 ERROR [ambari-heartbeat-processor-0] 
> StackVersionListener:128 - ServiceComponent DRUID_COORDINATOR doesn't 
> advertise version, however ServiceHostComponent DRUID_COORDINATOR on host 
> alejandro-3.c.pramod-thangali.internal advertised version as 2.6.0.0-559. 
> Skipping version update
> 27 Feb 2017 21:06:10,570 ERROR [ambari-heartbeat-processor-0] 
> StackVersionListener:128 - ServiceComponent DRUID_HISTORICAL doesn't 
> advertise version, however ServiceHostComponent DRUID_HISTORICAL on host 
> alejandro-3.c.pramod-thangali.internal advertised version as 2.6.0.0-559. 
> Skipping version update
> 27 Feb 2017 21:06:11,580 ERROR [ambari-heartbeat-processor-0] 
> StackVersionListener:128 - ServiceComponent DRUID_MIDDLEMANAGER doesn't 
> advertise version, however ServiceHostComponent DRUID_MIDDLEMANAGER on host 
> alejandro-3.c.pramod-thangali.internal advertised version as 2.6.0.0-559. 
> Skipping version update
> 27 Feb 2017 21:06:13,570 ERROR [ambari-heartbeat-processor-0] 
> StackVersionListener:128 - ServiceComponent DRUID_OVERLORD doesn't advertise 
> version, however ServiceHostComponent DRUID_OVERLORD on host 
> alejandro-3.c.pramod-thangali.internal advertised version as 2.6.0.0-559. 
> Skipping version update
> 27 Feb 2017 21:06:14,611 ERROR [ambari-heartbeat-processor-0] 
> StackVersionListener:128 - ServiceComponent DRUID_ROUTER doesn't advertise 
> version, however ServiceHostComponent DRUID_ROUTER on host 
> alejandro-3.c.pramod-thangali.internal advertised version as 2.6.0.0-559. 
> Skipping version update
> 27 Feb 2017 21:06:15,589 ERROR [ambari-heartbeat-processor-0] 
> StackVersionListener:128 - ServiceComponent DRUID_SUPERSET doesn't advertise 
> version, however ServiceHostComponent DRUID_SUPERSET on host 
> alejandro-3.c.pramod-thangali.internal advertised version as 2.6.0.0-559. 
> Skipping version update
> ERROR [ambari-client-thread-33] ClusterImpl:2882 - No service found for 
> config types '[cluster-env]', service config version not created
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-20260) Misc errors in Ambari Server log that need to be cleaned up

[Jayush Luniya (JIRA)]

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

Jayush Luniya commented on AMBARI-20260:


No tests required. Committed to trunk

commit 54374e9781e3d8cda52f36ecf328546f9fc9c69d
Author: Jayush Luniya 
Date:   Wed Mar 1 14:39:04 2017 -0800

AMBARI-20260: Misc errors in Ambari Server log that need to be cleaned up 
(jluniya)

> Misc errors in Ambari Server log that need to be cleaned up
> ---
>
> Key: AMBARI-20260
> URL: https://issues.apache.org/jira/browse/AMBARI-20260
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
>Priority: Minor
> Fix For: 3.0.0
>
> Attachments: AMBARI-20260.patch
>
>
> Misc ERRORs in Ambari Server log:
> {noformat}
> 27 Feb 2017 21:06:07,574 ERROR [ambari-heartbeat-processor-0] 
> StackVersionListener:128 - ServiceComponent DRUID_BROKER doesn't advertise 
> version, however ServiceHostComponent DRUID_BROKER on host 
> alejandro-3.c.pramod-thangali.internal advertised version as 2.6.0.0-559. 
> Skipping version update
> 27 Feb 2017 21:06:09,568 ERROR [ambari-heartbeat-processor-0] 
> StackVersionListener:128 - ServiceComponent DRUID_COORDINATOR doesn't 
> advertise version, however ServiceHostComponent DRUID_COORDINATOR on host 
> alejandro-3.c.pramod-thangali.internal advertised version as 2.6.0.0-559. 
> Skipping version update
> 27 Feb 2017 21:06:10,570 ERROR [ambari-heartbeat-processor-0] 
> StackVersionListener:128 - ServiceComponent DRUID_HISTORICAL doesn't 
> advertise version, however ServiceHostComponent DRUID_HISTORICAL on host 
> alejandro-3.c.pramod-thangali.internal advertised version as 2.6.0.0-559. 
> Skipping version update
> 27 Feb 2017 21:06:11,580 ERROR [ambari-heartbeat-processor-0] 
> StackVersionListener:128 - ServiceComponent DRUID_MIDDLEMANAGER doesn't 
> advertise version, however ServiceHostComponent DRUID_MIDDLEMANAGER on host 
> alejandro-3.c.pramod-thangali.internal advertised version as 2.6.0.0-559. 
> Skipping version update
> 27 Feb 2017 21:06:13,570 ERROR [ambari-heartbeat-processor-0] 
> StackVersionListener:128 - ServiceComponent DRUID_OVERLORD doesn't advertise 
> version, however ServiceHostComponent DRUID_OVERLORD on host 
> alejandro-3.c.pramod-thangali.internal advertised version as 2.6.0.0-559. 
> Skipping version update
> 27 Feb 2017 21:06:14,611 ERROR [ambari-heartbeat-processor-0] 
> StackVersionListener:128 - ServiceComponent DRUID_ROUTER doesn't advertise 
> version, however ServiceHostComponent DRUID_ROUTER on host 
> alejandro-3.c.pramod-thangali.internal advertised version as 2.6.0.0-559. 
> Skipping version update
> 27 Feb 2017 21:06:15,589 ERROR [ambari-heartbeat-processor-0] 
> StackVersionListener:128 - ServiceComponent DRUID_SUPERSET doesn't advertise 
> version, however ServiceHostComponent DRUID_SUPERSET on host 
> alejandro-3.c.pramod-thangali.internal advertised version as 2.6.0.0-559. 
> Skipping version update
> ERROR [ambari-client-thread-33] ClusterImpl:2882 - No service found for 
> config types '[cluster-env]', service config version not created
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-19429) Create an ODPi stack definition

[Roman Shaposhnik (JIRA)]

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

Roman Shaposhnik commented on AMBARI-19429:
---

[~Tim Thorpe] [~u39kun] the patch applies to branch-2.5 as well. Would be 
really nice to see it there.

> Create an ODPi stack definition
> ---
>
> Key: AMBARI-19429
> URL: https://issues.apache.org/jira/browse/AMBARI-19429
> Project: Ambari
>  Issue Type: Improvement
>  Components: stacks
>Affects Versions: 2.4.2
>Reporter: Roman Shaposhnik
>Assignee: Roman Shaposhnik
> Fix For: trunk
>
> Attachments: AMBARI-19429.patch2.gz, AMBARI-19429.patch.gz
>
>
> ODPi is a nonprofit organization committed to simplification & 
> standardization of the big data ecosystem with common reference 
> specifications and test suites. As part of its mission, ODPi has been 
> developing a series of specifications for how to integrate upstream Apache 
> projects into the coherent platform. Part of this standardization effort is 
> maintenance of the ODPi core stack definition which today includes:
>* Apache Zookeeper
>* Apache Hadoop
>* Apache Hive
> and has been maintained as a custom stack on ODPi side:
> 
> https://github.com/odpi/bigtop/tree/odpi-master/bigtop-packages/src/common/ambari/ODPi/1.0
> In conjunction with merge effort for Apache Bigtop BIGTOP-2666 I'd like to 
> propose that instead of migrating the stack definition to Bigtop, we should 
> actually migrate it to Ambari.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-20261) Unexpected popup after disable kerberos "You are in the process of disabling security on your cluster"

[Hudson (JIRA)]

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

Hudson commented on AMBARI-20261:
-

SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1148 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/1148/])
AMBARI-20261 Unexpected popup after disable kerberos "You are in the (bdenys: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=b7825488068ae0e634501053d999b6f8b1e0c091])
* (edit) ambari-web/app/routes/main.js


> Unexpected popup after disable kerberos "You are in the process of disabling 
> security on your cluster"
> --
>
> Key: AMBARI-20261
> URL: https://issues.apache.org/jira/browse/AMBARI-20261
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Denys Buzhor
>Assignee: Denys Buzhor
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20261.patch, kerberos-confirmation-popup.png
>
>
> STR:
> * Disable Security
> * Click on "Complete" button
> Confirmation popup is shown instead of closing *Disable Security* popup.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-19429) Create an ODPi stack definition

[Tim Thorpe (JIRA)]

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

Tim Thorpe commented on AMBARI-19429:
-

Is it too late to push this into 2.5 as well?  Not sure how close we are to a 
2.5 release but this shouldn't have any negative impacts.

> Create an ODPi stack definition
> ---
>
> Key: AMBARI-19429
> URL: https://issues.apache.org/jira/browse/AMBARI-19429
> Project: Ambari
>  Issue Type: Improvement
>  Components: stacks
>Affects Versions: 2.4.2
>Reporter: Roman Shaposhnik
>Assignee: Roman Shaposhnik
> Fix For: trunk
>
> Attachments: AMBARI-19429.patch2.gz, AMBARI-19429.patch.gz
>
>
> ODPi is a nonprofit organization committed to simplification & 
> standardization of the big data ecosystem with common reference 
> specifications and test suites. As part of its mission, ODPi has been 
> developing a series of specifications for how to integrate upstream Apache 
> projects into the coherent platform. Part of this standardization effort is 
> maintenance of the ODPi core stack definition which today includes:
>* Apache Zookeeper
>* Apache Hadoop
>* Apache Hive
> and has been maintained as a custom stack on ODPi side:
> 
> https://github.com/odpi/bigtop/tree/odpi-master/bigtop-packages/src/common/ambari/ODPi/1.0
> In conjunction with merge effort for Apache Bigtop BIGTOP-2666 I'd like to 
> propose that instead of migrating the stack definition to Bigtop, we should 
> actually migrate it to Ambari.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-19429) Create an ODPi stack definition

[Yusaku Sako (JIRA)]

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

Yusaku Sako updated AMBARI-19429:
-
Fix Version/s: trunk

> Create an ODPi stack definition
> ---
>
> Key: AMBARI-19429
> URL: https://issues.apache.org/jira/browse/AMBARI-19429
> Project: Ambari
>  Issue Type: Improvement
>  Components: stacks
>Affects Versions: 2.4.2
>Reporter: Roman Shaposhnik
>Assignee: Roman Shaposhnik
> Fix For: trunk
>
> Attachments: AMBARI-19429.patch2.gz, AMBARI-19429.patch.gz
>
>
> ODPi is a nonprofit organization committed to simplification & 
> standardization of the big data ecosystem with common reference 
> specifications and test suites. As part of its mission, ODPi has been 
> developing a series of specifications for how to integrate upstream Apache 
> projects into the coherent platform. Part of this standardization effort is 
> maintenance of the ODPi core stack definition which today includes:
>* Apache Zookeeper
>* Apache Hadoop
>* Apache Hive
> and has been maintained as a custom stack on ODPi side:
> 
> https://github.com/odpi/bigtop/tree/odpi-master/bigtop-packages/src/common/ambari/ODPi/1.0
> In conjunction with merge effort for Apache Bigtop BIGTOP-2666 I'd like to 
> propose that instead of migrating the stack definition to Bigtop, we should 
> actually migrate it to Ambari.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-20261) Unexpected popup after disable kerberos "You are in the process of disabling security on your cluster"

[Hudson (JIRA)]

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

Hudson commented on AMBARI-20261:
-

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6907 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6907/])
AMBARI-20261 Unexpected popup after disable kerberos "You are in the (bdenys: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=a17e6d4405d8405bc602cdfa9d3a4b2e6da86a58])
* (edit) ambari-web/app/routes/main.js


> Unexpected popup after disable kerberos "You are in the process of disabling 
> security on your cluster"
> --
>
> Key: AMBARI-20261
> URL: https://issues.apache.org/jira/browse/AMBARI-20261
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Denys Buzhor
>Assignee: Denys Buzhor
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20261.patch, kerberos-confirmation-popup.png
>
>
> STR:
> * Disable Security
> * Click on "Complete" button
> Confirmation popup is shown instead of closing *Disable Security* popup.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-20262) Startup Annotation Scanning Takes Too Long

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-20262:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12855456/AMBARI-20262.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:red}-1 javac{color:red}.  The patch appears to cause the build to 
fail.

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

This message is automatically generated.

> Startup Annotation Scanning Takes Too Long
> --
>
> Key: AMBARI-20262
> URL: https://issues.apache.org/jira/browse/AMBARI-20262
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20262.patch
>
>
> Currently, Ambari uses Spring's 
> {{ClassPathScanningCandidateComponentProvider}} along with an 
> {{AnnotationTypeFilter}} to find classes annotated in our classpath:
> {code}
>   ClassPathScanningCandidateComponentProvider scanner =
>   new ClassPathScanningCandidateComponentProvider(false);
>   // match only singletons that are eager listeners
>   for (Class cls : classes) {
> scanner.addIncludeFilter(new AnnotationTypeFilter(cls));
>   }
>   beanDefinitions = scanner.findCandidateComponents(AMBARI_PACKAGE);
> {code}
> This takes roughly 19 seconds on normal deployments. We can reduce this time 
> to roughly 8 seconds by switching over to Google's {{ClassPath}} via our 
> internal {{ClasspathScannerUtils}}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-20220) Parameterize the Startup Web Server Timeout Default Value

[Hudson (JIRA)]

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

Hudson commented on AMBARI-20220:
-

SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1147 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/1147/])
AMBARI-20220 - Parameterize the Startup Web Server Timeout Default Value 
(jhurley: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=6b93dc18270a1cd1d7ef23335e62870d09e671a0])
* (edit) ambari-server/src/test/python/TestAmbariServer.py
* (edit) ambari-server/src/main/python/ambari_server_main.py
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/configuration/Configuration.java
* (edit) ambari-server/src/main/python/ambari_server/serverConfiguration.py
* (edit) ambari-server/docs/configuration/index.md


> Parameterize the Startup Web Server Timeout Default Value
> -
>
> Key: AMBARI-20220
> URL: https://issues.apache.org/jira/browse/AMBARI-20220
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20220.patch
>
>
> The {{ambari-server start}} and {{ambari-server restart}} commands are 
> currently hard coded to wait a maximum of 50 seconds for the Jetty server to 
> bind to port 8080 (or whatever the configured port is).
> Under normal circumstances, this value should be fine. However, since Jetty 
> loads classes from views, the more views which are installed increases the 
> total load time before Jetty binds to the server port.
> {code}
> ambari-server restart --debug
> Using python  /usr/bin/python
> Restarting ambari-server
> Waiting for server stop...
> 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 found warnings. See 
> /var/log/ambari-server/ambari-server-check-database.log for more details.
> ERROR: Exiting with exit code 1.
> REASON: Server not yet listening on http port 8080 after 50 seconds. Exiting.
> {code}
> Although this a general problem with the architecture of Views, it's still 
> valuable to have this startup property configurable.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-20105) When spark thrift server and hive server2 located on different hosts, with kerberos spark thrift server keeps failing

[Shi Wang (JIRA)]

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

Shi Wang updated AMBARI-20105:
--
Description: Spark thrift server is run as hive user, when kerberos is 
enabled, hive user will need to be able to impersonate any request coming from 
hosts where spark thrift servers are installed. Need to change 
hadoop.proxyuser.hive.hosts to include spark thrift server hosts.

> When spark thrift server and hive server2 located on different hosts, with 
> kerberos spark thrift server keeps failing
> -
>
> Key: AMBARI-20105
> URL: https://issues.apache.org/jira/browse/AMBARI-20105
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: trunk, 2.5.0
>Reporter: Shi Wang
>Assignee: Shi Wang
>
> Spark thrift server is run as hive user, when kerberos is enabled, hive user 
> will need to be able to impersonate any request coming from hosts where spark 
> thrift servers are installed. Need to change hadoop.proxyuser.hive.hosts to 
> include spark thrift server hosts.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-20261) Unexpected popup after disable kerberos "You are in the process of disabling security on your cluster"

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-20261:


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

This message is automatically generated.

> Unexpected popup after disable kerberos "You are in the process of disabling 
> security on your cluster"
> --
>
> Key: AMBARI-20261
> URL: https://issues.apache.org/jira/browse/AMBARI-20261
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Denys Buzhor
>Assignee: Denys Buzhor
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20261.patch, kerberos-confirmation-popup.png
>
>
> STR:
> * Disable Security
> * Click on "Complete" button
> Confirmation popup is shown instead of closing *Disable Security* popup.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-20261) Unexpected popup after disable kerberos "You are in the process of disabling security on your cluster"

[Denys Buzhor (JIRA)]

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

Denys Buzhor updated AMBARI-20261:
--
Resolution: Fixed
Status: Resolved  (was: Patch Available)

Committed to trunk and branch-2.5

> Unexpected popup after disable kerberos "You are in the process of disabling 
> security on your cluster"
> --
>
> Key: AMBARI-20261
> URL: https://issues.apache.org/jira/browse/AMBARI-20261
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Denys Buzhor
>Assignee: Denys Buzhor
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20261.patch, kerberos-confirmation-popup.png
>
>
> STR:
> * Disable Security
> * Click on "Complete" button
> Confirmation popup is shown instead of closing *Disable Security* popup.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-20220) Parameterize the Startup Web Server Timeout Default Value

[Jonathan Hurley (JIRA)]

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

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

> Parameterize the Startup Web Server Timeout Default Value
> -
>
> Key: AMBARI-20220
> URL: https://issues.apache.org/jira/browse/AMBARI-20220
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20220.patch
>
>
> The {{ambari-server start}} and {{ambari-server restart}} commands are 
> currently hard coded to wait a maximum of 50 seconds for the Jetty server to 
> bind to port 8080 (or whatever the configured port is).
> Under normal circumstances, this value should be fine. However, since Jetty 
> loads classes from views, the more views which are installed increases the 
> total load time before Jetty binds to the server port.
> {code}
> ambari-server restart --debug
> Using python  /usr/bin/python
> Restarting ambari-server
> Waiting for server stop...
> 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 found warnings. See 
> /var/log/ambari-server/ambari-server-check-database.log for more details.
> ERROR: Exiting with exit code 1.
> REASON: Server not yet listening on http port 8080 after 50 seconds. Exiting.
> {code}
> Although this a general problem with the architecture of Views, it's still 
> valuable to have this startup property configurable.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-20225) Take care of hive-interactive-site's 'hive.tez.container.size' config during HDP upgrade from 2.5 to 2.6 and update default value for tez-interactive-site's config 't

[Hudson (JIRA)]

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

Hudson commented on AMBARI-20225:
-

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6906 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6906/])
AMBARI-20225. Take care of hive-interactive-site's (sshridhar: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=baefbcca0b60caac801f3addf0d015df23a5e96d])
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.5/services/HIVE/configuration/hive-interactive-site.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.5/services/HIVE/configuration/tez-interactive-site.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.5/services/stack_advisor.py
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/config-upgrade.xml
* (edit) 
ambari-server/src/main/resources/common-services/YARN/3.0.0.3.0/service_advisor.py
* (edit) ambari-server/src/test/python/stacks/2.5/common/test_stack_advisor.py
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/nonrolling-upgrade-2.6.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/upgrade-2.6.xml


> Take care of hive-interactive-site's 'hive.tez.container.size' config during 
> HDP upgrade from 2.5 to 2.6 and update default value for 
> tez-interactive-site's config 'tez.am.resource.memory.mb'.
> 
>
> Key: AMBARI-20225
> URL: https://issues.apache.org/jira/browse/AMBARI-20225
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk, 2.5.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-20225.patch
>
>
> *Background :*
> We are dealing with 2 specific configs here. 
> *(1).* 'tez.am.resource.memory.mb' for tez-interactive-site and 
> *(2).* 'hive.tez.container.size' for hive-interactive-site. 
> - 'tez.am.resource.memory.mb' already exists in tez-interactive-site from 
> Ambari-2.4 onwards and recently its default value had been changed to 
> 'SET_ON_FIRST_INVOCATION' in its hive-interacive-site.
> - 'hive.tez.container.size' was inherited and used from Hive1/hive-site in 
> Ambari 2.4. Starting from Ambari 2.5, it was added as a config explicitly in 
> hive-interactive-site with a default value of 'SET_ON_FIRST_INVOCATION'.
> The non-standard 'SET_ON_FIRST_INVOCATION' was introduced, so as to give a 
> hint in Stack Advisor (SA) call for the 1st time on Hive Server Interactive 
> ON (enable_hive_interactive config), so that config values for both can be 
> calculated and set for the 1st time. Subsequesnt calls in the lifecycle, will 
> just read the value set by SA or if later changed by user manually.
> *Problem :*
> 'SET_ON_FIRST_INVOCATION', being non-standard was breaking the code in 
> upgrade scenario. 
> *Fix:*
> Removing the use of 'SET_ON_FIRST_INVOCATION' and adding code for correct 
> behavior of configs during HDP upgrade.
>  
> *Possible scenarios:*
> *1. Ambari upgrade from 2.4 - > 2.5 having HDP 2.5. Implying 
> 2.5/stack_advisor.py code would have been updated with new LLAP GA logic.*
>- 'tez.am.resource.memory.mb' will already be there whether Hive Server 
> Interactive (HSI) is ON or OFF after Ambari upgrade. 
>   - If HSI if OFF before the upgrade was done, nothing to do over there.
>   - If HSI on ON before AMbari upgrade, or is made ON after Ambari 
> upgrade, SA logic has been updated to take of reading 
> 'hive.tez.container.size' from hive-site as it wont exist in 
> hive-interactive-site at this point. It will show up in hive-interative-site 
> aftre the HDP upgrade to 2.6
> *2. Ambari 2.4 having HDP 2.5 -> Upgrade to Ambari 2.5 -> Upgraded to HDP 2.6*
>- 'tez.am.resource.memory.mb' will already be there
>- As part of HDP 2.5 upgrade to HDP 2.6, 'hive.tez.container.size' would 
> have got added, having current value picked from 
> hive-site/hive.tez.container.size. SA code carries a calculation logic for 
> config 'hive.tez.container.size', which is bound to yield different value 
> compared to hive-site/'hive.tez.container.size'. The config's value will get 
> updated/caluclated (1). when HSI is made ON (meaning 
> 'enabled_hive_interactive' config detected as **True** in 
> changed-configurations).
>  
> *3. Ambari 2.5 with HDP 2.5 -> Upgraded to HDP 2.6*
>- Both 'hive.tez.container.size' and 'tez.am.resource.memory.mb' (alreday 
> present at HDP 2.5 in hive-interactive-site) will exist after the HDP upgrade.
> *Note* that a fresh value for 'hive.tez.container.size' and 
> 'tez.am.resource.memory.mb' is caluclated at 

[jira] [Commented] (AMBARI-20225) Take care of hive-interactive-site's 'hive.tez.container.size' config during HDP upgrade from 2.5 to 2.6 and update default value for tez-interactive-site's config 't

[Hudson (JIRA)]

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

Hudson commented on AMBARI-20225:
-

SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1146 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/1146/])
AMBARI-20225. Take care of hive-interactive-site's (sshridhar: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=ce1ed6e1aade5333c0ee26de469e8487061ccb8b])
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.5/services/HIVE/configuration/tez-interactive-site.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.5/services/HIVE/configuration/hive-interactive-site.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/upgrade-2.6.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/config-upgrade.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.5/services/stack_advisor.py
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/nonrolling-upgrade-2.6.xml
* (edit) ambari-server/src/test/python/stacks/2.5/common/test_stack_advisor.py


> Take care of hive-interactive-site's 'hive.tez.container.size' config during 
> HDP upgrade from 2.5 to 2.6 and update default value for 
> tez-interactive-site's config 'tez.am.resource.memory.mb'.
> 
>
> Key: AMBARI-20225
> URL: https://issues.apache.org/jira/browse/AMBARI-20225
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk, 2.5.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-20225.patch
>
>
> *Background :*
> We are dealing with 2 specific configs here. 
> *(1).* 'tez.am.resource.memory.mb' for tez-interactive-site and 
> *(2).* 'hive.tez.container.size' for hive-interactive-site. 
> - 'tez.am.resource.memory.mb' already exists in tez-interactive-site from 
> Ambari-2.4 onwards and recently its default value had been changed to 
> 'SET_ON_FIRST_INVOCATION' in its hive-interacive-site.
> - 'hive.tez.container.size' was inherited and used from Hive1/hive-site in 
> Ambari 2.4. Starting from Ambari 2.5, it was added as a config explicitly in 
> hive-interactive-site with a default value of 'SET_ON_FIRST_INVOCATION'.
> The non-standard 'SET_ON_FIRST_INVOCATION' was introduced, so as to give a 
> hint in Stack Advisor (SA) call for the 1st time on Hive Server Interactive 
> ON (enable_hive_interactive config), so that config values for both can be 
> calculated and set for the 1st time. Subsequesnt calls in the lifecycle, will 
> just read the value set by SA or if later changed by user manually.
> *Problem :*
> 'SET_ON_FIRST_INVOCATION', being non-standard was breaking the code in 
> upgrade scenario. 
> *Fix:*
> Removing the use of 'SET_ON_FIRST_INVOCATION' and adding code for correct 
> behavior of configs during HDP upgrade.
>  
> *Possible scenarios:*
> *1. Ambari upgrade from 2.4 - > 2.5 having HDP 2.5. Implying 
> 2.5/stack_advisor.py code would have been updated with new LLAP GA logic.*
>- 'tez.am.resource.memory.mb' will already be there whether Hive Server 
> Interactive (HSI) is ON or OFF after Ambari upgrade. 
>   - If HSI if OFF before the upgrade was done, nothing to do over there.
>   - If HSI on ON before AMbari upgrade, or is made ON after Ambari 
> upgrade, SA logic has been updated to take of reading 
> 'hive.tez.container.size' from hive-site as it wont exist in 
> hive-interactive-site at this point. It will show up in hive-interative-site 
> aftre the HDP upgrade to 2.6
> *2. Ambari 2.4 having HDP 2.5 -> Upgrade to Ambari 2.5 -> Upgraded to HDP 2.6*
>- 'tez.am.resource.memory.mb' will already be there
>- As part of HDP 2.5 upgrade to HDP 2.6, 'hive.tez.container.size' would 
> have got added, having current value picked from 
> hive-site/hive.tez.container.size. SA code carries a calculation logic for 
> config 'hive.tez.container.size', which is bound to yield different value 
> compared to hive-site/'hive.tez.container.size'. The config's value will get 
> updated/caluclated (1). when HSI is made ON (meaning 
> 'enabled_hive_interactive' config detected as **True** in 
> changed-configurations).
>  
> *3. Ambari 2.5 with HDP 2.5 -> Upgraded to HDP 2.6*
>- Both 'hive.tez.container.size' and 'tez.am.resource.memory.mb' (alreday 
> present at HDP 2.5 in hive-interactive-site) will exist after the HDP upgrade.
> *Note* that a fresh value for 'hive.tez.container.size' and 
> 'tez.am.resource.memory.mb' is caluclated at below conditions:
> (1). when HSI is made ON, meaning 'enabled_hive_interactive' config detected 
> 

[jira] [Created] (AMBARI-20263) Knox default topology config is wrong for Hbase service

[Sumit Gupta (JIRA)]

Sumit Gupta created AMBARI-20263:


 Summary: Knox default topology config is wrong for Hbase service
 Key: AMBARI-20263
 URL: https://issues.apache.org/jira/browse/AMBARI-20263
 Project: Ambari
  Issue Type: Bug
  Components: stacks
Affects Versions: 2.4.0
Reporter: Sumit Gupta


Under the "Configs" tab for Knox, the Advanced Topology section has an error 
for the  xml section for HBase. It looks like this:

{code}
  
WEBHBASE
http://{{hbase_master_host}}:{{hbase_master_port}}

{code}

Knox talks to the REST server so the host and port should match that. The 
hbase_master_host variable may work okay but certainly the port will be wrong.




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-8189) Ambari agent support for parallel task execution during deployment

[Dheeren Beborrtha (JIRA)]

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

Dheeren Beborrtha commented on AMBARI-8189:
---

[~ivanmi] I also see that this patch is already in Ambari 2.2.2.  I could set 
parallel_execution=1 in ambari. I am yet to see the test results. Can you 
please confirm/share your test results and any pitfall of enabling this?

Another parallel question: The default concurrency is set to 5 in Ambari code. 
Can this be exposed through ambari-agent.ini property?

> Ambari agent support for parallel task execution during deployment
> --
>
> Key: AMBARI-8189
> URL: https://issues.apache.org/jira/browse/AMBARI-8189
> Project: Ambari
>  Issue Type: Task
>Affects Versions: 2.0.0
>Reporter: Ivan Mitic
>Assignee: Ivan Mitic
> Attachments: AMBARI-8189.2.patch, AMBARI-8189.patch
>
>
> Ambari serializes all operations on the node, and by actually parallelizing 
> the independent setup activities, deployment time would significantly 
> decrease. Ambari stack definition already defines a notion of service 
> dependencies, so some basic infra requirements for parallel execution are 
> already in place.
> This is a tracking Jira where we can discuss this proposal and work on the 
> design/prototype and patch. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-20262) Startup Annotation Scanning Takes Too Long

[Jonathan Hurley (JIRA)]

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

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

> Startup Annotation Scanning Takes Too Long
> --
>
> Key: AMBARI-20262
> URL: https://issues.apache.org/jira/browse/AMBARI-20262
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20262.patch
>
>
> Currently, Ambari uses Spring's 
> {{ClassPathScanningCandidateComponentProvider}} along with an 
> {{AnnotationTypeFilter}} to find classes annotated in our classpath:
> {code}
>   ClassPathScanningCandidateComponentProvider scanner =
>   new ClassPathScanningCandidateComponentProvider(false);
>   // match only singletons that are eager listeners
>   for (Class cls : classes) {
> scanner.addIncludeFilter(new AnnotationTypeFilter(cls));
>   }
>   beanDefinitions = scanner.findCandidateComponents(AMBARI_PACKAGE);
> {code}
> This takes roughly 19 seconds on normal deployments. We can reduce this time 
> to roughly 8 seconds by switching over to Google's {{ClassPath}} via our 
> internal {{ClasspathScannerUtils}}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-20262) Startup Annotation Scanning Takes Too Long

[Jonathan Hurley (JIRA)]

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

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

> Startup Annotation Scanning Takes Too Long
> --
>
> Key: AMBARI-20262
> URL: https://issues.apache.org/jira/browse/AMBARI-20262
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20262.patch
>
>
> Currently, Ambari uses Spring's 
> {{ClassPathScanningCandidateComponentProvider}} along with an 
> {{AnnotationTypeFilter}} to find classes annotated in our classpath:
> {code}
>   ClassPathScanningCandidateComponentProvider scanner =
>   new ClassPathScanningCandidateComponentProvider(false);
>   // match only singletons that are eager listeners
>   for (Class cls : classes) {
> scanner.addIncludeFilter(new AnnotationTypeFilter(cls));
>   }
>   beanDefinitions = scanner.findCandidateComponents(AMBARI_PACKAGE);
> {code}
> This takes roughly 19 seconds on normal deployments. We can reduce this time 
> to roughly 8 seconds by switching over to Google's {{ClassPath}} via our 
> internal {{ClasspathScannerUtils}}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-20259) Superset not able to start on Ubuntu if ASCII encoding is set as default encoding

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-20259:


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

This message is automatically generated.

> Superset not able to start on Ubuntu if ASCII encoding is set as default 
> encoding
> -
>
> Key: AMBARI-20259
> URL: https://issues.apache.org/jira/browse/AMBARI-20259
> Project: Ambari
>  Issue Type: Bug
>Reporter: Nishant Bangarwa
>Assignee: Nishant Bangarwa
> Fix For: trunk, 2.5.0
>
> Attachments: ambari-20259.patch
>
>
> RuntimeError: Click will abort further execution because Python 3 was 
> configured to use ASCII as encoding for the environment.  Consult 
> http://click.pocoo.org/python3/for mitigation steps.
> This system supports the C.UTF-8 locale which is recommended.
> You might be able to resolve your issue by exporting the
> following environment variables:
> export LC_ALL=C.UTF-8
> export LANG=C.UTF-8



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-20262) Startup Annotation Scanning Takes Too Long

[Jonathan Hurley (JIRA)]

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

Jonathan Hurley updated AMBARI-20262:
-
Component/s: ambari-server

> Startup Annotation Scanning Takes Too Long
> --
>
> Key: AMBARI-20262
> URL: https://issues.apache.org/jira/browse/AMBARI-20262
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.5.0
>
>
> Currently, Ambari uses Spring's 
> {{ClassPathScanningCandidateComponentProvider}} along with an 
> {{AnnotationTypeFilter}} to find classes annotated in our classpath:
> {code}
>   ClassPathScanningCandidateComponentProvider scanner =
>   new ClassPathScanningCandidateComponentProvider(false);
>   // match only singletons that are eager listeners
>   for (Class cls : classes) {
> scanner.addIncludeFilter(new AnnotationTypeFilter(cls));
>   }
>   beanDefinitions = scanner.findCandidateComponents(AMBARI_PACKAGE);
> {code}
> This takes roughly 19 seconds on normal deployments. We can reduce this time 
> to roughly 8 seconds by switching over to Google's {{ClassPath}} via our 
> internal {{ClasspathScannerUtils}}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (AMBARI-20262) Startup Annotation Scanning Takes Too Long

[Jonathan Hurley (JIRA)]

Jonathan Hurley created AMBARI-20262:


 Summary: Startup Annotation Scanning Takes Too Long
 Key: AMBARI-20262
 URL: https://issues.apache.org/jira/browse/AMBARI-20262
 Project: Ambari
  Issue Type: Bug
Affects Versions: 2.5.0
Reporter: Jonathan Hurley
Assignee: Jonathan Hurley
Priority: Critical
 Fix For: 2.5.0


Currently, Ambari uses Spring's {{ClassPathScanningCandidateComponentProvider}} 
along with an {{AnnotationTypeFilter}} to find classes annotated in our 
classpath:

{code}
  ClassPathScanningCandidateComponentProvider scanner =
  new ClassPathScanningCandidateComponentProvider(false);

  // match only singletons that are eager listeners
  for (Class cls : classes) {
scanner.addIncludeFilter(new AnnotationTypeFilter(cls));
  }

  beanDefinitions = scanner.findCandidateComponents(AMBARI_PACKAGE);
{code}

This takes roughly 19 seconds on normal deployments. We can reduce this time to 
roughly 8 seconds by switching over to Google's {{ClassPath}} via our internal 
{{ClasspathScannerUtils}}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-20225) Take care of hive-interactive-site's 'hive.tez.container.size' config during HDP upgrade from 2.5 to 2.6 and update default value for tez-interactive-site's config 'tez

[Swapan Shridhar (JIRA)]

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

Swapan Shridhar updated AMBARI-20225:
-
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Take care of hive-interactive-site's 'hive.tez.container.size' config during 
> HDP upgrade from 2.5 to 2.6 and update default value for 
> tez-interactive-site's config 'tez.am.resource.memory.mb'.
> 
>
> Key: AMBARI-20225
> URL: https://issues.apache.org/jira/browse/AMBARI-20225
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk, 2.5.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-20225.patch
>
>
> *Background :*
> We are dealing with 2 specific configs here. 
> *(1).* 'tez.am.resource.memory.mb' for tez-interactive-site and 
> *(2).* 'hive.tez.container.size' for hive-interactive-site. 
> - 'tez.am.resource.memory.mb' already exists in tez-interactive-site from 
> Ambari-2.4 onwards and recently its default value had been changed to 
> 'SET_ON_FIRST_INVOCATION' in its hive-interacive-site.
> - 'hive.tez.container.size' was inherited and used from Hive1/hive-site in 
> Ambari 2.4. Starting from Ambari 2.5, it was added as a config explicitly in 
> hive-interactive-site with a default value of 'SET_ON_FIRST_INVOCATION'.
> The non-standard 'SET_ON_FIRST_INVOCATION' was introduced, so as to give a 
> hint in Stack Advisor (SA) call for the 1st time on Hive Server Interactive 
> ON (enable_hive_interactive config), so that config values for both can be 
> calculated and set for the 1st time. Subsequesnt calls in the lifecycle, will 
> just read the value set by SA or if later changed by user manually.
> *Problem :*
> 'SET_ON_FIRST_INVOCATION', being non-standard was breaking the code in 
> upgrade scenario. 
> *Fix:*
> Removing the use of 'SET_ON_FIRST_INVOCATION' and adding code for correct 
> behavior of configs during HDP upgrade.
>  
> *Possible scenarios:*
> *1. Ambari upgrade from 2.4 - > 2.5 having HDP 2.5. Implying 
> 2.5/stack_advisor.py code would have been updated with new LLAP GA logic.*
>- 'tez.am.resource.memory.mb' will already be there whether Hive Server 
> Interactive (HSI) is ON or OFF after Ambari upgrade. 
>   - If HSI if OFF before the upgrade was done, nothing to do over there.
>   - If HSI on ON before AMbari upgrade, or is made ON after Ambari 
> upgrade, SA logic has been updated to take of reading 
> 'hive.tez.container.size' from hive-site as it wont exist in 
> hive-interactive-site at this point. It will show up in hive-interative-site 
> aftre the HDP upgrade to 2.6
> *2. Ambari 2.4 having HDP 2.5 -> Upgrade to Ambari 2.5 -> Upgraded to HDP 2.6*
>- 'tez.am.resource.memory.mb' will already be there
>- As part of HDP 2.5 upgrade to HDP 2.6, 'hive.tez.container.size' would 
> have got added, having current value picked from 
> hive-site/hive.tez.container.size. SA code carries a calculation logic for 
> config 'hive.tez.container.size', which is bound to yield different value 
> compared to hive-site/'hive.tez.container.size'. The config's value will get 
> updated/caluclated (1). when HSI is made ON (meaning 
> 'enabled_hive_interactive' config detected as **True** in 
> changed-configurations).
>  
> *3. Ambari 2.5 with HDP 2.5 -> Upgraded to HDP 2.6*
>- Both 'hive.tez.container.size' and 'tez.am.resource.memory.mb' (alreday 
> present at HDP 2.5 in hive-interactive-site) will exist after the HDP upgrade.
> *Note* that a fresh value for 'hive.tez.container.size' and 
> 'tez.am.resource.memory.mb' is caluclated at below conditions:
> (1). when HSI is made ON, meaning 'enabled_hive_interactive' config detected 
> as **True** in changed-configurations, or
> (2). it's a cluster create operation, where HSI also is supposed to be 
> started. (BP scenario)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-20261) Unexpected popup after disable kerberos "You are in the process of disabling security on your cluster"

[Denys Buzhor (JIRA)]

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

Denys Buzhor updated AMBARI-20261:
--
Status: Patch Available  (was: Open)

> Unexpected popup after disable kerberos "You are in the process of disabling 
> security on your cluster"
> --
>
> Key: AMBARI-20261
> URL: https://issues.apache.org/jira/browse/AMBARI-20261
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Denys Buzhor
>Assignee: Denys Buzhor
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20261.patch, kerberos-confirmation-popup.png
>
>
> STR:
> * Disable Security
> * Click on "Complete" button
> Confirmation popup is shown instead of closing *Disable Security* popup.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-20261) Unexpected popup after disable kerberos "You are in the process of disabling security on your cluster"

[Denys Buzhor (JIRA)]

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

Denys Buzhor updated AMBARI-20261:
--
Attachment: AMBARI-20261.patch

> Unexpected popup after disable kerberos "You are in the process of disabling 
> security on your cluster"
> --
>
> Key: AMBARI-20261
> URL: https://issues.apache.org/jira/browse/AMBARI-20261
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Denys Buzhor
>Assignee: Denys Buzhor
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20261.patch, kerberos-confirmation-popup.png
>
>
> STR:
> * Disable Security
> * Click on "Complete" button
> Confirmation popup is shown instead of closing *Disable Security* popup.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-20225) Take care of hive-interactive-site's 'hive.tez.container.size' config during HDP upgrade from 2.5 to 2.6 and update default value for tez-interactive-site's config 't

[Swapan Shridhar (JIRA)]

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

Swapan Shridhar commented on AMBARI-20225:
--

commit 

trunk:

{code}
commit baefbcca0b60caac801f3addf0d015df23a5e96d
Author: Swapan Shridhar 
Date:   Mon Feb 27 22:56:54 2017 -0800

AMBARI-20225. Take care of hive-interactive-site's 
'hive.tez.container.size' config during HDP upgrade from 2.5 to 2.6 and update 
default value for tez-interactive-site's config 'tez.am.resource.memory.mb'.
{code}


branch-2.5:

{code}
commit ce1ed6e1aade5333c0ee26de469e8487061ccb8b
Author: Swapan Shridhar 
Date:   Mon Feb 27 22:56:54 2017 -0800

AMBARI-20225. Take care of hive-interactive-site's 
'hive.tez.container.size' config during HDP upgrade from 2.5 to 2.6 and update 
default value for tez-interactive-site's config 'tez.am.resource.memory.mb'.
{code}

> Take care of hive-interactive-site's 'hive.tez.container.size' config during 
> HDP upgrade from 2.5 to 2.6 and update default value for 
> tez-interactive-site's config 'tez.am.resource.memory.mb'.
> 
>
> Key: AMBARI-20225
> URL: https://issues.apache.org/jira/browse/AMBARI-20225
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk, 2.5.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-20225.patch
>
>
> *Background :*
> We are dealing with 2 specific configs here. 
> *(1).* 'tez.am.resource.memory.mb' for tez-interactive-site and 
> *(2).* 'hive.tez.container.size' for hive-interactive-site. 
> - 'tez.am.resource.memory.mb' already exists in tez-interactive-site from 
> Ambari-2.4 onwards and recently its default value had been changed to 
> 'SET_ON_FIRST_INVOCATION' in its hive-interacive-site.
> - 'hive.tez.container.size' was inherited and used from Hive1/hive-site in 
> Ambari 2.4. Starting from Ambari 2.5, it was added as a config explicitly in 
> hive-interactive-site with a default value of 'SET_ON_FIRST_INVOCATION'.
> The non-standard 'SET_ON_FIRST_INVOCATION' was introduced, so as to give a 
> hint in Stack Advisor (SA) call for the 1st time on Hive Server Interactive 
> ON (enable_hive_interactive config), so that config values for both can be 
> calculated and set for the 1st time. Subsequesnt calls in the lifecycle, will 
> just read the value set by SA or if later changed by user manually.
> *Problem :*
> 'SET_ON_FIRST_INVOCATION', being non-standard was breaking the code in 
> upgrade scenario. 
> *Fix:*
> Removing the use of 'SET_ON_FIRST_INVOCATION' and adding code for correct 
> behavior of configs during HDP upgrade.
>  
> *Possible scenarios:*
> *1. Ambari upgrade from 2.4 - > 2.5 having HDP 2.5. Implying 
> 2.5/stack_advisor.py code would have been updated with new LLAP GA logic.*
>- 'tez.am.resource.memory.mb' will already be there whether Hive Server 
> Interactive (HSI) is ON or OFF after Ambari upgrade. 
>   - If HSI if OFF before the upgrade was done, nothing to do over there.
>   - If HSI on ON before AMbari upgrade, or is made ON after Ambari 
> upgrade, SA logic has been updated to take of reading 
> 'hive.tez.container.size' from hive-site as it wont exist in 
> hive-interactive-site at this point. It will show up in hive-interative-site 
> aftre the HDP upgrade to 2.6
> *2. Ambari 2.4 having HDP 2.5 -> Upgrade to Ambari 2.5 -> Upgraded to HDP 2.6*
>- 'tez.am.resource.memory.mb' will already be there
>- As part of HDP 2.5 upgrade to HDP 2.6, 'hive.tez.container.size' would 
> have got added, having current value picked from 
> hive-site/hive.tez.container.size. SA code carries a calculation logic for 
> config 'hive.tez.container.size', which is bound to yield different value 
> compared to hive-site/'hive.tez.container.size'. The config's value will get 
> updated/caluclated (1). when HSI is made ON (meaning 
> 'enabled_hive_interactive' config detected as **True** in 
> changed-configurations).
>  
> *3. Ambari 2.5 with HDP 2.5 -> Upgraded to HDP 2.6*
>- Both 'hive.tez.container.size' and 'tez.am.resource.memory.mb' (alreday 
> present at HDP 2.5 in hive-interactive-site) will exist after the HDP upgrade.
> *Note* that a fresh value for 'hive.tez.container.size' and 
> 'tez.am.resource.memory.mb' is caluclated at below conditions:
> (1). when HSI is made ON, meaning 'enabled_hive_interactive' config detected 
> as **True** in changed-configurations, or
> (2). it's a cluster create operation, where HSI also is supposed to be 
> started. (BP scenario)



--
This 

[jira] [Created] (AMBARI-20261) Unexpected popup after disable kerberos "You are in the process of disabling security on your cluster"

[Denys Buzhor (JIRA)]

Denys Buzhor created AMBARI-20261:
-

 Summary: Unexpected popup after disable kerberos "You are in the 
process of disabling security on your cluster"
 Key: AMBARI-20261
 URL: https://issues.apache.org/jira/browse/AMBARI-20261
 Project: Ambari
  Issue Type: Bug
  Components: ambari-web
Affects Versions: 2.5.0
Reporter: Denys Buzhor
Assignee: Denys Buzhor
Priority: Critical
 Fix For: 2.5.0


STR:
* Disable Security
* Click on "Complete" button

Confirmation popup is shown instead of closing *Disable Security* popup.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-20260) Misc errors in Ambari Server log that need to be cleaned up

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-20260:


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

This message is automatically generated.

> Misc errors in Ambari Server log that need to be cleaned up
> ---
>
> Key: AMBARI-20260
> URL: https://issues.apache.org/jira/browse/AMBARI-20260
> Project: Ambari
>  Issue Type: Bug
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
>Priority: Minor
> Attachments: AMBARI-20260.patch
>
>
> Misc ERRORs in Ambari Server log:
> {noformat}
> 27 Feb 2017 21:06:07,574 ERROR [ambari-heartbeat-processor-0] 
> StackVersionListener:128 - ServiceComponent DRUID_BROKER doesn't advertise 
> version, however ServiceHostComponent DRUID_BROKER on host 
> alejandro-3.c.pramod-thangali.internal advertised version as 2.6.0.0-559. 
> Skipping version update
> 27 Feb 2017 21:06:09,568 ERROR [ambari-heartbeat-processor-0] 
> StackVersionListener:128 - ServiceComponent DRUID_COORDINATOR doesn't 
> advertise version, however ServiceHostComponent DRUID_COORDINATOR on host 
> alejandro-3.c.pramod-thangali.internal advertised version as 2.6.0.0-559. 
> Skipping version update
> 27 Feb 2017 21:06:10,570 ERROR [ambari-heartbeat-processor-0] 
> StackVersionListener:128 - ServiceComponent DRUID_HISTORICAL doesn't 
> advertise version, however ServiceHostComponent DRUID_HISTORICAL on host 
> alejandro-3.c.pramod-thangali.internal advertised version as 2.6.0.0-559. 
> Skipping version update
> 27 Feb 2017 21:06:11,580 ERROR [ambari-heartbeat-processor-0] 
> StackVersionListener:128 - ServiceComponent DRUID_MIDDLEMANAGER doesn't 
> advertise version, however ServiceHostComponent DRUID_MIDDLEMANAGER on host 
> alejandro-3.c.pramod-thangali.internal advertised version as 2.6.0.0-559. 
> Skipping version update
> 27 Feb 2017 21:06:13,570 ERROR [ambari-heartbeat-processor-0] 
> StackVersionListener:128 - ServiceComponent DRUID_OVERLORD doesn't advertise 
> version, however ServiceHostComponent DRUID_OVERLORD on host 
> alejandro-3.c.pramod-thangali.internal advertised version as 2.6.0.0-559. 
> Skipping version update
> 27 Feb 2017 21:06:14,611 ERROR [ambari-heartbeat-processor-0] 
> StackVersionListener:128 - ServiceComponent DRUID_ROUTER doesn't advertise 
> version, however ServiceHostComponent DRUID_ROUTER on host 
> alejandro-3.c.pramod-thangali.internal advertised version as 2.6.0.0-559. 
> Skipping version update
> 27 Feb 2017 21:06:15,589 ERROR [ambari-heartbeat-processor-0] 
> StackVersionListener:128 - ServiceComponent DRUID_SUPERSET doesn't advertise 
> version, however ServiceHostComponent DRUID_SUPERSET on host 
> alejandro-3.c.pramod-thangali.internal advertised version as 2.6.0.0-559. 
> Skipping version update
> ERROR [ambari-client-thread-33] ClusterImpl:2882 - No service found for 
> config types '[cluster-env]', service config version not created
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-20261) Unexpected popup after disable kerberos "You are in the process of disabling security on your cluster"

[Denys Buzhor (JIRA)]

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

Denys Buzhor updated AMBARI-20261:
--
Attachment: kerberos-confirmation-popup.png

> Unexpected popup after disable kerberos "You are in the process of disabling 
> security on your cluster"
> --
>
> Key: AMBARI-20261
> URL: https://issues.apache.org/jira/browse/AMBARI-20261
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Denys Buzhor
>Assignee: Denys Buzhor
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: kerberos-confirmation-popup.png
>
>
> STR:
> * Disable Security
> * Click on "Complete" button
> Confirmation popup is shown instead of closing *Disable Security* popup.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-20244) HBase indicates restart required after upgrade from Amabri-2.4+HDP-2.5

[Hudson (JIRA)]

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

Hudson commented on AMBARI-20244:
-

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6905 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6905/])
AMBARI-20244 : HBase indicates restart required after upgrade from (avijayan: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=2072511fdddeec369dc8ae517c848e9954b8400a])
* (edit) 
ambari-server/src/main/resources/common-services/HBASE/0.96.0.2.0/metainfo.xml
* (edit) 
ambari-server/src/main/resources/common-services/STORM/0.9.1/metainfo.xml
* (edit) 
ambari-server/src/main/resources/common-services/FLUME/1.4.0.2.0/metainfo.xml
* (edit) 
ambari-server/src/main/resources/common-services/STORM/1.0.1/metainfo.xml
* (edit) 
ambari-server/src/main/resources/stacks/PERF/1.0/services/FAKEHDFS/metainfo.xml
* (edit) 
ambari-server/src/main/resources/common-services/ACCUMULO/1.6.1.2.2.0/metainfo.xml
* (edit) 
ambari-server/src/main/resources/common-services/KAFKA/0.8.1/metainfo.xml
* (edit) 
ambari-server/src/main/resources/stacks/PERF/1.0/services/FAKEYARN/metainfo.xml
* (edit) 
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/metainfo.xml
* (edit) 
ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/metainfo.xml
* (edit) 
ambari-server/src/main/resources/stacks/PERF/1.0/services/FAKEHBASE/metainfo.xml


> HBase indicates restart required after upgrade from Amabri-2.4+HDP-2.5
> --
>
> Key: AMBARI-20244
> URL: https://issues.apache.org/jira/browse/AMBARI-20244
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics
>Affects Versions: 2.5.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20244.patch
>
>
> HBase indicates restart required after upgrade to Ambari-2.5 from Ambari-2.4 
> + HDP-2.6. The root cause seems to be the addition of a property to 
> ams-ssl-client config type
> Ambari-2.4 deployed
> {code}
> "properties" : {
> "ssl.client.truststore.location" : "/etc/security/clientKeys/all.jks",
> "ssl.client.truststore.password" : 
> "SECRET:ams-ssl-client:1:ssl.client.truststore.password",
> "ssl.client.truststore.type" : "jks"
>   }
> {code}
> Post upgrade it became the following - *ssl.client.truststore.alias* got 
> added.
> {code}
> "properties" : {
> "ssl.client.truststore.alias" : "",
> "ssl.client.truststore.location" : "/etc/security/clientKeys/all.jks",
> "ssl.client.truststore.password" : 
> "SECRET:ams-ssl-client:2:ssl.client.truststore.password",
> "ssl.client.truststore.type" : "jks"
>   }
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-20245) Setup tez ats related parameters

[Hudson (JIRA)]

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

Hudson commented on AMBARI-20245:
-

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6905 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6905/])
AMBARI-20245. Setup tez ats related parameters (smohanty) (smohanty: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=8c74cc4d5f7ff8a4bfab6eca55993f53d0aedf4d])
* (edit) pom.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.6/services/TEZ/configuration/tez-site.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.6/services/HIVE/configuration/tez-interactive-site.xml


> Setup tez ats related parameters
> 
>
> Key: AMBARI-20245
> URL: https://issues.apache.org/jira/browse/AMBARI-20245
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.5.0
>Reporter: Siddharth Seth
>Assignee: Sumit Mohanty
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20245.patch
>
>
> Dags per group needs to be set to 5.
> TASK_ATTEMPT events to be ignored needs to be set to 
> |tez-interactive-site|tez.history.logging.timeline.num-dags-per-group|5|
> |tez-site|tez.history.logging.timeline-cache-plugin.old-num-dags-per-group|5|
> |tez-intearactive-site|tez.history.logging.taskattempt-filters|EXECUTOR_BUSY,EXTERNAL_PREEMPTION|



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-20244) HBase indicates restart required after upgrade from Amabri-2.4+HDP-2.5

[Hudson (JIRA)]

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

Hudson commented on AMBARI-20244:
-

SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1145 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/1145/])
AMBARI-20244 : HBase indicates restart required after upgrade from (avijayan: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=9ecf90d0cb409c2c9c2119ae2eb0b3d53cfb4cf2])
* (edit) 
ambari-server/src/main/resources/common-services/HBASE/0.96.0.2.0/metainfo.xml
* (edit) 
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/metainfo.xml
* (edit) 
ambari-server/src/main/resources/common-services/ACCUMULO/1.6.1.2.2.0/metainfo.xml
* (edit) 
ambari-server/src/main/resources/stacks/PERF/1.0/services/FAKEHDFS/metainfo.xml
* (edit) 
ambari-server/src/main/resources/stacks/PERF/1.0/services/FAKEHBASE/metainfo.xml
* (edit) 
ambari-server/src/main/resources/common-services/STORM/0.9.1/metainfo.xml
* (edit) 
ambari-server/src/main/resources/common-services/STORM/1.0.1/metainfo.xml
* (edit) 
ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/metainfo.xml
* (edit) 
ambari-server/src/main/resources/common-services/FLUME/1.4.0.2.0/metainfo.xml
* (edit) 
ambari-server/src/main/resources/stacks/PERF/1.0/services/FAKEYARN/metainfo.xml
* (edit) 
ambari-server/src/main/resources/common-services/KAFKA/0.8.1/metainfo.xml


> HBase indicates restart required after upgrade from Amabri-2.4+HDP-2.5
> --
>
> Key: AMBARI-20244
> URL: https://issues.apache.org/jira/browse/AMBARI-20244
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics
>Affects Versions: 2.5.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20244.patch
>
>
> HBase indicates restart required after upgrade to Ambari-2.5 from Ambari-2.4 
> + HDP-2.6. The root cause seems to be the addition of a property to 
> ams-ssl-client config type
> Ambari-2.4 deployed
> {code}
> "properties" : {
> "ssl.client.truststore.location" : "/etc/security/clientKeys/all.jks",
> "ssl.client.truststore.password" : 
> "SECRET:ams-ssl-client:1:ssl.client.truststore.password",
> "ssl.client.truststore.type" : "jks"
>   }
> {code}
> Post upgrade it became the following - *ssl.client.truststore.alias* got 
> added.
> {code}
> "properties" : {
> "ssl.client.truststore.alias" : "",
> "ssl.client.truststore.location" : "/etc/security/clientKeys/all.jks",
> "ssl.client.truststore.password" : 
> "SECRET:ams-ssl-client:2:ssl.client.truststore.password",
> "ssl.client.truststore.type" : "jks"
>   }
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-20245) Setup tez ats related parameters

[Hudson (JIRA)]

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

Hudson commented on AMBARI-20245:
-

SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1145 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/1145/])
AMBARI-20245. Setup tez ats related parameters (smohanty) (smohanty: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=ae44ad03aecb26e7207b08c583291e2cde282072])
* (edit) pom.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.6/services/TEZ/configuration/tez-site.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.6/services/HIVE/configuration/tez-interactive-site.xml


> Setup tez ats related parameters
> 
>
> Key: AMBARI-20245
> URL: https://issues.apache.org/jira/browse/AMBARI-20245
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.5.0
>Reporter: Siddharth Seth
>Assignee: Sumit Mohanty
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20245.patch
>
>
> Dags per group needs to be set to 5.
> TASK_ATTEMPT events to be ignored needs to be set to 
> |tez-interactive-site|tez.history.logging.timeline.num-dags-per-group|5|
> |tez-site|tez.history.logging.timeline-cache-plugin.old-num-dags-per-group|5|
> |tez-intearactive-site|tez.history.logging.taskattempt-filters|EXECUTOR_BUSY,EXTERNAL_PREEMPTION|



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-18472) Can't switch to not current version for not default config gorup

[Hudson (JIRA)]

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

Hudson commented on AMBARI-18472:
-

SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1145 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/1145/])
AMBARI-18472 Can't switch to not current version for not default config 
(akovalenko: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=56432c6513d5679fc39dcb4d035c94b9dbd2e125])
* (edit) ambari-web/app/mixins/common/configs/configs_loader.js
* (edit) ambari-web/app/views/common/configs/config_history_flow.js


> Can't switch to not current version for not default config gorup
> 
>
> Key: AMBARI-18472
> URL: https://issues.apache.org/jira/browse/AMBARI-18472
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
> Fix For: 3.0.0
>
> Attachments: AMBARI-18472_branch-2.5.0.patch, AMBARI-18472.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-20254) Service Alert Popup - Unexpected User Experience

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-20254:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12855439/AMBARI-20254.v1.branch-2.5.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/10835//console

This message is automatically generated.

> Service Alert Popup - Unexpected User Experience
> 
>
> Key: AMBARI-20254
> URL: https://issues.apache.org/jira/browse/AMBARI-20254
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Vivek Ratnavel Subramanian
>Assignee: Vivek Ratnavel Subramanian
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20254.v0.branch-2.5.patch, 
> AMBARI-20254.v0.trunk.patch, AMBARI-20254.v1.branch-2.5.patch, tooltip2.png
>
>
> AMBARI-19049 introduced some UI changes that causes regression in UX for the 
> Service Alert popup.
> With the change, the user has to click on the expander to see any alert 
> context. And the expander UX is strange too. Clicking anywhere (including the 
> hyperlinked text as well as the background) in the header takes the user to 
> the alerts page. This is not the experience the user would expect based on 
> conventions.
> The cases in which too much context is displayed and therefore needs special 
> handling is not the norm, so crippling UX for the special case is not the way 
> to go.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-19429) Create an ODPi stack definition

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-19429:


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

This message is automatically generated.

> Create an ODPi stack definition
> ---
>
> Key: AMBARI-19429
> URL: https://issues.apache.org/jira/browse/AMBARI-19429
> Project: Ambari
>  Issue Type: Improvement
>  Components: stacks
>Affects Versions: 2.4.2
>Reporter: Roman Shaposhnik
>Assignee: Roman Shaposhnik
> Attachments: AMBARI-19429.patch2.gz, AMBARI-19429.patch.gz
>
>
> ODPi is a nonprofit organization committed to simplification & 
> standardization of the big data ecosystem with common reference 
> specifications and test suites. As part of its mission, ODPi has been 
> developing a series of specifications for how to integrate upstream Apache 
> projects into the coherent platform. Part of this standardization effort is 
> maintenance of the ODPi core stack definition which today includes:
>* Apache Zookeeper
>* Apache Hadoop
>* Apache Hive
> and has been maintained as a custom stack on ODPi side:
> 
> https://github.com/odpi/bigtop/tree/odpi-master/bigtop-packages/src/common/ambari/ODPi/1.0
> In conjunction with merge effort for Apache Bigtop BIGTOP-2666 I'd like to 
> propose that instead of migrating the stack definition to Bigtop, we should 
> actually migrate it to Ambari.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-19429) Create an ODPi stack definition

[Roman Shaposhnik (JIRA)]

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

Roman Shaposhnik updated AMBARI-19429:
--
Attachment: AMBARI-19429.patch2.gz

Apologies for the RAT failure (I really should've known better). The new patch 
that passes mvn clean apache-rat:check from the root level is attached. Please 
consider pushing it.

> Create an ODPi stack definition
> ---
>
> Key: AMBARI-19429
> URL: https://issues.apache.org/jira/browse/AMBARI-19429
> Project: Ambari
>  Issue Type: Improvement
>  Components: stacks
>Affects Versions: 2.4.2
>Reporter: Roman Shaposhnik
>Assignee: Roman Shaposhnik
> Attachments: AMBARI-19429.patch2.gz, AMBARI-19429.patch.gz
>
>
> ODPi is a nonprofit organization committed to simplification & 
> standardization of the big data ecosystem with common reference 
> specifications and test suites. As part of its mission, ODPi has been 
> developing a series of specifications for how to integrate upstream Apache 
> projects into the coherent platform. Part of this standardization effort is 
> maintenance of the ODPi core stack definition which today includes:
>* Apache Zookeeper
>* Apache Hadoop
>* Apache Hive
> and has been maintained as a custom stack on ODPi side:
> 
> https://github.com/odpi/bigtop/tree/odpi-master/bigtop-packages/src/common/ambari/ODPi/1.0
> In conjunction with merge effort for Apache Bigtop BIGTOP-2666 I'd like to 
> propose that instead of migrating the stack definition to Bigtop, we should 
> actually migrate it to Ambari.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-20244) HBase indicates restart required after upgrade from Amabri-2.4+HDP-2.5

[Aravindan Vijayan (JIRA)]

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

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

Pushed to branch-2.5 and trunk.

> HBase indicates restart required after upgrade from Amabri-2.4+HDP-2.5
> --
>
> Key: AMBARI-20244
> URL: https://issues.apache.org/jira/browse/AMBARI-20244
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics
>Affects Versions: 2.5.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20244.patch
>
>
> HBase indicates restart required after upgrade to Ambari-2.5 from Ambari-2.4 
> + HDP-2.6. The root cause seems to be the addition of a property to 
> ams-ssl-client config type
> Ambari-2.4 deployed
> {code}
> "properties" : {
> "ssl.client.truststore.location" : "/etc/security/clientKeys/all.jks",
> "ssl.client.truststore.password" : 
> "SECRET:ams-ssl-client:1:ssl.client.truststore.password",
> "ssl.client.truststore.type" : "jks"
>   }
> {code}
> Post upgrade it became the following - *ssl.client.truststore.alias* got 
> added.
> {code}
> "properties" : {
> "ssl.client.truststore.alias" : "",
> "ssl.client.truststore.location" : "/etc/security/clientKeys/all.jks",
> "ssl.client.truststore.password" : 
> "SECRET:ams-ssl-client:2:ssl.client.truststore.password",
> "ssl.client.truststore.type" : "jks"
>   }
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-20254) Service Alert Popup - Unexpected User Experience

[Vivek Ratnavel Subramanian (JIRA)]

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

Vivek Ratnavel Subramanian updated AMBARI-20254:

Attachment: AMBARI-20254.v1.branch-2.5.patch

> Service Alert Popup - Unexpected User Experience
> 
>
> Key: AMBARI-20254
> URL: https://issues.apache.org/jira/browse/AMBARI-20254
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Vivek Ratnavel Subramanian
>Assignee: Vivek Ratnavel Subramanian
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20254.v0.branch-2.5.patch, 
> AMBARI-20254.v0.trunk.patch, AMBARI-20254.v1.branch-2.5.patch, tooltip2.png
>
>
> AMBARI-19049 introduced some UI changes that causes regression in UX for the 
> Service Alert popup.
> With the change, the user has to click on the expander to see any alert 
> context. And the expander UX is strange too. Clicking anywhere (including the 
> hyperlinked text as well as the background) in the header takes the user to 
> the alerts page. This is not the experience the user would expect based on 
> conventions.
> The cases in which too much context is displayed and therefore needs special 
> handling is not the norm, so crippling UX for the special case is not the way 
> to go.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-20245) Setup tez ats related parameters

[Sumit Mohanty (JIRA)]

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

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

Committed to trunk and branch-2.5

> Setup tez ats related parameters
> 
>
> Key: AMBARI-20245
> URL: https://issues.apache.org/jira/browse/AMBARI-20245
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.5.0
>Reporter: Siddharth Seth
>Assignee: Sumit Mohanty
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20245.patch
>
>
> Dags per group needs to be set to 5.
> TASK_ATTEMPT events to be ignored needs to be set to 
> |tez-interactive-site|tez.history.logging.timeline.num-dags-per-group|5|
> |tez-site|tez.history.logging.timeline-cache-plugin.old-num-dags-per-group|5|
> |tez-intearactive-site|tez.history.logging.taskattempt-filters|EXECUTOR_BUSY,EXTERNAL_PREEMPTION|



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-20181) HiveView2.0: Can not create a table with space in column name with upload table feature

[Hudson (JIRA)]

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

Hudson commented on AMBARI-20181:
-

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6904 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6904/])
AMBARI-20181 : hive view 2.0 : added back ticks in column names to 
(nitiraj.rathore: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=d562216ed7784fd5898668b17ddf80abdbf642b1])
* (add) 
contrib/views/hive20/src/test/java/org/apache/ambari/view/hive20/internal/query/generators/InsertFromQueryGeneratorSpecTest.groovy
* (edit) 
contrib/views/hive20/src/main/java/org/apache/ambari/view/hive20/internal/query/generators/InsertFromQueryGenerator.java
* (edit) 
contrib/views/hive20/src/main/java/org/apache/ambari/view/hive20/internal/dto/ColumnInfo.java
* (edit) 
contrib/views/hive20/src/test/java/org/apache/ambari/view/hive20/internal/query/generators/CreateTableQueryGeneratorTest.java
* (edit) 
contrib/views/hive20/src/main/java/org/apache/ambari/view/hive20/internal/query/generators/CreateTableQueryGenerator.java


> HiveView2.0: Can not create a table with space in column name with upload 
> table feature
> ---
>
> Key: AMBARI-20181
> URL: https://issues.apache.org/jira/browse/AMBARI-20181
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Yesha Vora
>Assignee: Nitiraj Singh Rathore
>Priority: Critical
> Attachments: AMBARI-20181_branch-2.5_2.patch
>
>
> Scenario:
> * Go to HiveView
> * Go to table tab
> * Click on Upload table
> * Upload a CSV file such that it column name has a space in it. 
> * Click on create table.
> The table creation failed because it does not add `` in the column name where 
> it has space or other special chars. 
> Currently, table creation is failing with below error.
> {code}
> org.apache.hive.service.cli.HiveSQLException: Error while compiling 
> statement: FAILED: SemanticException [Error 10004]: Line 1:56 Invalid table 
> alias or column reference 'Issue': (possible column names are: summary, issue 
> key, issue id, parent id, issue type, status, project key, project name, 
> project type, project lead, project description, project url, priority, 
> resolution, assignee, reporter, creator, affects version, fix versions, 
> component, labels){code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-20245) Setup tez ats related parameters

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty commented on AMBARI-20245:


Thanks [~afernandez]/[~rlevas]

> Setup tez ats related parameters
> 
>
> Key: AMBARI-20245
> URL: https://issues.apache.org/jira/browse/AMBARI-20245
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.5.0
>Reporter: Siddharth Seth
>Assignee: Sumit Mohanty
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20245.patch
>
>
> Dags per group needs to be set to 5.
> TASK_ATTEMPT events to be ignored needs to be set to 
> |tez-interactive-site|tez.history.logging.timeline.num-dags-per-group|5|
> |tez-site|tez.history.logging.timeline-cache-plugin.old-num-dags-per-group|5|
> |tez-intearactive-site|tez.history.logging.taskattempt-filters|EXECUTOR_BUSY,EXTERNAL_PREEMPTION|



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-20113) Not able to compute the table statistics for partitioned table

[Hudson (JIRA)]

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

Hudson commented on AMBARI-20113:
-

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6904 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6904/])
Revert "AMBARI-20113 : hive20 view : fixed : Not able to compute the 
(nitiraj.rathore: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=8bcc953df901af5926d05c4d901a716c3246937e])
* (edit) 
contrib/views/hive20/src/main/java/org/apache/ambari/view/hive20/internal/query/generators/AnalyzeTableQueryGenerator.java
* (edit) 
contrib/views/hive20/src/main/java/org/apache/ambari/view/hive20/resources/browser/DDLService.java
* (edit) 
contrib/views/hive20/src/main/java/org/apache/ambari/view/hive20/resources/browser/DDLProxy.java
* (delete) 
contrib/views/hive20/src/test/java/org/apache/ambari/view/hive20/internal/query/generators/AnalyzeTableQueryGeneratorSpecTest.groovy
AMBARI-20113 : hive20 view : fixed : Not able to compute the table 
(nitiraj.rathore: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=a749f97abbc44217fbb6f8e4868deaf6c4811fab])
* (add) 
contrib/views/hive20/src/test/java/org/apache/ambari/view/hive20/internal/query/generators/AnalyzeTableQueryGeneratorSpecTest.groovy
* (edit) 
contrib/views/hive20/src/main/java/org/apache/ambari/view/hive20/resources/browser/DDLProxy.java
* (edit) 
contrib/views/hive20/src/main/java/org/apache/ambari/view/hive20/internal/query/generators/AnalyzeTableQueryGenerator.java
* (edit) 
contrib/views/hive20/src/main/java/org/apache/ambari/view/hive20/resources/browser/DDLService.java


> Not able to compute the table statistics for partitioned table
> --
>
> Key: AMBARI-20113
> URL: https://issues.apache.org/jira/browse/AMBARI-20113
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Supreeth Sharma
>Assignee: Nitiraj Singh Rathore
>Priority: Critical
>  Labels: HiveView2.0
> Fix For: 2.5.0
>
> Attachments: AMBARI-20113_branch-2.5_3.patch
>
>
> Not able to compute the table statistics for partitioned table. API to 
> compute the stat is failing with below error :
> {code}
> Error while compiling statement: FAILED: SemanticException [Error 10115]: 
> Table is partitioned and partition specification is needed
> {code}
> Attaching the complete stack trace.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-18472) Can't switch to not current version for not default config gorup

[Aleksandr Kovalenko (JIRA)]

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

Aleksandr Kovalenko commented on AMBARI-18472:
--

committed to branch-2.5.0

> Can't switch to not current version for not default config gorup
> 
>
> Key: AMBARI-18472
> URL: https://issues.apache.org/jira/browse/AMBARI-18472
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
> Fix For: 3.0.0
>
> Attachments: AMBARI-18472_branch-2.5.0.patch, AMBARI-18472.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-18472) Can't switch to not current version for not default config gorup

[Aleksandr Kovalenko (JIRA)]

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

Aleksandr Kovalenko updated AMBARI-18472:
-
Attachment: AMBARI-18472_branch-2.5.0.patch

> Can't switch to not current version for not default config gorup
> 
>
> Key: AMBARI-18472
> URL: https://issues.apache.org/jira/browse/AMBARI-18472
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
> Fix For: 3.0.0
>
> Attachments: AMBARI-18472_branch-2.5.0.patch, AMBARI-18472.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-20181) HiveView2.0: Can not create a table with space in column name with upload table feature

[Hudson (JIRA)]

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

Hudson commented on AMBARI-20181:
-

SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1144 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/1144/])
AMBARI-20181 : hive view 2.0 : added back ticks in column names to 
(nitiraj.rathore: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=1546cc9df66cc06087b0402bd572fb23f08bdb52])
* (add) 
contrib/views/hive20/src/test/java/org/apache/ambari/view/hive20/internal/query/generators/InsertFromQueryGeneratorSpecTest.groovy
* (edit) 
contrib/views/hive20/src/test/java/org/apache/ambari/view/hive20/internal/query/generators/CreateTableQueryGeneratorTest.java
* (edit) 
contrib/views/hive20/src/main/java/org/apache/ambari/view/hive20/internal/dto/ColumnInfo.java
* (edit) 
contrib/views/hive20/src/main/java/org/apache/ambari/view/hive20/internal/query/generators/CreateTableQueryGenerator.java
* (edit) 
contrib/views/hive20/src/main/java/org/apache/ambari/view/hive20/internal/query/generators/InsertFromQueryGenerator.java


> HiveView2.0: Can not create a table with space in column name with upload 
> table feature
> ---
>
> Key: AMBARI-20181
> URL: https://issues.apache.org/jira/browse/AMBARI-20181
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Yesha Vora
>Assignee: Nitiraj Singh Rathore
>Priority: Critical
> Attachments: AMBARI-20181_branch-2.5_2.patch
>
>
> Scenario:
> * Go to HiveView
> * Go to table tab
> * Click on Upload table
> * Upload a CSV file such that it column name has a space in it. 
> * Click on create table.
> The table creation failed because it does not add `` in the column name where 
> it has space or other special chars. 
> Currently, table creation is failing with below error.
> {code}
> org.apache.hive.service.cli.HiveSQLException: Error while compiling 
> statement: FAILED: SemanticException [Error 10004]: Line 1:56 Invalid table 
> alias or column reference 'Issue': (possible column names are: summary, issue 
> key, issue id, parent id, issue type, status, project key, project name, 
> project type, project lead, project description, project url, priority, 
> resolution, assignee, reporter, creator, affects version, fix versions, 
> component, labels){code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-20113) Not able to compute the table statistics for partitioned table

[Hudson (JIRA)]

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

Hudson commented on AMBARI-20113:
-

SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1144 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/1144/])
Revert "AMBARI-20113 : hive20 view : fixed : Not able to compute the 
(nitiraj.rathore: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=0de07e09361b79db25090546a46516affee5ada2])
* (edit) 
contrib/views/hive20/src/main/java/org/apache/ambari/view/hive20/internal/query/generators/AnalyzeTableQueryGenerator.java
* (edit) 
contrib/views/hive20/src/main/java/org/apache/ambari/view/hive20/resources/browser/DDLProxy.java
* (delete) 
contrib/views/hive20/src/test/java/org/apache/ambari/view/hive20/internal/query/generators/AnalyzeTableQueryGeneratorSpecTest.groovy
* (edit) 
contrib/views/hive20/src/main/java/org/apache/ambari/view/hive20/resources/browser/DDLService.java
AMBARI-20113 : hive20 view : fixed : Not able to compute the table 
(nitiraj.rathore: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=90f0d2560546d843aaa315f7a8c36fc27b8d8d4a])
* (edit) 
contrib/views/hive20/src/main/java/org/apache/ambari/view/hive20/resources/browser/DDLService.java
* (add) 
contrib/views/hive20/src/test/java/org/apache/ambari/view/hive20/internal/query/generators/AnalyzeTableQueryGeneratorSpecTest.groovy
* (edit) 
contrib/views/hive20/src/main/java/org/apache/ambari/view/hive20/internal/query/generators/AnalyzeTableQueryGenerator.java
* (edit) 
contrib/views/hive20/src/main/java/org/apache/ambari/view/hive20/resources/browser/DDLProxy.java


> Not able to compute the table statistics for partitioned table
> --
>
> Key: AMBARI-20113
> URL: https://issues.apache.org/jira/browse/AMBARI-20113
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Supreeth Sharma
>Assignee: Nitiraj Singh Rathore
>Priority: Critical
>  Labels: HiveView2.0
> Fix For: 2.5.0
>
> Attachments: AMBARI-20113_branch-2.5_3.patch
>
>
> Not able to compute the table statistics for partitioned table. API to 
> compute the stat is failing with below error :
> {code}
> Error while compiling statement: FAILED: SemanticException [Error 10115]: 
> Table is partitioned and partition specification is needed
> {code}
> Attaching the complete stack trace.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-20188) HiveView 2.0: Add a note on Save To HDFS popup box that full hdfs url is not supported

[Yesha Vora (JIRA)]

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

Yesha Vora updated AMBARI-20188:

Description: 
Save To HDFS option does not work if full hdfs url is provided. 

Steps to reproduce:
* Run a query
* Click on Save To HDFS
* Enter "hdfs://mycluster/tmp/yyy.csv" in path

Since full url is not supported, the pop up box should have a note stating 
that. 
It should also print an example. 
Otherwise it will not be clear to user on how to enter the hdfs path.

  was:
Save To HDFS option should work if full hdfs url is provided. 

Steps to reproduce:
* Run a query
* Click on Save To HDFS
* Enter "hdfs://mycluster/tmp/yyy.csv" in path

This is a valid path. HDFS Put works with "hdfs://mycluster/tmp/yyy.csv" as 
destination. 
{code}
[root@xxx ~]# hdfs dfs -put  /tmp/all_nodes hdfs://mycluster/tmp/
[root@xxx ~]# hdfs dfs -ls /tmp
Found 4 items
-rw-r--r--   3 cstm-hdfs hdfs 67 2017-02-24 20:15 /tmp/all_nodes
-rw-r--r--   3 admin hdfs   1324 2017-02-24 20:03 
/tmp/yeshabugs.csv{code}

However it does not work from Hive View. It does not throw any error either.


> HiveView 2.0: Add a note on Save To HDFS popup box that full hdfs url is not 
> supported
> --
>
> Key: AMBARI-20188
> URL: https://issues.apache.org/jira/browse/AMBARI-20188
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Yesha Vora
>
> Save To HDFS option does not work if full hdfs url is provided. 
> Steps to reproduce:
> * Run a query
> * Click on Save To HDFS
> * Enter "hdfs://mycluster/tmp/yyy.csv" in path
> Since full url is not supported, the pop up box should have a note stating 
> that. 
> It should also print an example. 
> Otherwise it will not be clear to user on how to enter the hdfs path.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-20245) Setup tez ats related parameters

[Alejandro Fernandez (JIRA)]

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

Alejandro Fernandez commented on AMBARI-20245:
--

[~rlevas], that's fine; we still haven't added Hive or Tez to HDP 3.0.

> Setup tez ats related parameters
> 
>
> Key: AMBARI-20245
> URL: https://issues.apache.org/jira/browse/AMBARI-20245
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.5.0
>Reporter: Siddharth Seth
>Assignee: Sumit Mohanty
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20245.patch
>
>
> Dags per group needs to be set to 5.
> TASK_ATTEMPT events to be ignored needs to be set to 
> |tez-interactive-site|tez.history.logging.timeline.num-dags-per-group|5|
> |tez-site|tez.history.logging.timeline-cache-plugin.old-num-dags-per-group|5|
> |tez-intearactive-site|tez.history.logging.taskattempt-filters|EXECUTOR_BUSY,EXTERNAL_PREEMPTION|



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-20188) HiveView 2.0: Add a note on Save To HDFS popup box that full hdfs url is not supported

[Yesha Vora (JIRA)]

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

Yesha Vora updated AMBARI-20188:

Issue Type: Improvement  (was: Bug)

> HiveView 2.0: Add a note on Save To HDFS popup box that full hdfs url is not 
> supported
> --
>
> Key: AMBARI-20188
> URL: https://issues.apache.org/jira/browse/AMBARI-20188
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Yesha Vora
>
> Save To HDFS option should work if full hdfs url is provided. 
> Steps to reproduce:
> * Run a query
> * Click on Save To HDFS
> * Enter "hdfs://mycluster/tmp/yyy.csv" in path
> This is a valid path. HDFS Put works with "hdfs://mycluster/tmp/yyy.csv" as 
> destination. 
> {code}
> [root@xxx ~]# hdfs dfs -put  /tmp/all_nodes hdfs://mycluster/tmp/
> [root@xxx ~]# hdfs dfs -ls /tmp
> Found 4 items
> -rw-r--r--   3 cstm-hdfs hdfs 67 2017-02-24 20:15 /tmp/all_nodes
> -rw-r--r--   3 admin hdfs   1324 2017-02-24 20:03 
> /tmp/yeshabugs.csv{code}
> However it does not work from Hive View. It does not throw any error either.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-20188) HiveView 2.0: Add a note on Save To HDFS popup box that full hdfs url is not supported

[Yesha Vora (JIRA)]

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

Yesha Vora updated AMBARI-20188:

Summary: HiveView 2.0: Add a note on Save To HDFS popup box that full hdfs 
url is not supported  (was: HiveView 2.0: Save To HDFS does not work with full 
hdfs url)

> HiveView 2.0: Add a note on Save To HDFS popup box that full hdfs url is not 
> supported
> --
>
> Key: AMBARI-20188
> URL: https://issues.apache.org/jira/browse/AMBARI-20188
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Yesha Vora
>
> Save To HDFS option should work if full hdfs url is provided. 
> Steps to reproduce:
> * Run a query
> * Click on Save To HDFS
> * Enter "hdfs://mycluster/tmp/yyy.csv" in path
> This is a valid path. HDFS Put works with "hdfs://mycluster/tmp/yyy.csv" as 
> destination. 
> {code}
> [root@xxx ~]# hdfs dfs -put  /tmp/all_nodes hdfs://mycluster/tmp/
> [root@xxx ~]# hdfs dfs -ls /tmp
> Found 4 items
> -rw-r--r--   3 cstm-hdfs hdfs 67 2017-02-24 20:15 /tmp/all_nodes
> -rw-r--r--   3 admin hdfs   1324 2017-02-24 20:03 
> /tmp/yeshabugs.csv{code}
> However it does not work from Hive View. It does not throw any error either.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-20260) Misc errors in Ambari Server log that need to be cleaned up

[Alejandro Fernandez (JIRA)]

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

Alejandro Fernandez commented on AMBARI-20260:
--

[~jluniya], +1 for [^AMBARI-20260.patch]

> Misc errors in Ambari Server log that need to be cleaned up
> ---
>
> Key: AMBARI-20260
> URL: https://issues.apache.org/jira/browse/AMBARI-20260
> Project: Ambari
>  Issue Type: Bug
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
>Priority: Minor
> Attachments: AMBARI-20260.patch
>
>
> Misc ERRORs in Ambari Server log:
> {noformat}
> 27 Feb 2017 21:06:07,574 ERROR [ambari-heartbeat-processor-0] 
> StackVersionListener:128 - ServiceComponent DRUID_BROKER doesn't advertise 
> version, however ServiceHostComponent DRUID_BROKER on host 
> alejandro-3.c.pramod-thangali.internal advertised version as 2.6.0.0-559. 
> Skipping version update
> 27 Feb 2017 21:06:09,568 ERROR [ambari-heartbeat-processor-0] 
> StackVersionListener:128 - ServiceComponent DRUID_COORDINATOR doesn't 
> advertise version, however ServiceHostComponent DRUID_COORDINATOR on host 
> alejandro-3.c.pramod-thangali.internal advertised version as 2.6.0.0-559. 
> Skipping version update
> 27 Feb 2017 21:06:10,570 ERROR [ambari-heartbeat-processor-0] 
> StackVersionListener:128 - ServiceComponent DRUID_HISTORICAL doesn't 
> advertise version, however ServiceHostComponent DRUID_HISTORICAL on host 
> alejandro-3.c.pramod-thangali.internal advertised version as 2.6.0.0-559. 
> Skipping version update
> 27 Feb 2017 21:06:11,580 ERROR [ambari-heartbeat-processor-0] 
> StackVersionListener:128 - ServiceComponent DRUID_MIDDLEMANAGER doesn't 
> advertise version, however ServiceHostComponent DRUID_MIDDLEMANAGER on host 
> alejandro-3.c.pramod-thangali.internal advertised version as 2.6.0.0-559. 
> Skipping version update
> 27 Feb 2017 21:06:13,570 ERROR [ambari-heartbeat-processor-0] 
> StackVersionListener:128 - ServiceComponent DRUID_OVERLORD doesn't advertise 
> version, however ServiceHostComponent DRUID_OVERLORD on host 
> alejandro-3.c.pramod-thangali.internal advertised version as 2.6.0.0-559. 
> Skipping version update
> 27 Feb 2017 21:06:14,611 ERROR [ambari-heartbeat-processor-0] 
> StackVersionListener:128 - ServiceComponent DRUID_ROUTER doesn't advertise 
> version, however ServiceHostComponent DRUID_ROUTER on host 
> alejandro-3.c.pramod-thangali.internal advertised version as 2.6.0.0-559. 
> Skipping version update
> 27 Feb 2017 21:06:15,589 ERROR [ambari-heartbeat-processor-0] 
> StackVersionListener:128 - ServiceComponent DRUID_SUPERSET doesn't advertise 
> version, however ServiceHostComponent DRUID_SUPERSET on host 
> alejandro-3.c.pramod-thangali.internal advertised version as 2.6.0.0-559. 
> Skipping version update
> ERROR [ambari-client-thread-33] ClusterImpl:2882 - No service found for 
> config types '[cluster-env]', service config version not created
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-20260) Misc errors in Ambari Server log that need to be cleaned up

[Jayush Luniya (JIRA)]

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

Jayush Luniya updated AMBARI-20260:
---
Attachment: AMBARI-20260.patch

> Misc errors in Ambari Server log that need to be cleaned up
> ---
>
> Key: AMBARI-20260
> URL: https://issues.apache.org/jira/browse/AMBARI-20260
> Project: Ambari
>  Issue Type: Bug
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
>Priority: Minor
> Attachments: AMBARI-20260.patch
>
>
> Misc ERRORs in Ambari Server log:
> {noformat}
> 27 Feb 2017 21:06:07,574 ERROR [ambari-heartbeat-processor-0] 
> StackVersionListener:128 - ServiceComponent DRUID_BROKER doesn't advertise 
> version, however ServiceHostComponent DRUID_BROKER on host 
> alejandro-3.c.pramod-thangali.internal advertised version as 2.6.0.0-559. 
> Skipping version update
> 27 Feb 2017 21:06:09,568 ERROR [ambari-heartbeat-processor-0] 
> StackVersionListener:128 - ServiceComponent DRUID_COORDINATOR doesn't 
> advertise version, however ServiceHostComponent DRUID_COORDINATOR on host 
> alejandro-3.c.pramod-thangali.internal advertised version as 2.6.0.0-559. 
> Skipping version update
> 27 Feb 2017 21:06:10,570 ERROR [ambari-heartbeat-processor-0] 
> StackVersionListener:128 - ServiceComponent DRUID_HISTORICAL doesn't 
> advertise version, however ServiceHostComponent DRUID_HISTORICAL on host 
> alejandro-3.c.pramod-thangali.internal advertised version as 2.6.0.0-559. 
> Skipping version update
> 27 Feb 2017 21:06:11,580 ERROR [ambari-heartbeat-processor-0] 
> StackVersionListener:128 - ServiceComponent DRUID_MIDDLEMANAGER doesn't 
> advertise version, however ServiceHostComponent DRUID_MIDDLEMANAGER on host 
> alejandro-3.c.pramod-thangali.internal advertised version as 2.6.0.0-559. 
> Skipping version update
> 27 Feb 2017 21:06:13,570 ERROR [ambari-heartbeat-processor-0] 
> StackVersionListener:128 - ServiceComponent DRUID_OVERLORD doesn't advertise 
> version, however ServiceHostComponent DRUID_OVERLORD on host 
> alejandro-3.c.pramod-thangali.internal advertised version as 2.6.0.0-559. 
> Skipping version update
> 27 Feb 2017 21:06:14,611 ERROR [ambari-heartbeat-processor-0] 
> StackVersionListener:128 - ServiceComponent DRUID_ROUTER doesn't advertise 
> version, however ServiceHostComponent DRUID_ROUTER on host 
> alejandro-3.c.pramod-thangali.internal advertised version as 2.6.0.0-559. 
> Skipping version update
> 27 Feb 2017 21:06:15,589 ERROR [ambari-heartbeat-processor-0] 
> StackVersionListener:128 - ServiceComponent DRUID_SUPERSET doesn't advertise 
> version, however ServiceHostComponent DRUID_SUPERSET on host 
> alejandro-3.c.pramod-thangali.internal advertised version as 2.6.0.0-559. 
> Skipping version update
> ERROR [ambari-client-thread-33] ClusterImpl:2882 - No service found for 
> config types '[cluster-env]', service config version not created
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-20260) Misc errors in Ambari Server log that need to be cleaned up

[Jayush Luniya (JIRA)]

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

Jayush Luniya commented on AMBARI-20260:


[~afernandez] [~sumitmohanty] can you review the patch?

> Misc errors in Ambari Server log that need to be cleaned up
> ---
>
> Key: AMBARI-20260
> URL: https://issues.apache.org/jira/browse/AMBARI-20260
> Project: Ambari
>  Issue Type: Bug
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
>Priority: Minor
> Attachments: AMBARI-20260.patch
>
>
> Misc ERRORs in Ambari Server log:
> {noformat}
> 27 Feb 2017 21:06:07,574 ERROR [ambari-heartbeat-processor-0] 
> StackVersionListener:128 - ServiceComponent DRUID_BROKER doesn't advertise 
> version, however ServiceHostComponent DRUID_BROKER on host 
> alejandro-3.c.pramod-thangali.internal advertised version as 2.6.0.0-559. 
> Skipping version update
> 27 Feb 2017 21:06:09,568 ERROR [ambari-heartbeat-processor-0] 
> StackVersionListener:128 - ServiceComponent DRUID_COORDINATOR doesn't 
> advertise version, however ServiceHostComponent DRUID_COORDINATOR on host 
> alejandro-3.c.pramod-thangali.internal advertised version as 2.6.0.0-559. 
> Skipping version update
> 27 Feb 2017 21:06:10,570 ERROR [ambari-heartbeat-processor-0] 
> StackVersionListener:128 - ServiceComponent DRUID_HISTORICAL doesn't 
> advertise version, however ServiceHostComponent DRUID_HISTORICAL on host 
> alejandro-3.c.pramod-thangali.internal advertised version as 2.6.0.0-559. 
> Skipping version update
> 27 Feb 2017 21:06:11,580 ERROR [ambari-heartbeat-processor-0] 
> StackVersionListener:128 - ServiceComponent DRUID_MIDDLEMANAGER doesn't 
> advertise version, however ServiceHostComponent DRUID_MIDDLEMANAGER on host 
> alejandro-3.c.pramod-thangali.internal advertised version as 2.6.0.0-559. 
> Skipping version update
> 27 Feb 2017 21:06:13,570 ERROR [ambari-heartbeat-processor-0] 
> StackVersionListener:128 - ServiceComponent DRUID_OVERLORD doesn't advertise 
> version, however ServiceHostComponent DRUID_OVERLORD on host 
> alejandro-3.c.pramod-thangali.internal advertised version as 2.6.0.0-559. 
> Skipping version update
> 27 Feb 2017 21:06:14,611 ERROR [ambari-heartbeat-processor-0] 
> StackVersionListener:128 - ServiceComponent DRUID_ROUTER doesn't advertise 
> version, however ServiceHostComponent DRUID_ROUTER on host 
> alejandro-3.c.pramod-thangali.internal advertised version as 2.6.0.0-559. 
> Skipping version update
> 27 Feb 2017 21:06:15,589 ERROR [ambari-heartbeat-processor-0] 
> StackVersionListener:128 - ServiceComponent DRUID_SUPERSET doesn't advertise 
> version, however ServiceHostComponent DRUID_SUPERSET on host 
> alejandro-3.c.pramod-thangali.internal advertised version as 2.6.0.0-559. 
> Skipping version update
> ERROR [ambari-client-thread-33] ClusterImpl:2882 - No service found for 
> config types '[cluster-env]', service config version not created
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-20260) Misc errors in Ambari Server log that need to be cleaned up

[Jayush Luniya (JIRA)]

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

Jayush Luniya updated AMBARI-20260:
---
Status: Patch Available  (was: In Progress)

> Misc errors in Ambari Server log that need to be cleaned up
> ---
>
> Key: AMBARI-20260
> URL: https://issues.apache.org/jira/browse/AMBARI-20260
> Project: Ambari
>  Issue Type: Bug
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
>Priority: Minor
> Attachments: AMBARI-20260.patch
>
>
> Misc ERRORs in Ambari Server log:
> {noformat}
> 27 Feb 2017 21:06:07,574 ERROR [ambari-heartbeat-processor-0] 
> StackVersionListener:128 - ServiceComponent DRUID_BROKER doesn't advertise 
> version, however ServiceHostComponent DRUID_BROKER on host 
> alejandro-3.c.pramod-thangali.internal advertised version as 2.6.0.0-559. 
> Skipping version update
> 27 Feb 2017 21:06:09,568 ERROR [ambari-heartbeat-processor-0] 
> StackVersionListener:128 - ServiceComponent DRUID_COORDINATOR doesn't 
> advertise version, however ServiceHostComponent DRUID_COORDINATOR on host 
> alejandro-3.c.pramod-thangali.internal advertised version as 2.6.0.0-559. 
> Skipping version update
> 27 Feb 2017 21:06:10,570 ERROR [ambari-heartbeat-processor-0] 
> StackVersionListener:128 - ServiceComponent DRUID_HISTORICAL doesn't 
> advertise version, however ServiceHostComponent DRUID_HISTORICAL on host 
> alejandro-3.c.pramod-thangali.internal advertised version as 2.6.0.0-559. 
> Skipping version update
> 27 Feb 2017 21:06:11,580 ERROR [ambari-heartbeat-processor-0] 
> StackVersionListener:128 - ServiceComponent DRUID_MIDDLEMANAGER doesn't 
> advertise version, however ServiceHostComponent DRUID_MIDDLEMANAGER on host 
> alejandro-3.c.pramod-thangali.internal advertised version as 2.6.0.0-559. 
> Skipping version update
> 27 Feb 2017 21:06:13,570 ERROR [ambari-heartbeat-processor-0] 
> StackVersionListener:128 - ServiceComponent DRUID_OVERLORD doesn't advertise 
> version, however ServiceHostComponent DRUID_OVERLORD on host 
> alejandro-3.c.pramod-thangali.internal advertised version as 2.6.0.0-559. 
> Skipping version update
> 27 Feb 2017 21:06:14,611 ERROR [ambari-heartbeat-processor-0] 
> StackVersionListener:128 - ServiceComponent DRUID_ROUTER doesn't advertise 
> version, however ServiceHostComponent DRUID_ROUTER on host 
> alejandro-3.c.pramod-thangali.internal advertised version as 2.6.0.0-559. 
> Skipping version update
> 27 Feb 2017 21:06:15,589 ERROR [ambari-heartbeat-processor-0] 
> StackVersionListener:128 - ServiceComponent DRUID_SUPERSET doesn't advertise 
> version, however ServiceHostComponent DRUID_SUPERSET on host 
> alejandro-3.c.pramod-thangali.internal advertised version as 2.6.0.0-559. 
> Skipping version update
> ERROR [ambari-client-thread-33] ClusterImpl:2882 - No service found for 
> config types '[cluster-env]', service config version not created
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-20260) Misc errors in Ambari Server log that need to be cleaned up

[Jayush Luniya (JIRA)]

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

Jayush Luniya updated AMBARI-20260:
---
Summary: Misc errors in Ambari Server log that need to be cleaned up  (was: 
0 Misc errors in Ambari Server log that need to be cleaned up)

> Misc errors in Ambari Server log that need to be cleaned up
> ---
>
> Key: AMBARI-20260
> URL: https://issues.apache.org/jira/browse/AMBARI-20260
> Project: Ambari
>  Issue Type: Bug
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
>Priority: Minor
>
> Misc ERRORs in Ambari Server log:
> {noformat}
> 27 Feb 2017 21:06:07,574 ERROR [ambari-heartbeat-processor-0] 
> StackVersionListener:128 - ServiceComponent DRUID_BROKER doesn't advertise 
> version, however ServiceHostComponent DRUID_BROKER on host 
> alejandro-3.c.pramod-thangali.internal advertised version as 2.6.0.0-559. 
> Skipping version update
> 27 Feb 2017 21:06:09,568 ERROR [ambari-heartbeat-processor-0] 
> StackVersionListener:128 - ServiceComponent DRUID_COORDINATOR doesn't 
> advertise version, however ServiceHostComponent DRUID_COORDINATOR on host 
> alejandro-3.c.pramod-thangali.internal advertised version as 2.6.0.0-559. 
> Skipping version update
> 27 Feb 2017 21:06:10,570 ERROR [ambari-heartbeat-processor-0] 
> StackVersionListener:128 - ServiceComponent DRUID_HISTORICAL doesn't 
> advertise version, however ServiceHostComponent DRUID_HISTORICAL on host 
> alejandro-3.c.pramod-thangali.internal advertised version as 2.6.0.0-559. 
> Skipping version update
> 27 Feb 2017 21:06:11,580 ERROR [ambari-heartbeat-processor-0] 
> StackVersionListener:128 - ServiceComponent DRUID_MIDDLEMANAGER doesn't 
> advertise version, however ServiceHostComponent DRUID_MIDDLEMANAGER on host 
> alejandro-3.c.pramod-thangali.internal advertised version as 2.6.0.0-559. 
> Skipping version update
> 27 Feb 2017 21:06:13,570 ERROR [ambari-heartbeat-processor-0] 
> StackVersionListener:128 - ServiceComponent DRUID_OVERLORD doesn't advertise 
> version, however ServiceHostComponent DRUID_OVERLORD on host 
> alejandro-3.c.pramod-thangali.internal advertised version as 2.6.0.0-559. 
> Skipping version update
> 27 Feb 2017 21:06:14,611 ERROR [ambari-heartbeat-processor-0] 
> StackVersionListener:128 - ServiceComponent DRUID_ROUTER doesn't advertise 
> version, however ServiceHostComponent DRUID_ROUTER on host 
> alejandro-3.c.pramod-thangali.internal advertised version as 2.6.0.0-559. 
> Skipping version update
> 27 Feb 2017 21:06:15,589 ERROR [ambari-heartbeat-processor-0] 
> StackVersionListener:128 - ServiceComponent DRUID_SUPERSET doesn't advertise 
> version, however ServiceHostComponent DRUID_SUPERSET on host 
> alejandro-3.c.pramod-thangali.internal advertised version as 2.6.0.0-559. 
> Skipping version update
> ERROR [ambari-client-thread-33] ClusterImpl:2882 - No service found for 
> config types '[cluster-env]', service config version not created
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (AMBARI-20260) 0 Misc errors in Ambari Server log that need to be cleaned up

[Jayush Luniya (JIRA)]

Jayush Luniya created AMBARI-20260:
--

 Summary: 0 Misc errors in Ambari Server log that need to be 
cleaned up
 Key: AMBARI-20260
 URL: https://issues.apache.org/jira/browse/AMBARI-20260
 Project: Ambari
  Issue Type: Bug
Reporter: Jayush Luniya
Assignee: Jayush Luniya
Priority: Minor


Misc ERRORs in Ambari Server log:
{noformat}
27 Feb 2017 21:06:07,574 ERROR [ambari-heartbeat-processor-0] 
StackVersionListener:128 - ServiceComponent DRUID_BROKER doesn't advertise 
version, however ServiceHostComponent DRUID_BROKER on host 
alejandro-3.c.pramod-thangali.internal advertised version as 2.6.0.0-559. 
Skipping version update
27 Feb 2017 21:06:09,568 ERROR [ambari-heartbeat-processor-0] 
StackVersionListener:128 - ServiceComponent DRUID_COORDINATOR doesn't advertise 
version, however ServiceHostComponent DRUID_COORDINATOR on host 
alejandro-3.c.pramod-thangali.internal advertised version as 2.6.0.0-559. 
Skipping version update
27 Feb 2017 21:06:10,570 ERROR [ambari-heartbeat-processor-0] 
StackVersionListener:128 - ServiceComponent DRUID_HISTORICAL doesn't advertise 
version, however ServiceHostComponent DRUID_HISTORICAL on host 
alejandro-3.c.pramod-thangali.internal advertised version as 2.6.0.0-559. 
Skipping version update
27 Feb 2017 21:06:11,580 ERROR [ambari-heartbeat-processor-0] 
StackVersionListener:128 - ServiceComponent DRUID_MIDDLEMANAGER doesn't 
advertise version, however ServiceHostComponent DRUID_MIDDLEMANAGER on host 
alejandro-3.c.pramod-thangali.internal advertised version as 2.6.0.0-559. 
Skipping version update
27 Feb 2017 21:06:13,570 ERROR [ambari-heartbeat-processor-0] 
StackVersionListener:128 - ServiceComponent DRUID_OVERLORD doesn't advertise 
version, however ServiceHostComponent DRUID_OVERLORD on host 
alejandro-3.c.pramod-thangali.internal advertised version as 2.6.0.0-559. 
Skipping version update
27 Feb 2017 21:06:14,611 ERROR [ambari-heartbeat-processor-0] 
StackVersionListener:128 - ServiceComponent DRUID_ROUTER doesn't advertise 
version, however ServiceHostComponent DRUID_ROUTER on host 
alejandro-3.c.pramod-thangali.internal advertised version as 2.6.0.0-559. 
Skipping version update
27 Feb 2017 21:06:15,589 ERROR [ambari-heartbeat-processor-0] 
StackVersionListener:128 - ServiceComponent DRUID_SUPERSET doesn't advertise 
version, however ServiceHostComponent DRUID_SUPERSET on host 
alejandro-3.c.pramod-thangali.internal advertised version as 2.6.0.0-559. 
Skipping version update


ERROR [ambari-client-thread-33] ClusterImpl:2882 - No service found for config 
types '[cluster-env]', service config version not created
{noformat}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-20113) Not able to compute the table statistics for partitioned table

[Hudson (JIRA)]

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

Hudson commented on AMBARI-20113:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6903 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6903/])
AMBARI-20113 : hive20 view : fixed : Not able to compute the table 
(nitiraj.rathore: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=a72f3dda7992aeb717fbf71401b6f60253054c41])
* (edit) 
contrib/views/hive20/src/main/java/org/apache/ambari/view/hive20/resources/browser/DDLProxy.java
* (edit) 
contrib/views/hive20/src/main/java/org/apache/ambari/view/hive20/resources/browser/DDLService.java
* (add) 
contrib/views/hive20/src/test/java/org/apache/ambari/view/hive20/internal/query/generators/AnalyzeTableQueryGeneratorSpecTest.groovy
* (edit) 
contrib/views/hive20/src/main/java/org/apache/ambari/view/hive20/internal/query/generators/AnalyzeTableQueryGenerator.java


> Not able to compute the table statistics for partitioned table
> --
>
> Key: AMBARI-20113
> URL: https://issues.apache.org/jira/browse/AMBARI-20113
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Supreeth Sharma
>Assignee: Nitiraj Singh Rathore
>Priority: Critical
>  Labels: HiveView2.0
> Fix For: 2.5.0
>
> Attachments: AMBARI-20113_branch-2.5_3.patch
>
>
> Not able to compute the table statistics for partitioned table. API to 
> compute the stat is failing with below error :
> {code}
> Error while compiling statement: FAILED: SemanticException [Error 10115]: 
> Table is partitioned and partition specification is needed
> {code}
> Attaching the complete stack trace.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-20113) Not able to compute the table statistics for partitioned table

[Hudson (JIRA)]

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

Hudson commented on AMBARI-20113:
-

SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1143 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/1143/])
AMBARI-20113 : hive20 view : fixed : Not able to compute the table 
(nitiraj.rathore: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=457b7635c6f0242ae108626c15168dd8196c1a17])
* (add) 
contrib/views/hive20/src/test/java/org/apache/ambari/view/hive20/internal/query/generators/AnalyzeTableQueryGeneratorSpecTest.groovy
* (edit) 
contrib/views/hive20/src/main/java/org/apache/ambari/view/hive20/resources/browser/DDLProxy.java
* (edit) 
contrib/views/hive20/src/main/java/org/apache/ambari/view/hive20/internal/query/generators/AnalyzeTableQueryGenerator.java
* (edit) 
contrib/views/hive20/src/main/java/org/apache/ambari/view/hive20/resources/browser/DDLService.java


> Not able to compute the table statistics for partitioned table
> --
>
> Key: AMBARI-20113
> URL: https://issues.apache.org/jira/browse/AMBARI-20113
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Supreeth Sharma
>Assignee: Nitiraj Singh Rathore
>Priority: Critical
>  Labels: HiveView2.0
> Fix For: 2.5.0
>
> Attachments: AMBARI-20113_branch-2.5_3.patch
>
>
> Not able to compute the table statistics for partitioned table. API to 
> compute the stat is failing with below error :
> {code}
> Error while compiling statement: FAILED: SemanticException [Error 10115]: 
> Table is partitioned and partition specification is needed
> {code}
> Attaching the complete stack trace.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-20259) Superset not able to start on Ubuntu if ASCII encoding is set as default encoding

[Nishant Bangarwa (JIRA)]

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

Nishant Bangarwa updated AMBARI-20259:
--
Status: Patch Available  (was: Open)

> Superset not able to start on Ubuntu if ASCII encoding is set as default 
> encoding
> -
>
> Key: AMBARI-20259
> URL: https://issues.apache.org/jira/browse/AMBARI-20259
> Project: Ambari
>  Issue Type: Bug
>Reporter: Nishant Bangarwa
>Assignee: Nishant Bangarwa
> Fix For: trunk, 2.5.0
>
> Attachments: ambari-20259.patch
>
>
> RuntimeError: Click will abort further execution because Python 3 was 
> configured to use ASCII as encoding for the environment.  Consult 
> http://click.pocoo.org/python3/for mitigation steps.
> This system supports the C.UTF-8 locale which is recommended.
> You might be able to resolve your issue by exporting the
> following environment variables:
> export LC_ALL=C.UTF-8
> export LANG=C.UTF-8



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-20259) Superset not able to start on Ubuntu if ASCII encoding is set as default encoding

[Nishant Bangarwa (JIRA)]

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

Nishant Bangarwa updated AMBARI-20259:
--
Attachment: ambari-20259.patch

> Superset not able to start on Ubuntu if ASCII encoding is set as default 
> encoding
> -
>
> Key: AMBARI-20259
> URL: https://issues.apache.org/jira/browse/AMBARI-20259
> Project: Ambari
>  Issue Type: Bug
>Reporter: Nishant Bangarwa
>Assignee: Nishant Bangarwa
> Fix For: trunk, 2.5.0
>
> Attachments: ambari-20259.patch
>
>
> RuntimeError: Click will abort further execution because Python 3 was 
> configured to use ASCII as encoding for the environment.  Consult 
> http://click.pocoo.org/python3/for mitigation steps.
> This system supports the C.UTF-8 locale which is recommended.
> You might be able to resolve your issue by exporting the
> following environment variables:
> export LC_ALL=C.UTF-8
> export LANG=C.UTF-8



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-20181) HiveView2.0: Can not create a table with space in column name with upload table feature

[Nitiraj Singh Rathore (JIRA)]

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

Nitiraj Singh Rathore updated AMBARI-20181:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

committed patch to branch-2.5 and trunk

> HiveView2.0: Can not create a table with space in column name with upload 
> table feature
> ---
>
> Key: AMBARI-20181
> URL: https://issues.apache.org/jira/browse/AMBARI-20181
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Yesha Vora
>Assignee: Nitiraj Singh Rathore
>Priority: Critical
> Attachments: AMBARI-20181_branch-2.5_2.patch
>
>
> Scenario:
> * Go to HiveView
> * Go to table tab
> * Click on Upload table
> * Upload a CSV file such that it column name has a space in it. 
> * Click on create table.
> The table creation failed because it does not add `` in the column name where 
> it has space or other special chars. 
> Currently, table creation is failing with below error.
> {code}
> org.apache.hive.service.cli.HiveSQLException: Error while compiling 
> statement: FAILED: SemanticException [Error 10004]: Line 1:56 Invalid table 
> alias or column reference 'Issue': (possible column names are: summary, issue 
> key, issue id, parent id, issue type, status, project key, project name, 
> project type, project lead, project description, project url, priority, 
> resolution, assignee, reporter, creator, affects version, fix versions, 
> component, labels){code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-20181) HiveView2.0: Can not create a table with space in column name with upload table feature

[Nitiraj Singh Rathore (JIRA)]

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

Nitiraj Singh Rathore updated AMBARI-20181:
---
Attachment: (was: AMBARI-20181_branch-2.5.patch)

> HiveView2.0: Can not create a table with space in column name with upload 
> table feature
> ---
>
> Key: AMBARI-20181
> URL: https://issues.apache.org/jira/browse/AMBARI-20181
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Yesha Vora
>Assignee: Nitiraj Singh Rathore
>Priority: Critical
> Attachments: AMBARI-20181_branch-2.5_2.patch
>
>
> Scenario:
> * Go to HiveView
> * Go to table tab
> * Click on Upload table
> * Upload a CSV file such that it column name has a space in it. 
> * Click on create table.
> The table creation failed because it does not add `` in the column name where 
> it has space or other special chars. 
> Currently, table creation is failing with below error.
> {code}
> org.apache.hive.service.cli.HiveSQLException: Error while compiling 
> statement: FAILED: SemanticException [Error 10004]: Line 1:56 Invalid table 
> alias or column reference 'Issue': (possible column names are: summary, issue 
> key, issue id, parent id, issue type, status, project key, project name, 
> project type, project lead, project description, project url, priority, 
> resolution, assignee, reporter, creator, affects version, fix versions, 
> component, labels){code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-20181) HiveView2.0: Can not create a table with space in column name with upload table feature

[Nitiraj Singh Rathore (JIRA)]

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

Nitiraj Singh Rathore updated AMBARI-20181:
---
Attachment: AMBARI-20181_branch-2.5_2.patch

update patch to remove conflicts

> HiveView2.0: Can not create a table with space in column name with upload 
> table feature
> ---
>
> Key: AMBARI-20181
> URL: https://issues.apache.org/jira/browse/AMBARI-20181
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Yesha Vora
>Assignee: Nitiraj Singh Rathore
>Priority: Critical
> Attachments: AMBARI-20181_branch-2.5_2.patch, 
> AMBARI-20181_branch-2.5.patch
>
>
> Scenario:
> * Go to HiveView
> * Go to table tab
> * Click on Upload table
> * Upload a CSV file such that it column name has a space in it. 
> * Click on create table.
> The table creation failed because it does not add `` in the column name where 
> it has space or other special chars. 
> Currently, table creation is failing with below error.
> {code}
> org.apache.hive.service.cli.HiveSQLException: Error while compiling 
> statement: FAILED: SemanticException [Error 10004]: Line 1:56 Invalid table 
> alias or column reference 'Issue': (possible column names are: summary, issue 
> key, issue id, parent id, issue type, status, project key, project name, 
> project type, project lead, project description, project url, priority, 
> resolution, assignee, reporter, creator, affects version, fix versions, 
> component, labels){code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)