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-14937) Make rpc call timeout for replication adaptive
Date Sun, 19 Jun 2016 04:39:05 GMT

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

Hadoop QA commented on HBASE-14937:
-----------------------------------

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:red}-1{color} | {color:red} patch {color} | {color:red} 0m 3s {color} | {color:red}
HBASE-14937 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/12778212/HBASE-14937.patch
|
| JIRA Issue | HBASE-14937 |
| Console output | https://builds.apache.org/job/PreCommit-HBASE-Build/2294/console |
| Powered by | Apache Yetus 0.2.1   http://yetus.apache.org |


This message was automatically generated.



> Make rpc call timeout for replication adaptive
> ----------------------------------------------
>
>                 Key: HBASE-14937
>                 URL: https://issues.apache.org/jira/browse/HBASE-14937
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Ashish Singhi
>            Assignee: Ashish Singhi
>              Labels: replication
>             Fix For: 2.0.0, 1.4.0
>
>         Attachments: HBASE-14937.patch
>
>
> When peer cluster replication is disabled and lot of writes are happening in active cluster
and later on peer cluster replication is enabled then there are chances that replication requests
to peer cluster may time out.
> This is possible after HBASE-13153 and it can also happen with many and many WAL data
replication still pending to replicate.
> Approach to this problem will be discussed in the comments.



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

Mime
View raw message