You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2018/09/12 19:33:00 UTC

[jira] [Created] (HBASE-21193) Retrying Callable doesn't take max retries from current context; uses defaults instead

stack created HBASE-21193:
-----------------------------

             Summary: 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


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)