Re: How many threads impala start for handling partitioned join?

Thanks for the reply. I saw IMPALA-3902 seems to add support for multithread execution. It describes the goal is to support running multiple fragment instances on a single node, is that means coordinator generate multiple instances for a plan

Podling Report Reminder - November 2017

Dear podling, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for Wed, 15 November 2017, 10:30 am PDT. The report for your podling will

Please hold off merging new code changes

A few recent changes have destabilised a lot of tests - see IMPALA-6106 and IMPALA-6108 in particular. Until those are sorted out let's avoid merging any code changes that don't fix flaky or broken tests - it will just make it more difficult to root-cause any further failures. I'll send out

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

[GitHub] incubator-impala pull request #3: fix doc about parquet under incubation

Github user Humbedooh closed the pull request at: https://github.com/apache/incubator-impala/pull/3 ---

Re: How many threads impala start for handling partitioned join?

Hello JJ, No, currently Impala uses one thread to execute the join (without regard for the amount of partitions that fit into memory). HTH On 25 October 2017 at 05:44, 俊杰陈 wrote: > Hi > > When Impala does a partitioned join on a node, it split the build input > into