[
https://issues.apache.org/jira/browse/KUDU-3723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18057709#comment-18057709
]
ASF subversion and git services commented on KUDU-3723:
-------------------------------------------------------
Commit 0a63f0318421e4ec58f79e3c185b496db8025d42 in kudu's branch
refs/heads/master from Alexey Serbin
[ https://gitbox.apache.org/repos/asf?p=kudu.git;h=0a63f0318 ]
[tserver] log errors on invalid schemas
To help troubleshoot issues like KUDU-3723, it's useful to report on
invalid table and partition schemas sent by the catalog manager to
tablet servers. This patch adds corresponding logs, and wraps the
related rare conditions with EXPECT_FALSE().
This changelist doesn't contain any functional modifications.
Change-Id: I2b0d05106cb5c8e0acc8cacd34c9703dbc25b4b7
Reviewed-on: http://gerrit.cloudera.org:8080/23956
Tested-by: Kudu Jenkins
Reviewed-by: Gabriella Lotz <[email protected]>
Reviewed-by: Abhishek Chennaka <[email protected]>
> Dropping and adding back same range partition right away isn't working for
> certain table schemas
> ------------------------------------------------------------------------------------------------
>
> Key: KUDU-3723
> URL: https://issues.apache.org/jira/browse/KUDU-3723
> Project: Kudu
> Issue Type: Bug
> Components: tserver
> Affects Versions: 1.17.0, 1.18.0, 1.18.1
> Reporter: Alexey Serbin
> Assignee: Alexey Serbin
> Priority: Major
>
> For a Kudu table partitioned by both range and hash, the following sequence
> leads to the table being stuck in a limbo state where it cannot be opened or
> operated by any other means, effectively rendering it inaccessible:
> * adding a new range with custom hash partition scheme
> * immediately drop the newly added range
> * immediately try adding the same range again
> The reproduction scenario is available at
> http://gerrit.cloudera.org:8080/23778 It's 100% repeatable/reproducible.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
