[ 
https://issues.apache.org/jira/browse/SPARK-18798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15736057#comment-15736057
 ] 

Narendra commented on SPARK-18798:
----------------------------------

I am putting below  code it says 
 logWarning("Killing executors is only supported in coarse-grained mode") , 
this means it is supported only in Mesos ? if i am wrong please correct 

/**
   * :: DeveloperApi ::
   * Request that the cluster manager kill the specified executors.
   *
   * @note This is an indication to the cluster manager that the application 
wishes to adjust
   * its resource usage downwards. If the application wishes to replace the 
executors it kills
   * through this method with new ones, it should follow up explicitly with a 
call to
   * {{SparkContext#requestExecutors}}.
   *
   * @return whether the request is received.
   */
  @DeveloperApi
  def killExecutors(executorIds: Seq[String]): Boolean = {
    schedulerBackend match {
      case b: CoarseGrainedSchedulerBackend =>
        b.killExecutors(executorIds, replace = false, force = true).nonEmpty
      case _ =>
        logWarning("Killing executors is only supported in coarse-grained mode")
        false
    }
  }

> Expose the kill Executor in Yarn Mode
> -------------------------------------
>
>                 Key: SPARK-18798
>                 URL: https://issues.apache.org/jira/browse/SPARK-18798
>             Project: Spark
>          Issue Type: Improvement
>            Reporter: Narendra
>
> Expose the kill Executor in Yarn Mode
> I can see spark already has exposed the kill Executor method through spark 
> context  for Mesos , fi spark can expose the same method for Yarn it will 
> good feature if some want to test application stability by killing randomly 
> Executor
> I see spark have kill Executor in YarnAllocator, it won't we much time 
> consuming to expose this , anyone can work I can also 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

Reply via email to