hadoop-yarn-issues mailing list archives

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

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

Vinod Kumar Vavilapalli commented on YARN-387:
----------------------------------------------

I went this route and generated a patch. But it didn't look great mainly for reasons like
RM also using AMNMProtocol for launching containers. Having functional names is much better
- so I am going with
 - ApplicationClientProtocol (other options are simply ClientProtocol or worse ClientRMProtocol)
 - ContainerManagerProtocol
 - ApplicationMasterProtocol
 - ResourceManagerAdminProtocol
 - ResourceTrackerProtocol
 - LocalizationProtocol

Thoughts?

Clearly have to get this in for 2.1-beta.
                
> 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
>
> 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