[
https://issues.apache.org/jira/browse/HBASE-1112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12667444#action_12667444
]
stack commented on HBASE-1112:
------------------------------
oh... .didn't realize. Thats good. One dir per server. No harm moving all
these into a subdir though I'd say, named @LOG@ or @LOGS@ as Samuel suggests.
Also, yes, highly unlikely that there'd be a table with a clashing name but I
suppose no harm doing the little work to ensure it doesn't happen.
> we will lose data if the table name happens to be the logs' dir name
> --------------------------------------------------------------------
>
> Key: HBASE-1112
> URL: https://issues.apache.org/jira/browse/HBASE-1112
> Project: Hadoop HBase
> Issue Type: Bug
> Reporter: Samuel Guo
> Priority: Minor
> Fix For: 0.20.0
>
> Attachments: HBASE-1112.patch
>
>
> If the tablename happens to equal with the logs' dir name of a certain
> regionserver, the table will store table's data into the same dir in HDFS
> shared with the regionserver's log dir. If the specified region server fails,
> the dir may be removed after the logs are replayed. And here, we lose the
> data.
> I suggest that a special char like '_' could be added before the logdir's
> name, just as what root region and meta region have done. So we can prevent
> the user table's data from being stored in a log dir. for example,
> 'log_10.132.15.1_1231465024534_60020' will be changed to
> '_log_10.132.15.1_1231465024534_60020'.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
