spark-instrumented-optimizer/resource-managers
“attilapiros” e4e4e2b842 [SPARK-26891][YARN] Fixing flaky test in YarnSchedulerBackendSuite
The test "RequestExecutors reflects node blacklist and is serializable" is flaky because of multi threaded access of the mock task scheduler. For details check [Mockito FAQ (occasional exceptions like: WrongTypeOfReturnValue)](https://github.com/mockito/mockito/wiki/FAQ#is-mockito-thread-safe). So instead of mocking the task scheduler in the test TaskSchedulerImpl is simply subclassed.

This multithreaded access of the `nodeBlacklist()` method is coming from:
1) the unit test thread via calling of the method `prepareRequestExecutors()`
2) the `DriverEndpoint.onStart` which runs a periodic task that ends up calling this method

Existing unittest.

Closes #23801 from attilapiros/SPARK-26891.

Authored-by: “attilapiros” <piros.attila.zsolt@gmail.com>
Signed-off-by: Marcelo Vanzin <vanzin@cloudera.com>
2019-02-19 13:29:42 -08:00
..
kubernetes [SPARK-26733][K8S] Cleanup entrypoint.sh. 2019-02-05 16:00:18 -08:00
mesos [SPARK-26817][CORE] Use System.nanoTime to measure time intervals 2019-02-13 13:12:16 -06:00
yarn [SPARK-26891][YARN] Fixing flaky test in YarnSchedulerBackendSuite 2019-02-19 13:29:42 -08:00