Re: avoid log spam with 0 HH rows delivered
Fixed in 1.0? https://issues.apache.org/jira/browse/CASSANDRA-3176 2012/3/2 Radim Kolar h...@sendmail.cz: Can be something made to remove these empty delivery attempts from log? Its just tombstoned row. [default@system] list HintsColumnFamily; Using default limit of 100 --- RowKey: 00 1 Row Returned. Elapsed time: 234 msec(s). INFO [HintedHandoff:1] 2012-03-02 05:44:32,359 HintedHandOffManager.java (line 296) Started hinted handoff for token: 0 with IP: /64.6.104.18 INFO [HintedHandoff:1] 2012-03-02 05:44:32,362 HintedHandOffManager.java (line 373) Finished hinted handoff of 0 rows to endpoint /64.6.104.18 INFO [HintedHandoff:1] 2012-03-02 05:54:31,641 HintedHandOffManager.java (line 296) Started hinted handoff for token: 0 with IP: /64.6.104.18 INFO [HintedHandoff:1] 2012-03-02 05:54:31,644 HintedHandOffManager.java (line 373) Finished hinted handoff of 0 rows to endpoint /64.6.104.18 INFO [HintedHandoff:1] 2012-03-02 06:04:25,253 HintedHandOffManager.java (line 296) Started hinted handoff for token: 0 with IP: /64.6.104.18 INFO [HintedHandoff:1] 2012-03-02 06:04:25,255 HintedHandOffManager.java (line 373) Finished hinted handoff of 0 rows to endpoint /64.6.104.18 INFO [HintedHandoff:1] 2012-03-02 06:14:57,984 HintedHandOffManager.java (line 296) Started hinted handoff for token: 0 with IP: /64.6.104.18 INFO [HintedHandoff:1] 2012-03-02 06:14:58,013 HintedHandOffManager.java (line 373) Finished hinted handoff of 0 rows to endpoint /64.6.104.18 INFO [HintedHandoff:1] 2012-03-02 06:24:15,206 HintedHandOffManager.java (line 296) Started hinted handoff for token: 0 with IP: /64.6.104.18 INFO [HintedHandoff:1] 2012-03-02 06:24:15,208 HintedHandOffManager.java (line 373) Finished hinted handoff of 0 rows to endpoint /64.6.104.18 INFO [HintedHandoff:1] 2012-03-02 06:34:43,108 HintedHandOffManager.java (line 296) Started hinted handoff for token: 0 with IP: /64.6.104.18 INFO [HintedHandoff:1] 2012-03-02 06:34:43,110 HintedHandOffManager.java (line 373) Finished hinted handoff of 0 rows to endpoint /64.6.104.18 -- w3m
Re: sstable2json timestamp format
It turns out to be a pycassa 1.5.0 issue, solved by the just released 1.5.1: https://github.com/pycassa/pycassa/blob/681905ce1037a130d8fed37ea9bd41e2a4fe8bbd/CHANGES Sorry for the noise. Thank you Tyler! bye, lele. -- nickname: Lele Gaifax | Quando vivrò di quello che ho pensato ieri real: Emanuele Gaifas | comincerò ad aver paura di chi mi copia. l...@metapensiero.it | -- Fortunato Depero, 1929.
Re: avoid log spam with 0 HH rows delivered
Dne 2.3.2012 9:49, Maki Watanabe napsal(a): Fixed in 1.0? https://issues.apache.org/jira/browse/CASSANDRA-3176 that patch test if sstable is empty before continuing HH delivery but in my case table is not empty - it contains one tombstoned row.
Re: unidirectional communication/replication
If you need to dump a lot of data consider the Hadoop integration. http://wiki.apache.org/cassandra/HadoopSupport It can run a bit faster than going through the thrift api. cassandra hadoop integration reads sstables directly instead of going via thrift?
Re: how stable is 1.0 these days?
beware of https://issues.apache.org/jira/browse/CASSANDRA-3820 though if you have many keys per node other than that, yep, it seems solid /Marcus On Wed, Feb 29, 2012 at 6:20 PM, Thibaut Britz thibaut.br...@trendiction.com wrote: Thanks! We will test it on our test cluster in the coming weeks and hopefully put it into production on our 200 node main cluster. :) Thibaut On Wed, Feb 29, 2012 at 5:52 PM, Edward Capriolo edlinuxg...@gmail.comwrote: On Wed, Feb 29, 2012 at 10:35 AM, Thibaut Britz thibaut.br...@trendiction.com wrote: Any more feedback on larger deployments of 1.0.*? We are eager to try out the new features in production, but don't want to run into bugs as on former 0.7 and 0.8 versions. Thanks, Thibaut On Tue, Jan 31, 2012 at 6:59 AM, Ben Coverston ben.covers...@datastax.com wrote: I'm not sure what Carlo is referring to, but generally if you have done, thousands of migrations you can end up in a situation where the migrations take a long time to replay, and there are some race conditions that can be problematic in the case where there are thousands of migrations that may need to be replayed while a node is bootstrapped. If you get into this situation it can be fixed by copying migrations from a known good schema to the node that you are trying to bootstrap. Generally I would advise against frequent schema updates. Unlike rows in column families the schema itself is designed to be relatively static. On Mon, Jan 30, 2012 at 2:14 PM, Jim Newsham jnews...@referentia.com wrote: Could you also elaborate for creating/dropping column families? We're currently working on moving to 1.0 and using dynamically created tables, so I'm very interested in what issues we might encounter. So far the only thing I've encountered (with 1.0.7 + hector 1.0-2) is that dropping a cf may sometimes fail with UnavailableException. I think this happens when the cf is busy being compacted. When I sleep/retry within a loop it eventually succeeds. Thanks, Jim On 1/26/2012 7:32 AM, Pierre-Yves Ritschard wrote: Can you elaborate on the composite types instabilities ? is this specific to hector as the radim's posts suggests ? These one liner answers are quite stressful :) On Thu, Jan 26, 2012 at 1:28 PM, Carlo Pirescarlopi...@gmail.com wrote: If you need to use composite types and create/drop column families on the fly you must be prepared to instabilities. -- Ben Coverston DataStax -- The Apache Cassandra Company I would call 1.0.7 rock fricken solid. Incredibly stable. It has been that way since I updated to 0.8.8 really. TBs of data, billions of requests a day, and thanks to JAMM, memtable type auto-tuning, and other enhancements I rarely, if ever, find a node in a state where it requires a restart. My clusters are beast-ing. There always is bugs in software, but coming from a guy who ran cassandra 0.6.1.Administration on my Cassandra cluster is like a vacation now.
Way to force the propagation of a schema change?
Hi everyone, I add a column family dynamically and notice that when describe schema versions return 2 values. Then it quickly changes back to 1. Sometimes this stays at 2 and does not change. Then I cannot insert values to the created column family, as it causes an exception. Is there a way to force the schema propagation through the thrift API (not the CLI)? Thanks in advance. -- Regards, Tharindu blog: http://mackiemathew.com/
Re: avoid log spam with 0 HH rows delivered
How about to truncate HintsColumnFamily and then execute nodetool repair as work around? On 2012/03/02, at 18:11, Radim Kolar h...@sendmail.cz wrote: Dne 2.3.2012 9:49, Maki Watanabe napsal(a): Fixed in 1.0? https://issues.apache.org/jira/browse/CASSANDRA-3176 that patch test if sstable is empty before continuing HH delivery but in my case table is not empty - it contains one tombstoned row.
Re: avoid log spam with 0 HH rows delivered
Dne 2.3.2012 13:24, Watanabe Maki napsal(a): How about to truncate HintsColumnFamily and then execute nodetool repair as work around? i got this exception in CLI. Its weird, all my nodes are UP and no exception message in server log. [default@unknown] use system; Authenticated to keyspace: system [default@system] truncate HintsColumnFamily ; null UnavailableException() at org.apache.cassandra.thrift.Cassandra$truncate_result.read(Cassandra.java:20212)
What is the best way to secure remote Cassandra (dev) server ?
We have our development Cassandra 1.0.8 server running on EC2 and wanted to secure it. I read securing the entire server with firewall is one of the options. What are the other cheaper options to secure a development server ? regards, Ramesh
Re: What is the best way to secure remote Cassandra (dev) server ?
Put it on a non-routable internal network. 192.168.x.x 172.16.x.x Etc... On Mar 2, 2012 1:56 PM, investtr investt...@gmail.com wrote: We have our development Cassandra 1.0.8 server running on EC2 and wanted to secure it. I read securing the entire server with firewall is one of the options. What are the other cheaper options to secure a development server ? regards, Ramesh
Re: Way to force the propagation of a schema change?
After adding a column family you must code your app to wait until schema versions became 1 in the cluster to add a new row. This is something that must be solved in the application layer. In pycassa (python api) the system manager code already do this. I don't know about others clients. 2012/3/2 Tharindu Mathew mcclou...@gmail.com Hi everyone, I add a column family dynamically and notice that when describe schema versions return 2 values. Then it quickly changes back to 1. Sometimes this stays at 2 and does not change. Then I cannot insert values to the created column family, as it causes an exception. Is there a way to force the schema propagation through the thrift API (not the CLI)? Thanks in advance. -- Regards, Tharindu blog: http://mackiemathew.com/ -- Carlo Pires 62 8209-1444 TIM 62 3251-1383 Skype: carlopires
Re: What is the best way to secure remote Cassandra (dev) server ?
On 03/02/2012 08:00 AM, Sasha Dolgy wrote: Put it on a non-routable internal network. 192.168.x.x 172.16.x.x Etc... On Mar 2, 2012 1:56 PM, investtr investt...@gmail.com mailto:investt...@gmail.com wrote: We have our development Cassandra 1.0.8 server running on EC2 and wanted to secure it. I read securing the entire server with firewall is one of the options. What are the other cheaper options to secure a development server ? regards, Ramesh Thanks Sasha. That is a good option. regards, Ramesh
Cassandra Triggers Capability published out to GitHub
FYI -- http://brianoneill.blogspot.com/2012/03/cassandra-triggers-for-indexing-and.html https://github.com/hmsonline/cassandra-triggers Feedback welcome. Contribution and involvement is even better. ;) -brian -- Brian ONeill Lead Architect, Health Market Science (http://healthmarketscience.com) mobile:215.588.6024 blog: http://weblogs.java.net/blog/boneill42/ blog: http://brianoneill.blogspot.com/
Test Data creation in Cassandra
What is the best way to create millions of test data in Cassandra ? I would like to have some script where I first insert say 100 rows in a CF. Then reinsert the same data on 'server side' with new unique key. That will make it 200 rows. Then continue the exercise a few times till I get lot of records. I don't care if the column names and values are identical between the different rows. Just a lot of records generated for a few seed records. The rows are very fat. So I don't want to use any client side scripting that would push individual or batched rows to cassandra. Thanks for any tips.
Re: avoid log spam with 0 HH rows delivered
https://issues.apache.org/jira/browse/CASSANDRA-3955 On Fri, Mar 2, 2012 at 1:53 AM, Radim Kolar h...@sendmail.cz wrote: Can be something made to remove these empty delivery attempts from log? Its just tombstoned row. [default@system] list HintsColumnFamily; Using default limit of 100 --- RowKey: 00 1 Row Returned. Elapsed time: 234 msec(s). INFO [HintedHandoff:1] 2012-03-02 05:44:32,359 HintedHandOffManager.java (line 296) Started hinted handoff for token: 0 with IP: /64.6.104.18 INFO [HintedHandoff:1] 2012-03-02 05:44:32,362 HintedHandOffManager.java (line 373) Finished hinted handoff of 0 rows to endpoint /64.6.104.18 INFO [HintedHandoff:1] 2012-03-02 05:54:31,641 HintedHandOffManager.java (line 296) Started hinted handoff for token: 0 with IP: /64.6.104.18 INFO [HintedHandoff:1] 2012-03-02 05:54:31,644 HintedHandOffManager.java (line 373) Finished hinted handoff of 0 rows to endpoint /64.6.104.18 INFO [HintedHandoff:1] 2012-03-02 06:04:25,253 HintedHandOffManager.java (line 296) Started hinted handoff for token: 0 with IP: /64.6.104.18 INFO [HintedHandoff:1] 2012-03-02 06:04:25,255 HintedHandOffManager.java (line 373) Finished hinted handoff of 0 rows to endpoint /64.6.104.18 INFO [HintedHandoff:1] 2012-03-02 06:14:57,984 HintedHandOffManager.java (line 296) Started hinted handoff for token: 0 with IP: /64.6.104.18 INFO [HintedHandoff:1] 2012-03-02 06:14:58,013 HintedHandOffManager.java (line 373) Finished hinted handoff of 0 rows to endpoint /64.6.104.18 INFO [HintedHandoff:1] 2012-03-02 06:24:15,206 HintedHandOffManager.java (line 296) Started hinted handoff for token: 0 with IP: /64.6.104.18 INFO [HintedHandoff:1] 2012-03-02 06:24:15,208 HintedHandOffManager.java (line 373) Finished hinted handoff of 0 rows to endpoint /64.6.104.18 INFO [HintedHandoff:1] 2012-03-02 06:34:43,108 HintedHandOffManager.java (line 296) Started hinted handoff for token: 0 with IP: /64.6.104.18 INFO [HintedHandoff:1] 2012-03-02 06:34:43,110 HintedHandOffManager.java (line 373) Finished hinted handoff of 0 rows to endpoint /64.6.104.18
