Github user mwws commented on a diff in the pull request:

    https://github.com/apache/spark/pull/8760#discussion_r40281631
  
    --- Diff: 
core/src/main/scala/org/apache/spark/scheduler/BlacklistStrategy.scala ---
    @@ -0,0 +1,156 @@
    +/*
    + * Licensed to the Apache Software Foundation (ASF) under one or more
    + * contributor license agreements.  See the NOTICE file distributed with
    + * this work for additional information regarding copyright ownership.
    + * The ASF licenses this file to You under the Apache License, Version 2.0
    + * (the "License"); you may not use this file except in compliance with
    + * the License.  You may obtain a copy of the License at
    + *
    + *    http://www.apache.org/licenses/LICENSE-2.0
    + *
    + * Unless required by applicable law or agreed to in writing, software
    + * distributed under the License is distributed on an "AS IS" BASIS,
    + * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
    + * See the License for the specific language governing permissions and
    + * limitations under the License.
    + */
    +
    +package org.apache.spark.scheduler
    +
    +import scala.collection.mutable
    +
    +import org.apache.spark.Logging
    +import org.apache.spark.SparkConf
    +import org.apache.spark.util.SystemClock
    +
    +/**
    + * The interface to determine executor blacklist and node blacklist.
    + */
    +trait BlacklistStrategy {
    +  val expireTimeInMillisecond: Long
    +
    +  // TaskId is optional here because the BlacklistStrategy could be 
unrelated to TaskId
    --- End diff --
    
    My original thinking was becasue (1) nodeBlacklist could depend on the 
result of executorBlacklist (2) executorBlacklist might be taskId related ==> 
then nodeBlacklist could also be taskId related. Your suggestion extinguish the 
possibility to make nodeBlacklist taskId related. And In "speculate" mode, when 
calling ```getExecutorBlacklist``` related to some taskId, we would like to 
```getNodeBlacklist``` related to the same taskId.
    
    Maybe we just keep both method with/without taskId to make the API more 
extendable and provide additional layer of trait to simplify the implementation?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to