Re: Does this mem-tracker.h assertion ring a bell?

Filed https://issues.apache.org/jira/browse/IMPALA-6118. -- Philip On Wed, Oct 25, 2017 at 2:50 PM, Tim Armstrong wrote: > Will you file a JIRA for this bug? Sounds like something we don't want to > lose track of. > > - Tim > > On Wed, Oct 25, 2017 at 11:05 AM, Philip

Re: Does this mem-tracker.h assertion ring a bell?

Will you file a JIRA for this bug? Sounds like something we don't want to lose track of. - Tim On Wed, Oct 25, 2017 at 11:05 AM, Philip Zeyliger wrote: > Thanks. I'm beginning to think my patch is not causing these breakages. A > different run was almost clean, with some

Re: Does this mem-tracker.h assertion ring a bell?

Thanks. I'm beginning to think my patch is not causing these breakages. A different run was almost clean, with some TPC-DS query tests failing, that I think are also new. -- Philip On Wed, Oct 25, 2017 at 10:36 AM, Tim Armstrong wrote: > Yeah it's probably another

Re: Does this mem-tracker.h assertion ring a bell?

Yeah it's probably another consequence of https://issues.apache.org/jira/browse/IMPALA-5789. Maybe your patch changed the timing enough to trigger it. I think the bug might be related to using directory.capacity() as the argument to Release(). Calling directory.clear() after releasing the memory

Re: Does this mem-tracker.h assertion ring a bell?

Maybe related to https://issues.apache.org/jira/browse/IMPALA-6099? On Wed, Oct 25, 2017 at 10:02 AM, Philip Zeyliger wrote: > Hi folks, > > I'm debugging some test failures related to an LLVM/AvroCodegen patch I've > got going on. The failures are in the parallel EE tests,

Does this mem-tracker.h assertion ring a bell?

Hi folks, I'm debugging some test failures related to an LLVM/AvroCodegen patch I've got going on. The failures are in the parallel EE tests, and most of them are complaining that Impala is out to lunch. It looks like the following assertion is firing, causing an impalad to fail, causing many