You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@impala.apache.org by "Tim Armstrong (JIRA)" <ji...@apache.org> on 2018/11/02 23:57:00 UTC

[jira] [Resolved] (IMPALA-4713) Java backtrace should be logged for all frontend errors

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

Tim Armstrong resolved IMPALA-4713.
-----------------------------------
    Resolution: Won't Fix

I think this is currently too vague to be useful. I think this specific bug might have been because the JVM doesn't always create stack traces for NPE: https://stackoverflow.com/questions/2411487/nullpointerexception-in-java-with-no-stacktrace

Anyway, we should file JIRAs for more specific issues as we encounter them.

> Java backtrace should be logged for all frontend errors
> -------------------------------------------------------
>
>                 Key: IMPALA-4713
>                 URL: https://issues.apache.org/jira/browse/IMPALA-4713
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Frontend
>    Affects Versions: Impala 2.6.0
>            Reporter: Tim Armstrong
>            Priority: Major
>              Labels: ramp-up, supportability
>
> I'm trying to debug failure queries where an IllegalStateException is thrown wrapping a NullPointerException from an "invalidate metadata <table>" query.
> The error message shows up in impala-shell but it doesn't appear that the Java backtrace is logged anywhere in the logs. This makes it impossible to determine where the NPE has come from.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)