Hi Matt:
The admission control configuration is :
[cid:[email protected]]
And what we guess that could be bottolneck during“completed admission”
is :
1. Reading MetaData from MySQL (should not be the bottolneck)
2. Reading MetaData from HDFS
3. In the queue (Any way to know a query is in the queue?)
Any Idea about that ?
Thanks
Best Regards,
Songbo
发件人: Matthew Jacobs [mailto:[email protected]]
发送时间: 2016年9月1日 9:17
收件人: 廖松博
抄送: [email protected]
主题: Re: Impala Query is waiting for “completed admission”
It's hard to tell what's going on from that alone. It looks like planning and
admission are taking a long time. How is your admission control configured?
On Wed, Aug 31, 2016 at 6:12 PM, 廖松博
<[email protected]<mailto:[email protected]>> wrote:
Hi Matt,
Recently our impala cluster is too slow for any sql query (whether
small or large query):
[cid:[email protected]]
This SQL is a small query and it is supposed to be completed in 2s,
but a lot more actually , and it seems “completed admission” takes a lot of
time, and this phase is “the planning”, right ?
Any idea about what operation in this phase could be the bottleneck and any way
to locate and solve that ?
Thanks.
Best Regards,
Songbo
