[ 
https://issues.apache.org/jira/browse/YARN-3062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14277573#comment-14277573
 ] 

Prakash Ramachandran commented on YARN-3062:
--------------------------------------------

thanks for the clarification.[~zjshen] could be the reason, will check and 
update. 

so to clarify 
* if I have 2 primaryFilters while creating the entity,  any update to entity 
has to use the TimelineEntity.addPrimaryFilter for both primaryFilters?
* can a new primaryfilter be added in an update. (2 primaryfilters at entity 
creation time, add a new filter in update to make 3 filters, every subsequent 
update sets all 3 filters)
* can the primaryFilter value be changed in an update?
 


> timelineserver gives inconsistent data for otherinfo field based on the 
> filter param
> ------------------------------------------------------------------------------------
>
>                 Key: YARN-3062
>                 URL: https://issues.apache.org/jira/browse/YARN-3062
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: timelineserver
>    Affects Versions: 2.4.0, 2.5.0, 2.6.0
>            Reporter: Prakash Ramachandran
>         Attachments: withfilter.json, withoutfilter.json
>
>
> When otherinfo field gets updated, in some cases the data returned for an 
> entity is dependent on the filter usage. 
> for ex in the attached files for the 
> - entity: "vertex_1421164610335_0020_1_01",
> - entitytype: "TEZ_VERTEX_ID",
> for the otherinfo.numTasks,  got updated from 1009 to 253
> - using 
> {code}http://machine:8188/ws/v1/timeline/TEZ_VERTEX_ID/vertex_1421164610335_0020_1_01/
>  {code} gives the updated value: 253
> - using 
> {code}http://cn042-10:8188/ws/v1/timeline/TEZ_VERTEX_ID?limit=11&primaryFilter=TEZ_DAG_ID%3Adag_1421164610335_0020_1{code}
>  gives the old value: 1009
>  
> for the otherinfo.status field, which gets updated,   both of them show the 
> updated value. 
> TEZ-1942 has more details.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to