[
https://issues.apache.org/jira/browse/HBASE-21193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16625771#comment-16625771
]
stack commented on HBASE-21193:
-------------------------------
Thank you [~xucang] for taking a look. I'm glad the maxattempts is working. I
need to do better explanation of the phenomenon I saw.... why I thought it
wasn't working. I've lost my context though now and rather than leave this
issue open, let me resolve it. I'll assign it to you since you did some nice
work. Thank you.
> Retrying Callable doesn't take max retries from current context; uses
> defaults instead
> --------------------------------------------------------------------------------------
>
> Key: HBASE-21193
> URL: https://issues.apache.org/jira/browse/HBASE-21193
> Project: HBase
> Issue Type: Bug
> Reporter: stack
> Priority: Major
>
> This makes it hard to change retry count on a read of meta for instance.
> I noticed this when trying to change the defaults for a meta read. I made a
> customer Connection inside in the master with a new Configuration that had
> rpc retries and timings upped radically. My reads nonetheless were finishing
> at the usual retry point (31 tries after 60 seconds or so) because it looked
> like the Retrying Callable that does the read was taking max retries from
> defaults rather than reading the passed in Configuration.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
