[
https://issues.apache.org/jira/browse/HBASE-14937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15048997#comment-15048997
]
Ashish Singhi commented on HBASE-14937:
---------------------------------------
To solve this problem client can simply increase the timeout value for
{{hbase.rpc.timeout}} as per their requirement (by default it is 1 minute) but
this will apply to all the RPC requests so rather than doing this we can make
it adaptive by adding another configuration {{hbase.replication.rpc.timeout}}
with default value as {{hbase.rpc.timeout}} and set this as call timeout value
to the rpc request and on every {{CallTimeOutException}} we can increase this
value with some multiplier for some configurable number of times and set this
timeout value for the next retry of replication request.
Any other thoughts ?
> 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
>
> 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)
