Yes, that is what I assumed.
In our usecase though, we want it dropped from both mem and disk (and
actually forget about the block at slave entirely), right ?
 On Feb 6, 2014 8:00 AM, "ignatich" <notifications@github.com> wrote:

> In core/src/main/scala/org/apache/spark/storage/BlockManager.scala:
>
> > @@ -720,6 +725,13 @@ private[spark] class BlockManager(
> >    }
> >
> >    /**
> > +   * Drop a block from memory, possibly putting it on disk if applicable.
> > +   */
> > +  def dropFromMemory(blockId: BlockId) {
> > +    memoryStore.asInstanceOf[MemoryStore].dropFromMemory(blockId)
> > +  }
> > +
>
> This is basically same thing that happens when a block is evicted from
> cache. So it removes block from memoryStore and saves it to disk if needed
> (which it is for broadcasts since they use StorageLevel.MEMORY_AND_DISK).
>
> --
> Reply to this email directly or view it on GitHub<https://github.com/apache/incubator-spark/pull/543/files#r9488335>
> .
>