[
https://issues.apache.org/jira/browse/SAMZA-58?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhijie Shen updated SAMZA-58:
-----------------------------
Attachment: SAMZA-58.2.patch
I created a new patch, which address Chris' comments. It is worth mentioning:
1. I still keep the loop, as i think it's necessary to prevent the process from
exiting early.
2. I keep progress 0 as we've not concluded a correct Samza progress.
BTW, when we think about whether the loop is required or not, it's better not
to make the assumption we need the implementation of AMRMClientAsyncImpl, given
it may be changed in the future. Probably we want something like that
AMRMClientAsync can have the API block the caller until unregistration.
Unfortunately, we don't have it on hand right now. Thoughts?
> Use YARN's AMRMClientAsync client library
> -----------------------------------------
>
> Key: SAMZA-58
> URL: https://issues.apache.org/jira/browse/SAMZA-58
> Project: Samza
> Issue Type: Bug
> Components: yarn
> Affects Versions: 0.6.0
> Reporter: Chris Riccomini
> Assignee: Zhijie Shen
> Attachments: SAMZA-58.1.patch, SAMZA-58.2.patch
>
>
> YARN 2.2.0 has a nice Async API for clients and AMs. This API didn't exist
> when we did the initial YARN integration for Samza. We should upgrade Samza
> to use these new APIs.
> The API is loosely based off Samza's own AM code, so we can probably strip
> out a lot of it (YarnAppMaster, mainly), and switch everything over to the
> call-back based API.
> For details, see:
> https://issues.apache.org/jira/browse/YARN-417
> This new API is used in DistributedShell now, so we can use that for testing.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
