[
https://issues.apache.org/jira/browse/HBASE-12432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14199568#comment-14199568
]
stack commented on HBASE-12432:
-------------------------------
bq. Shouldn't we should consolidate these into a single execution path?
What do you think I'm going to say ? (smile)
> 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
> Fix For: 2.0.0, 0.98.8, 0.99.2
>
> Attachments: HBASE-12432.00-0.98.patch, 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)
