[SPARK-3496] Block replication can by mistake choose driver BlockManager as a peer for replication

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 1.0.2, 1.1.0
• Fix Version/s: 1.1.1, 1.2.0
• Component/s: Block Manager, DStreams, Spark Core
• Target Version/s: 1.1.1, 1.2.0
• Assignee: Tathagata Das
• Reporter: Tathagata Das
• Created: 12/Sep/14 01:41
• Updated: 11/Nov/14 02:37
• Resolved: 02/Oct/14 20:50

Description

When selecting peer block managers for replicating a block, the driver block manager can also get chosen accidentally. This is because BlockManagerMasterActor did not filter out the driver block manager.

Issue Links

• links to: [Github] Pull Request #3191 (tdas)
• links to: Github pull request