You are viewing a plain text version of this content. The canonical link for it is here.
Posted to reviews@spark.apache.org by suyanNone <gi...@git.apache.org> on 2015/09/01 11:54:33 UTC

[GitHub] spark pull request: [SPARK-6157][CORE]Unroll unsuccessful memory_a...

Github user suyanNone commented on the pull request:

    https://github.com/apache/spark/pull/4887#issuecomment-136657671
  
    @srowen @nitin2goyal  I not sure it is need because there is a big change for memory threshold per thread.
    
    In the previous situation, it is aim to resolve memory_and_disk level block, first unroll failed, but it will reserved unroll memory for this thread,  and that unroll memory part should release after that block already put into disk.  


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

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