[YARN-3986] getTransferredContainers in AbstractYarnScheduler should be present in YarnScheduler interface instead

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.7.0
• Fix Version/s: 2.8.0, 3.0.0-alpha1
• Component/s: scheduler
• Target Version/s: 2.8.0
• Assignee: Varun Saxena
• Reporter: Varun Saxena
• Created: 28/Jul/15 08:58
• Updated: 30/Aug/16 01:18
• Resolved: 21/Aug/15 05:29

Description

Currently getTransferredContainers is present in AbstractYarnScheduler.
But in ApplicationMasterService, while registering AM, we are calling this method by typecasting it to AbstractYarnScheduler, which is incorrect.

This method should be moved to YarnScheduler.

Because if a custom scheduler is to be added, it will implement YarnScheduler, not AbstractYarnScheduler.
As ApplicationMasterService is calling getTransferredContainers by typecasting it to AbstractYarnScheduler, it is imposing an indirect dependency on AbstractYarnScheduler for any pluggable custom scheduler.

We can move the method to YarnScheduler and leave the definition in AbstractYarnScheduler as it is.

Issue Links

• relates to: YARN-4078 getPendingResourceRequestForAttempt is present in AbstractYarnScheduler should be present in YarnScheduler interface instead