Open
Description
Backend
VL (Velox)
Bug description
When run nexmark query with GlutenSourceFuntion, when call cancel, the task still run with no stop. In nexmark running period, it will call cancel to stop warmup stage, but the task is still run。
and when force stop it by using stop-cluster.sh, it will cause memory leak as we see in the .out log
E0623 14:41:44.004539 1848634 MemoryManager.cc:264] [Velox4J MemoryManager DTOR] Memory leak found on Velox memory pool: Memory Pool[Query Memory Pool - EID 0 AGGREGATE root[root] parent[root] MALLOC track-usage thread-safe]<unlimited max capacity capacity 128.00MB used 83.12KB available 0B reservation [used 0B, reserved 2.00MB, min 0B] counters [allocs 0, frees 0, reserves 0, releases 0, collisions 0])>. Please make sure your code released all opened resources already.
E0623 14:41:44.004683 1848634 MemoryManager.cc:264] [Velox4J MemoryManager DTOR] Memory leak found on Velox memory pool: Memory Pool[root AGGREGATE root[root] parent[null] MALLOC track-usage thread-safe]<unlimited max capacity capacity 128.00MB used 159.88KB available 0B reservation [used 0B, reserved 2.00MB, min 0B] counters [allocs 0, frees 0, reserves 0, releases 0, collisions 0])>. Please make sure your code released all opened resources already.
E0623 14:41:44.004729 1848634 MemoryManager.cc:299] [Velox4J MemoryManager DTOR] There are 4 outstanding Velox memory pools.
Gluten version
No response
Spark version
None
Spark configurations
No response
System information
No response