@impala.incubator.apache.org
抄送: Matthew Jacobs
主题: 答复: 答复: Catalog Server Out of memory when upgrading from CDH 5.5 -> 5.7
Thanks Dimitris, is there a formula to compute the size of the serialized
metadata of one table ? So we can see if it is over 2G.
Thanks again.
发件人: Dimitris Tsirogian
Hi all,
I see the issue https://issues.cloudera.org/browse/IMPALA-3910 , it
says “No one table is large enough to breach the 2GB array size limit (as
described in IMPALA-2648) but multi table updates may.”
Is that true ? If yes, a concurrent DDL should be avoid , otherwise
it
: 答复: Catalog Server Out of memory when upgrading from CDH 5.5 -> 5.7
That error message indicates that the size of the serialized metadata of some
tables exceed the maximum allowed size of a byte array (2GB) and doesn't have
anything to do with the size of the heap. The logs indicate
@impala.incubator.apache.org
主题: Re: 答复: 答复: Catalog Server Out of memory when upgrading from CDH 5.5 -> 5.7
You may want to consider the following steps:
1. Restart the entire cluster and not just the catalog. If an impalad detects a
change in the catalog (caused by a restart) it asks for full updates.
2. Ver
>
>
> Songbo
>
>
>
> *发件人:* Dimitris Tsirogiannis [mailto:dtsirogian...@cloudera.com]
> *发送时间:* 2016年9月23日 11:33
> *收件人:* user@impala.incubator.apache.org
> *抄送:* Matthew Jacobs
> *主题:* Re: 答复: Catalog Server Out of memory when upgrading from CDH 5.5 ->
>
@impala.incubator.apache.org
抄送: Matthew Jacobs
主题: Re: 答复: Catalog Server Out of memory when upgrading from CDH 5.5 -> 5.7
That error message indicates that the size of the serialized metadata of some
tables exceed the maximum allowed size of a byte array (2GB) and doesn't have
anything to
gbo
>
>
>
> *发件人:* Dimitris Tsirogiannis [mailto:dtsirogian...@cloudera.com]
> *发送时间:* 2016年9月23日 8:49
> *收件人:* user@impala.incubator.apache.org
> *抄送:* Matthew Jacobs
> *主题:* Re: Catalog Server Out of memory when upgrading from CDH 5.5 -> 5.7
>
>
>
> There seem to
There seem to be some events after sept 21 that trigger a spike in memory
usage. Can you identify from CM what these events might be? For
example, refreshing tables with lots of metadata. Looking at the catalog
logs might also give you some hints on what the system is doing during
those memory spik
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.
