Re: Broken/Flaky Tests

+1 - thanks for worrying about build health. On 25 May 2018 at 17:18, Jim Apple wrote: > Sounds good to me. Thanks for taking ownership! > > On Fri, May 25, 2018 at 5:10 PM Thomas Tauber-Marshall < > tmarsh...@cloudera.com> wrote: > > > Hey Impala community, > > > > There

Re: Broken/Flaky Tests

Sounds good to me. Thanks for taking ownership! On Fri, May 25, 2018 at 5:10 PM Thomas Tauber-Marshall < tmarsh...@cloudera.com> wrote: > Hey Impala community, > > There seems to have been an unusually large number of flaky or broken tests > < >

Broken/Flaky Tests

Hey Impala community, There seems to have been an unusually large number of flaky or broken tests

Re:Re: impalad cause lots of system cpu

Hi Hongxiang, You can also look into logs of Impala.WARNING and Impala.ERROR. There may be some useful messages if you encounter server-level issues, e.g. OOM in Impalad side, failure in processing impalad catalog update, etc. Besides, tracking metrics in