Re: Exception thrown on repair after change was made to existing cassandra type

Thank you Alexander, The restart did the trick. Thank you, Robert Robert Sicoie On Tue, Dec 6, 2016 at 5:00 PM, Alexander Dejanovski wrote: > Hi Robert, > > Some of your nodes did not accept the new schema, or several alter > commands were issued on different nodes

Exception thrown on repair after change was made to existing cassandra type

Hi guys, I am running cassandra 3.0.5 on 5 nodes, NetworkTopologyStrategy, factor 2 I had to add new 3 columns to an existing type and I've done it through cqlsh. After one of the alter commands I've got *OperationTimedOut: errors={'x.x.x.x': 'Request timed out while waiting for schema

Re: Exception thrown on repair after change was made to existing cassandra type

Any suggestion is more than welcome. The fact is that the same alter commands worked in two other environments and now fails in the thirds environment. No downtime is accepted. Thanks, Robert Robert Sicoie On Tue, Dec 6, 2016 at 4:11 PM, Robert Sicoie wrote: > Hi

node decommission throttled

I'm trying to decommission one C* node from 6 nodes cluster and see that outbound network traffic on this node doesn't go over ~30Mb/s. Looks like it is throttled somewhere in C* Should stream_throughput_outbound_megabits_per_sec limit apply on "decommissioning streams" as well? >From my

Re: Exception thrown on repair after change was made to existing cassandra type

Hi Robert, Some of your nodes did not accept the new schema, or several alter commands were issued on different nodes concurrently. Repair cannot fix that as it works on data, not on schema. To fix your issue, roll restart your whole cluster and all nodes should get back in agreement on the

RE: Cassandra 2.x Stability

On the cassandra web itself. http://cassandra.apache.org/download/ From: James Rothering [mailto:jrother...@codojo.me] Sent: 07 December 2016 00:50 To: user@cassandra.apache.org Subject: Re: Cassandra 2.x Stability Is there an official notification of these EOL dates somewhere? On Wed, Nov 30,

Re: Cassandra 2.x Stability

Is there an official notification of these EOL dates somewhere? On Wed, Nov 30, 2016 at 4:38 AM, kurt Greaves wrote: > Latest release in 2.2. 2.1 is borderline EOL and from my experience 2.2 is > quite stable and has some handy bugfixes that didn't actually make it into >

RPM builds in-tree now

I know there are some RPM users out there, so I've committed a redhat/ directory and tested build/install/service on CentOS 7 from the resulting packages on the following branches: - cassandra-2.1 - cassandra-2.2 - cassandra-3.0 - cassandra-3.11 - cassandra-3.X - trunk I need to work on getting

Re: Ring show high load average when restarting a node.

Hi, The feature of speculative execution in Cassandra 2.0 helps in this case. You can get further explanation on below link. http://www.datastax.com/dev/blog/rapid-read-protection-in-cassandra-2-0-2 Thanks! On Tue, Dec 6, 2016 at 10:13 AM, Sungju Hong wrote: > Hello, > >

[Announcement] BigGraphite

Hello Cassandra users On behalf of Corentin Chary from Criteo, I'm happy to announce the release of BigGraphite, an OSS Graphite plugin dedicated for time series based on Apache Cassandra. BigGraphite is leveraging latest features as SASI index & Back Pressure. More info here:

Re: [Announcement] BigGraphite

This looks super cool On Tue, 6 Dec 2016 at 01:49 DuyHai Doan wrote: > Hello Cassandra users > > On behalf of Corentin Chary from Criteo, I'm happy to announce the release > of BigGraphite, an OSS Graphite plugin dedicated for time series based on > Apache Cassandra.