vinooganesh opened a new pull request #35224:
URL: https://github.com/apache/spark/pull/35224
<!--
Thanks for sending a pull request! Here are some tips for you:
1. If this is your first time, please read our contributor guidelines:
https://spark.apache.org/contributing.html
2. Ensure you have added or run the appropriate tests for your PR:
https://spark.apache.org/developer-tools.html
3. If the PR is unfinished, add '[WIP]' in your PR title, e.g.,
'[WIP][SPARK-XXXX] Your PR title ...'.
4. Be sure to keep the PR description updated to reflect all changes.
5. Please write your PR title to summarize what this PR proposes.
6. If possible, provide a concise example to reproduce the issue for a
faster review.
7. If you want to add a new configuration, please read the guideline first
for naming configurations in
'core/src/main/scala/org/apache/spark/internal/config/ConfigEntry.scala'.
8. If you want to add or modify an error type or message, please read the
guideline first in
'core/src/main/resources/error/README.md'.
-->
### What changes were proposed in this pull request?
The memory leak that was partially fixed in
https://github.com/apache/spark/pull/28128 doesn't cover the case where
sessionState is touched. From the initial description: "Once SessionState is
touched, it will add two more listeners into the SparkContext, namely
SQLAppStatusListener and ExecutionListenerBus."
### Why are the changes needed?
This fixes a memory leak that that can cause a spark application to oom if
many spark sessions are created
### Does this PR introduce _any_ user-facing change?
No
### How was this patch tested?
Unit test included as a part of the PR.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
