cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksey Yeschenko (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-9960) UDTs still visible after drop/recreate keyspace
Date Fri, 07 Aug 2015 14:29:46 GMT

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

Aleksey Yeschenko commented on CASSANDRA-9960:
----------------------------------------------

Having {{select * from system.schema_usertypes;}} return nothing, but

{{select * FROM system.schema_usertypes WHERE keyspace_name='ks' AND type_name='typename';}}
returning something is a sign of something nasty, assuming that both requests were routed
to the same node. Seeing something like this makes me a bit worried.

> UDTs still visible after drop/recreate keyspace
> -----------------------------------------------
>
>                 Key: CASSANDRA-9960
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9960
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Jaroslav Kamenik
>            Assignee: Robert Stupp
>            Priority: Critical
>             Fix For: 2.2.x
>
>
> When deploying my app from the scratch I run sequence - drop keyspaces, create keyspaces,
create UDTs, create tables, generate lots of data... After few cycles, randomly, cassandra
ends in state, where I cannot see anything in table system.schema_usertypes, when I select
all rows, but queries with specified keyspace_name and type_name return old values. Usually
it helps to restart C* and old data disapear, sometimes it needs to delete all C* data. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message