You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Reynold Xin (JIRA)" <ji...@apache.org> on 2016/11/02 06:17:59 UTC
[jira] [Closed] (SPARK-16972) Move DriverEndpoint out of
CoarseGrainedSchedulerBackend
[ https://issues.apache.org/jira/browse/SPARK-16972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Reynold Xin closed SPARK-16972.
-------------------------------
Resolution: Won't Fix
Closing this as won't fix for now given the comments on the pull request. The risk of introducing a bug and making it more difficult to back port bug fixes outweighs the benefits in this case. If there is a stronger reason to do this (e.g. simplifies the development of new features), we can do this in the future.
> Move DriverEndpoint out of CoarseGrainedSchedulerBackend
> --------------------------------------------------------
>
> Key: SPARK-16972
> URL: https://issues.apache.org/jira/browse/SPARK-16972
> Project: Spark
> Issue Type: Improvement
> Components: Scheduler
> Affects Versions: 2.0.0
> Reporter: Liu Shaohui
>
> The CoarseGrainedSchedulerBackend class is too large and complex to understand or make improvements, because it contains an inner class DriverEndpoint and many members of CoarseGrainedSchedulerBackend are used in DriverEndpoint.
> So I am trying to move DriverEndpoint out of CoarseGrainedSchedulerBackend and make these two classes clean and easy to understand.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org