You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Running TPCC stockLevel queries with local lookupJoin oom kills the server. It seems it is somehow creating an enormous ScanResponse, maybe a lack of batching?
29397: sql: don't remove batch limit in local lookup join r=jordanlewis a=jordanlewis
Previously, the local lookup join node was created with an underlying
scan with an explicitly disabled batch limit. This is the wrong thing to
do, since that scan will be used as a full table scan - it needs a batch
limit to prevent OOM errors.
Closes#29389.
Release note: None
Co-authored-by: Jordan Lewis <[email protected]>
Running TPCC stockLevel queries with local lookupJoin oom kills the server. It seems it is somehow creating an enormous ScanResponse, maybe a lack of batching?
Here's a heap profile.
localLookup.pprof.gz
The text was updated successfully, but these errors were encountered: