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 "Tsuyoshi Ozawa (JIRA)" <ji...@apache.org> on 2015/09/01 13:11:47 UTC

[jira] [Updated] (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:all-tabpanel ]

Tsuyoshi Ozawa updated YARN-3841:
---------------------------------
    Summary: [Storage implementation] Adding retry semantics to HDFS backing storage  (was: [Storage implementation] Create HDFS backing storage implementation for ATS writes)

> [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
>         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.3.4#6332)