hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Heng Chen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-13773) Replication should not use ZooKeeper at all for coordination
Date Mon, 26 Oct 2015 13:03:27 GMT

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

Heng Chen commented on HBASE-13773:
-----------------------------------

{quote}
If a cluster having 100 RS, will it create 100 tables ?
{quote} 
You are right. we update the v2, any suggestions? 
{code}
* We use two tables to do it.
 *
 * The first one is 'RSManager' which used to store RS and queueId information
 * RowKey is 'RS name', table only has one columnFamily 'CF', and columnKey is queueId, columnValue
is null
 *
 * The secondary table is 'RSWals' which used to store RS wals information.
 * RowKey is 'RS name + queueId', table only has one columnFamily 'CF', and columnKey is wal
file, columnValue is position
{code}


> Replication should not use ZooKeeper at all for coordination
> ------------------------------------------------------------
>
>                 Key: HBASE-13773
>                 URL: https://issues.apache.org/jira/browse/HBASE-13773
>             Project: HBase
>          Issue Type: Sub-task
>    Affects Versions: 2.0.0, 1.0.1, 1.1.0, 0.98.12, 1.2.0
>            Reporter: Andrew Purtell
>            Assignee: Maddineni Sukumar
>            Priority: Critical
>         Attachments: ReplicationQueueHBaseImpl.java, ReplicationQueueHBaseImpl_v2.java
>
>
> Introduce a new system table for replication state and use this table for coordination
instead of znodes.‚Äč



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message