Skip to content
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

Insert query that is OOM'ing in Clickhouse is returning OK to dbt #360

Open
barberscott opened this issue Sep 23, 2024 · 1 comment
Open
Labels
bug Something isn't working

Comments

@barberscott
Copy link

Describe the bug

I have an insert query that is consisently out of memory-ing. In the Clickhouse logs I can see an exception 241 being thrown on the query.

In dbt, I see:

13:36:37  dbt_clickhouse adapter: SQL status: OK in 136.20 seconds

In query_log I see:

Code: 241. DB::Exception: Memory limit (total) exceeded: would use 146.96 GiB (attempt to allocate chunk of 68720781687 bytes), maximum: 100.80 GiB. OvercommitTracker decision: Query was selected to stop by OvercommitTracker.: While executing FillingRightJoinSide. (MEMORY_LIMIT_EXCEEDED) (version 24.5.1.22957 (official build))

and the problem is that dbt then proceeds despite reaching the OOM -- I would expect dbt to fail here. This seems to have started to happen on/around September 4 or so.

@barberscott barberscott added the bug Something isn't working label Sep 23, 2024
@barberscott barberscott changed the title Query that is OOM'ing in Clickhouse is returning OK to dbt Insert query that is OOM'ing in Clickhouse is returning OK to dbt Sep 23, 2024
@barberscott
Copy link
Author

Near as I can tell, this only seems to impact OOMs on inserts. OOMs on select are appropriately reporting state.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant