Hi, previously, i got the same situation, the root cause is related to below haproxy config
> timeout client 1h > timeout server 1h > maybe, it's same with you condition On Tue, Aug 6, 2019 at 5:40 AM Antoni Ivanov <[email protected]> wrote: > Hi, > > > > I am investigating the most common errors we see in our Impala Cluster. > > The most common is with query status = ‘Session Closed’ > > > > I can see from the code ( > https://github.com/apache/impala/blob/72c9370856d7436885adbee3e8da7e7d9336df15/be/src/service/impala-server.cc#L1435) > > > that it is set when Session is closed and this happens when connection is > closed (ConnectionEnd > <https://github.com/apache/impala/blob/72c9370856d7436885adbee3e8da7e7d9336df15/be/src/service/impala-server.cc#L2094> > ) > > and this is called when Thrift transport is closed > <https://github.com/apache/impala/blob/82f753e3044bd2482f35d137fbb28516fc0ef86c/be/src/rpc/TAcceptQueueServer.cpp> > (and query has not completed or failed in some way it would be marked as > Session Closed > > > > Does this mean that the remote end has simply dropped the connection ? > > E.g there has been network interruption or someone killed (SIGKILL) the > remote process ? > > We have (TCP) load balancer (HaProxy) and I am wondering if for example > Load Balancer tcp timeout can cause such error. Or can client socket > timeout cause it? > > > > I’d be grateful for any insides into the semantics of when “Session > Closed” is set. > > > > > > > > Thanks, > > Antoni > -- Regards, Hendry Suwanda Github: https://github.com/hendrysuwanda Blog: http://hendrysuwanda.github.io/
