Github user viirya commented on the issue:
https://github.com/apache/spark/pull/16387
@samkum I've expected this and your testing inspired me to change how the
memory consumers are spilled in order. I've submitted a PR #16603 for this.
Simply said, even I added a check and only spill the map if it has
elements. Currently, the map will be chose to spill even it has few elements
added since last time it spilled.
Because of that, I will hope #16603 can be reviewed and merged first before
this. So we won't see the GC issue.
Can you test #16603 and see if it helps GC issue of this PR? Thanks.
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
