You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Andrew Purtell (JIRA)" <ji...@apache.org> on 2009/08/03 01:46:14 UTC
[jira] Created: (HBASE-1733) Pluggable replication framework
Pluggable replication framework
-------------------------------
Key: HBASE-1733
URL: https://issues.apache.org/jira/browse/HBASE-1733
Project: Hadoop HBase
Issue Type: Sub-task
Reporter: Andrew Purtell
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HBASE-1733) Pluggable replication framework
Posted by "Andrew Purtell (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-1733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Purtell updated HBASE-1733:
----------------------------------
Description:
Put minimal support for replication into core and plan for the rest in contrib/. Support in core can look like:
# Scope tags in WAL and HCD (HBASE-1728, HBASE-1834). Generic integer, sufficient for any number of schemes.
and handled in this issue:
# Method to register remote watchers on WAL rolls, via watcher in ZK. So this is basically distributed upcall to the listeners on roll.
# Mechanism to prevent HLog from cleaning rolled logs until all listeners have finished with it, also implemented with ZK. Could only delete when no more ephemeral subnodes on the log node, where region server would hold an entry also and delete its entry when edit content has made it out to the storefiles.
was:Take rolled logs as input and send as output filtered streams of edits across peering links to associated remote clusters. Support pluggable replication policies. Include a default policy which considers values as only either locally or globally scoped.
> Pluggable replication framework
> -------------------------------
>
> Key: HBASE-1733
> URL: https://issues.apache.org/jira/browse/HBASE-1733
> Project: Hadoop HBase
> Issue Type: Sub-task
> Reporter: Andrew Purtell
> Fix For: 0.21.0
>
>
> Put minimal support for replication into core and plan for the rest in contrib/. Support in core can look like:
> # Scope tags in WAL and HCD (HBASE-1728, HBASE-1834). Generic integer, sufficient for any number of schemes.
> and handled in this issue:
> # Method to register remote watchers on WAL rolls, via watcher in ZK. So this is basically distributed upcall to the listeners on roll.
> # Mechanism to prevent HLog from cleaning rolled logs until all listeners have finished with it, also implemented with ZK. Could only delete when no more ephemeral subnodes on the log node, where region server would hold an entry also and delete its entry when edit content has made it out to the storefiles.
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HBASE-1733) Pluggable replication framework
Posted by "Andrew Purtell (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-1733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Purtell updated HBASE-1733:
----------------------------------
Description: Take rolled logs as input and send as output filtered streams of edits across peering links to associated remote clusters. Support pluggable replication policies. Include a default policy which considers values as only either locally or globally scoped.
Fix Version/s: 0.21.0
> Pluggable replication framework
> -------------------------------
>
> Key: HBASE-1733
> URL: https://issues.apache.org/jira/browse/HBASE-1733
> Project: Hadoop HBase
> Issue Type: Sub-task
> Reporter: Andrew Purtell
> Fix For: 0.21.0
>
>
> Take rolled logs as input and send as output filtered streams of edits across peering links to associated remote clusters. Support pluggable replication policies. Include a default policy which considers values as only either locally or globally scoped.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HBASE-1733) Pluggable replication framework
Posted by "Andrew Purtell (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-1733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Purtell updated HBASE-1733:
----------------------------------
Description:
Put minimal support for replication into core and plan for the rest in contrib/. Support in core can look like:
1. Scope tags in WAL and HCD (HBASE-1728, HBASE-1834). Generic integer, sufficient for any number of schemes.
and handled in this issue:
2. Method to register remote watchers on WAL rolls, via watcher in ZK. So this is basically distributed upcall to the listeners on roll.
3. Mechanism to prevent HLog from cleaning rolled logs until all listeners have finished with it, also implemented with ZK. Could only delete when no more ephemeral subnodes on the log node, where region server would hold an entry also and delete its entry when edit content has made it out to the storefiles.
was:
Put minimal support for replication into core and plan for the rest in contrib/. Support in core can look like:
# Scope tags in WAL and HCD (HBASE-1728, HBASE-1834). Generic integer, sufficient for any number of schemes.
and handled in this issue:
# Method to register remote watchers on WAL rolls, via watcher in ZK. So this is basically distributed upcall to the listeners on roll.
# Mechanism to prevent HLog from cleaning rolled logs until all listeners have finished with it, also implemented with ZK. Could only delete when no more ephemeral subnodes on the log node, where region server would hold an entry also and delete its entry when edit content has made it out to the storefiles.
> Pluggable replication framework
> -------------------------------
>
> Key: HBASE-1733
> URL: https://issues.apache.org/jira/browse/HBASE-1733
> Project: Hadoop HBase
> Issue Type: Sub-task
> Reporter: Andrew Purtell
> Fix For: 0.21.0
>
>
> Put minimal support for replication into core and plan for the rest in contrib/. Support in core can look like:
> 1. Scope tags in WAL and HCD (HBASE-1728, HBASE-1834). Generic integer, sufficient for any number of schemes.
> and handled in this issue:
> 2. Method to register remote watchers on WAL rolls, via watcher in ZK. So this is basically distributed upcall to the listeners on roll.
> 3. Mechanism to prevent HLog from cleaning rolled logs until all listeners have finished with it, also implemented with ZK. Could only delete when no more ephemeral subnodes on the log node, where region server would hold an entry also and delete its entry when edit content has made it out to the storefiles.
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.