[jira] [Updated] (HBASE-20046) Reconsider the implementation for serial replication
[ https://issues.apache.org/jira/browse/HBASE-20046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang updated HBASE-20046: -- Release Note: Now in replication we can make sure the order of pushing logs is same as the order of requests from client. Set the serial flag to true for a replication peer to enable this feature. > Reconsider the implementation for serial replication > > > Key: HBASE-20046 > URL: https://issues.apache.org/jira/browse/HBASE-20046 > Project: HBase > Issue Type: New Feature > Components: Replication >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Major > Fix For: 3.0.0, 2.1.0 > > Attachments: HBASE-20046.pdf > > > When implementing HBASE-9465 we added two new families to meta table, one is > rep meta and the other is rep_position. In general I think rep_meta is OK to > put into meta table since it records the open and close sequence id for a > region, but for rep_position, I think it should be put into another system > table instead of meta table. > This should be done before we finally release 2.0.0 or 1.5.0. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-20046) Reconsider the implementation for serial replication
[ https://issues.apache.org/jira/browse/HBASE-20046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang updated HBASE-20046: -- Attachment: HBASE-20046.pdf > Reconsider the implementation for serial replication > > > Key: HBASE-20046 > URL: https://issues.apache.org/jira/browse/HBASE-20046 > Project: HBase > Issue Type: New Feature > Components: Replication >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Major > Fix For: 3.0.0, 2.1.0 > > Attachments: HBASE-20046.pdf > > > When implementing HBASE-9465 we added two new families to meta table, one is > rep meta and the other is rep_position. In general I think rep_meta is OK to > put into meta table since it records the open and close sequence id for a > region, but for rep_position, I think it should be put into another system > table instead of meta table. > This should be done before we finally release 2.0.0 or 1.5.0. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-20046) Reconsider the implementation for serial replication
[ https://issues.apache.org/jira/browse/HBASE-20046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang updated HBASE-20046: -- Priority: Major (was: Blocker) Fix Version/s: (was: 1.5.0) (was: 2.0.0) 2.1.0 3.0.0 Issue Type: New Feature (was: Bug) > Reconsider the implementation for serial replication > > > Key: HBASE-20046 > URL: https://issues.apache.org/jira/browse/HBASE-20046 > Project: HBase > Issue Type: New Feature > Components: Replication >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Major > Fix For: 3.0.0, 2.1.0 > > > When implementing HBASE-9465 we added two new families to meta table, one is > rep meta and the other is rep_position. In general I think rep_meta is OK to > put into meta table since it records the open and close sequence id for a > region, but for rep_position, I think it should be put into another system > table instead of meta table. > This should be done before we finally release 2.0.0 or 1.5.0. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-20046) Reconsider the implementation for serial replication
[ https://issues.apache.org/jira/browse/HBASE-20046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang updated HBASE-20046: -- Summary: Reconsider the implementation for serial replication (was: Reconsider the meta schema change in HBASE-9465) > Reconsider the implementation for serial replication > > > Key: HBASE-20046 > URL: https://issues.apache.org/jira/browse/HBASE-20046 > Project: HBase > Issue Type: Bug > Components: Replication >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Blocker > Fix For: 3.0.0, 2.1.0 > > > When implementing HBASE-9465 we added two new families to meta table, one is > rep meta and the other is rep_position. In general I think rep_meta is OK to > put into meta table since it records the open and close sequence id for a > region, but for rep_position, I think it should be put into another system > table instead of meta table. > This should be done before we finally release 2.0.0 or 1.5.0. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
