[
https://issues.apache.org/jira/browse/YARN-6614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arun Suresh updated YARN-6614:
------------------------------
Attachment: YARN-6614.001.patch
Attaching intial patch.
[~curino] / [~subru] / [~giovanni.fumarola] do take a look. This would greatly
simplify the Federation Interceptor (and all other AMRMProxy frameworks) as
well:
Prior to this, ALL interceptors would have to decide if supports
DistributedScheduling or not, even though they have nothing to do with it. This
was because the DistributedScheduling was implemented as a wrapper protocol.
With this patch, I've essentially moved all the DistributedSchedulingProtocol
feilds inside the {{RegistedApplicationMaster}}, {{AllocateRequest}} and
{{AllocateResponse}} objects and removed the Protocol.
> Deprecate DistributedSchedulingProtocol and add required fields directly to
> ApplicationMasterProtocol
> -----------------------------------------------------------------------------------------------------
>
> Key: YARN-6614
> URL: https://issues.apache.org/jira/browse/YARN-6614
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Arun Suresh
> Assignee: Arun Suresh
> Attachments: YARN-6614.001.patch
>
>
> The {{DistributedSchedulingProtocol}} was initially designed as a wrapper
> protocol over the {{ApplicaitonMasterProtocol}}.
> This JIRA proposes to deprecate the protocol itself and move the extra fields
> of the {{RegisterDistributedSchedulingAMResponse}} and
> {{DistributedSchedulingAllocateResponse}} to the
> {{RegisterApplicationMasterResponse}} and {{AllocateResponse}} respectively.
> This will simplify the code quite a bit and make it easier to expose it as a
> preprocessor.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
