jomach opened a new issue, #7565:
URL: https://github.com/apache/hudi/issues/7565

   **_Tips before filing an issue_**
   
   - Have you gone through our [FAQs](https://hudi.apache.org/learn/faq/)?
   
   - Join the mailing list to engage in conversations and get faster support at 
[email protected].
   
   - If you have triaged this as a bug, then file an 
[issue](https://issues.apache.org/jira/projects/HUDI/issues) directly.
   
   **Describe the problem you faced**
   
   We are running Apache Hudi on a AWS Glue with 3 Nodes X2 and reading 
relative small amount of data. The job ends up failing on 
org.apache.hudi.table.action.commit.BaseSparkCommitActionExecutor.buildProfile(BaseSparkCommitActionExecutor.java:191)
   We are running 0.10.0 and spark 3.1.1
   
   <img width="1920" alt="Screenshot 2022-12-27 at 13 01 44" 
src="https://user-images.githubusercontent.com/4804546/209664106-8194ef08-c2bf-4592-a614-81b0c37a075e.png";>
   <img width="2029" alt="Screenshot 2022-12-27 at 12 50 26" 
src="https://user-images.githubusercontent.com/4804546/209664118-8771bffa-9b29-4e2b-ba57-8e4d12ba2519.png";>
   
   If we increase the number of workers to 6 then the job usually works. I 
think it has todo with skew keys, but I'm new to this project
   
   **Expected behavior**
   
   A clear and concise description of what you expected to happen.
   
   **Environment Description**
   
   * Hudi version : 0.10.0
   
   * Spark version : 3.1.1
   
   * Hive version : --
   
   * Hadoop version : AWS Glue
   
   * Storage (HDFS/S3/GCS..) : S3
   
   * Running on Docker? (yes/no) : No
   
   
   **Stacktrace**
   
   ExecutorLostFailure (executor 9 exited caused by one of the running tasks) 
Reason: Remote RPC client disassociated. Likely due to containers exceeding 
thresholds, or network issues. Check driver logs for WARN messages.
   
   
   
   


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