[jira] [Comment Edited] (HBASE-20691) Storage policy should allow deferring to HDFS

["Yu Li (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HBASE-20691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16532310#comment-16532310 ] 

Yu Li edited comment on HBASE-20691 at 7/4/18 6:27 AM:
-------------------------------------------------------

Pushed into master, branch-2, branch-2.0, branch-2.1, thanks all for review.

The branch-1 code base is different, attaching the patch for branch-1, will commit after HadoopQA check.


was (Author: carp84):
Pushed into master, branch-2, branch-2.1, branch-2.2, thanks all for review.

The branch-1 code base is different, attaching the patch for branch-1, will commit after HadoopQA check.

> Storage policy should allow deferring to HDFS
> ---------------------------------------------
>
>                 Key: HBASE-20691
>                 URL: https://issues.apache.org/jira/browse/HBASE-20691
>             Project: HBase
>          Issue Type: Bug
>          Components: Filesystem Integration, wal
>    Affects Versions: 1.5.0, 2.0.0
>            Reporter: Sean Busbey
>            Assignee: Yu Li
>            Priority: Blocker
>             Fix For: 2.1.0, 1.5.0
>
>         Attachments: HBASE-20691.branch-1.patch, HBASE-20691.patch, HBASE-20691.v2.patch, HBASE-20691.v3.patch, HBASE-20691.v4.patch, HBASE-20691.v5.patch, HBASE-20691.v6.patch, HBASE-20691.v7.patch, HBASE-20691.v8.patch
>
>
> In HBase 1.1 - 1.4 we can defer storage policy decisions to HDFS by using "NONE" as the storage policy in hbase configs.
> As described on this [dev@hbase thread "WAL storage policies and interactions with Hadoop admin tools."|https://lists.apache.org/thread.html/d220726fab4bb4c9e117ecc8f44246402dd97bfc986a57eb22311117@%3Cdev.hbase.apache.org%3E] we no longer have that option in 2.0.0 and 1.5.0 (as the branch is now). Additionally, we can't set the policy to HOT in the event that HDFS has changed the policy for a parent directory of our WALs.
> We should put back that ability. Presuming this is done by re-adopting the "NONE" placeholder variable, we need to ensure that value doesn't get passed to HDFS APIs. Since it isn't a valid storage policy attempting to use it will cause a bunch of logging churn (which will be a regression of the problem HBASE-18118 sought to fix).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)