hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-12432) RpcRetryingCaller should log after fixed number of retries like AsyncProcess
Date Thu, 06 Nov 2014 01:13:33 GMT

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

stack commented on HBASE-12432:
-------------------------------

Go for it [~ndimiduk] +1

> RpcRetryingCaller should log after fixed number of retries like AsyncProcess
> ----------------------------------------------------------------------------
>
>                 Key: HBASE-12432
>                 URL: https://issues.apache.org/jira/browse/HBASE-12432
>             Project: HBase
>          Issue Type: Improvement
>          Components: Client
>            Reporter: Nick Dimiduk
>            Assignee: Nick Dimiduk
>            Priority: Minor
>         Attachments: HBASE-12432.00.patch
>
>
> Scanner retry is handled by RpcRetryingCaller. This is different from multi, which is
handled by AsyncProcess. AsyncProcess will start logging operation status after hbase.client.start.log.errors.counter
retries have been attempted. Let's bring the same functionality over to Scanner path.
> Noticed this while debugging IntegrationTestMTTR.



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

Mime
View raw message