Re: Replicating Data Between Separate Data Centres

I did consider doubling down and replicating both Kafka and Cassandra to the secondary DC. It seemed a bit complicated (term used relatively), and I didn't want to think about the unlikely scenario of Cassandra writes getting across before the Kafka ones. Inserting everything in Kafka into

Re: PrepareStatement BUG

Yes, I discard using "SELECT *" statement and that fix the problem. 2015-10-02 1:50 GMT+08:00 Alexandre Dutra : > Hello Joseph, > > CASSANDRA-7910 is fixed for Cassandra 2.1.3, but it still needs a fix > driver-side: JAVA-420

Re: memory usage problem of Metadata.tokenMap.tokenToHost

That's great. Thanks, Alex! 2015-10-02 0:36 GMT+08:00 Alexandre Dutra : > I confirm that the optional schema metadata feature (JAVA-828 > ) has been merged > upstream and is included in driver 3.0.0-alpha3 and will

Re: Replicating Data Between Separate Data Centres

Hi Jeff, You're dead on with that article. That is a very good explanation of the problem I'm facing. You're also right that, fascinating though that research is, letting it anywhere near my production data is not something I'd think about. Basically, I want EACH_QUORUM, but I'm not willing to

Re: Replicating Data Between Separate Data Centres

Emit a message to a new kafka topic once the first write is persisted into cassandra with LOCAL_QUORUM (gives you low latency), then consume off of that topic to get higher-latency-but-causally-correct writes to subsequent (disconnected) DR DC. From: Philip Persad Reply-To:

Better setup to start using in production on one server

Hello, I’m ready to start deploying the service that uses Cassandra as a database. I have one dedicated server with the following config: Intel Xeon E3 1225v2 4cores 4 threads processor, 3 x 120Gb SSD drive, 32Gb RAM. What is the best option to start using cassandra on production on this

Re: Better setup to start using in production on one server

> On 14 Dec 2015, at 21:40, Robert Coli wrote: > > On Mon, Dec 14, 2015 at 3:46 AM, Vladimir Prudnikov > wrote: > [I want to run Cassandra on a single server] > > I struggle to imagine the purpose of doing this.

Re: Better setup to start using in production on one server

On 12/14/2015 05:46 AM, Vladimir Prudnikov wrote: > I have one dedicated server This might be OK as a dev/test set up, but defeats the purpose of a distributed database for production use. -- Kind regards, Michael

Re: Fatal Issues after upgrading to Cassandra 3.0.0/3.0.1 and using latest java driver 3.0.0-beta1

On Mon, Dec 14, 2015 at 1:17 PM, Carlos A wrote: > I had logged a bug on JIRA as I think it might be a better way of > reporting this: https://issues.apache.org/jira/browse/CASSANDRA-10861 > Thanks for keeping the list looped in on the JIRA URL. =Rob

Re: Issues on upgrading from 2.2.3 to 3.0

https://issues.apache.org/jira/browse/CASSANDRA-10745 GPFS seems like it SHOULD be easier to package and distribute in most use cases… From: "sean_r_dur...@homedepot.com" Reply-To: "user@cassandra.apache.org" Date: Monday, December 14, 2015 at 11:56 AM To: "user@cassandra.apache.org"

RE: Issues on upgrading from 2.2.3 to 3.0

Is there a JIRA for the discussion of dropping PropertyFileSnitch? That is all that we use, and it is much easier to package and distribute than GossipingPropertyFileSnitch. I would vote against dropping the more useful PropertyFileSnitch. Sean Durity – Lead Cassandra Admin From: Paulo Motta

Replicating Data Between Separate Data Centres

Hi, I'm currently looking at Cassandra in the context of Disaster Recovery. I have 2 Data Centres, one is the Primary and the other acts as a Standby. There is a Cassandra cluster in each Data Centre. For the time being I'm running Cassandra 2.0.9. Unfortunately, due to the nature of my data,

Data loss bug in upgrade to 3.0

We have discovered a critical bug for upgrade in the 3.0.0, 3.0.1 and 3.1 release. This bug, https://issues.apache.org/jira/browse/CASSANDRA-10822, only affects upgrades from a 2.x version (to any of the currently released 3.x version) and might cause data loss. As such, we strongly advice waiting

Fatal Issues after upgrading to Cassandra 3.0.0/3.0.1 and using latest java driver 3.0.0-beta1

Hello all, We had upgrade to Cassandra 3.0.0 and later to 3.0.1. That went well. System seems stable. However we have a Spring API that uses Cassandra and has a connection pool using the com.datastax.cassandra driver. We had to upgrade that as well as it would not work with the latest driver to

Re: Replicating Data Between Separate Data Centres

Could you define what you mean by Casual Consistency and explain why you think you won't have that when using LOCAL_QUORUM? I ask because LOCAL_QUORUM and multiple data centers are the way many of us handle DR, so I'd like to understand why it doesn't work for you. I'm afraid I don't understand

Re: Better setup to start using in production on one server

On Mon, Dec 14, 2015 at 3:46 AM, Vladimir Prudnikov wrote: > [I want to run Cassandra on a single server] I struggle to imagine the purpose of doing this. You are going to sign yourself up for repeated painful changes of RF, as well as downtimes. As Michael says, you

Re: Fatal Issues after upgrading to Cassandra 3.0.0/3.0.1 and using latest java driver 3.0.0-beta1

On Mon, Dec 14, 2015 at 12:52 PM, Carlos A wrote: > We had upgrade to Cassandra 3.0.0 and later to 3.0.1. That went well. > System seems stable. > https://www.eventbrite.com/engineering/what-version-of-cassandra-should-i-run/ Running cutting edge versions of server and

Re: Fatal Issues after upgrading to Cassandra 3.0.0/3.0.1 and using latest java driver 3.0.0-beta1

Rob, Indeed you are correct, thanks for that. But It is not production it is DEV server. We need some features of Cassandra 3 hence the need to upgrade it. It actually also helps the others by providing feedback. On Mon, Dec 14, 2015 at 1:59 PM, Robert Coli wrote: > On

RE: Issues on upgrading from 2.2.3 to 3.0

Thank you! I made my comments in the JIRA. Sean Durity – Lead Cassandra Admin From: Jeff Jirsa [mailto:jeff.ji...@crowdstrike.com] Sent: Monday, December 14, 2015 3:25 PM To: user@cassandra.apache.org Subject: Re: Issues on upgrading from 2.2.3 to 3.0

Re: Fatal Issues after upgrading to Cassandra 3.0.0/3.0.1 and using latest java driver 3.0.0-beta1

On Mon, Dec 14, 2015 at 1:02 PM, Carlos A wrote: > Indeed you are correct, thanks for that. But It is not production it is > DEV server. We need some features of Cassandra 3 hence the need to upgrade > it. > Sure, consider my response "response to a nick I don't recognize

Re: Fatal Issues after upgrading to Cassandra 3.0.0/3.0.1 and using latest java driver 3.0.0-beta1

I had logged a bug on JIRA as I think it might be a better way of reporting this: https://issues.apache.org/jira/browse/CASSANDRA-10861 On Mon, Dec 14, 2015 at 1:52 PM, Carlos A wrote: > Hello all, > > We had upgrade to Cassandra 3.0.0 and later to 3.0.1. That went well. >

Re: Replicating Data Between Separate Data Centres

Hi Jim, Thanks for taking the time to answer. By Causal Consistency, what I mean is that I need strict ordering of all related events which might have a causal relationship. For example (albeit slightly contrived), if we are looking at recording an event stream, it is very important that the

Re: Replicating Data Between Separate Data Centres

There is research into causal consistency and cassandra ( http://da-data.blogspot.com/2013/02/caring-about-causality-now-in-cassandra.html , for example), though you’ll note that it uses a fork ( https://github.com/wlloyd/eiger ) which is unlikely something you’d ever want to consider in

unsubscribe