Re: Proprietary Replication Strategies: Cassandra Driver Support

FYI there is an everywhere strategy waiting to be accepted: https://issues.apache.org/jira/browse/CASSANDRA-12629 On Sat, 8 Oct 2016 at 10:56 Vladimir Yudovin wrote: Well, it can be useful in some scenarios - e.g. temporary tables on nearest or the same node. Best

Re: Bootstrapping data from Cassandra 2.2.5 datacenter to 3.0.8 datacenter fails because of streaming errors

You can't stream between major versions. Don't tear down your first data center, upgrade it instead. On Mon, Oct 10, 2016 at 4:35 PM Abhishek Verma wrote: > Hi Cassandra users, > > We are trying to upgrade our Cassandra version from 2.2.5 to 3.0.8 > (running on Mesos, but that's

Bootstrapping data from Cassandra 2.2.5 datacenter to 3.0.8 datacenter fails because of streaming errors

Hi Cassandra users, We are trying to upgrade our Cassandra version from 2.2.5 to 3.0.8 (running on Mesos, but that's besides the point). We have two datacenters, so in order to preserve our data, we are trying to upgrade one datacenter at a time. Initially both DCs (dc1 and dc2) are running

[RELEASE] Apache Cassandra 2.1.16 released

The Cassandra team is pleased to announce the release of Apache Cassandra version 2.1.16. Apache Cassandra is a fully distributed database. It is the right choice when you need scalability and high availability without compromising performance. http://cassandra.apache.org/ Downloads of source

CASSANDRA-12758 in 2.1? (was: Re: [VOTE] Release Apache Cassandra 2.1.16)

I also agree this is minor and did not intend to re-roll. My question is whether CASSANDRA-12758 should go to to the 'cassandra-2.1' branch and be tagged with fixver of '2.1.x' in JIRA? Is this minor improvement satisfactory for a the critical-only nature of the 2.1 branch and go into the next

Re: [VOTE] Release Apache Cassandra 2.1.16

> It's too minor for a re-roll, and safe enough to just apply yourself if you > want it. Agreed. > > On Mon, Oct 10, 2016 at 2:44 PM, Michael Shuler > wrote: > >> Nate, do think CASSANDRA-12758 should go to 2.1.x? >> >> -- >> Michael >> >> On 10/10/2016 02:26 PM, Nate

Re: [VOTE] Release Apache Cassandra 2.1.16

It's too minor for a re-roll, and safe enough to just apply yourself if you want it. On Mon, Oct 10, 2016 at 2:44 PM, Michael Shuler wrote: > Nate, do think CASSANDRA-12758 should go to 2.1.x? > > -- > Michael > > On 10/10/2016 02:26 PM, Nate McCall wrote: > > Hi Romain,

Re: [VOTE] Release Apache Cassandra 2.1.16

Nate, do think CASSANDRA-12758 should go to 2.1.x? -- Michael On 10/10/2016 02:26 PM, Nate McCall wrote: > Hi Romain, > I appreciate you speaking up about this, but I stuck with my +1 in > order to get 2.1.16 with the NTR fix out since I have seen > CASSANDRA-11363 with every recent client

Re: [VOTE] Release Apache Cassandra 2.1.16

Hi Romain, I appreciate you speaking up about this, but I stuck with my +1 in order to get 2.1.16 with the NTR fix out since I have seen CASSANDRA-11363 with every recent client installation. Also, running the patch in production produced results satisfactory enough to me to preclude the need for

Failing tests 2016-10-10

trunk: === testall: 2 failures org.apache.cassandra.service.RemoveTest .testLocalHostId CASSANDRA-9541. org.apache.cassandra.db.KeyspaceTest .testLimitSSTables New failure. Needs a jira ticket.

[VOTE RESULT] Release Apache Cassandra 2.1.16

Including myself, I count 8 +1 votes and no -1 votes for this release. I'll get the release published! -- Kind regards, Michael On 10/05/2016 06:09 PM, Michael Shuler wrote: > I propose the following artifacts for release as 2.1.16. > > sha1: 87034cd05964e64c6c925597279865a40a8c152f > Git: >