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 "Haibo Chen (JIRA)" <ji...@apache.org> on 2017/02/28 19:46:45 UTC
[jira] [Commented] (YARN-4061) [Fault tolerance] Fault tolerant
writer for timeline v2
[ https://issues.apache.org/jira/browse/YARN-4061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15888753#comment-15888753 ]
Haibo Chen commented on YARN-4061:
----------------------------------
I notice that in FlowAcitivityColumnPrefix.store(byte[] rowKey, TypedBufferedMutator<FlowActivityTable> tableMutator, String qualifier, Long timestamp, Object inputValue, Attribute... attributes), timestamp is dropped (column.store gets a null for timestamp). This is not in line with one of our discussions in which I remember I was told that ATS clients set the timestamp explicitly so there is no out of order problem in our fault-torelant writer. Are I missing something?
> [Fault tolerance] Fault tolerant writer for timeline v2
> -------------------------------------------------------
>
> Key: YARN-4061
> URL: https://issues.apache.org/jira/browse/YARN-4061
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: timelineserver
> Reporter: Li Lu
> Assignee: Joep Rottinghuis
> Labels: YARN-5355, yarn-5355-merge-blocker
> Attachments: FaulttolerantwriterforTimelinev2.pdf
>
>
> We need to build a timeline writer that can be resistant to backend storage down time and timeline collector failures.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org