Chris Trezzo commented on YARN-2179:

[~vinodkv] Mocking YarnClient seems to be tricky due to it being an 
AbstractService. Would extending YarnClientImpl and only overriding methods I 
need to stub be a more reasonable approach? For this approach I would need to 
make the serviceStart and serviceStop methods in YarnClientImpl publicly 
visible for testing. It is still a little tricky due to the serviceStart and 
serviceStop methods of YarnClientImpl using ClientRMProxy. That is originally 
why I decided to just create a different dummy YarnClient implementation. Any 
thoughts on these alternative approaches, or am I just missing an easy way to 
mock YarnClient (which is highly possible)?

> Initial cache manager structure and context
> -------------------------------------------
>                 Key: YARN-2179
>                 URL: https://issues.apache.org/jira/browse/YARN-2179
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Chris Trezzo
>            Assignee: Chris Trezzo
>         Attachments: YARN-2179-trunk-v1.patch, YARN-2179-trunk-v2.patch, 
> YARN-2179-trunk-v3.patch, YARN-2179-trunk-v4.patch, YARN-2179-trunk-v5.patch, 
> YARN-2179-trunk-v6.patch, YARN-2179-trunk-v7.patch, YARN-2179-trunk-v8.patch, 
> YARN-2179-trunk-v9.patch
> Implement the initial shared cache manager structure and context. The 
> SCMContext will be used by a number of manager services (i.e. the backing 
> store and the cleaner service). The AppChecker is used to gather the 
> currently running applications on SCM startup (necessary for an scm that is 
> backed by an in-memory store).

This message was sent by Atlassian JIRA

Reply via email to