Re: What can NOT be done during repairs (2.2.x and 3.0.x)

. In which case, the failure is benign. > > Creating new keyspaces or tables will not pose any problems for the repair > sessions in-flight. Cheers! > > On Tue, Nov 7, 2017 at 3:19 AM, Herbert Fischer < > herbert.fisc...@crossengage.io> wrote: > >> Hello, >> >

Re: Stable Cassandra 3.x version for production

version of Cassandra 3.x is stable and production-ready? > > Regards > -- Herbert Fischer | Senior IT Architect CrossEngage GmbH | Bertha-Benz Straße 5 | 10557 Berlin E-Mail: herbert.fisc...@crossengage.io Web: www.crossengage.io Amtsgericht Berlin-Charlottenburg | HRB 169537 B G

What can NOT be done during repairs (2.2.x and 3.0.x)

Hello, I know from DS docs that we must not change the cluster topology while there are repairs going on, and vice-versa. Is there anything else that cannot be done while there are repairs happening? Are schema-changes fine? Is creating new keyspaces or tables fine? best, Herbert

Cassandra 2.2.4: FailureDetector: "Ignoring interval time of ..."

Hi, I'm using Cassandra 2.2.4 and I we are getting ~4k messages per hour, per node. It doesn't look good to me. Is it normal? If not, any idea on what might be wrong? Thanks Herbert

Re: Node stuck when joining a Cassandra 2.2.0 cluster

was in an unknown state, I could not find it through the cfId from the error messages. best On 5 January 2016 at 22:33, Robert Coli <rc...@eventbrite.com> wrote: > On Tue, Jan 5, 2016 at 3:01 AM, Herbert Fischer < > herbert.fisc...@crossengage.io> wrote: > >> We run a small Cass

Node stuck when joining a Cassandra 2.2.0 cluster

We run a small Cassandra 2.2.0 cluster, with 5 nodes, on bare-metal servers and we are going to replace those nodes with other nodes. I planned to add all the new nodes first, one-by-one, and later remove the old ones, one-by-one. Although the first new node gets stuck when joining the cluster. I

Re: New node stuck on joining Cluster (Cassandra 2.2.0)

Please ignore. On 5 January 2016 at 11:48, Herbert Fischer <herbert.fisc...@crossengage.io> wrote: > We run a small Cassandra 2.2.0 cluster, with 5 nodes, on barebone servers > and we are going to replace those nodes with other nodes. I planned to add > all the new nodes fi

New node stuck on joining Cluster (Cassandra 2.2.0)

We run a small Cassandra 2.2.0 cluster, with 5 nodes, on barebone servers and we are going to replace those nodes with other nodes. I planned to add all the new nodes first, one-by-one, and later remove the old ones, one-by-one. Although the first new node gets stuck when joining the cluster. I

cassandra-stress and "op rate"

even worse, with the setup with just one HDD. So my question is, what does it mean the "op rate" in the Results of cassandra-stress tool? Thanks in advance! -- Herbert Fischer