phoenix-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Simon Lee <si...@marketo.com>
Subject How to set up different phoenix timeout values for different client applications?
Date Wed, 09 Mar 2016 01:12:42 GMT
Hi all,

What is the best way to set up different phoenix query timeout values for different client
applications? Suppose there are 5 different Phoenix client applications. These applications
have different timeout requirements due to the characteristics of the applications. For example,
the timeout requirements are

Application A is 60,000 milliseconds
Application B is 1,200,000 milliseconds
Application C is 600,000 milliseconds
Application D and application E are 300,000 milliseconds

Currently, the phoenix.query.timeoutMs in hbase-site.xml on the region servers is set to 300,000
milliseconds

If phoenix.query.timeoutMs is set to 60,000 milliseconds on the client machine where application
A is located, will the value on the client (60,000) override the value on the region server
(300,000), so the application’s A query will time out after 60,000 milliseconds?

If phoenix.query.timeoutMs is set to 1,200,000 milliseconds on the client machine where application
B is located, will the value on the client (1,200,000) override the value on the region server
(300,000), so the application’s B query will not time out after 300,000 milliseconds?

The factory default value of phoenix.query.timeoutMs is 600,000. If timeout value is not set
on the client machine where application C is located, and timeout value is set on the region
servers, will the factory default value on the client (600,000) override the value on the
region server (300,000)? If so, the timeout value on the region server will never take effect.

Thanks!



Mime
View raw message