hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-16096) Replication keeps accumulating znodes
Date Mon, 18 Jul 2016 18:19:20 GMT

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

Hadoop QA commented on HBASE-16096:
-----------------------------------

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:red}-1{color} | {color:red} patch {color} | {color:red} 0m 4s {color} | {color:red}
HBASE-16096 does not apply to master. Rebase required? Wrong Branch? See https://yetus.apache.org/documentation/0.2.1/precommit-patchnames
for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Patch URL | https://issues.apache.org/jira/secure/attachment/12818595/HBASE-16096-v3.patch
|
| JIRA Issue | HBASE-16096 |
| Console output | https://builds.apache.org/job/PreCommit-HBASE-Build/2667/console |
| Powered by | Apache Yetus 0.2.1   http://yetus.apache.org |


This message was automatically generated.



> Replication keeps accumulating znodes
> -------------------------------------
>
>                 Key: HBASE-16096
>                 URL: https://issues.apache.org/jira/browse/HBASE-16096
>             Project: HBase
>          Issue Type: Bug
>          Components: Replication
>    Affects Versions: 2.0.0, 1.2.0, 1.3.0
>            Reporter: Ashu Pachauri
>            Assignee: Joseph
>         Attachments: HBASE-16096-v3.patch
>
>
> If there is an error while creating the replication source on adding the peer, the source
if not added to the in memory list of sources but the replication peer is. 
> However, in such a scenario, when you remove the peer, it is deleted from zookeeper successfully
but for removing the in memory list of peers, we wait for the corresponding sources to get
deleted (which as we said don't exist because of error creating the source). 
> The problem here is the ordering of operations for adding/removing source and peer. 
> Modifying the code to always remove queues from the underlying storage, even if there
exists no sources also requires a small refactoring of TableBasedReplicationQueuesImpl to
not abort on removeQueues() of an empty queue



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

Mime
View raw message