You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@impala.apache.org by "Matthew Jacobs (JIRA)" <ji...@apache.org> on 2017/05/09 17:16:04 UTC

[jira] [Resolved] (IMPALA-5079) Flaky tests: Kudu EE tests need longer HS2 connection timeouts

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

Matthew Jacobs resolved IMPALA-5079.
------------------------------------
    Resolution: Fixed

commit 532c5f26052070cccf90eac83de9ba0052879729
Author: Matthew Jacobs <mj...@cloudera.com>
Date:   Wed Apr 12 16:42:33 2017 -0700

    IMPALA-5079: Flaky Kudu tests; fix HS2 connection timeouts
    
    Fixes the HS2 timeouts for _all_ Kudu EE tests. Previously
    only 2 classes had the timeout set, but all the Kudu tests
    appear to be susceptible to this issue.
    
    Change-Id: Ibc48b4b7ae65ddf4bba087d079d4e4032f4d5f0f
    Reviewed-on: http://gerrit.cloudera.org:8080/6616
    Reviewed-by: Michael Brown <mi...@cloudera.com>
    Reviewed-by: Alex Behm <al...@cloudera.com>
    Tested-by: Impala Public Jenkins


> Flaky tests: Kudu EE tests need longer HS2 connection timeouts
> --------------------------------------------------------------
>
>                 Key: IMPALA-5079
>                 URL: https://issues.apache.org/jira/browse/IMPALA-5079
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Catalog
>            Reporter: Dimitris Tsirogiannis
>            Assignee: Matthew Jacobs
>            Priority: Blocker
>              Labels: broken-build, flaky-test
>             Fix For: Impala 2.9.0
>
>
> The following test started failing randomly. 
> {code}
> MainThread: Created database "test_kudu_col_null_changed_bc507455" for test ID "query_test/test_kudu.py::TestKuduOperations::()::test_kudu_col_null_changed"
> 11:38:31 ----------------------------- Captured stderr call -----------------------------
> 11:38:31 MainThread: Failed to open transport (tries_left=3)
> 11:38:31 Traceback (most recent call last):
> 11:38:31   File "/data/jenkins/workspace/impala-umbrella-build-and-test/repos/Impala/infra/python/env/lib/python2.6/site-packages/impala/hiveserver2.py", line 940, in _execute
> 11:38:31     return func(request)
> 11:38:31   File "/data/jenkins/workspace/impala-umbrella-build-and-test/repos/Impala/infra/python/env/lib/python2.6/site-packages/impala/_thrift_gen/TCLIService/TCLIService.py", line 265, in ExecuteStatement
> 11:38:31     return self.recv_ExecuteStatement()
> 11:38:31   File "/data/jenkins/workspace/impala-umbrella-build-and-test/repos/Impala/infra/python/env/lib/python2.6/site-packages/impala/_thrift_gen/TCLIService/TCLIService.py", line 276, in recv_ExecuteStatement
> 11:38:31     (fname, mtype, rseqid) = self._iprot.readMessageBegin()
> 11:38:31   File "/data/jenkins/workspace/impala-umbrella-build-and-test/repos/Impala/infra/python/env/lib/python2.6/site-packages/thrift/protocol/TBinaryProtocol.py", line 126, in readMessageBegin
> 11:38:31     sz = self.readI32()
> 11:38:31   File "/data/jenkins/workspace/impala-umbrella-build-and-test/repos/Impala/infra/python/env/lib/python2.6/site-packages/thrift/protocol/TBinaryProtocol.py", line 206, in readI32
> 11:38:31     buff = self.trans.readAll(4)
> 11:38:31   File "/data/jenkins/workspace/impala-umbrella-build-and-test/repos/Impala/infra/python/env/lib/python2.6/site-packages/thrift/transport/TTransport.py", line 58, in readAll
> 11:38:31     chunk = self.read(sz - have)
> 11:38:31   File "/data/jenkins/workspace/impala-umbrella-build-and-test/repos/Impala/infra/python/env/lib/python2.6/site-packages/thrift/transport/TTransport.py", line 159, in read
> 11:38:31     self.__rbuf = StringIO(self.__trans.read(max(sz, self.__rbuf_size)))
> 11:38:31   File "/data/jenkins/workspace/impala-umbrella-build-and-test/repos/Impala/infra/python/env/lib/python2.6/site-packages/thrift/transport/TSocket.py", line 103, in read
> 11:38:31     buff = self.handle.recv(sz)
> 11:38:31 timeout: timed out
> {code}
> Not clear what is going on from the error message or the logs. MJ do you mind taking a quick look? Feel free to reassign as you see fit. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)