Closed inviscid closed 1 week ago
@BohuTANG @Dousir9 - From our Slack chat
We would be happy to provide the data for two tables if that would help.
@inviscid Thank you very much for providing the data, could you send me the data on slack :)
Other Settings info:
Next time, you just need to use show settings where value != default
@Dousir9 I DM'd you the two table datasets in Slack
Search before asking
Version
v1.2.618-nightly
What's Wrong?
We found an issue with Inner Join operation completing for a join between two relatively small tables. (1 million & 4 million). We have 3 query pods with 3 CPUs and 24GB RAM. We kept getting OOM even when setting the max_memory_usage to 10GB. We finally set it down to 2.4GB and this kept it from OOM but then we received the following error:
The EXPLAIN:
Crash Fault Info
We have also set
join_spilling_memory_ratio = 0
andjoin_spilling_memory_ratio = 1
but it seems to have no impact on this error.Other Settings info:
How to Reproduce?
Inner Join with several join keys.
Are you willing to submit PR?