[jira] [Commented] (KUDU-2015) invalidate data format will causing kudu-tserver to crash. and kudu-table will be un available

["Todd Lipcon (JIRA)" <ji...@apache.org>]

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

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

Hi Bruce. I'm not quite following the description. What is the invalid data here? Also, do you have a full stack trace for the crash?

Are you able to reproduce on current versions?

> 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)