You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@hudi.apache.org by GitBox <gi...@apache.org> on 2021/11/22 08:17:45 UTC

[GitHub] [hudi] JB-data commented on issue #4055: [SUPPORT] Hudi with SqlQueryBasedTransformer fails-> spark error exit 134 or exit 143 in "isEmpty at DeltaSync.java:344" : Container from a bad node: container_yy on host: xxx Exit status: 134

JB-data commented on issue #4055:
URL: https://github.com/apache/hudi/issues/4055#issuecomment-975241019


   @xushiyan 
   Thanks for reply. Indeed the sql should say FROM sometable... I will correct.
   
   Where exactly should we check the application stacktrace? In both the the yarn application logs as the SPARK UI stacktrace I only find back the fact the container exited with code 134 or 143 (changes ), but not exactly why. The only place where I can infer where this happens is the stage in the spark ui that mentions: 
   isEmpty at DeltaSync.java:344
   so I am assuming it comes from there?


-- 
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: commits-unsubscribe@hudi.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org