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

Hudson commented on HBASE-20167:
--------------------------------

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.


> Optimize the implementation of ReplicationSourceWALReader
> ---------------------------------------------------------
>
>                 Key: HBASE-20167
>                 URL: https://issues.apache.org/jira/browse/HBASE-20167
>             Project: HBase
>          Issue Type: Sub-task
>          Components: Replication
>            Reporter: Duo Zhang
>            Assignee: Duo Zhang
>            Priority: Major
>             Fix For: 3.0.0
>
>         Attachments: HBASE-20167-v1.patch, HBASE-20167-v2.patch, 
> HBASE-20167.patch
>
>
> After HBASE-20148, serial replication will be an option for peer. Since an 
> instance of ReplicationSourceWALReader can only belongs to one peer, we do 
> not need to add the so many 'if' in the implementation of readWALEntries to 
> check whether we should consider serial replication. We can just make a sub 
> class or something similiar for serial replication to make the code clean.



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

Reply via email to