-
Notifications
You must be signed in to change notification settings - Fork 8.3k
Memory limit (total) exceeded issues with wait_end_of_query=1 #11153
Copy link
Copy link
Closed
Labels
bugConfirmed user-visible misbehaviour in official releaseConfirmed user-visible misbehaviour in official releasecomp-protocolsServer wire protocols + request/response handling (native TCP, HTTP, MySQL/PostgreSQL wire protoc...Server wire protocols + request/response handling (native TCP, HTTP, MySQL/PostgreSQL wire protoc...memoryWhen memory usage is higher than expectedWhen memory usage is higher than expected
Description
Using the version a2ed826 in case I run a QUERY like "SELECT 1" in loop using wait_end_of_query=1 after 7000 iterations all queries will fail with:
DynamicQueryHandler: Code: 241, e.displayText() = DB::Exception: Memory limit (total) exceeded: would use 14.40 GiB (attempt to allocate chunk of 4198133 bytes), maximum: 14.40 GiB, Stack trace (when copying this message, always include the lines below):
If wait_end_of_query is not specified the problem doesn't occur.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
bugConfirmed user-visible misbehaviour in official releaseConfirmed user-visible misbehaviour in official releasecomp-protocolsServer wire protocols + request/response handling (native TCP, HTTP, MySQL/PostgreSQL wire protoc...Server wire protocols + request/response handling (native TCP, HTTP, MySQL/PostgreSQL wire protoc...memoryWhen memory usage is higher than expectedWhen memory usage is higher than expected