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 "Abhishek Modi (JIRA)" <ji...@apache.org> on 2018/01/12 06:42:00 UTC
[jira] [Commented] (YARN-3841) [Storage implementation] Adding
retry semantics to HDFS backing storage
[ https://issues.apache.org/jira/browse/YARN-3841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16323624#comment-16323624 ]
Abhishek Modi commented on YARN-3841:
-------------------------------------
Hi [~gtCarrera9] [~ozawa],
At our company, we used HDFS as storage for trying out ATSv2. If it's fine for you, can I create a new patch on top of YARN-7055 branch. Thanks.
> [Storage implementation] Adding retry semantics to HDFS backing storage
> -----------------------------------------------------------------------
>
> Key: YARN-3841
> URL: https://issues.apache.org/jira/browse/YARN-3841
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: timelineserver
> Reporter: Tsuyoshi Ozawa
> Assignee: Tsuyoshi Ozawa
> Labels: YARN-5355
> Attachments: YARN-3841.001.patch
>
>
> HDFS backing storage is useful for following scenarios.
> 1. For Hadoop clusters which don't run HBase.
> 2. For fallback from HBase when HBase cluster is temporary unavailable. Quoting ATS design document of YARN-2928:
> {quote}
> In the case the HBase
> storage is not available, the plugin should buffer the writes temporarily (e.g. HDFS), and flush
> them once the storage comes back online. Reading and writing to hdfs as the the backup storage
> could potentially use the HDFS writer plugin unless the complexity of generalizing the HDFS
> writer plugin for this purpose exceeds the benefits of reusing it here.
> {quote}
--
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