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

2018-04-04 Thread Sergey Shelukhin (JIRA)

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

Sergey Shelukhin commented on AMBARI-20264:
---

[~jluniya] what's WE? there may be some perf bug with startup, and this is just 
sweeping it under the rug

> 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
>Priority: Major
> 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 

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

2017-03-01 Thread 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

2017-03-01 Thread 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-20264) HiveServer2 Interactive start failed after WE enable

2017-03-01 Thread 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] [Commented] (AMBARI-20264) HiveServer2 Interactive start failed after WE enable

2017-03-01 Thread 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" : 
>