[
https://issues.apache.org/jira/browse/YARN-3125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Li Lu updated YARN-3125:
------------------------
Attachment: YARN-3125_UT-022615.patch
Based on [~djp]'s v3 patch, I wrote a simple unit test for distributed shell
that helps us verify timeline v2 integration. I added this test into
TestDistributedShell, as a test for timeline V2. On my machine this single new
test passed, and I can see the successful info from the test logs. So in
general our prototype works.
However, we do have some (potentially quick, but may be important) problems on
running v1 and v2 timeline servers together. On the server side, in this UT,
both v1 and v2 servers are launched, with v2 server bind to a predefined port.
On the client side, now I've disabled the v1 URL in timeline client. Probably
we'd like a switch in our client to set timeline version? I believe now we need
to take care of the compatibility issues...
> [Event producers] Change distributed shell to use new timeline service
> ----------------------------------------------------------------------
>
> Key: YARN-3125
> URL: https://issues.apache.org/jira/browse/YARN-3125
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: timelineserver
> Reporter: Zhijie Shen
> Assignee: Junping Du
> Attachments: YARN-3125.patch, YARN-3125_UT-022615.patch,
> YARN-3125v2.patch, YARN-3125v3.patch
>
>
> We can start with changing distributed shell to use new timeline service once
> the framework is completed, in which way we can quickly verify the next gen
> is working fine end-to-end.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
