[
https://issues.apache.org/jira/browse/SPARK-5593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lianhui Wang updated SPARK-5593:
--------------------------------
Description:
More strictly, in ExecutorAllocationListener, we need to replace
onBlockManagerAdded, onBlockManagerRemoved with
onExecutorAdded,onExecutorRemoved. because at some time, onExecutorAdded and
onExecutorRemoved are more accurate to express these meanings. example at
SPARK-5529, BlockManager has been removed,but executor is existed.
[~andrewor14] [~sandyr]
was:
More strictly, in ExecutorAllocationListener, we need to replace
onBlockManagerAdded, onBlockManagerRemoved with
SparkListenerExecutorRemoved,SparkListenerExecutorAdded.
because at some time, SparkListenerExecutorRemoved,SparkListenerExecutorAdded
are more accurate to express executorRemoved,executorAdded. at SPARK-5529,
BlockManager has been removed,but executor is existed.
[~andrewor14] [~sandyr] Can you agree with me? if yes,i think i will update it.
> Replace BlockManager listener with Executor listener in
> ExecutorAllocationListener
> ----------------------------------------------------------------------------------
>
> Key: SPARK-5593
> URL: https://issues.apache.org/jira/browse/SPARK-5593
> Project: Spark
> Issue Type: Bug
> Reporter: Lianhui Wang
>
> More strictly, in ExecutorAllocationListener, we need to replace
> onBlockManagerAdded, onBlockManagerRemoved with
> onExecutorAdded,onExecutorRemoved. because at some time, onExecutorAdded and
> onExecutorRemoved are more accurate to express these meanings. example at
> SPARK-5529, BlockManager has been removed,but executor is existed.
> [~andrewor14] [~sandyr]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
