[
https://issues.apache.org/jira/browse/HBASE-1844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-1844:
-------------------------
Summary: The ability to set a (global) client side timeout (was: The
ability to set a client side timeout)
Retries and pause do this currently. Fixing them so they are less
coarse-grained won't be done for 0.20.x, it would require rewrite of client --
something we will probably do soon -- to keep a global timer on overall
request, one that included everything from a GCs to -ROOT- and .META. look ups,
as well as time-to-read.
Moving out of 0.20.1. Added 'global' to the subject.
This issue is related to hbase-1843
> The ability to set a (global) client side timeout
> -------------------------------------------------
>
> Key: HBASE-1844
> URL: https://issues.apache.org/jira/browse/HBASE-1844
> Project: Hadoop HBase
> Issue Type: New Feature
> Components: client
> Affects Versions: 0.20.0
> Reporter: Barney Frank
> Fix For: 0.20.1
>
>
> The ability to set a maximum wait time for a client request in milliseconds.
> For example, I would only wait 100ms for the data from HBase before I would
> move on with another process. An exception would be thrown if over the wait
> time. It would be speacified in the HBaseConfiguration (hbase-site.xml) on
> the client.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
