[ 
https://issues.apache.org/jira/browse/IMPALA-14955?focusedWorklogId=1019063&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-1019063
 ]

ASF GitHub Bot logged work on IMPALA-14955:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 07/May/26 01:08
            Start Date: 07/May/26 01:08
    Worklog Time Spent: 10m 
      Work Description: smengcl opened a new pull request, #89:
URL: https://github.com/apache/impala/pull/89

   https://issues.apache.org/jira/browse/IMPALA-14955
   
   When an HDFS/libhdfs operation fails, Impala currently includes libhdfs root 
cause output in `GetHdfsErrorMsg()`. However, some failures, especially 
exceptions raised inside filesystem client code, need the full Java stack trace 
to identify the actual failing path.
   
   This change appends `hdfsGetLastExceptionStackTrace()` to the HDFS error 
message when libhdfs provides one.
   
   ## Motivation
   
   We hit an issue earlier due to using Ozone (HCFS):
   
   ```
   Failed to close HDFS file
   Error(255): Unknown error 255
   Root cause: ArrayIndexOutOfBoundsException
   ```
   
   but the actual Java stack trace was not captured in the query/profile error. 
Including the libhdfs stack trace would be help immensely.




Issue Time Tracking
-------------------

            Worklog Id:     (was: 1019063)
    Remaining Estimate: 0h
            Time Spent: 10m

> Include libhdfs Java stack trace in HDFS error messages
> -------------------------------------------------------
>
>                 Key: IMPALA-14955
>                 URL: https://issues.apache.org/jira/browse/IMPALA-14955
>             Project: IMPALA
>          Issue Type: Improvement
>          Components: Backend
>            Reporter: Siyao Meng
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> When an HDFS/libhdfs operation fails, Impala currently includes libhdfs root 
> cause output in `GetHdfsErrorMsg()`. However, some failures, especially 
> exceptions raised inside filesystem client code, need the full Java stack 
> trace to identify the actual failing path.
> This change appends `hdfsGetLastExceptionStackTrace()` to the HDFS error 
> message when libhdfs provides one.



--
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