mridulm commented on code in PR #45052: URL: https://github.com/apache/spark/pull/45052#discussion_r1501739796
########## core/src/main/scala/org/apache/spark/storage/BlockManager.scala: ########## @@ -177,15 +177,17 @@ private[spark] class HostLocalDirManager( * Manager running on every node (driver and executors) which provides interfaces for putting and * retrieving blocks both locally and remotely into various stores (memory, disk, and off-heap). * - * Note that [[initialize()]] must be called before the BlockManager is usable. + * Note that [[initialize()]] must be called before the BlockManager is usable. Also, the + * `memoryManager` is initialized at a later stage after DriverPlugin is loaded, to allow the + * plugin to overwrite memory configurations. */ private[spark] class BlockManager( val executorId: String, rpcEnv: RpcEnv, val master: BlockManagerMaster, val serializerManager: SerializerManager, val conf: SparkConf, - memoryManager: MemoryManager, + var memoryManager: MemoryManager, Review Comment: I will need to look more - I dont this my hypothesis is the RC here ... even though `_env.blockManager.initialize` happens after `_taskScheduler.start()`, `_env.initializeMemoryManager` happens before and should have initialized the state. -- 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. To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org For additional commands, e-mail: reviews-h...@spark.apache.org