You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hawq.apache.org by "Lei Chang (JIRA)" <ji...@apache.org> on 2016/01/24 02:39:40 UTC
[jira] [Updated] (HAWQ-37) Abort transaction didn't rollback while
1 QE was terminated.
[ https://issues.apache.org/jira/browse/HAWQ-37?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lei Chang updated HAWQ-37:
--------------------------
Fix Version/s: 2.0.0
> Abort transaction didn't rollback while 1 QE was terminated.
> ------------------------------------------------------------
>
> Key: HAWQ-37
> URL: https://issues.apache.org/jira/browse/HAWQ-37
> Project: Apache HAWQ
> Issue Type: Bug
> Components: Dispatcher
> Reporter: Xiang Sheng
> Assignee: Ming LI
> Priority: Critical
> Fix For: 2.0.0
>
>
> Run workload tpch_parq10snp, 1 QE was terminated due to disk failure. And returned error "the relation already exists" while insert into the same relation.
> Steps to repeat the problem:
> 1, create table orders_x (like orders);
> 2, insert into orders_x select * from e_orders ;
> 3, kill 1 MPPEXEC process on segment to simulate the interrupted.
> 4, then "error returned: Query Executor Error in seg432 sfo-w163.ic:40000 pid=278795: server closed the connection unexpectedly "
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)