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-20426) Give up replicating anything in S state
Date Wed, 25 Apr 2018 09:32:00 GMT

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

Hadoop QA commented on HBASE-20426:
-----------------------------------

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m 14s{color} | {color:blue}
Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red}  0m  3s{color} | {color:red}
HBASE-20426 does not apply to HBASE-19064. Rebase required? Wrong Branch? See https://yetus.apache.org/documentation/0.7.0/precommit-patchnames
for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:d8b550f |
| JIRA Issue | HBASE-20426 |
| JIRA Patch URL | https://issues.apache.org/jira/secure/attachment/12920604/HBASE-20426-HBASE-19064.patch
|
| Console output | https://builds.apache.org/job/PreCommit-HBASE-Build/12631/console |
| Powered by | Apache Yetus 0.7.0   http://yetus.apache.org |


This message was automatically generated.



> Give up replicating anything in S state
> ---------------------------------------
>
>                 Key: HBASE-20426
>                 URL: https://issues.apache.org/jira/browse/HBASE-20426
>             Project: HBase
>          Issue Type: Sub-task
>          Components: Replication
>            Reporter: Duo Zhang
>            Assignee: Duo Zhang
>            Priority: Major
>             Fix For: HBASE-19064
>
>         Attachments: HBASE-20426-HBASE-19064.patch, HBASE-20426-HBASE-19064.patch, HBASE-20426-HBASE-19064.patch,
HBASE-20426-UT.patch
>
>
> When we transit the remote S cluster to DA, and then transit the old A cluster to S,
it is possible that we still have some entries which have not been replicated yet for the
old A cluster, and then the async replication will be blocked.
> And this may also lead to data inconsistency after we transit it to DA back later as
these entries will be replicated again, but the new data which are replicated from the remote
cluster will not be replicated back, which introduce a whole in the replication.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message