[
https://issues.apache.org/jira/browse/IMPALA-6959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16464000#comment-16464000
]
ASF subversion and git services commented on IMPALA-6959:
---------------------------------------------------------
Commit 9d36d38acc0d03ad48aeacdf2a4e05655c625b56 in impala's branch
refs/heads/2.x from [~arodoni_cloudera]
[ https://git-wip-us.apache.org/repos/asf?p=impala.git;h=9d36d38 ]
IMPALA-6959: [DOCS] Update to HAProxy configuration sample code
- Changed to deprecated timeouts: contimeout, clitimeout, srvtimeout
- Changed the sample timeout values to more realistic values
- Added a note that actual timeout values should depend on
the user cluster
Change-Id: Idff3aa9bbb58c1953cb7e9394ade01c7833c3a34
Reviewed-on: http://gerrit.cloudera.org:8080/10284
Reviewed-by: Alan Choi <[email protected]>
Reviewed-by: Alex Rodoni <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>
> Update HAProxy configuration sample for Impala
> ----------------------------------------------
>
> Key: IMPALA-6959
> URL: https://issues.apache.org/jira/browse/IMPALA-6959
> Project: IMPALA
> Issue Type: Task
> Components: Docs
> Affects Versions: Impala 2.12.0
> Reporter: Alex Rodoni
> Assignee: Alex Rodoni
> Priority: Major
> Fix For: Impala 3.0, Impala 2.13.0
>
>
> Our doc regarding setting up Impala HA using HAProxy:
> [https://www.cloudera.com/documentation/enterprise/latest/topics/impala_proxy.html]
> it uses the following timeout values:
> {code:java}
> contimeout 5000
> clitimeout 50000
> srvtimeout 50000
> {code}
> Two issues here:
> 1. contimeout, clitimeout and srvtimeout are old, the new config names should
> be
> {code:java}
> timeout connect
> timeout client
> timeout server
> {code}
> The outdated config names shows that our docs are also outdated
> 2. the timeout value of 50000, which is 50 seconds is too low, it will cause
> impala client to timeout all the time, the correct value should be at least 1
> hour to start with:
> {code:java}
> timeout client 3600s
> timeout server 3600s
> {code}
> And we should also mention that these values should be dependant on how users
> use the cluster and how long their queries are running. It is NOT one config
> fits for all case.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
