[
https://issues.apache.org/jira/browse/YARN-3039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Junping Du updated YARN-3039:
-----------------------------
Attachment: YARN-3039-v4.patch
Upload v4 patch with necessary unit tests, especially end-to-end test. This
patch is ready for review now.
Something new since v3 patch:
- Add callback in AMRMClient (async) for aggregator address updating
- Add retry logic in TimelineClient for service discovery in v2 case
- Non-blocking call in DistributedShell AM for put/post entities (for v2 case)
so it won't block other core logic
- TimelineClient in v2 case won't get aggregator address from configuration but
by auto discovery now. Verify it works end-to-end with TestDistributedShell.
> [Aggregator wireup] Implement ATS app-appgregator service discovery
> -------------------------------------------------------------------
>
> Key: YARN-3039
> URL: https://issues.apache.org/jira/browse/YARN-3039
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: timelineserver
> Reporter: Sangjin Lee
> Assignee: Junping Du
> Attachments: Service Binding for applicationaggregator of ATS
> (draft).pdf, Service Discovery For Application Aggregator of ATS (v2).pdf,
> YARN-3039-no-test.patch, YARN-3039-v2-incomplete.patch,
> YARN-3039-v3-core-changes-only.patch, YARN-3039-v4.patch
>
>
> Per design in YARN-2928, implement ATS writer service discovery. This is
> essential for off-node clients to send writes to the right ATS writer. This
> should also handle the case of AM failures.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
