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:[email protected]] Sent: Monday, April 10, 2017 6:27 PM To: [email protected] Cc: [email protected] 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 <[email protected]<mailto:[email protected]>> 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
