<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>question Re: Impalad exit when  execute 'compute stats' on table whose schema is not compatible with parquet in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Impalad-exit-when-execute-compute-stats-on-table-whose/m-p/64505#M74442</link>
    <description>&lt;P&gt;Thanks for the report! I suspect you are hitting this issue:&lt;/P&gt;&lt;P&gt;&lt;A href="https://issues.apache.org/jira/browse/IMPALA-5186" target="_blank"&gt;https://issues.apache.org/jira/browse/IMPALA-5186&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;As a workaround you can set the following query option:&lt;/P&gt;&lt;P&gt;SET MT_DOP=0;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Please let us know if that worked or not.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Sat, 10 Feb 2018 05:57:21 GMT</pubDate>
    <dc:creator>alex.behm</dc:creator>
    <dc:date>2018-02-10T05:57:21Z</dc:date>
    <item>
      <title>Impalad exit when  execute 'compute stats' on table whose schema is not compatible with parquet file</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Impalad-exit-when-execute-compute-stats-on-table-whose/m-p/64494#M74441</link>
      <description>&lt;P&gt;Recently we found lots of impala daemon exit in our cluster&amp;nbsp;when&amp;nbsp;executing 'compute stats' for some table. How to reproduce:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Impala version:&lt;/STRONG&gt;&amp;nbsp;2.7.0-cdh5.10.0&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;OL&gt;
&lt;LI&gt;Create table col_str_int&lt;/LI&gt;
&lt;LI&gt;
&lt;PRE&gt;create table sample.col_str_int(
  s STRING,
  i INT
) stored as parquet;&lt;/PRE&gt;
Generate Parquet File with incompatible schema&lt;/LI&gt;
&lt;LI&gt;
&lt;PRE&gt;create table sample.col_str_str (
  s string,
  i string
) stored as parquet;
insert into sample.col_str_str values("some_str", "false");&lt;/PRE&gt;
Copy parquet file to table&lt;/LI&gt;
&lt;LI&gt;
&lt;PRE&gt;hadoop fs -cp /user/hive/warehouse/sample.db/col_str_str/* /user/hive/warehouse/sample.db/col_str_int/&lt;/PRE&gt;
Compute Stats
&lt;PRE&gt;refresh sample.col_str_int;
compute stats sample.col_str_int;&lt;/PRE&gt;
&lt;/LI&gt;
&lt;/OL&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Here is the message before impalad exit:&lt;/P&gt;
&lt;PRE&gt;Wrote minidump to /data1/impala/logs/minidumps/impalad/57d8e9ec-a075-5f0c-54dbe818-09c7889c.dmp
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x0000000000000000, pid=25400, tid=0x00007f4c2c458700
#
# JRE version: Java(TM) SE Runtime Environment (8.0_121-b13) (build 1.8.0_121-b13)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.121-b13 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C  0x0000000000000000
#
# Core dump written. Default location: /var/lib/impala/core or core.25400
#
# An error report file with more information is saved as:
# /var/lib/impala/hs_err_pid25400.log
#
# If you would like to submit a bug report, please visit:
#   http://bugreport.java.com/bugreport/crash.jsp
#
"impalad.node153-84-98-jylt.qiyi.hadoop.impala.log.INFO.20180209-203116.25400" 501L, 28262C&lt;/PRE&gt;
&lt;P&gt;So I want to ask:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Is this a know issue,&amp;nbsp;has it been fixed in latest version?&lt;/LI&gt;
&lt;LI&gt;Is there any workaround to such problem?&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 16 Sep 2022 12:50:55 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Impalad-exit-when-execute-compute-stats-on-table-whose/m-p/64494#M74441</guid>
      <dc:creator>linhao</dc:creator>
      <dc:date>2022-09-16T12:50:55Z</dc:date>
    </item>
    <item>
      <title>Re: Impalad exit when  execute 'compute stats' on table whose schema is not compatible with parquet</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Impalad-exit-when-execute-compute-stats-on-table-whose/m-p/64505#M74442</link>
      <description>&lt;P&gt;Thanks for the report! I suspect you are hitting this issue:&lt;/P&gt;&lt;P&gt;&lt;A href="https://issues.apache.org/jira/browse/IMPALA-5186" target="_blank"&gt;https://issues.apache.org/jira/browse/IMPALA-5186&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;As a workaround you can set the following query option:&lt;/P&gt;&lt;P&gt;SET MT_DOP=0;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Please let us know if that worked or not.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 10 Feb 2018 05:57:21 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Impalad-exit-when-execute-compute-stats-on-table-whose/m-p/64505#M74442</guid>
      <dc:creator>alex.behm</dc:creator>
      <dc:date>2018-02-10T05:57:21Z</dc:date>
    </item>
    <item>
      <title>Re: Impalad exit when  execute 'compute stats' on table whose schema is not compatible with parquet</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Impalad-exit-when-execute-compute-stats-on-table-whose/m-p/64506#M74443</link>
      <description>&lt;P&gt;Thanks for you reply. I try to&amp;nbsp;&lt;SPAN&gt;SET MT_DOP=0; before compute stats and &lt;STRONG&gt;it works&lt;/STRONG&gt;! The impalad does not crash any more&amp;nbsp;althougth compute stats still fail due to incompataible schema.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Sat, 10 Feb 2018 07:46:47 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Impalad-exit-when-execute-compute-stats-on-table-whose/m-p/64506#M74443</guid>
      <dc:creator>linhao</dc:creator>
      <dc:date>2018-02-10T07:46:47Z</dc:date>
    </item>
  </channel>
</rss>

