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

chunhui shen commented on HBASE-7213:
-------------------------------------

From
{code}
public HLog getWAL(HRegionInfo regionInfo) throws IOException {
    //TODO: at some point this should delegate to the HLogFactory
    //currently, we don't care about the region as much as we care about the 
    //table.. (hence checking the tablename below)
    if (regionInfo != null && 
        Arrays.equals(regionInfo.getTableName(), HConstants.META_TABLE_NAME)) {
      return getMetaWAL();
    }
{code}

what about ROOT region? we put its logs with other user regions?
In MetaServerShutdownHadnler, we consider META and ROOT both are meta regions.


Correct me if wrong

Thanks. 
                
> Have HLog files for .META. edits only
> -------------------------------------
>
>                 Key: HBASE-7213
>                 URL: https://issues.apache.org/jira/browse/HBASE-7213
>             Project: HBase
>          Issue Type: Improvement
>          Components: master, regionserver
>            Reporter: Devaraj Das
>            Assignee: Devaraj Das
>            Priority: Critical
>             Fix For: 0.96.0
>
>         Attachments: 7213-2.10.patch, 7213-2.11.patch, 7213-2.12.patch, 
> 7213-2.14.patch, 7213-2.14.patch, 7213-2.4.patch, 7213-2.6.patch, 
> 7213-2.8.patch, 7213-2.9.patch, 7213-in-progress.2.2.patch, 
> 7213-in-progress.2.patch, 7213-in-progress.patch, 7213v13.txt, 
> TEST-org.apache.hadoop.hbase.client.TestMultiParallel.xml
>
>
> Over on HBASE-6774, there is a discussion on separating out the edits for 
> .META. regions from the other regions' edits w.r.t where the edits are 
> written. This jira is to track an implementation of that.

--
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

Reply via email to