hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Guanghao Zhang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-17289) Avoid adding a replication peer named "lock"
Date Mon, 12 Dec 2016 02:26:58 GMT

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

Guanghao Zhang commented on HBASE-17289:

Yes, I can do it by adding new ut... But I thought it is ok to be public. Because this is
a final String as constant. And in branch-1, it can be used on ReplicationZKNodeCleaner and
it is public too.

> Avoid adding a replication peer named "lock"
> --------------------------------------------
>                 Key: HBASE-17289
>                 URL: https://issues.apache.org/jira/browse/HBASE-17289
>             Project: HBase
>          Issue Type: Bug
>          Components: Replication
>    Affects Versions: 1.3.0, 1.4.0, 1.1.7, 0.98.23, 1.2.4
>            Reporter: Guanghao Zhang
>            Assignee: Guanghao Zhang
>            Priority: Minor
>         Attachments: HBASE-17289-branch-1.1.patch, HBASE-17289-branch-1.2.patch, HBASE-17289-branch-1.3.patch,
> When zk based replication queue is used and useMulti is false, the steps of transfer
replication queues are first add a lock, then copy nodes, finally clean old queue and the
lock. And the default lock znode's name is "lock". So we should avoid adding a peer named

This message was sent by Atlassian JIRA

View raw message