hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arun C Murthy (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-387) Fix inconsistent protocol naming
Date Sun, 16 Jun 2013 23:26:20 GMT

    [ https://issues.apache.org/jira/browse/YARN-387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13684844#comment-13684844
] 

Arun C Murthy commented on YARN-387:
------------------------------------

I don't think there are perfect answers, but ApplicationClientProtocol makes it clear it is
for *all* application clients and is more than merely application submission by providing
cluster information etc. 

Also, ApplicationMasterProtocol is the protocol we expect AMs to communicate with RM on; also,
it is more than just the protocol for just getting resources from the Scheduler since it has
registration, eventually we'll need to add cluster information etc.

However, these are fairly subjective and we'll just have to get to some consensus.
                
> 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

Mime
View raw message