You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Varun Saxena (JIRA)" <ji...@apache.org> on 2017/07/20 12:28:01 UTC
[jira] [Assigned] (YARN-6850) Ensure that supplemented timestamp is
stored only for flow run metrics
[ https://issues.apache.org/jira/browse/YARN-6850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Varun Saxena reassigned YARN-6850:
----------------------------------
Assignee: Varun Saxena
> Ensure that supplemented timestamp is stored only for flow run metrics
> ----------------------------------------------------------------------
>
> Key: YARN-6850
> URL: https://issues.apache.org/jira/browse/YARN-6850
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: timelineserver
> Reporter: Vrushali C
> Assignee: Varun Saxena
> Labels: yarn-5355-merge-blocker
>
> In timeline service v2, ColumnHelper#getPutTimestamp supplements the timestamp and is called by ColumnHelper#store. This is not conditional and called for every put.
> We need to ensure that the cell timestamps for metrics in entity and application (and sub application) tables are "correct" timestamps since we will be enabling TTLs for these cells.
> The supplemented timestamp is to be used only in the flow run table by the coprocessor which intercepts all reads & writes to cells in this table. It looks at the supplemented timestamp to figure out which app id this particular cell belongs to. This is done in order to ensure no collision occurs when two apps belonging to same flow run write the same metric at the same timestamp.
> Discovered in the discussion in YARN-4455
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org