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.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to