[jira] [Comment Edited] (AMBARI-25371) Ambari v2.7.3
[
https://issues.apache.org/jira/browse/AMBARI-25371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17071046#comment-17071046
]
Hakan Damar edited comment on AMBARI-25371 at 3/30/20, 2:53 PM:
I tested in v2.7.5 and problem is still exists.
I try to build in docker container. (Centos 7)
{code:java}
System info:
Bower version: 1.3.8
Node version: 4.5.0
OS: Linux 4.9.0-12-amd64 x64
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] Ambari Main 2.7.5.0.0 .. SUCCESS [ 3.911 s]
[INFO] Apache Ambari Project POM 2.7.5.0.0 SUCCESS [ 0.174 s]
[INFO] Ambari Web 2.7.5.0.0 ... SUCCESS [ 57.985 s]
[INFO] Ambari Views 2.7.5.0.0 . SUCCESS [ 1.078 s]
[INFO] Ambari Admin View 2.7.5.0.0 FAILURE [ 5.349 s]
[INFO] ambari-utility 1.0.0.0-SNAPSHOT SKIPPED
[INFO] ambari-metrics 2.7.5.0.0 ... SKIPPED
[INFO] Ambari Metrics Common 2.7.5.0.0 SKIPPED
[INFO] Ambari Metrics Hadoop Sink 2.7.5.0.0 ... SKIPPED
[INFO] Ambari Metrics Flume Sink 2.7.5.0.0 SKIPPED
[INFO] Ambari Metrics Kafka Sink 2.7.5.0.0 SKIPPED
[INFO] Ambari Metrics Storm Sink 2.7.5.0.0 SKIPPED
[INFO] Ambari Metrics Storm Sink (Legacy) 2.7.5.0.0 ... SKIPPED
[INFO] Ambari Metrics Collector 2.7.5.0.0 . SKIPPED
[INFO] Ambari Metrics Monitor 2.7.5.0.0 ... SKIPPED
[INFO] Ambari Metrics Grafana 2.7.5.0.0 ... SKIPPED
[INFO] Ambari Metrics Host Aggregator 2.7.5.0.0 ... SKIPPED
[INFO] Ambari Metrics Assembly 2.7.5.0.0 .. SKIPPED
[INFO] Ambari Service Advisor 1.0.0.0-SNAPSHOT SKIPPED
[INFO] Ambari Server 2.7.5.0.0 SKIPPED
[INFO] Ambari Functional Tests 2.7.5.0.0 .. SKIPPED
[INFO] Ambari Agent 2.7.5.0.0 . SKIPPED
[INFO] ambari-logsearch 2.7.5.0.0 . SKIPPED
[INFO] Ambari Logsearch Appender 2.7.5.0.0 SKIPPED
[INFO] Ambari Logsearch Config Api 2.7.5.0.0 .. SKIPPED
[INFO] Ambari Logsearch Config JSON 2.7.5.0.0 . SKIPPED
[INFO] Ambari Logsearch Config Solr 2.7.5.0.0 . SKIPPED
[INFO] Ambari Logsearch Config Zookeeper 2.7.5.0.0 SKIPPED
[INFO] Ambari Logsearch Config Local 2.7.5.0.0 SKIPPED
[INFO] Ambari Logsearch Log Feeder Plugin Api 2.7.5.0.0 ... SKIPPED
[INFO] Ambari Logsearch Log Feeder Container Registry 2.7.5.0.0 SKIPPED
[INFO] Ambari Logsearch Log Feeder 2.7.5.0.0 .. SKIPPED
[INFO] Ambari Logsearch Web 2.7.5.0.0 . SKIPPED
[INFO] Ambari Logsearch Server 2.7.5.0.0 .. SKIPPED
[INFO] Ambari Logsearch Assembly 2.7.5.0.0 SKIPPED
[INFO] Ambari Logsearch Integration Test 2.7.5.0.0 SKIPPED
[INFO] ambari-infra 2.7.5.0.0 . SKIPPED
[INFO] Ambari Infra Solr Client 2.7.5.0.0 . SKIPPED
[INFO] Ambari Infra Solr Plugin 2.7.5.0.0 . SKIPPED
[INFO] Ambari Infra Manager 2.7.5.0.0 . SKIPPED
[INFO] Ambari Infra Assembly 2.7.5.0.0 SKIPPED
[INFO] Ambari Infra Manager Integration Tests 2.7.5.0.0 ... SKIPPED
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 01:08 min
[INFO] Finished at: 2020-03-30T14:43:10Z
[INFO]
[ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec
(Bower install) on project ambari-admin: Command execution failed. Process
exited with an error: 1 (Exit value: 1) -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please
read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn -rf :ambari-admin
[root@3b81611c8517 apache-ambari-2.7.5-src]# mvn --version
Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)
Maven home: /opt/maven
Java version: 1.8.0_242, vendor: Oracle Corporation, runtime:
/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.242.b08-0.el7_7.x86_64/jre
Default locale: en_US, platform encoding: ANSI_X3.4-1968
OS name: "linux", version: "4.9.0-12-amd64", arch: "amd64", family: "unix"
{code}
was (Author: hakand):
I tested in v2.7.5
[jira] [Commented] (AMBARI-25371) Ambari v2.7.3
[
https://issues.apache.org/jira/browse/AMBARI-25371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17071046#comment-17071046
]
Hakan Damar commented on AMBARI-25371:
--
I tested in v2.7.5 and problem is still exists.
{code:java}
System info:
Bower version: 1.3.8
Node version: 4.5.0
OS: Linux 4.9.0-12-amd64 x64
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] Ambari Main 2.7.5.0.0 .. SUCCESS [ 3.911 s]
[INFO] Apache Ambari Project POM 2.7.5.0.0 SUCCESS [ 0.174 s]
[INFO] Ambari Web 2.7.5.0.0 ... SUCCESS [ 57.985 s]
[INFO] Ambari Views 2.7.5.0.0 . SUCCESS [ 1.078 s]
[INFO] Ambari Admin View 2.7.5.0.0 FAILURE [ 5.349 s]
[INFO] ambari-utility 1.0.0.0-SNAPSHOT SKIPPED
[INFO] ambari-metrics 2.7.5.0.0 ... SKIPPED
[INFO] Ambari Metrics Common 2.7.5.0.0 SKIPPED
[INFO] Ambari Metrics Hadoop Sink 2.7.5.0.0 ... SKIPPED
[INFO] Ambari Metrics Flume Sink 2.7.5.0.0 SKIPPED
[INFO] Ambari Metrics Kafka Sink 2.7.5.0.0 SKIPPED
[INFO] Ambari Metrics Storm Sink 2.7.5.0.0 SKIPPED
[INFO] Ambari Metrics Storm Sink (Legacy) 2.7.5.0.0 ... SKIPPED
[INFO] Ambari Metrics Collector 2.7.5.0.0 . SKIPPED
[INFO] Ambari Metrics Monitor 2.7.5.0.0 ... SKIPPED
[INFO] Ambari Metrics Grafana 2.7.5.0.0 ... SKIPPED
[INFO] Ambari Metrics Host Aggregator 2.7.5.0.0 ... SKIPPED
[INFO] Ambari Metrics Assembly 2.7.5.0.0 .. SKIPPED
[INFO] Ambari Service Advisor 1.0.0.0-SNAPSHOT SKIPPED
[INFO] Ambari Server 2.7.5.0.0 SKIPPED
[INFO] Ambari Functional Tests 2.7.5.0.0 .. SKIPPED
[INFO] Ambari Agent 2.7.5.0.0 . SKIPPED
[INFO] ambari-logsearch 2.7.5.0.0 . SKIPPED
[INFO] Ambari Logsearch Appender 2.7.5.0.0 SKIPPED
[INFO] Ambari Logsearch Config Api 2.7.5.0.0 .. SKIPPED
[INFO] Ambari Logsearch Config JSON 2.7.5.0.0 . SKIPPED
[INFO] Ambari Logsearch Config Solr 2.7.5.0.0 . SKIPPED
[INFO] Ambari Logsearch Config Zookeeper 2.7.5.0.0 SKIPPED
[INFO] Ambari Logsearch Config Local 2.7.5.0.0 SKIPPED
[INFO] Ambari Logsearch Log Feeder Plugin Api 2.7.5.0.0 ... SKIPPED
[INFO] Ambari Logsearch Log Feeder Container Registry 2.7.5.0.0 SKIPPED
[INFO] Ambari Logsearch Log Feeder 2.7.5.0.0 .. SKIPPED
[INFO] Ambari Logsearch Web 2.7.5.0.0 . SKIPPED
[INFO] Ambari Logsearch Server 2.7.5.0.0 .. SKIPPED
[INFO] Ambari Logsearch Assembly 2.7.5.0.0 SKIPPED
[INFO] Ambari Logsearch Integration Test 2.7.5.0.0 SKIPPED
[INFO] ambari-infra 2.7.5.0.0 . SKIPPED
[INFO] Ambari Infra Solr Client 2.7.5.0.0 . SKIPPED
[INFO] Ambari Infra Solr Plugin 2.7.5.0.0 . SKIPPED
[INFO] Ambari Infra Manager 2.7.5.0.0 . SKIPPED
[INFO] Ambari Infra Assembly 2.7.5.0.0 SKIPPED
[INFO] Ambari Infra Manager Integration Tests 2.7.5.0.0 ... SKIPPED
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 01:08 min
[INFO] Finished at: 2020-03-30T14:43:10Z
[INFO]
[ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec
(Bower install) on project ambari-admin: Command execution failed. Process
exited with an error: 1 (Exit value: 1) -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please
read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn -rf :ambari-admin
[root@3b81611c8517 apache-ambari-2.7.5-src]# mvn --version
Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)
Maven home: /opt/maven
Java version: 1.8.0_242, vendor: Oracle Corporation, runtime:
/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.242.b08-0.el7_7.x86_64/jre
Default locale: en_US, platform encoding: ANSI_X3.4-1968
OS name: "linux", version: "4.9.0-12-amd64", arch: "amd64", family: "unix"
{code}
> Ambari v2.7.3
> -
>
> Key: AMBARI-25371
> URL:
[jira] [Created] (AMBARI-25498) Allow the addition of HS2I nodes in HA
Johndee Burks created AMBARI-25498:
--
Summary: Allow the addition of HS2I nodes in HA
Key: AMBARI-25498
URL: https://issues.apache.org/jira/browse/AMBARI-25498
Project: Ambari
Issue Type: Improvement
Reporter: Johndee Burks
Currently there is a limitation documented
[here|https://docs.cloudera.com/HDPDocuments/HDP3/HDP-3.1.5/managing-hive/content/hive_setup_multiple_hsi.html].
That says:
"Multiple HiveServer Interactives do not work in active/passive mode unless you
set up all instances during the LLAP setup process, immediately after enabling
interactive query. Do not select {{Add HiveServer2 Interactive}} from Actions
after completing the LLAP setup. If you add an additional HiveServer
Interactive instance in the way, it will not operate in active/passive mode."
We should create this functionality.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (AMBARI-25498) Allow the addition of HS2I nodes in HA
[
https://issues.apache.org/jira/browse/AMBARI-25498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Johndee Burks updated AMBARI-25498:
---
Affects Version/s: 3.0.0
> Allow the addition of HS2I nodes in HA
> --
>
> Key: AMBARI-25498
> URL: https://issues.apache.org/jira/browse/AMBARI-25498
> Project: Ambari
> Issue Type: Improvement
>Affects Versions: 3.0.0
>Reporter: Johndee Burks
>Priority: Minor
>
> Currently there is a limitation documented
> [here|https://docs.cloudera.com/HDPDocuments/HDP3/HDP-3.1.5/managing-hive/content/hive_setup_multiple_hsi.html].
> That says:
> "Multiple HiveServer Interactives do not work in active/passive mode unless
> you set up all instances during the LLAP setup process, immediately after
> enabling interactive query. Do not select {{Add HiveServer2 Interactive}}
> from Actions after completing the LLAP setup. If you add an additional
> HiveServer Interactive instance in the way, it will not operate in
> active/passive mode."
> We should create this functionality.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
