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
distsql: fix recently introduced leak of CancelFunc
In 27a65c9 we introduced the logic to
make sure that remote flows respect the quiesce signal. However, we
consciusly ignored the returned CancelFunc since the lifetime of the
context is non-trivial. This introduced a leak of that CancelFunc since
we keep the reference to it in the stopper even when the flow exits, so
every time a remote flow runs on a node, the leak would slowly grow.
This leak is now fixed by ensuring the cancellation function is always
called. This is achieved by passing the function as another thing to do
on the "flow cleanup" (we already always need to close the reserved
memory account, so we have the necessary infrastructure set up).
Release note (bug fix): In 25.1.8, 25.2.1, 25.2.2, and 25.3 betas, a slow
memory leak was introduced that would accumulate whenever a node
executes a part of the distributed plan (the gateway node of the plan is
not affected). The leak can only be mitigated by restarting the node and
is now fixed.
0 commit comments