eaton created SPARK-20386:
-----------------------------
Summary: The log info "Added %s in memory on %s (size: %s, free:
%s)" in function "org.apache.spark.storage.BlockManagerInfo.updateBlockInfo"
is not accurate if the block exists on the slave already
Key: SPARK-20386
URL: https://issues.apache.org/jira/browse/SPARK-20386
Project: Spark
Issue Type: Bug
Components: Spark Core
Affects Versions: 2.1.0
Reporter: eaton
The log info"Added %s in memory on %s (size: %s, free: %s)" in function
"org.apache.spark.storage.BlockManagerInfo.updateBlockInfo" is not accurate if
the block exists on the slave already;
the current code is:
if (storageLevel.useMemory) {
blockStatus = BlockStatus(storageLevel, memSize = memSize, diskSize = 0)
_blocks.put(blockId, blockStatus)
_remainingMem -= memSize
logInfo("Added %s in memory on %s (size: %s, free: %s)".format(
blockId, blockManagerId.hostPort, Utils.bytesToString(memSize),
Utils.bytesToString(_remainingMem)))
}
If the block exists on the slave already, the added memory should be memSize -
originalMemSize, the originalMemSize is _blocks.get(blockId).memSize
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
