You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Duo Zhang (JIRA)" <ji...@apache.org> on 2018/02/05 08:22:00 UTC

[jira] [Commented] (HBASE-19936) Introduce a new base class for replication peer procedure

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

Duo Zhang commented on HBASE-19936:
-----------------------------------

[~zghaobac] FYI. Just a simple refactoring.

> 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)