[
https://issues.apache.org/jira/browse/YARN-387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13684878#comment-13684878
]
Vinod Kumar Vavilapalli commented on YARN-387:
----------------------------------------------
Yeah, ApplicationMasterProtocol is definitely more than scheduling. I thought
of that too first, but it isn't representative.
ApplicationClientProtocol is more protocol for ApplicationClient.
There still isn't consistency, but didn't seem like we'll have the perfect
names. Some explanation:
- ApplicationClientProtocol: Protocol for App clients
- ContainerManagerProtocol: Protocol to talk to ContainerManager
- ApplicationMasterProtocol: Protocol for ApplicationMasters
- ResourceManagerAdminProtocol: Protocol to administer ResourceManager
As you see, the verbs ARE different. But balancing verbosity, avoiding
abbreviations, representing functionality is a little difficult excercise and
the names we got now seem to be in the best balance for me.
> Fix inconsistent protocol naming
> --------------------------------
>
> Key: YARN-387
> URL: https://issues.apache.org/jira/browse/YARN-387
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Vinod Kumar Vavilapalli
> Assignee: Vinod Kumar Vavilapalli
> Priority: Blocker
> Labels: incompatible
> Attachments: YARN-387-20130616.txt
>
>
> We now have different and inconsistent naming schemes for various protocols.
> It was hard to explain to users, mainly in direct interactions at
> talks/presentations and user group meetings, with such naming.
> We should fix these before we go beta.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
