[jira] [Updated] (PHOENIX-6884) Phoenix to use hbase.rpc.read.timeout and hbase.rpc.write.timeout

["Tanuj Khurana (Jira)" <ji...@apache.org>]

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

Tanuj Khurana updated PHOENIX-6884:
-----------------------------------
    Fix Version/s:     (was: 5.2.0)
                       (was: 5.1.4)

> Phoenix to use hbase.rpc.read.timeout and hbase.rpc.write.timeout
> -----------------------------------------------------------------
>
>                 Key: PHOENIX-6884
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-6884
>             Project: Phoenix
>          Issue Type: Improvement
>            Reporter: Kadir Ozdemir
>            Assignee: Tanuj Khurana
>            Priority: Major
>
> Phoenix uses the same RPC timeout, hbase.rpc.timeout, for both read and write operations currently. HBASE-15866 split hbase.rpc.timeout into hbase.rpc.read.timeout and hbase.rpc.write.timeout. 
> The paging feature (PHOENIX-6211, PHOENIX-6207 and PHOENIX-5998) slices server side operations into small chunks (i.e., pages) and allows all queries make progress without timeouts. This feature makes Phoenix a better time-sharing system and thus improves availability. 
> In order to take advantage of the paging feature fully, we need to set the timeout for scan RPCs to a small value. While it is reasonable to reduce the RPC timeout for the read path because of the paging feature, it is not safe to reduce it for the write path drastically. This is because of the batch writes and synchronous index updates within a batch write. This means we need to start separately configuring read and write RPC timeouts.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)