[
https://issues.apache.org/jira/browse/HBASE-20148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16391038#comment-16391038
]
Duo Zhang commented on HBASE-20148:
-----------------------------------
OK there is a problem with the bulk load replication feature, we used to have
the same problem if a table is serial but does not enable bulk load... Now
since we change the serial option to peer, when scoping an WAL entry before
logging, we just skip the serial replication check and treat all as serial
replication, then the problemis exposed. Let me try to find a compatible way to
deal with it...
Thanks.
> Make serial replication as a option for a peer instead of a table
> -----------------------------------------------------------------
>
> Key: HBASE-20148
> URL: https://issues.apache.org/jira/browse/HBASE-20148
> Project: HBase
> Issue Type: Sub-task
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Priority: Major
> Attachments: HBASE-20148.patch
>
>
> Discussed with [~zghaobac] and [~openinx] offline, HBASE-20147 can only be
> solved by adding new stages when creating a new replication peer. It will
> also effect he processing even if you do not have any table with serial
> replication. And also, the new logic introduced in ReplicationSource related
> classes will also be executed even if you do not have serial replication
> tables.
> So, we think that it maybe a better choice to move the option to
> ReplicationPeerConfig. Since if there is one table in the peer requires
> serial replication, then all the tables in this peer will be automatically
> 'serial' since the wal for these tables are mixed with the one which requires
> serial replication.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
