Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/16603
> what is reported by a consumer as used need not match what it releases as
freed
Right, but if even the sum of the reported used memory is not enough for
the new consumer, spilling existing consumers is just causing harm. You can
just report there's not enough memory without spilling anything.
But it's fine to leave that for a separate discussion, since I believe
that's how the current code behaves anyway.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
