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

Quanlong Huang commented on IMPALA-14155:
-----------------------------------------

The ERROR logs also explain why the SLF4J logs are missing:
{noformat}
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further 
details.{noformat}
This is not a problem with Apache Hive 3. When building on the default CDP Hive 
version, we still hit this issue if using awssdk bundle-2.24.6.jar. Reproduced 
it this way:
{noformat}
mvn dependency:get -Dartifact=software.amazon.awssdk:bundle:2.24.6
vim fe/target/build-classpath.txt
# Replace "awssdk/bundle/2.23.5/bundle-2.23.5.jar " with 
"awssdk/bundle/2.24.6/bundle-2.24.6.jar"{noformat}
Then start Impala cluster, all the logs from SLF4j are missing.

> Missing Java logs when running on Apache Hive3
> ----------------------------------------------
>
>                 Key: IMPALA-14155
>                 URL: https://issues.apache.org/jira/browse/IMPALA-14155
>             Project: IMPALA
>          Issue Type: Bug
>            Reporter: Quanlong Huang
>            Assignee: Quanlong Huang
>            Priority: Major
>
> When building on Apache Hive 3.1.3 (i.e. USE_APACHE_COMPONENTS=true), 
> catalogd and impalad logs are missing almost all the Java logs. The only log 
> of the Java codes is
> {code}
> I20250616 00:31:31.442186 626874 GlogAppender.java:140] Logging 
> (re)initialized. Impala: VLOG, All other: INFO{code}
> Some tests failed due to this, e.g. 
> tests/custom_cluster/test_local_catalog.py::TestLocalCatalogCompactUpdates::test_restart_catalogd
> Note that C++ logs are shown as expected.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to