[SPARK-20191] RackResolver not correctly being overridden in YARN tests

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.3, 2.1.1, 2.2.0
• Fix Version/s: 2.1.2, 2.2.0
• Component/s: Spark Core, YARN
• Assignee: Marcelo Masiero Vanzin
• Reporter: Marcelo Masiero Vanzin
• Created: 02/Apr/17 00:27
• Updated: 17/May/20 18:14
• Resolved: 04/Apr/17 18:48

Description

YARN tests currently try to override YARN's RackResolver, but that class self-initializes the first time it's called, storing state in static variables and ignoring any further config params that might override the initial behavior.

So we need a better solution for Spark tests, so that tests such as LocalityPlacementStrategySuite don't flood the DNS server with requests (making the test really slow in certain environments).

Issue Links

• links to: [Github] Pull Request #17508 (vanzin)