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

Anoop Sam John commented on HBASE-19166:
----------------------------------------

bq.On an hbase1 splitting hbase2 logs and failing as per the above, that might 
be ok;
That should be an issue no?  When the cluster is a mix of HBase 1 and 2 RSs 
(upgrade in progress)  and one  2.0 RS crashed and the WAL split is been done 
by a 1.x server?

> Add translation for handling hbase.regionserver.wal.WALEdit
> -----------------------------------------------------------
>
>                 Key: HBASE-19166
>                 URL: https://issues.apache.org/jira/browse/HBASE-19166
>             Project: HBase
>          Issue Type: Bug
>          Components: wal
>            Reporter: Ted Yu
>            Assignee: stack
>            Priority: Blocker
>             Fix For: 2.0.0
>
>
> For hlog generated by 1.x, using WALPlayer from hbase2 would result in:
> {code}
> 2017-11-02 21:22:40,907 INFO  [main] mapreduce.Job: Task Id : 
> attempt_1509641483571_0003_m_000000_0, Status : FAILED
> Error: java.lang.ClassCastException: 
> org.apache.hadoop.hbase.regionserver.wal.WALEdit cannot be cast to 
> org.apache.hadoop.hbase.wal.WALEdit
>         at 
> org.apache.hadoop.hbase.mapreduce.WALPlayer$WALCellMapper.map(WALPlayer.java:143)
>         at org.apache.hadoop.mapreduce.Mapper.run(Mapper.java:146)
>         at org.apache.hadoop.mapred.MapTask.runNewMapper(MapTask.java:793)
> {code}
> HBASE-16479 relocated WALEdit.
> Chatting with Enis, he mentioned adding translation for handling 
> hbase.regionserver.wal.WALEdit
> This way, WAL from 1.x can be recognized by hbase-2



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

Reply via email to