[jira] [Updated] (HBASE-20138) Find a way to deal with the conflicts when updating replication position
[ https://issues.apache.org/jira/browse/HBASE-20138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zheng Hu updated HBASE-20138: - Component/s: Replication > Find a way to deal with the conflicts when updating replication position > > > Key: HBASE-20138 > URL: https://issues.apache.org/jira/browse/HBASE-20138 > Project: HBase > Issue Type: Sub-task > Components: Replication >Reporter: Duo Zhang >Assignee: Zheng Hu >Priority: Major > Fix For: 3.0.0, 2.1.0 > > Attachments: HBASE-20138.v1.patch, HBASE-20138.v2.patch, > HBASE-20138.v3.patch, HBASE-20138.v4.patch, HBASE-20138.v5.patch, > HBASE-20138.v6.patch, HBASE-20138.v7.patch > > > For now if a table is not created with SERIAL_REPLICATION_SCOPE and later > converted to SERIAL_REPLICATION_SCOPE , then we may have multiple replication > sources which replicate the different ranges for the same region and update > the queue storage concurrently. This will cause problem if the lower range > finish at last since the replication position will be wrong... > Need to find a way to deal with this. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-20138) Find a way to deal with the conflicts when updating replication position
[ https://issues.apache.org/jira/browse/HBASE-20138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zheng Hu updated HBASE-20138: - Resolution: Fixed Hadoop Flags: Reviewed Status: Resolved (was: Patch Available) > Find a way to deal with the conflicts when updating replication position > > > Key: HBASE-20138 > URL: https://issues.apache.org/jira/browse/HBASE-20138 > Project: HBase > Issue Type: Sub-task > Components: Replication >Reporter: Duo Zhang >Assignee: Zheng Hu >Priority: Major > Fix For: 3.0.0, 2.1.0 > > Attachments: HBASE-20138.v1.patch, HBASE-20138.v2.patch, > HBASE-20138.v3.patch, HBASE-20138.v4.patch, HBASE-20138.v5.patch, > HBASE-20138.v6.patch, HBASE-20138.v7.patch > > > For now if a table is not created with SERIAL_REPLICATION_SCOPE and later > converted to SERIAL_REPLICATION_SCOPE , then we may have multiple replication > sources which replicate the different ranges for the same region and update > the queue storage concurrently. This will cause problem if the lower range > finish at last since the replication position will be wrong... > Need to find a way to deal with this. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-20138) Find a way to deal with the conflicts when updating replication position
[ https://issues.apache.org/jira/browse/HBASE-20138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zheng Hu updated HBASE-20138: - Attachment: HBASE-20138.v7.patch > Find a way to deal with the conflicts when updating replication position > > > Key: HBASE-20138 > URL: https://issues.apache.org/jira/browse/HBASE-20138 > Project: HBase > Issue Type: Sub-task >Reporter: Duo Zhang >Assignee: Zheng Hu >Priority: Major > Fix For: 3.0.0, 2.1.0 > > Attachments: HBASE-20138.v1.patch, HBASE-20138.v2.patch, > HBASE-20138.v3.patch, HBASE-20138.v4.patch, HBASE-20138.v5.patch, > HBASE-20138.v6.patch, HBASE-20138.v7.patch > > > For now if a table is not created with SERIAL_REPLICATION_SCOPE and later > converted to SERIAL_REPLICATION_SCOPE , then we may have multiple replication > sources which replicate the different ranges for the same region and update > the queue storage concurrently. This will cause problem if the lower range > finish at last since the replication position will be wrong... > Need to find a way to deal with this. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-20138) Find a way to deal with the conflicts when updating replication position
[ https://issues.apache.org/jira/browse/HBASE-20138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zheng Hu updated HBASE-20138: - Attachment: HBASE-20138.v6.patch > Find a way to deal with the conflicts when updating replication position > > > Key: HBASE-20138 > URL: https://issues.apache.org/jira/browse/HBASE-20138 > Project: HBase > Issue Type: Sub-task >Reporter: Duo Zhang >Assignee: Zheng Hu >Priority: Major > Fix For: 3.0.0, 2.1.0 > > Attachments: HBASE-20138.v1.patch, HBASE-20138.v2.patch, > HBASE-20138.v3.patch, HBASE-20138.v4.patch, HBASE-20138.v5.patch, > HBASE-20138.v6.patch > > > For now if a table is not created with SERIAL_REPLICATION_SCOPE and later > converted to SERIAL_REPLICATION_SCOPE , then we may have multiple replication > sources which replicate the different ranges for the same region and update > the queue storage concurrently. This will cause problem if the lower range > finish at last since the replication position will be wrong... > Need to find a way to deal with this. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-20138) Find a way to deal with the conflicts when updating replication position
[ https://issues.apache.org/jira/browse/HBASE-20138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zheng Hu updated HBASE-20138: - Attachment: HBASE-20138.v5.patch > Find a way to deal with the conflicts when updating replication position > > > Key: HBASE-20138 > URL: https://issues.apache.org/jira/browse/HBASE-20138 > Project: HBase > Issue Type: Sub-task >Reporter: Duo Zhang >Assignee: Zheng Hu >Priority: Major > Fix For: 3.0.0, 2.1.0 > > Attachments: HBASE-20138.v1.patch, HBASE-20138.v2.patch, > HBASE-20138.v3.patch, HBASE-20138.v4.patch, HBASE-20138.v5.patch > > > For now if a table is not created with SERIAL_REPLICATION_SCOPE and later > converted to SERIAL_REPLICATION_SCOPE , then we may have multiple replication > sources which replicate the different ranges for the same region and update > the queue storage concurrently. This will cause problem if the lower range > finish at last since the replication position will be wrong... > Need to find a way to deal with this. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-20138) Find a way to deal with the conflicts when updating replication position
[ https://issues.apache.org/jira/browse/HBASE-20138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zheng Hu updated HBASE-20138: - Attachment: HBASE-20138.v4.patch > Find a way to deal with the conflicts when updating replication position > > > Key: HBASE-20138 > URL: https://issues.apache.org/jira/browse/HBASE-20138 > Project: HBase > Issue Type: Sub-task >Reporter: Duo Zhang >Assignee: Zheng Hu >Priority: Major > Fix For: 3.0.0, 2.1.0 > > Attachments: HBASE-20138.v1.patch, HBASE-20138.v2.patch, > HBASE-20138.v3.patch, HBASE-20138.v4.patch > > > For now if a table is not created with SERIAL_REPLICATION_SCOPE and later > converted to SERIAL_REPLICATION_SCOPE , then we may have multiple replication > sources which replicate the different ranges for the same region and update > the queue storage concurrently. This will cause problem if the lower range > finish at last since the replication position will be wrong... > Need to find a way to deal with this. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-20138) Find a way to deal with the conflicts when updating replication position
[ https://issues.apache.org/jira/browse/HBASE-20138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zheng Hu updated HBASE-20138: - Attachment: HBASE-20138.v3.patch > Find a way to deal with the conflicts when updating replication position > > > Key: HBASE-20138 > URL: https://issues.apache.org/jira/browse/HBASE-20138 > Project: HBase > Issue Type: Sub-task >Reporter: Duo Zhang >Assignee: Zheng Hu >Priority: Major > Fix For: 3.0.0, 2.1.0 > > Attachments: HBASE-20138.v1.patch, HBASE-20138.v2.patch, > HBASE-20138.v3.patch > > > For now if a table is not created with SERIAL_REPLICATION_SCOPE and later > converted to SERIAL_REPLICATION_SCOPE , then we may have multiple replication > sources which replicate the different ranges for the same region and update > the queue storage concurrently. This will cause problem if the lower range > finish at last since the replication position will be wrong... > Need to find a way to deal with this. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-20138) Find a way to deal with the conflicts when updating replication position
[ https://issues.apache.org/jira/browse/HBASE-20138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zheng Hu updated HBASE-20138: - Attachment: HBASE-20138.v2.patch > Find a way to deal with the conflicts when updating replication position > > > Key: HBASE-20138 > URL: https://issues.apache.org/jira/browse/HBASE-20138 > Project: HBase > Issue Type: Sub-task >Reporter: Duo Zhang >Assignee: Zheng Hu >Priority: Major > Fix For: 3.0.0, 2.1.0 > > Attachments: HBASE-20138.v1.patch, HBASE-20138.v2.patch > > > For now if a table is not created with SERIAL_REPLICATION_SCOPE and later > converted to SERIAL_REPLICATION_SCOPE , then we may have multiple replication > sources which replicate the different ranges for the same region and update > the queue storage concurrently. This will cause problem if the lower range > finish at last since the replication position will be wrong... > Need to find a way to deal with this. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-20138) Find a way to deal with the conflicts when updating replication position
[ https://issues.apache.org/jira/browse/HBASE-20138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zheng Hu updated HBASE-20138: - Fix Version/s: 2.1.0 3.0.0 Status: Patch Available (was: Open) > Find a way to deal with the conflicts when updating replication position > > > Key: HBASE-20138 > URL: https://issues.apache.org/jira/browse/HBASE-20138 > Project: HBase > Issue Type: Sub-task >Reporter: Duo Zhang >Assignee: Zheng Hu >Priority: Major > Fix For: 3.0.0, 2.1.0 > > Attachments: HBASE-20138.v1.patch > > > For now if a table is not created with SERIAL_REPLICATION_SCOPE and later > converted to SERIAL_REPLICATION_SCOPE , then we may have multiple replication > sources which replicate the different ranges for the same region and update > the queue storage concurrently. This will cause problem if the lower range > finish at last since the replication position will be wrong... > Need to find a way to deal with this. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-20138) Find a way to deal with the conflicts when updating replication position
[ https://issues.apache.org/jira/browse/HBASE-20138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zheng Hu updated HBASE-20138: - Attachment: HBASE-20138.v1.patch > Find a way to deal with the conflicts when updating replication position > > > Key: HBASE-20138 > URL: https://issues.apache.org/jira/browse/HBASE-20138 > Project: HBase > Issue Type: Sub-task >Reporter: Duo Zhang >Assignee: Zheng Hu >Priority: Major > Attachments: HBASE-20138.v1.patch > > > For now if a table is not created with SERIAL_REPLICATION_SCOPE and later > converted to SERIAL_REPLICATION_SCOPE , then we may have multiple replication > sources which replicate the different ranges for the same region and update > the queue storage concurrently. This will cause problem if the lower range > finish at last since the replication position will be wrong... > Need to find a way to deal with this. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
