You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@spark.apache.org by "Hyukjin Kwon (JIRA)" <ji...@apache.org> on 2019/05/21 04:38:22 UTC

[jira] [Resolved] (SPARK-14192) Executor is dead in Driver but alive in AM when driver losts rpc with executor, but executor is alive.

     [ https://issues.apache.org/jira/browse/SPARK-14192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hyukjin Kwon resolved SPARK-14192.
----------------------------------
    Resolution: Incomplete

> Executor is dead in Driver but alive in AM when driver losts rpc with executor, but executor is alive.
> ------------------------------------------------------------------------------------------------------
>
>                 Key: SPARK-14192
>                 URL: https://issues.apache.org/jira/browse/SPARK-14192
>             Project: Spark
>          Issue Type: Bug
>          Components: Scheduler
>            Reporter: meiyoula
>            Priority: Major
>              Labels: bulk-closed
>
> reproduce steps:
> 1. start up spark-sql with: bin/spark-sql --master yarn --num-executors 1
> 2. lost driver and executor connection, but make sure executor is still alive
> 3. execute "show tables", the process will be stuck. Because the driver ask Am to allocate an executor, but AM see the executor is still alive, so don't allocate new one.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org