[
https://issues.apache.org/jira/browse/IMPALA-6500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Armstrong updated IMPALA-6500:
----------------------------------
Summary: Impala crashes under certain hypervisors that return out-of-range
CPU IDs (was: Impala crashes under hypervisors that return out-of-range CPU
IDs)
> Impala crashes under certain hypervisors that return out-of-range CPU IDs
> -------------------------------------------------------------------------
>
> Key: IMPALA-6500
> URL: https://issues.apache.org/jira/browse/IMPALA-6500
> Project: IMPALA
> Issue Type: Bug
> Components: Backend
> Affects Versions: Impala 2.10.0
> Environment: RHEL 6.5 (Santiago), Kernel version:
> 2.6.32-431.el6.x86_64, CDH 5.13.1 single node, Impala 2.10, VMware ESXi,
> v5.0.0
> Reporter: Osama Suleiman
> Assignee: Tim Armstrong
> Priority: Critical
> Labels: crash
> Fix For: Impala 3.0, Impala 2.12.0
>
> Attachments: 000000_0, 7b977512-5aa4-4f40-9ae47184-35853042.dmp,
> 7b977512-5aa4-4f40-9ae47184-35853042.txt, hs_err_pid9910.log, impalad.ERROR,
> impalad.INFO, impalad.INFO2, query_result.txt, shared_libs.txt
>
>
> I have a Parquet table created by Hive and I am doing multiple different
> queries on it, such as:
> SELECT product_category,
> SUM(cast(profit AS DECIMAL(15,2))) as total_profit,
> SUM(cast(sales AS DECIMAL(15,2))) as total_sales
> FROM copy_orders
> GROUP BY product_category;
> and:
> SELECT customer_name,
> SUM(cast(profit AS DECIMAL(15,2))) as total_profit,
> SUM(cast(sales AS DECIMAL(15,2))) as total_sales
> FROM copy_orders
> GROUP BY customer_name
> ORDER BY total_profit DESC
> LIMIT 10;
> These two queries tend to run successfully in some rare occasions, most of
> the time running those queries on HUE's Impala query editor will return:
> ??Could not connect to hostname:21050 (code THRIFTTRANSPORT):
> TTransportException('Could not connect to hostname:21050',)??
> Simultaneously, the Impala Daemon crashes according to the Cloudera Manager
> and then it will work again approximately 1 min later. Meanwhile, You can run
> other simple queries and it will run successfully.
> I have attached a log file for a sample run of one of the queries since they
> all generate relevant logs. I have tried to use ??SET disable_codegen=1?? but
> the problem resumed.
> I have added both the impalad.ERROR and impalad.INFO files after running the
> 2nd query 2 times: the 1st time I used "SET disable_codegen=1" which
> sometimes work, and after that, it ran successfully (represented by
> impalad.INFO). The other time, at which the query has failed, is logged in
> the (impalad.INFO2) while impalad.ERROR doesn't seem to have changed at all.
> It seems that all the old logs gets removed from the main logging files
> (impalad.INFO and impalad.ERROR) since running the query keeps restarting the
> Impala Daemon.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
