You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Sandeep Pal (Jira)" <ji...@apache.org> on 2020/12/14 17:42:00 UTC

[jira] [Updated] (HBASE-25383) HBase doesn't update and remove the peer config from hbase.replication.source.custom.walentryfilters if the config is already set on the peer.

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

Sandeep Pal updated HBASE-25383:
--------------------------------
    Description: 
Currently, we cannot update the peer-based config even if we change the value of the config.
Secondly, once the configuration is added, there is no smooth way to remove the peer config.   
        Summary: HBase doesn't update and remove the peer config from hbase.replication.source.custom.walentryfilters if the config is already set on the peer.   (was: HBase doesn't update the peer config from hbase.replication.source.custom.walentryfilters if the config is already set on the peer. )

> HBase doesn't update and remove the peer config from hbase.replication.source.custom.walentryfilters if the config is already set on the peer. 
> -----------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-25383
>                 URL: https://issues.apache.org/jira/browse/HBASE-25383
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Sandeep Pal
>            Assignee: Sandeep Pal
>            Priority: Major
>
> Currently, we cannot update the peer-based config even if we change the value of the config.
> Secondly, once the configuration is added, there is no smooth way to remove the peer config.   



--
This message was sent by Atlassian Jira
(v8.3.4#803005)