[jira] [Resolved] (IMPALA-6704) session-expiry-test is flaky if no minicluster is running

["Philip Zeyliger (JIRA)" <ji...@apache.org>]

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

Philip Zeyliger resolved IMPALA-6704.
-------------------------------------
    Resolution: Fixed
      Assignee: Philip Zeyliger

> session-expiry-test is flaky if no minicluster is running
> ---------------------------------------------------------
>
>                 Key: IMPALA-6704
>                 URL: https://issues.apache.org/jira/browse/IMPALA-6704
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Backend
>    Affects Versions: Impala 2.11.0
>            Reporter: Philip Zeyliger
>            Assignee: Philip Zeyliger
>            Priority: Major
>         Attachments: happy.txt, sad.txt
>
>
> I have found that on certain machines (in my case, on a 32-core machine but not on an 8-core machine), {{session-expiry-test}} is flaky if no minicluster is running. We tend to expect backend tests like this one to not require the minicluster, but in Jenkins runs, I believe the minicluster is running, hiding this flakiness.
> Oddly, I found adding {{--alsologtostderr}} to the test to make it fail more reliably, on my machine. If you don't specify {{--alsologtostderr}} it mostly runs fine.
> Here's the quick log:
> {code}
> $ be/build/debug/service/session-expiry-test --alsologtostderr
> ...
> I0314 20:57:04.724493 15172 impala-server.cc:1237] Default query options:TQueryOptions ....
> E0314 20:57:05.355170 15172 impala-server.cc:278] Could not read the root directory at hdfs://localhost:20500. Error was:
> Call From XXXXXXXX to localhost:20500 failed on connection exception: java.net.ConnectException: Connection refused; For more details see:  http://wiki.apache.org/hadoop/ConnectionRefused
> E0314 20:57:05.355419 15172 impala-server.cc:281] Aborting Impala Server startup due to improper configuration. Impalad exiting.
> {code}
> I've not looked into it deeply, but naively it looks like on a slower machine, the test finishes before its impala server class has a chance to talk to HDFS.
> I've attached the full log output from successful and unsuccessful runs.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)