Hi guys,
We are using CDH 5.10.0, the impala page of CM shows:
[cid:image001.png@01D2C8B0.C07C0C00]
We set the limit to 10:
[cid:image002.png@01D2C8B0.C07C0C00]
But not help.
I found some similar issues:
From our - the Apache project's - perspective, I don't think there is much
reason to be concerned about mixing 6.5 and 6.7 on the same cluster.
On 19 October 2016 at 02:14, 廖松博
<liaoson...@gridsum.com<mailto:liaoson...@gridsum.com>> wrote:
Hi all,
I notice from
http://www.clouder
ads.
Dimitris
On Thu, Sep 22, 2016 at 9:45 PM, 廖松博
<liaoson...@gridsum.com<mailto:liaoson...@gridsum.com>> wrote:
Hi Dimitris,
statestore_frequency_update_ms not change during the update, is 2000ms
by default. And not more frequent REFRESH statement.
Actually we
Hi guys,
We upgrade out CDH cluster from 5.5 to 5.7 at Sep 20, and from the
following figure:
[cid:image001.jpg@01D21574.46A788E0]
You can see the catalog server in impala 2.5 use much more memory than
what in impala 2.3 and causes the out of memory error.
Thanks a lot for your patient.
Songbo
-邮件原件-
发件人: Matthew Jacobs [mailto:m...@cloudera.com]
发送时间: 2016年7月26日 13:40
收件人: 廖松博
抄送: user@impala.incubator.apache.org
主题: Re: Impala user resource isolation best practice
If memory cannot be spilled to disk then the query will be killed
oudera.com]
发送时间: 2016年7月26日 8:33
收件人: 廖松博
抄送: user@impala.incubator.apache.org
主题: Re: Impala user resource isolation best practice
On Mon, Jul 25, 2016 at 4:36 PM, 廖松博 <liaoson...@gridsum.com> wrote:
> Hi Matt,
> Thanks for reply, but there are still something confuse me:
&g
[mailto:m...@cloudera.com]
发送时间: 2016年7月19日 11:35
收件人: 廖松博
抄送: user@impala.incubator.apache.org
主题: Re: Impala user resource isolation best practice
Hi Songbo,
Yes, setting the MEM_LIMITs is a good idea. In Impala 2.5 and after, you can
set a per-pool default query mem limit. Cloudera Manager makes
