hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ted Yu (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-17543) Create additional ReplicationEndpoint WALEntryFilters by configuration
Date Wed, 01 Feb 2017 01:15:51 GMT

     [ https://issues.apache.org/jira/browse/HBASE-17543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Ted Yu updated HBASE-17543:
    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

Test failure was not related.

Thanks for the patch, Geoffrey

> Create additional ReplicationEndpoint WALEntryFilters by configuration
> ----------------------------------------------------------------------
>                 Key: HBASE-17543
>                 URL: https://issues.apache.org/jira/browse/HBASE-17543
>             Project: HBase
>          Issue Type: Improvement
>          Components: Replication
>            Reporter: Geoffrey Jacoby
>            Assignee: Geoffrey Jacoby
>             Fix For: 2.0.0, 1.4.0
>         Attachments: HBASE-17543-branch-1.patch, HBASE-17543.patch, HBASE-17543.v2.patch,
> The existing BaseReplicationEndpoint creates a ChainWALEntryFilter containing a NamespaceTableCfWALEntryFilter
and a ScopeWALEntryFilter. Adding a custom WALEntryFilter type to this chain requires creating
an entirely new ReplicationEndpoint subclass and creating a new peer on the running cluster,
which can be operationally complex to transition to without data loss in cases such as master/master.
> For WALEntryFilters without constructor parameters, it would be straightforward to have
a Configuration option to list additional WALEntryFilter classes the operator wants to include
in the filter chain in the default endpoint, and then have the endpoint instantiate the filters
via reflection. Then filter logic could be added (or removed) with only a hbase-site.xml change
and a rolling restart. 

This message was sent by Atlassian JIRA

View raw message