hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Hsieh (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-8352) Rename '.snapshot' directory
Date Tue, 16 Apr 2013 17:35:16 GMT

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

Jonathan Hsieh commented on HBASE-8352:
---------------------------------------

bq. If hbase.snapshot.use_newdir is true we use .hbase_snapshot, if false we use .snapshot

Since HDFS snapshots seems to have an api to enable it, we could query for that instead of
introducing a new config.  We could also do a hadoop version check type query (if 1.x use
old default, if 2.x use new).

bq. We'd add both .snapshot and .hbase_snapshot to HBASE_NON_TABLE_DIRS

+1 to this in 0.94+.  Regardless of what fix we choose, preemptively doing this doesn't hurt.

bq. Thoughts? Too much effort?

I think if we put the warnings that show up in logs in, I'll be satisfied.
                
> Rename '.snapshot' directory
> ----------------------------
>
>                 Key: HBASE-8352
>                 URL: https://issues.apache.org/jira/browse/HBASE-8352
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Ted Yu
>            Assignee: Ted Yu
>            Priority: Critical
>             Fix For: 0.98.0, 0.94.7, 0.95.1
>
>         Attachments: 8352-0.94-v1.txt, 8352-trunk.txt
>
>
> Testing HBase Snapshot on top of Hadoop's Snapshot branch (http://svn.apache.org/viewvc/hadoop/common/branches/HDFS-2802/),
we found that both features used '.snapshot' directory to store metadata.
> HDFS (built from HDFS-2802 branch) doesn't allow paths with .snapshot as a component
> From discussion on dev@hbase.apache.org, (see http://search-hadoop.com/m/kY6C3cXMs51),
consensus was to rename '.snapshot' directory in HBase so that both features can co-exist
smoothly.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message