The mini stress has been prone to hangs in the past due to test bugs. I'd recommend dumping the impala-server metrics and checking whether the impala.thrift-server.beeswax-frontend.connections-in-use is close to 64. Then look at how many queries are actually still in flight. If there are fewer than 64 queries in flight, then it's probably a test bug (because the tests did not yet close their connections despite being done).
You can grab http://localhost:25000/metrics?raw&json On Wed, Nov 16, 2016 at 5:29 PM, Tim Armstrong <[email protected]> wrote: > It's probably worth looking at the debug pages to see what queries are > active. Probably also worth grabbing stack traces with gdb or core dumps > with gcore. If it's a hang then it's often possible to diagnose from the > backtraces. > > Could also be worth running perf top to see where it's spending time (if > anywhere). > > On Wed, Nov 16, 2016 at 5:19 PM, Jim Apple <[email protected]> wrote: > > > I'm running the EE tests on a machine and it seems to be stuck in the > > stress tests. I have access to the machine for now, but my Jenkins > > install is going to steal it from me when the job is force-timed-out > > in a few hours. What should I look at now to try and understand what > > is happening - in particular, what could be useful to me now but not > > visible in the logs? > > >
