hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ashish Singhi (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-14937) Make rpc call timeout for replication adaptive
Date Fri, 04 Mar 2016 11:20:40 GMT

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

Ashish Singhi commented on HBASE-14937:
---------------------------------------

[~andrew.purtell@gmail.com], how about adding another configuration which will limit these
callTimeout value ? So that user can set this max replication rpc timeout value according
to her/his needs. Default being 2 hours.

> 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.3.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