[
https://issues.apache.org/jira/browse/YARN-4061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15762438#comment-15762438
]
Li Lu commented on YARN-4061:
-----------------------------
Thanks [~jrottinghuis]!
bq. For our usecase, that makes the puts idempotent. Other use-cases may not
need this requirement, but they do need to deal with duplicate puts.
That makes sense to me. However do we think this is too specific (at least for
now) for our use case in timeline v2? I can understand if there are concerns in
the HBase community if we'd like to put this immediately into HBase codebase...
Maybe what we can do is to expose buffered mutators from Hbase, and implement
our own spooling buffered mutator in timeline code?
> [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.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
