You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Geoffrey Jacoby (JIRA)" <ji...@apache.org> on 2017/06/28 22:58:00 UTC

[jira] [Reopened] (PHOENIX-2916) Need a client-side level property to control write timeout

     [ https://issues.apache.org/jira/browse/PHOENIX-2916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Geoffrey Jacoby reopened PHOENIX-2916:
--------------------------------------
      Assignee: Geoffrey Jacoby

Reopening because now that we have PHOENIX-541 and PHOENIX-3612, one client-side upsert batch can consist of multiple HBase rpc calls, so the HBase-level write timeout introduced in HBASE-15866 isn't as expressive as a true phoenix.update.timeoutMs would be. 

> Need a client-side level property to control write timeout
> ----------------------------------------------------------
>
>                 Key: PHOENIX-2916
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-2916
>             Project: Phoenix
>          Issue Type: New Feature
>            Reporter: Alex Warshavsky
>            Assignee: Geoffrey Jacoby
>            Priority: Minor
>
> Currently, there's a client side property phoenix.query.timeoutMs which allows query to timeout after the specified time. However, there's no equivalent property to allow upserts (writes) to timeout if the client requires a shorted wait time than the default in Phoenix/HBase. This should apply to the underlying operations related to writes - upsert, commit. Also it should control timeout for writes in the HBase client, which might include Zookeeper client timeout as well.
> Proposed property name: phoenix.update.timeoutMs



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)