Re: Is anyone using version 0.7 schema update API
http://github.com/fauna/cassandra/tree/master/lib/cassandra/0.7/ Unclear to me what problems you are experiencing. On Sun, Jul 11, 2010 at 2:27 PM, GH wrote: > Hi Dop, > > Do you have any code on dynamically creating KeySpace and ColumnFamily. > Currently I was all but creating a new client to do that which seems to be > the wrong way. > If you have something that works that will put me on the right track I hope. > > > Gavan > > > On Mon, Jul 12, 2010 at 2:41 AM, Dop Sun wrote: >> >> Based on current source codes in the head, moving from 0.6.x to 0.7, means >> some code changes in the client side (other than server side changes, like >> storage_conf.xml). >> >> >> >> Something like: >> >> 1. New Clock class instead of timestamp: this may be trivia, but it >> takes some time to change >> >> 2. Moving key space out of the API >> >> 3. Key changed from string to byte >> >> 4. Some API change, like get_count >> >> >> >> I’m still exploring the changes since I’m working on a Java client for >> Cassandra. There should be longer list than what I have discovered. >> >> >> >> But, 0.7 is really good. I love the one can dynamically create Key Space >> and Column Family. Also, I love the key to be a byte array instead of >> string. >> >> >> >> Enjoy the migrating. J >> >> >> >> Dop >> >> >> >> From: GH [mailto:gavan.h...@gmail.com] >> Sent: Sunday, July 11, 2010 8:42 PM >> To: user@cassandra.apache.org >> Subject: Is anyone using version 0.7 schema update API >> >> >> >> I want to move on to 0.7 using this API rather than storage-conf.xml >> conversion. >> >> Any info that you can advise on how you used it would be much appreciated. >> >> >> >> Thanks >> >> Gavan >
Re: advice, is cassandra suitable for a multi-tanency vBulletin type application?
On Sun, Jul 11, 2010 at 8:39 AM, S Ahmed wrote: > I want to build a vBulletin type application (forums, threads, posts, user > management, etc). > Support multi-tenancy for a Saas type environment. > Would Cassandra be suitable for this type of application? > > > Thanks in advance. Most likely, it is technically a fine fit. But Cassandra is very early stage software, so you should expect that the documentation will not always be clear and things will change from version to version. If you are not extremely self-reliant, you may find it a frustrating experience. Unless you are confident you will have trouble scaling traditional technologies, it might not make business sense. Paul Prescod
RE: Is anyone using version 0.7 schema update API
My work for Cassandra 0.7 just started, which ensures existing API working for 0.7. Supporting new features, like creating KeySpace and ColumnFamily, will be added once the existing functionality tested. You may follow changes on http://code.google.com/p/jassandra/. Dop From: GH [mailto:gavan.h...@gmail.com] Sent: Monday, July 12, 2010 5:28 AM To: user@cassandra.apache.org Subject: Re: Is anyone using version 0.7 schema update API Hi Dop, Do you have any code on dynamically creating KeySpace and ColumnFamily. Currently I was all but creating a new client to do that which seems to be the wrong way. If you have something that works that will put me on the right track I hope. Gavan On Mon, Jul 12, 2010 at 2:41 AM, Dop Sun wrote: Based on current source codes in the head, moving from 0.6.x to 0.7, means some code changes in the client side (other than server side changes, like storage_conf.xml). Something like: 1. New Clock class instead of timestamp: this may be trivia, but it takes some time to change 2. Moving key space out of the API 3. Key changed from string to byte 4. Some API change, like get_count I'm still exploring the changes since I'm working on a Java client for Cassandra. There should be longer list than what I have discovered. But, 0.7 is really good. I love the one can dynamically create Key Space and Column Family. Also, I love the key to be a byte array instead of string. Enjoy the migrating. J Dop From: GH [mailto:gavan.h...@gmail.com] Sent: Sunday, July 11, 2010 8:42 PM To: user@cassandra.apache.org Subject: Is anyone using version 0.7 schema update API I want to move on to 0.7 using this API rather than storage-conf.xml conversion. Any info that you can advise on how you used it would be much appreciated. Thanks Gavan
Re: Is anyone using version 0.7 schema update API
Hi Dop, Do you have any code on dynamically creating KeySpace and ColumnFamily. Currently I was all but creating a new client to do that which seems to be the wrong way. If you have something that works that will put me on the right track I hope. Gavan On Mon, Jul 12, 2010 at 2:41 AM, Dop Sun wrote: > Based on current source codes in the head, moving from 0.6.x to 0.7, > means some code changes in the client side (other than server side changes, > like storage_conf.xml). > > > > Something like: > > 1. New Clock class instead of timestamp: this may be trivia, but it > takes some time to change > > 2. Moving key space out of the API > > 3. Key changed from string to byte > > 4. Some API change, like get_count > > > > I’m still exploring the changes since I’m working on a Java client for > Cassandra. There should be longer list than what I have discovered. > > > > But, 0.7 is really good. I love the one can dynamically create Key Space > and Column Family. Also, I love the key to be a byte array instead of > string. > > > > Enjoy the migrating. J > > > > Dop > > > > *From:* GH [mailto:gavan.h...@gmail.com] > *Sent:* Sunday, July 11, 2010 8:42 PM > *To:* user@cassandra.apache.org > *Subject:* Is anyone using version 0.7 schema update API > > > > I want to move on to 0.7 using this API rather than storage-conf.xml > conversion. > > Any info that you can advise on how you used it would be much appreciated. > > > > Thanks > > Gavan >
Re: Question about CL.ZERO
And, to be clear, there is no good reason to use CL.ZERO and it can be a serious resource hog on the coordinator. On Sun, Jul 11, 2010 at 9:21 AM, ChingShen wrote: > Hi all, > > Does it mean that the coordinator node always return success to the client > at CL.ZERO? But if the coordinator node sends a request to a given node > B(RF=1), then B is down, what happened? The coordinator node will write the > hint locally? > > Thanks. > > Shen >
Re: Question about CL.ZERO
On Sun, Jul 11, 2010 at 11:21 AM, ChingShen wrote: > Hi all, > > Does it mean that the coordinator node always return success to the client > at CL.ZERO? Yes. > But if the coordinator node sends a request to a given node > B(RF=1), then B is down, what happened? The coordinator node will write the > hint locally? Sort of: if the coordinator knows when it begins processing the request that B is down, it will write a hint. But if it has not yet detected that B is down, then it will attempt a write. If the write times out then no further attempts are made. -- Jonathan Ellis Project Chair, Apache Cassandra co-founder of Riptano, the source for professional Cassandra support http://riptano.com
Re: nodetool move gives exception
That looks like it was asked to move when it didn't know about any other nodes in the cluster. Usually this indicates a misconfiguration. On Sun, Jul 11, 2010 at 7:07 AM, Sagar Agrawal wrote: > When I did nodetool move , nodetool streams for that node shows > mode:bootstrapping > but modetool move gave following exception > http://gist.github.com/471503 > > but the mode is still bootstrapping... > > what does that mean? > > Thanks > -- Jonathan Ellis Project Chair, Apache Cassandra co-founder of Riptano, the source for professional Cassandra support http://riptano.com
RE: Is anyone using version 0.7 schema update API
Based on current source codes in the head, moving from 0.6.x to 0.7, means some code changes in the client side (other than server side changes, like storage_conf.xml). Something like: 1. New Clock class instead of timestamp: this may be trivia, but it takes some time to change 2. Moving key space out of the API 3. Key changed from string to byte 4. Some API change, like get_count I'm still exploring the changes since I'm working on a Java client for Cassandra. There should be longer list than what I have discovered. But, 0.7 is really good. I love the one can dynamically create Key Space and Column Family. Also, I love the key to be a byte array instead of string. Enjoy the migrating. J Dop From: GH [mailto:gavan.h...@gmail.com] Sent: Sunday, July 11, 2010 8:42 PM To: user@cassandra.apache.org Subject: Is anyone using version 0.7 schema update API I want to move on to 0.7 using this API rather than storage-conf.xml conversion. Any info that you can advise on how you used it would be much appreciated. Thanks Gavan
Question about CL.ZERO
Hi all, Does it mean that the coordinator node always return success to the client at CL.ZERO? But if the coordinator node sends a request to a given node B(RF=1), then B is down, what happened? The coordinator node will write the hint locally? Thanks. Shen
advice, is cassandra suitable for a multi-tanency vBulletin type application?
I want to build a vBulletin type application (forums, threads, posts, user management, etc). Support multi-tenancy for a Saas type environment. Would Cassandra be suitable for this type of application? Thanks in advance.
Re: Strange "Address already in use" error
Something is already using the port (probably 7000 (default, used internal by cassandra)) you tried to bind. Use e.g. 'lsof -i' to investigate the port usage further. // Roger Schildmeijer On 11 jul 2010, at 17.15em, osishkin osishkin wrote: > I'm testing a simple Cassandra cluster on two machines. For some reaon > after a while one of the nodes in the cluster crashes. > At first I thought the fault was on me, so I simply started it up again. > After the second time this happenned I noticed the following message errors - > > INFO 17:28:05,624 Mycolumnfamily has reached its threshold; switching > in a fresh Memtable at > CommitLogContext(file='/var/lib/cassandra/commitlogMY/CommitLog-1278858485610.log', > position=116) > INFO 17:28:05,625 Enqueuing flush of Memtable(Mycolumnfamily)@1499027801 > INFO 17:28:05,672 Writing Memtable(Mycolumnfamily)@1499027801 > INFO 17:28:05,730 Completed flushing > /var/lib/cassandra/dataMY/MYKeyspace1/Mycolumnfamily-27-Data.db > INFO 17:28:05,731 Log replay complete > INFO 17:28:05,756 Saved Token found: 66090367128402196046887347762075208662 > INFO 17:28:05,756 Saved ClusterName found: MY Cluster > WARN 17:28:05,760 Unable to start GCInspector (currently only > supported on the Sun JVM) > INFO 17:28:05,760 Starting up server gossip > ERROR 17:28:05,766 Exception encountered during startup. > java.net.BindException: Address already in use >at sun.nio.ch.Net.bind(Native Method) >at > sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:137) >at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:59) >at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:52) >at > org.apache.cassandra.net.MessagingService.listen(MessagingService.java:138) >at > org.apache.cassandra.service.StorageService.initServer(StorageService.java:328) >at > org.apache.cassandra.thrift.CassandraDaemon.setup(CassandraDaemon.java:99) >at > org.apache.cassandra.thrift.CassandraDaemon.main(CassandraDaemon.java:177) > Exception encountered during startup. > > Obviously nothing has changed on the machines, I'm using default ports > that aren't taken by any other application (I saw people had problems > with 8080, but it's not used on my machines. 9160 isn't either). When > I started up cassandra again on both nodes, things worked just fine > (until further notice at least). > So I'm kind of at a loss here. > > Any idea as to what is wrong would be appreciated > Thank you.
Strange "Address already in use" error
I'm testing a simple Cassandra cluster on two machines. For some reaon after a while one of the nodes in the cluster crashes. At first I thought the fault was on me, so I simply started it up again. After the second time this happenned I noticed the following message errors - INFO 17:28:05,624 Mycolumnfamily has reached its threshold; switching in a fresh Memtable at CommitLogContext(file='/var/lib/cassandra/commitlogMY/CommitLog-1278858485610.log', position=116) INFO 17:28:05,625 Enqueuing flush of Memtable(Mycolumnfamily)@1499027801 INFO 17:28:05,672 Writing Memtable(Mycolumnfamily)@1499027801 INFO 17:28:05,730 Completed flushing /var/lib/cassandra/dataMY/MYKeyspace1/Mycolumnfamily-27-Data.db INFO 17:28:05,731 Log replay complete INFO 17:28:05,756 Saved Token found: 66090367128402196046887347762075208662 INFO 17:28:05,756 Saved ClusterName found: MY Cluster WARN 17:28:05,760 Unable to start GCInspector (currently only supported on the Sun JVM) INFO 17:28:05,760 Starting up server gossip ERROR 17:28:05,766 Exception encountered during startup. java.net.BindException: Address already in use at sun.nio.ch.Net.bind(Native Method) at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:137) at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:59) at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:52) at org.apache.cassandra.net.MessagingService.listen(MessagingService.java:138) at org.apache.cassandra.service.StorageService.initServer(StorageService.java:328) at org.apache.cassandra.thrift.CassandraDaemon.setup(CassandraDaemon.java:99) at org.apache.cassandra.thrift.CassandraDaemon.main(CassandraDaemon.java:177) Exception encountered during startup. Obviously nothing has changed on the machines, I'm using default ports that aren't taken by any other application (I saw people had problems with 8080, but it's not used on my machines. 9160 isn't either). When I started up cassandra again on both nodes, things worked just fine (until further notice at least). So I'm kind of at a loss here. Any idea as to what is wrong would be appreciated Thank you.
Re: Is anyone using version 0.7 schema update API
http://wiki.apache.org/cassandra/LiveSchemaUpdates On 11 jul 2010, at 14.42em, GH wrote: > I want to move on to 0.7 using this API rather than storage-conf.xml > conversion. > Any info that you can advise on how you used it would be much appreciated. > > Thanks > Gavan
Is anyone using version 0.7 schema update API
I want to move on to 0.7 using this API rather than storage-conf.xml conversion. Any info that you can advise on how you used it would be much appreciated. Thanks Gavan
nodetool move gives exception
When I did nodetool move , nodetool streams for that node shows mode:bootstrapping but modetool move gave following exception http://gist.github.com/471503 but the mode is still bootstrapping... what does that mean? Thanks
