-
Notifications
You must be signed in to change notification settings - Fork 411
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
internal.DeltaError: Generic DeltaTable error: Internal error: Invalid HashJoinExec partition count mismatch 1!=2 #2188
Comments
You may need more CPUs, I saw this recently and upping the number of CPUs resolved this. |
@echai58 Thank you! Perhaps you know the way to evaluate how many CPUs may potentially be needed? |
@t1g0rz Were you able to solve the problem by increasing the CPU? I have the same issue inside a Pod in Kubernetes |
@germanmunuera how much vcpus are you assigning to the pod? |
|
@germanmunuera Yep, everything is fine now. I added up to 4 CPUs and this resolved the issue. |
python 3.11 Had the same issue here with:
Resolved by increasing to: The question is why does this resolve it? |
Solved with 2 CPUs! |
Wanted to follow up on this, @ion-elgreco @Blajda are either of you aware of why datafusion requires > 1 cpu for merging? |
Nope, but you can try asking the question in datafusion repo :) |
apache/datafusion#10095 - a datafusion pr was opened recently that should resolve this issue! |
Any idea when the datafusion fix will make it into a realease? |
It's included in Python v0.18.1 |
Environment
Delta-rs version:
rust-v0.17.0
Binding:
python
deltalake-0.15.3
Environment:
Bug
What happened:
When I run a simple script a few times (twice, in my case) to simulate updating and partitioning, I encounter the following error.
What you expected to happen:
Table updated w/o any issues
How to reproduce it:
Here is the script. You can run it on t2.micto AWS
More details:
How it looked:
But if I try to update the same delta table from my laptop there are no errors at all.
Memory consumption from ubuntu VM:
The text was updated successfully, but these errors were encountered: