For the sake of defensive programming, would you mind getting the previous value of `spark.executor.extraClassPath` and restoring it afterwards, instead of clearing it? The `spark.driver.port` value is a different situation, where Spark internally sets that parameter, and would reuse it if it remains set.