impala-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jim Apple <jbap...@cloudera.com>
Subject Re: Re:
Date Mon, 10 Apr 2017 17:02:10 GMT
This email has no subject, so gmail can't see that they are the same thread.

On Mon, Apr 10, 2017 at 9:59 AM, Antoni Ivanov <aivanov@vmware.com> wrote:

> I am not sure I understand I think that’s the same thread – RSS link
> <https://lists.apache.org/api/atom.lua?mid=c6ee7194bcc9b723828b24863767eb3a35325e7d4945e9a26b70392d@%3Cuser.impala.apache.org%3E>
> (Did I respond incorrectly in some way?)
>
>
>
> -Antoni
>
>
>
> We deliver the VMware Analytics Cloud (VAC)
> Learn more about VAC here <https://wiki.eng.vmware.com/VAC>
>
>
>
> *From:* Jim Apple [mailto:jbapple@cloudera.com]
> *Sent:* Monday, April 10, 2017 6:27 PM
> *To:* user@impala.incubator.apache.org
> *Cc:* user@impala.apache.org
> *Subject:* Re:
>
>
>
> Is this question any different from the one on the thread with the title
> "Slow Impalad nodes"?
>
>
>
> On Mon, Apr 10, 2017 at 2:16 AM, Antoni Ivanov <aivanov@vmware.com> wrote:
>
> Hi again,
>
> Any idea how to workaround those type of issues now?
> If I understand correctly - Impala is limited by the most under-performing
> node
> Because fragments get scheduled on "round-robin" principle accross nodes.
> Nodes with worse CPU or  bad network will slow-down all queries (with
> fragments) on them?
>
> Is that correct?
>
> And 3rd question. Is there JIRA that I can follow which aims to add
> "dynamic scheduling" to Impala.
>
> Thanks,
> Antoni
>
>
>

Mime
View raw message