[ 
https://issues.apache.org/jira/browse/KUDU-2015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16022087#comment-16022087
 ] 

Todd Lipcon commented on KUDU-2015:
-----------------------------------

[~bruceSz] -- can you provide some details how to reproduce this? eg what API 
code did you use the create the table?

Using impala on recent versions it seems to work fine:
{code}
[vd0340:21000] > create table cst (pin string primary key not null, age int) 
partition by hash(pin) partitions 2 stored as kudu;
Query: create table cst (pin string primary key not null, age int) partition by 
hash(pin) partitions 2 stored as kudu

Fetched 0 row(s) in 2.58s
[vd0340:21000] > insert into cst values (("test1",2),("test2",3),("test3",3));
Query: insert into cst values (("test1",2),("test2",3),("test3",3))
Query submitted at: 2017-05-23 16:34:10 (Coordinator: 
http://vd0340.halxg.cloudera.com:25000)
Query progress can be monitored at: 
http://vd0340.halxg.cloudera.com:25000/query_plan?query_id=4843343f209f37b1:233aecc400000000
Modified 3 row(s), 0 row error(s) in 4.44s
[vd0340:21000] > select * from cst;
Query: select * from cst
Query submitted at: 2017-05-23 16:34:20 (Coordinator: 
http://vd0340.halxg.cloudera.com:25000)
Query progress can be monitored at: 
http://vd0340.halxg.cloudera.com:25000/query_plan?query_id=6949ceed89d63420:35b8663f00000000
+-------+-----+
| pin   | age |
+-------+-----+
| test1 | 2   |
| test2 | 3   |
| test3 | 3   |
+-------+-----+
Fetched 3 row(s) in 2.14s
{code}

> invalidate data format will causing kudu-tserver to crash. and kudu-table 
> will be un available
> ----------------------------------------------------------------------------------------------
>
>                 Key: KUDU-2015
>                 URL: https://issues.apache.org/jira/browse/KUDU-2015
>             Project: Kudu
>          Issue Type: Bug
>          Components: client, impala, tserver
>    Affects Versions: 1.1.0
>            Reporter: zhangsong
>            Priority: Critical
>
> when issuing insert into clause using impala , have issue wrong insert 
> clause, which in turn causing the kudu-table unreadable and kudu-tserver 
> crash.
> the test table 's schema: 
> CREATE EXTERNAL TABLE `cst` (
> `pin` STRING,
> `age` INT
> )
> TBLPROPERTIES(...)
> the insert into issue "insert into cst values 
> (("test1",2),("test2",3),("test3",3))" 
> after insertion , impala-shell prompt successfully.
> but then select on this table will failed. 
> also found kudu-tservers(one leader and two follower) hold same tablet of the 
> table  crashed.
> FATAL msg on them is : "F0516 20:03:18.752769 39540 
> tablet_peer_mm_ops.cc:128] Check failed: _s.ok() FlushMRS failed on 
> 8ea48349d89d405c94334f832b1bae18: Invalid argument: Failed to finish DRS 
> writer: index too large"
> fortunately , it is a test table which only causing 3 kudu-tserver die.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to