hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-7765) A tool to replay HLog entries in case a log file is missed while log splitting
Date Wed, 06 Feb 2013 06:59:13 GMT

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

stack commented on HBASE-7765:
------------------------------

Thanks Himanshu.  I just committed below:

{code}
@@ -263,6 +266,10 @@
 <programlisting>$ bin/hbase org.apache.hadoop.hbase.mapreduce.WALPlayer /backuplogdir
oldTable1,oldTable2 newTable1,newTable2
 </programlisting>
        </para>
+       <para>
+           WALPlayer, by default, runs as a mapreduce job.  To NOT run WALPlayer as a mapreduce
job on your cluster,
+           force it to run all in the local process by adding the flags <code>-Dmapred.job.tracker=local</code>
on the command line.
+       </para>
     </section>
     <section xml:id="rowcounter">
        <title>RowCounter and CellCounter</title>
{code}

Hopefully that'll do it.  Will now close this issue hopefully for good.  Again sorry for premature
close Himanshu and Kevin.
                
> A tool to replay HLog entries in case a log file is missed while log splitting
> ------------------------------------------------------------------------------
>
>                 Key: HBASE-7765
>                 URL: https://issues.apache.org/jira/browse/HBASE-7765
>             Project: HBase
>          Issue Type: New Feature
>          Components: wal
>    Affects Versions: 0.94.4
>            Reporter: Himanshu Vashishtha
>            Assignee: Himanshu Vashishtha
>
> There may be a case where a HLog can escape the Log splitting. 
> It will be good to have a standalone tool that reads entries from a HLog, and replays
it back to HBase. 

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