|| at Apr 19, 2013 at 8:21 am
thank you for your creating issue.
I'll watch this issue on JIRA.
If you have any further questions, please feel free to contact me.
I'm looking forward to when impala GA is released very much !!
2013/4/19 Henry Robinson <email@example.com
Thanks for your bug reports, and apologies for this issue, which I've
to track. We may be
asking for more details shortly, but we hope to have it fixed soon.
On 18 April 2013 23:56, Yukinori SUDA wrote:
thank you for your report.
I think that they result from the same reason.
2013/4/19 邱睿 <firstname.lastname@example.org
I meet the exactly same problem. Impalad daemon always crashes on
C [impalad+0x4ed2a7] _ZN6impala12HdfsScanNode14UpdateCountersEv+0x97
在 2013年4月19日星期五UTC+8下午1时16分09秒，Suda Yukinori写道：
I updated from 0.6 to 0.7.1 using parcel feature in Cloudera Manager
When I run even the very simple query (select * from TABLE limit 1),
every impalad daemon on nodes always crashes.
impala-shell says "Error communicating with impalad: TSocket read 0
And impalad daemon also outputs log file of "hs_err_pidXXXX.log" (maybe
XXXX is process id).
"A fatal error has been detected by the Java Runtime Environment:" is
written in the head of this file.
Is this problem of Java ?
Of course, the same query on both hive and (rollbacked) impala 0.6
Has anyone seen similar behavior ?
The attached file is log file above.