[
https://issues.apache.org/jira/browse/PHOENIX-3846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16007257#comment-16007257
]
Geoffrey Jacoby commented on PHOENIX-3846:
------------------------------------------
[~easyliangjob] - Is that property set on both source and target clusters? Is
there an exception you're seeing in the logs? What version of Phoenix/HBase are
you using?
I've used both the IndexedWALEditCodec setting for secondary indexes and HBase
replication together in production, and haven't seen any issue. However, if you
were trying to write IndexedWALEditCodecs to the source cluster while the
target cluster wasn't set up properly to read them, I'd expect that to break
replication.
> IndexedWALEditCodec make hbase cluster replication does not work
> ----------------------------------------------------------------
>
> Key: PHOENIX-3846
> URL: https://issues.apache.org/jira/browse/PHOENIX-3846
> Project: Phoenix
> Issue Type: Bug
> Reporter: Yi Liang
>
> <property>
> <name>hbase.regionserver.wal.codec</name>
> <value>org.apache.hadoop.hbase.regionserver.wal.IndexedWALEditCodec</value>
> </property>
> When have above settings, the hbase cluster replication does not work. If I
> change above value back to WALCellCodec, the hbase cluster replication works
> fine.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
