Hey Jason,
Your RF=3, do you have 3 nodes up and running in this DC? We have seen
this issue with 2.1.x and cqlsh where schema changes would trigger the
"keyspace not found" error in cqlsh if not all nodes were up and
running when altering KS schema in a DC with NetworkTopologyStrategy
and RF=3. For us, bringing all the nodes up to meet RF would then fix
the problem.
As well, you might want to restart the node and see if the "keyspace
not found" still occurs: same here, since 2.1.x we've had cases where
a restart was required for cqlsh and / or drivers to see the schema
changes.
J.
On Fri, Jan 16, 2015 at 3:56 AM, Jason Wee <peich...@gmail.com> wrote:
> $ cqlsh 192.168.0.2 9042
> Connected to just4fun at 192.168.0.2:9042.
> [cqlsh 5.0.1 | Cassandra 2.1.1 | CQL spec 3.2.0 | Native protocol v3]
> Use HELP for help.
> cqlsh> DESCRIBE KEYSPACES
>
> <empty>
>
> cqlsh> create keyspace foobar with replication = {'class':'SimpleStrategy',
> 'replication_factor':3};
> errors={}, last_host=192.168.0.2
> cqlsh> DESCRIBE KEYSPACES;
>
> <empty>
>
> cqlsh> use foobar;
> cqlsh:foobar> DESCRIBE TABLES;
>
> Keyspace 'foobar' not found.
>
>
> Just trying cassandra 2.1 and encounter the above erorr, can anyone explain
> why is this and where to even begin troubleshooting?
>
> Jason
