Re: write timeout

Bug report posted @ https://issues.apache.org/jira/browse/CASSANDRA-9023 On Mon, Mar 23, 2015 at 11:21 PM, Robert Coli wrote: > On Mon, Mar 23, 2015 at 7:27 AM, Brian Tarbox > wrote: > > > My group is seeing the same thing and also can not figure out why its > > happening. > > > > On Mon, Mar 2

Re: 3.0 and the Cassandra release process

Hey all, I had a hallway conversation with some folks here last week, and they expressed some concerns with this proposal. I will not attempt to summarize their arguments as I don't believe I could do them ample justice, but I strongly encouraged those individuals to speak up and be heard on this

Re: write timeout

On Mon, Mar 23, 2015 at 7:27 AM, Brian Tarbox wrote: > My group is seeing the same thing and also can not figure out why its > happening. > > On Mon, Mar 23, 2015 at 8:36 AM, Anishek Agarwal > wrote: > >> Forgot to mention I am using Cassandra 2.0.13 >> > This seems like a rather significant bug

Re: 3.0 and the Cassandra release process

+1 -- Ranger Tsao 2015-03-20 22:57 GMT+08:00 Ryan McGuire : > I'm taking notes from the infrastructure doc and wrote down some action > items for my team: > > https://gist.github.com/EnigmaCurry/d53eccb55f5d0986c976 > > > -- > > [image: datastax_logo.png]

Re: write timeout

Forgot to mention I am using Cassandra 2.0.13 On Mon, Mar 23, 2015 at 5:59 PM, Anishek Agarwal wrote: > Hello, > > I am using a single node server class machine with 16 CPUs with 32GB RAM > with a single drive attached to it. > > my table structure is as below > > CREATE TABLE t1(id bigint, ts

write timeout

Hello, I am using a single node server class machine with 16 CPUs with 32GB RAM with a single drive attached to it. my table structure is as below CREATE TABLE t1(id bigint, ts timestamp, cat1 set, cat2 set, lat float, lon float, a bigint, primary key (id, ts)); I am trying to insert 300 entri