You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@cassandra.apache.org by kedar <ke...@netcore.co.in> on 2016/02/11 11:10:10 UTC
Keyspaces not found in cqlsh
I am using cqlsh 5.0.1 | Cassandra 2.1.2, recently we are unable to see
/ desc keyspaces and query tables through cqlsh on either of the two nodes
cqlsh> desc keyspaces
<empty>
cqlsh> use user_index;
cqlsh:user_index> desc table list_1_10;
Keyspace 'user_index' not found.
cqlsh:user_index>
cqlsh> select * from system.schema_keyspaces;
Keyspace 'system' not found.
cqlsh>
We are running a 2 node cluster. The Python - Django app that inserts
data is running without any failure and system logs show nothing abnormal.
./nodetool repair on one node hasn't helped ./nodetool cfstats shows all
the tables too
--
Thanks,
Kedar Parikh
Ext : 2224
Dir : +91 22 61782224
Mob : +91 9819634734
Email : kedar.parikh@netcore.co.in
Web : www.netcore.co.in
Re: Keyspaces not found in cqlsh
Posted by Ryan Svihla <rs...@foundev.pro>.
Kedar,
I recommend asking the user list user@cassandra.apache.org this list is for the development of cassandra and you're more likely to find someone on the user list who may have hit this issue.
Curious issue though I haven't seen that myself.
Regards,
Ryan Svihla
> On Feb 11, 2016, at 7:56 AM, kedar <ke...@netcore.co.in> wrote:
>
> Dev Team,
>
> Need some help with a burning cqlsh issue
>
> I am using cqlsh 5.0.1 | Cassandra 2.1.2, recently we are unable to see
> / desc keyspaces and query tables through cqlsh on either of the two nodes
>
> cqlsh> desc keyspaces
>
> <empty>
>
> cqlsh> use user_index;
> cqlsh:user_index> desc table list_1_10;
>
> Keyspace 'user_index' not found.
> cqlsh:user_index>
> cqlsh> select * from system.schema_keyspaces;
> Keyspace 'system' not found.
> cqlsh>
> We are running a 2 node cluster. The Python - Django app that inserts
> data is running without any failure and system logs show nothing abnormal.
>
> ./nodetool repair on one node hasn't helped ./nodetool cfstats shows all
> the tables too
>
> ls -l cassandra/data/* on each node:
>
> https://gist.github.com/anonymous/3dddbe728a52c07d7c52
> https://gist.github.com/anonymous/302ade0875dd6410087b
>
>
>
>
> --
> Thanks,
> Kedar Parikh
>
>
>
>
>
>
>
>
>
Re: Keyspaces not found in cqlsh
Posted by Ryan Svihla <rs...@foundev.pro>.
Kedar,
I recommend asking the user list user@cassandra.apache.org this list is for the development of cassandra and you're more likely to find someone on the user list who may have hit this issue.
Curious issue though I haven't seen that myself.
Regards,
Ryan Svihla
> On Feb 11, 2016, at 7:56 AM, kedar <ke...@netcore.co.in> wrote:
>
> Dev Team,
>
> Need some help with a burning cqlsh issue
>
> I am using cqlsh 5.0.1 | Cassandra 2.1.2, recently we are unable to see
> / desc keyspaces and query tables through cqlsh on either of the two nodes
>
> cqlsh> desc keyspaces
>
> <empty>
>
> cqlsh> use user_index;
> cqlsh:user_index> desc table list_1_10;
>
> Keyspace 'user_index' not found.
> cqlsh:user_index>
> cqlsh> select * from system.schema_keyspaces;
> Keyspace 'system' not found.
> cqlsh>
> We are running a 2 node cluster. The Python - Django app that inserts
> data is running without any failure and system logs show nothing abnormal.
>
> ./nodetool repair on one node hasn't helped ./nodetool cfstats shows all
> the tables too
>
> ls -l cassandra/data/* on each node:
>
> https://gist.github.com/anonymous/3dddbe728a52c07d7c52
> https://gist.github.com/anonymous/302ade0875dd6410087b
>
>
>
>
> --
> Thanks,
> Kedar Parikh
>
>
>
>
>
>
>
>
>
Keyspaces not found in cqlsh
Posted by kedar <ke...@netcore.co.in>.
Dev Team,
Need some help with a burning cqlsh issue
I am using cqlsh 5.0.1 | Cassandra 2.1.2, recently we are unable to see
/ desc keyspaces and query tables through cqlsh on either of the two nodes
cqlsh> desc keyspaces
<empty>
cqlsh> use user_index;
cqlsh:user_index> desc table list_1_10;
Keyspace 'user_index' not found.
cqlsh:user_index>
cqlsh> select * from system.schema_keyspaces;
Keyspace 'system' not found.
cqlsh>
We are running a 2 node cluster. The Python - Django app that inserts
data is running without any failure and system logs show nothing abnormal.
./nodetool repair on one node hasn't helped ./nodetool cfstats shows all
the tables too
ls -l cassandra/data/* on each node:
https://gist.github.com/anonymous/3dddbe728a52c07d7c52
https://gist.github.com/anonymous/302ade0875dd6410087b
--
Thanks,
Kedar Parikh
Re: Keyspaces not found in cqlsh
Posted by Sebastian Estevez <se...@datastax.com>.
>
> On restart of one node 1 could see repeated errors like " Mutation of
> 22076203 bytes is too large for the maxiumum size of 16777216"
Commitlog segment size is the right lever to get C* to accept larger writes
but this is not a traditional use for cassandra. Cassandra is built to
handle lots and lots of small writes, not huge ones. I envision you will
have other pains as a result of your large mutations. If you want to write
huge values consider chunking them up into smaller writes.
Followed by a rolling restart again. And now there is a single version and
> keyspaces are back in cqlsh.
Good, your original problem was due to the schema disagreement issue and
the rolling restart solved it.
All the best,
[image: datastax_logo.png] <http://www.datastax.com/>
Sebastián Estévez
Solutions Architect | 954 905 8615 | sebastian.estevez@datastax.com
[image: linkedin.png] <https://www.linkedin.com/company/datastax> [image:
facebook.png] <https://www.facebook.com/datastax> [image: twitter.png]
<https://twitter.com/datastax> [image: g+.png]
<https://plus.google.com/+Datastax/about>
<http://feeds.feedburner.com/datastax>
<http://goog_410786983>
<http://www.datastax.com/gartner-magic-quadrant-odbms>
DataStax is the fastest, most scalable distributed database technology,
delivering Apache Cassandra to the world’s most innovative enterprises.
Datastax is built to be agile, always-on, and predictably scalable to any
size. With more than 500 customers in 45 countries, DataStax is the
database technology and transactional backbone of choice for the worlds
most innovative companies such as Netflix, Adobe, Intuit, and eBay.
On Thu, Feb 11, 2016 at 10:41 AM, kedar <ke...@netcore.co.in> wrote:
> Thanks a ton Sebastian.
>
> On restart of one node 1 could see repeated errors like " Mutation of
> 22076203 bytes is too large for the maxiumum size of 16777216"
>
> So I increased commitlog_segment_size_in_mb from 32 to 64mb.
>
> Followed by a rolling restart again. And now there is a single version and
> keyspaces are back in cqlsh.
>
> Cluster Information:
> Name: Test Cluster
> Snitch: org.apache.cassandra.locator.DynamicEndpointSnitch
> Partitioner: org.apache.cassandra.dht.Murmur3Partitioner
> Schema versions:
> 9f5b5675-c9e7-3ae3-8ad6-6654fa4fb3e7: [IP1, IP2]
>
> On the flip side what could be implications of increasing
> commitlog_segment_size_in_mb
>
> Thanks,
> Kedar Parikh
>
> On Thursday 11 February 2016 08:18 PM, Sebastian Estevez wrote:
>
> If its a tarball then root should be fine but there were some files owned
> by the Cassandra user so you may want to chown those back to root.
>
> I haven't seen your exact issue before but you have two schema versions
> from your describe cluster so a rolling restart should help.
>
> all the best,
>
> Sebastián
> On Feb 11, 2016 9:28 AM, "kedar" < <ke...@netcore.co.in>
> kedar.parikh@netcore.co.in> wrote:
>
>> Thanks Sebastian,
>>
>> Cassandra installation in our case is simply an untar.
>>
>> Cassandra is started using supervisord and user as root, would you still
>> recommend I try using Cassandra user.
>>
>> ./nodetool describecluster
>> Cluster Information:
>> Name: Test Cluster
>> Snitch: org.apache.cassandra.locator.DynamicEndpointSnitch
>> Partitioner: org.apache.cassandra.dht.Murmur3Partitioner
>> Schema versions:
>> cd361577-6947-3390-a787-be28fe499787: [Ip1]
>>
>> 9f5b5675-c9e7-3ae3-8ad6-6654fa4fb3e7: [Ip2]
>>
>> Interestingly
>> ./nodetool cfstats shows all the tables
>>
>> Thanks,
>> Kedar Parikh
>>
>> On Thursday 11 February 2016 07:34 PM, Sebastian Estevez wrote:
>>
>> Keep this on. The user list, it's not appropriate for the dev list.
>>
>> 1) I noticed that some of your files are owned by root and others by
>> Cassandra. If this is a package install you should always start C* as a
>> service and chown your files and directories so they are owned by the
>> Cassandra user, not root. Never start Cassandra directly as root.
>>
>> 2) Once you have fixed your file ownerships, restart Cassandra on each
>> node one at a time. You should see your sstables and commitlog get picked
>> up by Cassandra in the the system.log on startup. Share the output of
>> 'nodetool describecluster' before and after.
>>
>> all the best,
>>
>> Sebastián
>> On Feb 11, 2016 6:30 AM, "kedar" <ke...@netcore.co.in> wrote:
>>
>>> Thanks,
>>>
>>> kindly refer the following:
>>>
>>> https://gist.github.com/anonymous/3dddbe728a52c07d7c52
>>> https://gist.github.com/anonymous/302ade0875dd6410087b
>>>
>>> Thanks,
>>> Kedar Parikh
>>>
>>>
>>>
>>> On Thursday 11 February 2016 04:35 PM, Romain Hardouin wrote:
>>>
>>>> Would you mind pasting the ouput for both nodes in gist/paste/whatever?
>>>> https://gist.github.com <http://paste.debian.net>
>>>> http://paste.debian.net
>>>>
>>>>
>>>>
>>>> Le Jeudi 11 février 2016 11h57, kedar < <ke...@netcore.co.in>
>>>> kedar.parikh@netcore.co.in> a écrit :
>>>> Thanks for the reply.
>>>>
>>>> ls -l cassandra/data/* lists various *.db files
>>>>
>>>> This problem is on both nodes.
>>>>
>>>> Thanks,
>>>> Kedar Parikh
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>
>
Re: Keyspaces not found in cqlsh
Posted by kedar <ke...@netcore.co.in>.
Thanks a ton Sebastian.
On restart of one node 1 could see repeated errors like " Mutation of
22076203 bytes is too large for the maxiumum size of 16777216"
So I increased commitlog_segment_size_in_mb from 32 to 64mb.
Followed by a rolling restart again. And now there is a single version
and keyspaces are back in cqlsh.
Cluster Information:
Name: Test Cluster
Snitch: org.apache.cassandra.locator.DynamicEndpointSnitch
Partitioner: org.apache.cassandra.dht.Murmur3Partitioner
Schema versions:
9f5b5675-c9e7-3ae3-8ad6-6654fa4fb3e7: [IP1, IP2]
On the flip side what could be implications of increasing
commitlog_segment_size_in_mb
Thanks,
Kedar Parikh
On Thursday 11 February 2016 08:18 PM, Sebastian Estevez wrote:
>
> If its a tarball then root should be fine but there were some files
> owned by the Cassandra user so you may want to chown those back to root.
>
> I haven't seen your exact issue before but you have two schema
> versions from your describe cluster so a rolling restart should help.
>
> all the best,
>
> Sebastián
>
> On Feb 11, 2016 9:28 AM, "kedar" <kedar.parikh@netcore.co.in
> <ma...@netcore.co.in>> wrote:
>
> Thanks Sebastian,
>
> Cassandra installation in our case is simply an untar.
>
> Cassandra is started using supervisord and user as root, would you
> still recommend I try using Cassandra user.
>
> ./nodetool describecluster
> Cluster Information:
> Name: Test Cluster
> Snitch: org.apache.cassandra.locator.DynamicEndpointSnitch
> Partitioner: org.apache.cassandra.dht.Murmur3Partitioner
> Schema versions:
> cd361577-6947-3390-a787-be28fe499787: [Ip1]
>
> 9f5b5675-c9e7-3ae3-8ad6-6654fa4fb3e7: [Ip2]
>
> Interestingly
> ./nodetool cfstats shows all the tables
>
> Thanks,
> Kedar Parikh
>
> On Thursday 11 February 2016 07:34 PM, Sebastian Estevez wrote:
>>
>> Keep this on. The user list, it's not appropriate for the dev list.
>>
>> 1) I noticed that some of your files are owned by root and others
>> by Cassandra. If this is a package install you should always
>> start C* as a service and chown your files and directories so
>> they are owned by the Cassandra user, not root. Never start
>> Cassandra directly as root.
>>
>> 2) Once you have fixed your file ownerships, restart Cassandra on
>> each node one at a time. You should see your sstables and
>> commitlog get picked up by Cassandra in the the system.log on
>> startup. Share the output of 'nodetool describecluster' before
>> and after.
>>
>> all the best,
>>
>> Sebastián
>>
>> On Feb 11, 2016 6:30 AM, "kedar" <kedar.parikh@netcore.co.in
>> <ma...@netcore.co.in>> wrote:
>>
>> Thanks,
>>
>> kindly refer the following:
>>
>> https://gist.github.com/anonymous/3dddbe728a52c07d7c52
>> https://gist.github.com/anonymous/302ade0875dd6410087b
>>
>> Thanks,
>> Kedar Parikh
>>
>>
>>
>> On Thursday 11 February 2016 04:35 PM, Romain Hardouin wrote:
>>
>> Would you mind pasting the ouput for both nodes in
>> gist/paste/whatever? https://gist.github.com
>> http://paste.debian.net
>>
>>
>>
>> Le Jeudi 11 février 2016 11h57, kedar
>> <kedar.parikh@netcore.co.in
>> <ma...@netcore.co.in>> a écrit :
>> Thanks for the reply.
>>
>> ls -l cassandra/data/* lists various *.db files
>>
>> This problem is on both nodes.
>>
>> Thanks,
>> Kedar Parikh
>>
>>
>>
>>
>>
>>
>>
>>
>
Re: Keyspaces not found in cqlsh
Posted by Sebastian Estevez <se...@datastax.com>.
If its a tarball then root should be fine but there were some files owned
by the Cassandra user so you may want to chown those back to root.
I haven't seen your exact issue before but you have two schema versions
from your describe cluster so a rolling restart should help.
all the best,
Sebastián
On Feb 11, 2016 9:28 AM, "kedar" <ke...@netcore.co.in> wrote:
> Thanks Sebastian,
>
> Cassandra installation in our case is simply an untar.
>
> Cassandra is started using supervisord and user as root, would you still
> recommend I try using Cassandra user.
>
> ./nodetool describecluster
> Cluster Information:
> Name: Test Cluster
> Snitch: org.apache.cassandra.locator.DynamicEndpointSnitch
> Partitioner: org.apache.cassandra.dht.Murmur3Partitioner
> Schema versions:
> cd361577-6947-3390-a787-be28fe499787: [Ip1]
>
> 9f5b5675-c9e7-3ae3-8ad6-6654fa4fb3e7: [Ip2]
>
> Interestingly
> ./nodetool cfstats shows all the tables
>
> Thanks,
> Kedar Parikh
>
> On Thursday 11 February 2016 07:34 PM, Sebastian Estevez wrote:
>
> Keep this on. The user list, it's not appropriate for the dev list.
>
> 1) I noticed that some of your files are owned by root and others by
> Cassandra. If this is a package install you should always start C* as a
> service and chown your files and directories so they are owned by the
> Cassandra user, not root. Never start Cassandra directly as root.
>
> 2) Once you have fixed your file ownerships, restart Cassandra on each
> node one at a time. You should see your sstables and commitlog get picked
> up by Cassandra in the the system.log on startup. Share the output of
> 'nodetool describecluster' before and after.
>
> all the best,
>
> Sebastián
> On Feb 11, 2016 6:30 AM, "kedar" <ke...@netcore.co.in> wrote:
>
>> Thanks,
>>
>> kindly refer the following:
>>
>> https://gist.github.com/anonymous/3dddbe728a52c07d7c52
>> https://gist.github.com/anonymous/302ade0875dd6410087b
>>
>> Thanks,
>> Kedar Parikh
>>
>> <http://www.netcore.co.in>
>>
>> On Thursday 11 February 2016 04:35 PM, Romain Hardouin wrote:
>>
>>> Would you mind pasting the ouput for both nodes in gist/paste/whatever?
>>> https://gist.github.com http://paste.debian.net
>>>
>>>
>>>
>>> Le Jeudi 11 février 2016 11h57, kedar <ke...@netcore.co.in> a
>>> écrit :
>>> Thanks for the reply.
>>>
>>> ls -l cassandra/data/* lists various *.db files
>>>
>>> This problem is on both nodes.
>>>
>>> Thanks,
>>> Kedar Parikh
>>>
>>> <http://www.netcore.co.in>
>>>
>>>
>>>
>>>
>>
>>
>>
>
Re: Keyspaces not found in cqlsh
Posted by kedar <ke...@netcore.co.in>.
Thanks Sebastian,
Cassandra installation in our case is simply an untar.
Cassandra is started using supervisord and user as root, would you still
recommend I try using Cassandra user.
./nodetool describecluster
Cluster Information:
Name: Test Cluster
Snitch: org.apache.cassandra.locator.DynamicEndpointSnitch
Partitioner: org.apache.cassandra.dht.Murmur3Partitioner
Schema versions:
cd361577-6947-3390-a787-be28fe499787: [Ip1]
9f5b5675-c9e7-3ae3-8ad6-6654fa4fb3e7: [Ip2]
Interestingly
./nodetool cfstats shows all the tables
Thanks,
Kedar Parikh
On Thursday 11 February 2016 07:34 PM, Sebastian Estevez wrote:
>
> Keep this on. The user list, it's not appropriate for the dev list.
>
> 1) I noticed that some of your files are owned by root and others by
> Cassandra. If this is a package install you should always start C* as
> a service and chown your files and directories so they are owned by
> the Cassandra user, not root. Never start Cassandra directly as root.
>
> 2) Once you have fixed your file ownerships, restart Cassandra on each
> node one at a time. You should see your sstables and commitlog get
> picked up by Cassandra in the the system.log on startup. Share the
> output of 'nodetool describecluster' before and after.
>
> all the best,
>
> Sebastián
>
> On Feb 11, 2016 6:30 AM, "kedar" <kedar.parikh@netcore.co.in
> <ma...@netcore.co.in>> wrote:
>
> Thanks,
>
> kindly refer the following:
>
> https://gist.github.com/anonymous/3dddbe728a52c07d7c52
> https://gist.github.com/anonymous/302ade0875dd6410087b
>
> Thanks,
> Kedar Parikh
>
> <http://www.netcore.co.in>
>
> On Thursday 11 February 2016 04:35 PM, Romain Hardouin wrote:
>
> Would you mind pasting the ouput for both nodes in
> gist/paste/whatever? https://gist.github.com
> http://paste.debian.net
>
>
>
> Le Jeudi 11 février 2016 11h57, kedar
> <kedar.parikh@netcore.co.in
> <ma...@netcore.co.in>> a écrit :
> Thanks for the reply.
>
> ls -l cassandra/data/* lists various *.db files
>
> This problem is on both nodes.
>
> Thanks,
> Kedar Parikh
>
> <http://www.netcore.co.in>
>
>
>
>
>
>
Re: Keyspaces not found in cqlsh
Posted by Sebastian Estevez <se...@datastax.com>.
Keep this on. The user list, it's not appropriate for the dev list.
1) I noticed that some of your files are owned by root and others by
Cassandra. If this is a package install you should always start C* as a
service and chown your files and directories so they are owned by the
Cassandra user, not root. Never start Cassandra directly as root.
2) Once you have fixed your file ownerships, restart Cassandra on each node
one at a time. You should see your sstables and commitlog get picked up by
Cassandra in the the system.log on startup. Share the output of 'nodetool
describecluster' before and after.
all the best,
Sebastián
On Feb 11, 2016 6:30 AM, "kedar" <ke...@netcore.co.in> wrote:
> Thanks,
>
> kindly refer the following:
>
> https://gist.github.com/anonymous/3dddbe728a52c07d7c52
> https://gist.github.com/anonymous/302ade0875dd6410087b
>
> Thanks,
> Kedar Parikh
>
> Ext : 2224
> Dir : +91 22 61782224
> Mob : +91 9819634734
> Email : kedar.parikh@netcore.co.in
> Web : www.netcore.co.in
>
> On Thursday 11 February 2016 04:35 PM, Romain Hardouin wrote:
>
>> Would you mind pasting the ouput for both nodes in gist/paste/whatever?
>> https://gist.github.com http://paste.debian.net
>>
>>
>>
>> Le Jeudi 11 février 2016 11h57, kedar <ke...@netcore.co.in> a
>> écrit :
>> Thanks for the reply.
>>
>> ls -l cassandra/data/* lists various *.db files
>>
>> This problem is on both nodes.
>>
>> Thanks,
>> Kedar Parikh
>>
>> Ext : 2224
>> Dir : +91 22 61782224
>> Mob : +91 9819634734
>> Email : kedar.parikh@netcore.co.in
>> Web : www.netcore.co.in
>>
>>
>>
>>
>
>
>
Re: Keyspaces not found in cqlsh
Posted by kedar <ke...@netcore.co.in>.
Thanks,
kindly refer the following:
https://gist.github.com/anonymous/3dddbe728a52c07d7c52
https://gist.github.com/anonymous/302ade0875dd6410087b
Thanks,
Kedar Parikh
Ext : 2224
Dir : +91 22 61782224
Mob : +91 9819634734
Email : kedar.parikh@netcore.co.in
Web : www.netcore.co.in
On Thursday 11 February 2016 04:35 PM, Romain Hardouin wrote:
> Would you mind pasting the ouput for both nodes in gist/paste/whatever? https://gist.github.com http://paste.debian.net
>
>
>
> Le Jeudi 11 février 2016 11h57, kedar <ke...@netcore.co.in> a écrit :
> Thanks for the reply.
>
> ls -l cassandra/data/* lists various *.db files
>
> This problem is on both nodes.
>
> Thanks,
> Kedar Parikh
>
> Ext : 2224
> Dir : +91 22 61782224
> Mob : +91 9819634734
> Email : kedar.parikh@netcore.co.in
> Web : www.netcore.co.in
>
>
>
Re: Keyspaces not found in cqlsh
Posted by Romain Hardouin <ro...@yahoo.fr>.
Would you mind pasting the ouput for both nodes in gist/paste/whatever? https://gist.github.com http://paste.debian.net
Le Jeudi 11 février 2016 11h57, kedar <ke...@netcore.co.in> a écrit :
Thanks for the reply.
ls -l cassandra/data/* lists various *.db files
This problem is on both nodes.
Thanks,
Kedar Parikh
Ext : 2224
Dir : +91 22 61782224
Mob : +91 9819634734
Email : kedar.parikh@netcore.co.in
Web : www.netcore.co.in
Re: Keyspaces not found in cqlsh
Posted by kedar <ke...@netcore.co.in>.
Thanks for the reply.
ls -l cassandra/data/* lists various *.db files
This problem is on both nodes.
Thanks,
Kedar Parikh
Ext : 2224
Dir : +91 22 61782224
Mob : +91 9819634734
Email : kedar.parikh@netcore.co.in
Web : www.netcore.co.in
On Thursday 11 February 2016 03:57 PM, Romain Hardouin wrote:
> What is the output on both nodes of the following command?
> ls -l /var/lib/cassandra/data/system/*
> If one node seems odd you can try "nodetool resetlocalschema" but the other node must be in clean state.
>
> Best,
> Romain
>
>
> Le Jeudi 11 février 2016 11h10, kedar <ke...@netcore.co.in> a écrit :
> I am using cqlsh 5.0.1 | Cassandra 2.1.2, recently we are unable to see
> / desc keyspaces and query tables through cqlsh on either of the two nodes
>
> cqlsh> desc keyspaces
>
> <empty>
>
> cqlsh> use user_index;
> cqlsh:user_index> desc table list_1_10;
>
> Keyspace 'user_index' not found.
> cqlsh:user_index>
> cqlsh> select * from system.schema_keyspaces;
> Keyspace 'system' not found.
> cqlsh>
> We are running a 2 node cluster. The Python - Django app that inserts
> data is running without any failure and system logs show nothing abnormal.
>
> ./nodetool repair on one node hasn't helped ./nodetool cfstats shows all
> the tables too
>
Re: Keyspaces not found in cqlsh
Posted by Romain Hardouin <ro...@yahoo.fr>.
What is the output on both nodes of the following command?
ls -l /var/lib/cassandra/data/system/*
If one node seems odd you can try "nodetool resetlocalschema" but the other node must be in clean state.
Best,
Romain
Le Jeudi 11 février 2016 11h10, kedar <ke...@netcore.co.in> a écrit :
I am using cqlsh 5.0.1 | Cassandra 2.1.2, recently we are unable to see
/ desc keyspaces and query tables through cqlsh on either of the two nodes
cqlsh> desc keyspaces
<empty>
cqlsh> use user_index;
cqlsh:user_index> desc table list_1_10;
Keyspace 'user_index' not found.
cqlsh:user_index>
cqlsh> select * from system.schema_keyspaces;
Keyspace 'system' not found.
cqlsh>
We are running a 2 node cluster. The Python - Django app that inserts
data is running without any failure and system logs show nothing abnormal.
./nodetool repair on one node hasn't helped ./nodetool cfstats shows all
the tables too
--
Thanks,
Kedar Parikh
Ext : 2224
Dir : +91 22 61782224
Mob : +91 9819634734
Email : kedar.parikh@netcore.co.in
Web : www.netcore.co.in