[jira] [Updated] (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:all-tabpanel ] Duo Zhang updated HBASE-19936: -- Fix Version/s: 2.2.0 > 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, 2.1.0, 2.2.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)
[jira] [Updated] (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:all-tabpanel ] Duo Zhang updated HBASE-19936: -- Fix Version/s: 2.1.0 > 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, 2.1.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)
[jira] [Updated] (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:all-tabpanel ] Duo Zhang updated HBASE-19936: -- Fix Version/s: 2.1.0 > 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, 2.1.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)
[jira] [Updated] (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:all-tabpanel ] Duo Zhang updated HBASE-19936: -- Resolution: Fixed Hadoop Flags: Reviewed Status: Resolved (was: Patch Available) Pushed to master and branch HBASE-19397-branch-2. Thanks [~zghaobac] for reviewing. > 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)
[jira] [Updated] (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:all-tabpanel ] Duo Zhang updated HBASE-19936: -- Status: Patch Available (was: Open) > 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)
[jira] [Updated] (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:all-tabpanel ] Duo Zhang updated HBASE-19936: -- Attachment: maxlimit > 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)
[jira] [Updated] (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:all-tabpanel ] Duo Zhang updated HBASE-19936: -- Attachment: HBASE-19936.patch > 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)
[jira] [Updated] (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:all-tabpanel ] Duo Zhang updated HBASE-19936: -- Attachment: (was: maxlimit) > 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)
