-
Notifications
You must be signed in to change notification settings - Fork 416
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Validation failed for GlutenHashAggregateExecTransformer class #729
Comments
Hi @obedmr Here's one example
Note currently Gluten only supports Scala 2.12, so please also check if the Spark version is correct for the 2nd issue, it's due to missing the numa core range in spark conf:
the core rage expects two numa nodes splited by "|", you may need to fill with the right number in your system Thanks, -yuan |
The validation failure in |
Can you try the solution? If solved, I will close this issue. @obedmr |
Hi @jinchengchenghh, I'm sorry that I havent replied before, the issue has been solved, there were other packages that were included that were causing the issue, alongside the clean you just mentioned. Thanks a lot for all the support. |
Describe the bug
I've been trying to run the TPC-H benchmark in a 1 master and 1 worker Spark cluster with Gluten+Velox configuration.
When running the benchmark, I'm seeing a couple of issues in the benchmark's logs. Any hint or suggestion is well received.
1. Validation failed for
GlutenHashAggregateExecTransformer
classBelow part of the log and a couple of consecuent logs, not sure if they're generated because the failed validation.
2. Failed stage caused by an exception
To Reproduce
Basically, it's a 1 master and 1 worker cluster, deployed in Kubernetes, not using Yarn. Below my spark configuration file's section that applies to Gluten
Expected behavior
I would expect the Spark cluster accept the TPC-H workload and generate results
Additional context
I'm attaching a couple of log files that show the first and the second issues.
issue1.log
issue2.log
The text was updated successfully, but these errors were encountered: