bootstrap failure and strange gossiper state

2015-03-15 Thread Karl Rieb
I am also experiencing issues bootstrapping new nodes in my 2.0.10 Cassandra cluster. The first attempt to bootstrap ALWAYS fails, followed by a second bootstrap attempt that ALWAYS succeeds. The first attempt at bootstrapping fails with: INFO [main] 2015-03-15 02:41:02,550 StorageService.java

Re: Cassandra metrics Graphite

2014-12-17 Thread Karl Rieb
This seemed to be due to a bug with how metric names are converted to file system paths. os.path.join() is used, but the metric path converts into an absolute path (e.g /org/apache/cassandra). This means you end up doing something like: os.path.join('/opt/graphite/storage/whatever',

2.0.10 debian/ubuntu apt release?

2014-09-12 Thread Karl Rieb
Hi, Wondering when 2.0.10 will be available through the datastax apt repository? -Karl

Re: 2.0.10 debian/ubuntu apt release?

2014-09-12 Thread Karl Rieb
Awesome! Thanks! -Karl On Sep 12, 2014, at 5:34 PM, Michael Shuler mich...@pbandjelly.org wrote: On 09/12/2014 01:50 PM, Karl Rieb wrote: Hi, Wondering when 2.0.10 will be available through the datastax apt repository? I'll have 2.0.10 deb/rpm packages in the repos on Monday, barring

Re: DataType protocol ID error for TIMESTAMPs when upgrading from 1.2.11 to 2.0.9

2014-07-21 Thread Karl Rieb
0x6e6...@gmail.com wrote: On Sat, Jul 19, 2014 at 7:35 PM, Karl Rieb karl.r...@gmail.com wrote: Can now be followed at: https://issues.apache.org/jira/browse/CASSANDRA-7576. Nice work! Finally we have a proper solution to this issue, so well done to you. For reference, I consider

Re: DataType protocol ID error for TIMESTAMPs when upgrading from 1.2.11 to 2.0.9

2014-07-19 Thread Karl Rieb
Hood 0x6e6...@gmail.com wrote: On Fri, Jul 18, 2014 at 3:03 PM, Karl Rieb karl.r...@gmail.com wrote: Why is the protocol ID correct for some tables but not others? I have no idea. Why does it work when I do a clean install on a new 2.0.x cluster? I still have no idea. The bug seems

Re: DataType protocol ID error for TIMESTAMPs when upgrading from 1.2.11 to 2.0.9

2014-07-19 Thread Karl Rieb
Will do! On Jul 19, 2014, at 11:22 AM, Robert Stupp sn...@snazy.de wrote: Can you submit a ticket in C* JIRA at issues.apache.org? -- Sent from my iPhone Am 19.07.2014 um 16:45 schrieb Karl Rieb karl.r...@gmail.com: Ben! I think I have an idea of exactly where the bug is! I did

Re: DataType protocol ID error for TIMESTAMPs when upgrading from 1.2.11 to 2.0.9

2014-07-19 Thread Karl Rieb
Can now be followed at: https://issues.apache.org/jira/browse/CASSANDRA-7576 . On Sat, Jul 19, 2014 at 1:03 PM, Karl Rieb karl.r...@gmail.com wrote: Will do! On Jul 19, 2014, at 11:22 AM, Robert Stupp sn...@snazy.de wrote: Can you submit a ticket in C* JIRA at issues.apache.org? -- Sent

Re: DataType protocol ID error for TIMESTAMPs when upgrading from 1.2.11 to 2.0.9

2014-07-18 Thread Karl Rieb
be providing patches to these issues. I will post to the Datastax java driver mailing list and see if they are willing to add a patch. -Karl On Jul 18, 2014, at 3:59 AM, Ben Hood 0x6e6...@gmail.com wrote: On Fri, Jul 18, 2014 at 3:38 AM, Karl Rieb karl.r...@gmail.com wrote: Any

DataType protocol ID error for TIMESTAMPs when upgrading from 1.2.11 to 2.0.9

2014-07-17 Thread Karl Rieb
Hi, I've been testing an in-place upgrade of a 1.2.11 cluster to 2.0.9. The 1.2.11 nodes all have a schema defined through CQL with existing data before I perform the rolling upgrade. While the upgrade is in progress, services are continuing to read and write data to the cluster (strictly using