hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Purtell (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-12091) Optionally ignore edits for dropped tables for replication.
Date Wed, 01 Nov 2017 19:18:00 GMT

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

Andrew Purtell commented on HBASE-12091:
----------------------------------------

{code}
+  public static final String REPLICATION_CONTINUE_ON_DELETED_TABLE_KEY =
+      "hbase.replication.continue.on.deleted.tables";
{code}
This is ok, but it may not be clear what "continue on deleted" means. It would be clearer
to call this "hbase.replication.drop.on.deleted.tables".

> Optionally ignore edits for dropped tables for replication.
> -----------------------------------------------------------
>
>                 Key: HBASE-12091
>                 URL: https://issues.apache.org/jira/browse/HBASE-12091
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Lars Hofhansl
>            Assignee: Lars Hofhansl
>            Priority: Major
>             Fix For: 1.4.0
>
>         Attachments: 12091-v2-branch-1.txt, 12091-v3-branch-1.txt, 12091-v4-branch-1.txt,
12091.txt
>
>
> We just ran into a scenario where we dropped a table from both the source and the sink,
but the source still has outstanding edits that now it could not get rid of. Now all replication
is backed up behind these unreplicatable edits.
> We should have an option to ignore edits for tables dropped at the source.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message