[ https://issues.apache.org/jira/browse/HBASE-19166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16362929#comment-16362929 ]
stack commented on HBASE-19166: ------------------------------- Regards the description, a WALPlayer from hbase1 trying to read a hbase2 WAL, just use an hbase2 WALPlayer to do the job. On an hbase1 splitting hbase2 logs and failing as per the above, that might be ok; it just means we need to add more RegionServers to the cluster of hbase2-type that can split the logs. Need to plan rolling upgrade. That'll tell us if we need this facility or not. Meantime moving out of beta-2. > 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)