You are viewing a plain text version of this content. The canonical link for it is here.

Posted to reviews@spark.apache.org by GitBox <gi...@apache.org> on 2018/12/31 16:02:45 UTC

[GitHub] srowen commented on issue #23401: Trigger GC on executor node idle

srowen commented on issue #23401: Trigger GC on executor node idle
URL: https://github.com/apache/spark/pull/23401#issuecomment-450662180
 
 
   Please see https://spark.apache.org/contributing.html
   I don't think we should do this. Forcing a full GC has downsides like clearing weak references that still usefully cache data. GC already triggers in the background when thresholds are reached. Let's not add a second version plus a new flag to tune on top.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org