Github user JeetKunDoug commented on the issue:

    https://github.com/apache/spark/pull/21322
  
    @viirya it seems from my admittedly cursory look at where we use the 
`cachedValues` reference map that we should be OK in this case - if there's a 
deserialized version of the variable (the only case we really care about), 
it'll have a hard reference in an entry in MemoryStore, and, when removed 
(which occurs if `BlockManager` drops it from memory) we can do the cleanup 
there explicitly. Perhaps I missed a way to have a broadcast variable in 
deserialized form in the cache but _not_ in `MemoryStore.entries`?


---

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to