[
https://issues.apache.org/jira/browse/IMPALA-10094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17188765#comment-17188765
]
Joe McDonnell commented on IMPALA-10094:
----------------------------------------
[~vihangk1] It is a long-standing thing from the prehistory (years and years
ago) when s3 support was limited. We just haven't done the work to get the
tests enabled and working on s3, etc. We should do this.
> TestResetMetadata.test_refresh_updated_partitions fails due to connection
> error
> -------------------------------------------------------------------------------
>
> Key: IMPALA-10094
> URL: https://issues.apache.org/jira/browse/IMPALA-10094
> Project: IMPALA
> Issue Type: Bug
> Reporter: Norbert Luksa
> Assignee: Vihang Karajgaonkar
> Priority: Major
>
> This has occurred in the last few builds in
> impala-cdpd-master-staging-core-s3:
> [https://master-02.jenkins.cloudera.com/job/impala-cdpd-master-staging-core-s3/14/]
> Error message:
> {code:java}
> metadata/test_reset_metadata.py:49: in test_refresh_updated_partitions
> "alter table {0} add partition (year=2020, month=8)".format(tbl))
> common/impala_test_suite.py:983: in run_stmt_in_hive
> raise RuntimeError(stderr)
> E RuntimeError: SLF4J: Class path contains multiple SLF4J bindings.
> E SLF4J: Found binding in
> [jar:file:/data0/jenkins/workspace/impala-cdpd-master-staging-core-s3/Impala-Toolchain/cdp_components-5250295/apache-hive-3.1.3000.7.2.2.0-135-bin/lib/log4j-slf4j-impl-2.10.0.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> E SLF4J: Found binding in
> [jar:file:/data0/jenkins/workspace/impala-cdpd-master-staging-core-s3/Impala-Toolchain/cdp_components-5250295/hadoop-3.1.1.7.2.2.0-135/share/hadoop/common/lib/slf4j-log4j12-1.7.30.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> E SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an
> explanation.
> E SLF4J: Actual binding is of type
> [org.apache.logging.slf4j.Log4jLoggerFactory]
> E ERROR StatusLogger No log4j2 configuration file found. Using default
> configuration: logging only errors to the console. Set system property
> 'log4j2.debug' to show Log4j2 internal initialization logging.
> E SLF4J: Class path contains multiple SLF4J bindings.
> E SLF4J: Found binding in
> [jar:file:/data0/jenkins/workspace/impala-cdpd-master-staging-core-s3/Impala-Toolchain/cdp_components-5250295/apache-hive-3.1.3000.7.2.2.0-135-bin/lib/log4j-slf4j-impl-2.10.0.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> E SLF4J: Found binding in
> [jar:file:/data0/jenkins/workspace/impala-cdpd-master-staging-core-s3/Impala-Toolchain/cdp_components-5250295/hadoop-3.1.1.7.2.2.0-135/share/hadoop/common/lib/slf4j-log4j12-1.7.30.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> E SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an
> explanation.
> E SLF4J: Actual binding is of type
> [org.apache.logging.slf4j.Log4jLoggerFactory]
> E Connecting to jdbc:hive2://localhost:11050
> E 20/08/18 05:10:24 [main]: WARN jdbc.HiveConnection: Failed to connect to
> localhost:11050
> E Could not open connection to the HS2 server. Please check the server URI
> and if the URI is correct, then ask the administrator to check the server
> status.
> E Error: Could not open client transport with JDBC Uri:
> jdbc:hive2://localhost:11050: java.net.ConnectException: Connection refused
> (Connection refused) (state=08S01,code=0){code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
