[
https://issues.apache.org/jira/browse/CASSANDRA-8012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14181345#comment-14181345
]
Deives Michellis commented on CASSANDRA-8012:
---------------------------------------------
I think it is worth mentioning it here...
Once I bumped the whole cluster to 2.1.0, this issue went away.
(It was a test VM cluster with 5 nodes and about 700k of actual data per node,
so YMMV with bigger datasets)
I will do this upgrade on a larger, multi-dc cluster with slightly more data
(about 50Tb in total) and will post the results :)
> cqlsh "DESCRIBE KEYSPACES;" returns empty after upgrade
> -------------------------------------------------------
>
> Key: CASSANDRA-8012
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8012
> Project: Cassandra
> Issue Type: Bug
> Components: Tools
> Environment: cassandra 2.1.0
> Reporter: Shawn Zhou
> Assignee: Tyler Hobbs
> Labels: cqlsh
>
> after upgrade from 2.0.7 to 2.1.0
> run cqlsh "DESCRIBE KEYSPACES;" returns empty result;
> query individual table does return data;
> See below:
> {noformat}
> [root@dc1-stg-cassandra-08 cassandra]# cqlsh
> dc1-stg-cassandra-08.dc01.revsci.net -k as_user_segment
> Connected to Stage Cluster at dc1-stg-cassandra-08.dc01.revsci.net:9042.
> [cqlsh 5.0.1 | Cassandra 2.1.0 | CQL spec 3.2.0 | Native protocol v3]
> Use HELP for help.
> cqlsh:as_user_segment> DESCRIBE KEYSPACES;
> <empty>
> cqlsh:as_user_segment> select * from user_segments_blob where id =
> '8e6090087fc1a7591a99dc4cb744ac43';
> id | segments
> ----------------------------------+------------------------------------------------------------------------------------
> 8e6090087fc1a7591a99dc4cb744ac43 |
> 0x94160000b0150000911d00003b0e0000211a0000ee22000072160000ab1c0000df0f000042040000
> (1 rows)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
