[
https://issues.apache.org/jira/browse/HBASE-20148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16416636#comment-16416636
]
Hudson commented on HBASE-20148:
--------------------------------
Results for branch HBASE-19064
[build #77 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/HBASE-19064/77/]:
(x) *{color:red}-1 overall{color}*
----
details (if available):
(x) {color:red}-1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/HBASE-19064/77//General_Nightly_Build_Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/HBASE-19064/77//JDK8_Nightly_Build_Report_(Hadoop2)/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/HBASE-19064/77//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
> 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
> Components: Replication
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Priority: Major
> Fix For: 3.0.0
>
> Attachments: HBASE-20148-v1.patch, HBASE-20148-v2.patch,
> HBASE-20148-v3.patch, 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)
