[
https://issues.apache.org/jira/browse/HBASE-19936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16352639#comment-16352639
]
Hudson commented on HBASE-19936:
--------------------------------
FAILURE: Integrated in Jenkins build HBase-Trunk_matrix #4531 (See
[https://builds.apache.org/job/HBase-Trunk_matrix/4531/])
HBASE-19936 Introduce a new base class for replication peer procedure
(zhangduo: rev ad3a1ba4955ee8a6d8470f1ad4fcc4f2c69e6787)
* (edit)
hbase-server/src/main/java/org/apache/hadoop/hbase/master/replication/ModifyPeerProcedure.java
* (edit) hbase-protocol-shaded/src/main/protobuf/MasterProcedure.proto
* (add)
hbase-server/src/main/java/org/apache/hadoop/hbase/master/replication/AbstractPeerProcedure.java
> Introduce a new base class for replication peer procedure
> ---------------------------------------------------------
>
> Key: HBASE-19936
> URL: https://issues.apache.org/jira/browse/HBASE-19936
> Project: HBase
> Issue Type: Sub-task
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Priority: Major
> Fix For: 3.0.0
>
> Attachments: HBASE-19936.patch
>
>
> As the sync replication peer state transition will have more steps than
> normal replication peer, it will be good to have a common base class for them.
> Since the peer id will be stored in this class, I tend to change the protobuf
> message name from 'ModifyPeerStateData' to
> 'ReplicationPeerProcedureStateData'. This will be committed to master and
> HBASE-19397-branch-2.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
