[jira] [Updated] (YARN-3240) [Data Mode] Implement client API to put generic entities
[ https://issues.apache.org/jira/browse/YARN-3240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Saxena updated YARN-3240: --- Fix Version/s: 2.9.0 > [Data Mode] Implement client API to put generic entities > > > Key: YARN-3240 > URL: https://issues.apache.org/jira/browse/YARN-3240 > Project: Hadoop YARN > Issue Type: Sub-task > Components: timelineserver >Reporter: Zhijie Shen >Assignee: Zhijie Shen > Fix For: 2.9.0, 3.0.0-alpha1 > > Attachments: YARN-3240.1.patch, YARN-3240.2.patch, YARN-3240.3.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-3240) [Data Mode] Implement client API to put generic entities
[
https://issues.apache.org/jira/browse/YARN-3240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhijie Shen updated YARN-3240:
--
Attachment: YARN-3240.3.patch
Create the new patch:
1. Fix some minor bugs.
2. Per offline discussion, let's have a setter for the timeline service address
to allow user to update the service address upon new discovery.
3. Per offline discussion, the client is bounded to a particular app,
therefore, let's still keep the appId as the param for the constructor, such
that there's no need to tell which app the entities are associated with in each
call.
I ran through the changed unit tests and all
timelineservice/appalicationhistory unit tests locally. All of them were passed.
Please note that when applying the patch, make sure {{.keep}} file is applied
too.
[Data Mode] Implement client API to put generic entities
Key: YARN-3240
URL: https://issues.apache.org/jira/browse/YARN-3240
Project: Hadoop YARN
Issue Type: Sub-task
Components: timelineserver
Reporter: Zhijie Shen
Assignee: Zhijie Shen
Attachments: YARN-3240.1.patch, YARN-3240.2.patch, YARN-3240.3.patch
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (YARN-3240) [Data Mode] Implement client API to put generic entities
[ https://issues.apache.org/jira/browse/YARN-3240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-3240: -- Attachment: YARN-3240.2.patch Made a new patch: 1. Fix the bugs in the previous one. 2. Add an integration test to demonstrate that the client and the server can communicate. [Data Mode] Implement client API to put generic entities Key: YARN-3240 URL: https://issues.apache.org/jira/browse/YARN-3240 Project: Hadoop YARN Issue Type: Sub-task Components: timelineserver Reporter: Zhijie Shen Assignee: Zhijie Shen Attachments: YARN-3240.1.patch, YARN-3240.2.patch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (YARN-3240) [Data Mode] Implement client API to put generic entities
[ https://issues.apache.org/jira/browse/YARN-3240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-3240: -- Attachment: YARN-3240.1.patch In this Jira, I aim to make the basic client write APIs ready. Later on, we can add more advanced APIs to simply putting predefined data, such as flow. Bellow is the summary of this patch: 1. Added the two Java methods of TimelineClient to operate the new generic timeline entity data object. One is for blocking call, while the other is for the async call. The two methods wrap over the same REST HTTP API, but giving different async param. At the server side, the aggregator can consume this param to determine whether to use sync or asycn call to persist the timeline data. It needs the resource URI and the context appID to know where the request should be sent to and which conceptual per-app aggregator should be routed to. This is blocked by YARN-3039. For now, I just leave them unset in the code. 2. Change the endpoint at per-node web service accordingly to make the client and the server be paired. 3. One more data object, TimelineEntities, which is the collection of TimelineEntity, is added to host multiple entities for one request to the aggregator. The rationale behind putting the new client API inside the existing timeline client is: 1. Most of TimelineClientImpl code could be reused, including making HTTP calls, security, retry and so on. 2. Not all the client APIs will be deprecated, but just those that operate on the old data model. For example, delegation token related APIs may still stay. [Data Mode] Implement client API to put generic entities Key: YARN-3240 URL: https://issues.apache.org/jira/browse/YARN-3240 Project: Hadoop YARN Issue Type: Sub-task Components: timelineserver Reporter: Zhijie Shen Assignee: Zhijie Shen Attachments: YARN-3240.1.patch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
