[
https://issues.apache.org/jira/browse/HBASE-15507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15205332#comment-15205332
]
Enis Soztutar commented on HBASE-15507:
---------------------------------------
Sounds good.
Make this a part of Replication 2.0 parent jira?
bq. HBASE-11393, which will consolidate tableCFs in the same znode as the rest
of ReplicationPeerConfig, may help here, but with or without it it still seems
like there needs to be further work to add update config/data API support to
ReplicationAdmin and a callback mechanism to notify the endpoints of config
parameter changes.
[~chenheng] can say more. We have a zk tracker now, but you are right that we
need the ReplicationEndpoint to be notified.
> Online modification of enabled ReplicationPeerConfig
> ----------------------------------------------------
>
> Key: HBASE-15507
> URL: https://issues.apache.org/jira/browse/HBASE-15507
> Project: HBase
> Issue Type: Improvement
> Components: Replication
> Affects Versions: 2.0.0, 1.2.0, 1.3.0
> Reporter: Geoffrey Jacoby
> Assignee: Geoffrey Jacoby
>
> It's currently possible to update the table CFs for a replication peer while
> it's running, but not the peer configuration or data maps introduced as part
> of custom replication endpoints in HBASE-11367.
> This means that if you have a custom endpoint that depends on some
> configuration parameter, you have to remove the peer and recreate it in order
> to change the param. In some use cases that's not possible without risking
> data loss.
> HBASE-11393, which will consolidate tableCFs in the same znode as the rest of
> ReplicationPeerConfig, may help here, but with or without it it still seems
> like there needs to be further work to add update config/data API support to
> ReplicationAdmin and a callback mechanism to notify the endpoints of config
> parameter changes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
