[jira] [Resolved] (IMPALA-6959) Update HAProxy configuration sample for Impala

["Alex Rodoni (JIRA)" <ji...@apache.org>]

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

Alex Rodoni resolved IMPALA-6959.
---------------------------------
       Resolution: Fixed
    Fix Version/s: Impala 3.0

> 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
>
>
> 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)