Re: Problem with Keyspace after drop
I have tried restarting all of the nodes with no change. Created JIRA https://issues.apache.org/jira/browse/CASSANDRA-4219 Thanks, Jeff On May 3, 2012, at 9:46 PM, Sylvain Lebresne wrote: > Would you mind opening a ticket on JIRA > (https://issues.apache.org/jira/browse/CASSANDRA). This is > definitively a bug and it's be easier to follow up there. > > Did you try restarting the node on which you try the create keyspace? > > -- > Sylvain > > On Thu, May 3, 2012 at 8:43 PM, Jeff Williams > wrote: >> As a follow up, I am running version 1.1 and have tried nodetool repair, >> cleanup, compact. I can create other keyspaces, but still can't create a >> keyspace called PlayLog even though it is not listed anywhere. >> >> On May 3, 2012, at 6:35 PM, Jeff Williams wrote: >> >>> Hi, >>> >>> I'm doing testing and wanted to drop a keyspace (with a column family) to >>> re-add it with a different strategy. So I ran in cqlsh: >>> >>> DROP KEYSPACE PlayLog; >>> >>> CREATE KEYSPACE PlayLog WITH strategy_class = 'SimpleStrategy' >>> AND strategy_options:replication_factor = 2; >>> >>> And everything seemed to be fine. I ran some inserts, which also seemed to >>> go fine, but then selecting them gave me: >>> >>> cqlsh:PlayLog> select count(*) from playlog; >>> TSocket read 0 bytes >>> >>> I wasn't sure what was wrong, so I tried dropping and creating again, and >>> now when I try to create I get: >>> >>> cqlsh> CREATE KEYSPACE PlayLog WITH strategy_class = 'SimpleStrategy' >>> ... AND strategy_options:replication_factor = 2; >>> TSocket read 0 bytes >>> >>> And the keyspace doesn't get created. In the log it shows: >>> >>> ERROR [Thrift:4] 2012-05-03 18:23:05,124 CustomTThreadPoolServer.java (line >>> 204) Error occurred during processing of message. >>> java.lang.RuntimeException: java.util.concurrent.ExecutionException: >>> java.lang.AssertionError >>>at >>> org.apache.cassandra.utils.FBUtilities.waitOnFuture(FBUtilities.java:372) >>>at >>> org.apache.cassandra.service.MigrationManager.announce(MigrationManager.java:191) >>>at >>> org.apache.cassandra.service.MigrationManager.announceNewKeyspace(MigrationManager.java:129) >>>at >>> org.apache.cassandra.cql.QueryProcessor.processStatement(QueryProcessor.java:701) >>>at >>> org.apache.cassandra.cql.QueryProcessor.process(QueryProcessor.java:875) >>>at >>> org.apache.cassandra.thrift.CassandraServer.execute_cql_query(CassandraServer.java:1235) >>>at >>> org.apache.cassandra.thrift.Cassandra$Processor$execute_cql_query.getResult(Cassandra.java:3458) >>>at >>> org.apache.cassandra.thrift.Cassandra$Processor$execute_cql_query.getResult(Cassandra.java:3446) >>>at org.apache.thrift.ProcessFunction.process(ProcessFunction.java:32) >>>at org.apache.thrift.TBaseProcessor.process(TBaseProcessor.java:34) >>>at >>> org.apache.cassandra.thrift.CustomTThreadPoolServer$WorkerProcess.run(CustomTThreadPoolServer.java:186) >>>at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown >>> Source) >>>at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) >>>at java.lang.Thread.run(Unknown Source) >>> Caused by: java.util.concurrent.ExecutionException: java.lang.AssertionError >>>at java.util.concurrent.FutureTask$Sync.innerGet(Unknown Source) >>>at java.util.concurrent.FutureTask.get(Unknown Source) >>>at >>> org.apache.cassandra.utils.FBUtilities.waitOnFuture(FBUtilities.java:368) >>>... 13 more >>> Caused by: java.lang.AssertionError >>>at >>> org.apache.cassandra.db.DefsTable.updateKeyspace(DefsTable.java:441) >>>at >>> org.apache.cassandra.db.DefsTable.mergeKeyspaces(DefsTable.java:339) >>>at org.apache.cassandra.db.DefsTable.mergeSchema(DefsTable.java:269) >>>at >>> org.apache.cassandra.service.MigrationManager$1.call(MigrationManager.java:214) >>>at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) >>>at java.util.concurrent.FutureTask.run(Unknown Source) >>>... 3 more >>> ERROR [MigrationStage:1] 2012-05-03 18:23:05,124 >>> AbstractCassandraDaemon.java (line 134) Exception in thread >>> Thread[MigrationStage:1,5,main] >>> java.lang.AssertionError >>>at >>> org.apache.cassandra.db.DefsTable.updateKeyspace(DefsTable.java:441) >>>at >>> org.apache.cassandra.db.DefsTable.mergeKeyspaces(DefsTable.java:339) >>>at org.apache.cassandra.db.DefsTable.mergeSchema(DefsTable.java:269) >>>at >>> org.apache.cassandra.service.MigrationManager$1.call(MigrationManager.java:214) >>>at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) >>>at java.util.concurrent.FutureTask.run(Unknown Source) >>>at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown >>> Source) >>>at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) >>>
R: Cassandra is not storing values correctly.
When I store some values in a certain column these values are only stored when cassandra is running. What do you mean? When i restart cassandra the values that i stored are misteriously gone Are you sure that your cluster is ok? And that you are not writing columns' TTL? And also the old values that i deleted before reappear. definitely: http://wiki.apache.org/cassandra/Operations#Frequency_of_nodetool_repair Regards,Carlo Messaggio originale Da: linuxispossi...@gmail.com Data: 04/05/2012 9.57 A: Ogg: Cassandra is not storing values correctly. Hi everyone, i'm using Cassandra as main storage for my PHP platform, but actually seems that cassandra is not working properly. When I store some values in a certain column these values are only stored when cassandra is running. When i restart cassandra the values that i stored are misteriously gone. No trace. And also the old values that i deletedbefore reappear. Have a good day.
Re: Misleading CQL behaviour regarding LIMIT clause
On Thu, May 3, 2012 at 8:07 PM, Roshan wrote: > I have created a CF and it has around 10 million rows. But If I try to > select statement with the LIMIT 100, it returns 79 records. Don't know why > this behavior? > > *Statement I used:* > SELECT * FROM ActivityLog WHERE userid = '%s' AND created >= '%s' AND > created <= '%s' LIMIT 100 My guess would be that, total number of rows in the columnfamily notwithstanding, there are only 79 for the given the predicates. -- Eric Evans Acunu | http://www.acunu.com | @acunu
getting status of long running repair
I know repair may take a long time to run. I am running repair on a node with about 15 GB of data and it is taking more than 24 hours. Is that normal? Is there any way to get status of the repair? tpstats does show 2 active and 2 pending AntiEntropySessions. But netstats and compactionstats show no activity. Bill
Re: getting status of long running repair
On Fri, May 4, 2012 at 10:30 AM, Bill Au wrote: > I know repair may take a long time to run. I am running repair on a node > with about 15 GB of data and it is taking more than 24 hours. Is that > normal? Is there any way to get status of the repair? tpstats does show 2 > active and 2 pending AntiEntropySessions. But netstats and compactionstats > show no activity. As indicated by various recent threads to this effect, many versions of cassandra (including current 1.0.x release) contain bugs which sometimes prevent repair from completing. The other threads suggest that some of these bugs result in the state you are in now, where you do not see anything that looks like appropriate activity. Unfortunately the only solution offered on these other threads is the one I will now offer, which is to restart the participating nodes and re-start the repair. I am unaware of any JIRA tickets tracking these bugs (which doesn't mean they don't exist, of course) so you might want to file one. :) =Rob -- =Robert Coli AIM>ALK - rc...@palominodb.com YAHOO - rcoli.palominob SKYPE - rcoli_palominodb
stream data using bulkoutputformat
Hi Group: I am following this great example to use bulkouputformat to streaming the data from hadoop to cassandra. http://shareitexploreit.blogspot.com/2012/03/bulkloadto-cassandra-with-hado op.html. It works perfectly when my keyspace has one cf. But in my case, I have 2 coulumn families defined in the keyspace that I want to stream the data to both of them at the same mapper. Seems like the configHelper can only set one output column family. Is there a way that I can set multiple column families in one keyspace and output data to all the cfs? Thx Shawna
Re: stream data using bulkoutputformat
We're working on this over at https://issues.apache.org/jira/browse/CASSANDRA-4208 On Fri, May 4, 2012 at 4:56 PM, Shawna Qian wrote: > Hi Group: > > I am following this great example to use bulkouputformat to streaming the > data from hadoop to cassandra. > http://shareitexploreit.blogspot.com/2012/03/bulkloadto-cassandra-with-hado > op.html. It works perfectly when my keyspace has one cf. > > But in my case, I have 2 coulumn families defined in the keyspace that I > want to stream the data to both of them at the same mapper. Seems like > the configHelper can only set one output column family. Is there a way > that I can set multiple column families in one keyspace and output data to > all the cfs? > > > Thx > Shawna > -- Jonathan Ellis Project Chair, Apache Cassandra co-founder of DataStax, the source for professional Cassandra support http://www.datastax.com
Updating CF to reversed type
Is it possible to update CF definition to use "reversed" type? If it's possible then what happens to the old values, do they still remain ordered in ascending order?
