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 2019/04/30 20:56:31 UTC

[GitHub] [spark] attilapiros edited a comment on issue #24499: [SPARK-25888][Core] Serve local disk persisted blocks by the external service after releasing executor by dynamic allocation

attilapiros edited a comment on issue #24499: [SPARK-25888][Core] Serve local disk persisted blocks by the external service after releasing executor by dynamic allocation
URL: https://github.com/apache/spark/pull/24499#issuecomment-488112458
 
 
   @vanzin Thanks for the review!
   
   Yes, the storage level is used in two contexts: 
   - desired state (coming from the user)
   - actual state
   
   I have checked and in `UpdateBlockInfo` message the actual state is reflected so `useDisk` is only true when the disk store really contains the block.

----------------------------------------------------------------
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.
 
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