Could you look at the cassandra log? This is probably due to an
error on the server side.
On Fri, Nov 18, 2011 at 4:20 AM, Maxim Potekhin potek...@bnl.gov wrote:
Should I file a ticket? I consistently see this behavior after a mass
delete.
On 11/17/2011 12:46 PM, Maxim Potekhin wrote:
On Wed, Nov 16, 2011 at 2:51 PM, Jone Lura jone.l...@ecc.no wrote:
Hi,
I am trying to find out how to use CQL to be able to use cassandra-jdbc in my
application, and I have some questions.
I have tried to find the answers int the documentation of Cassandra Query
Language (CQL) v2.0, but I
It's pleasing to see interest out there. We'll try to do some cleanups
and push it to github this weekend.
You can follow us on twitter: @elasticinbox
Regards,
Rustam.
On Fri Nov 18 01:42:01 2011, Andrey V. Panov wrote:
I'm also interesting in your project and will be glad to follow you on
Thanks!!
--
Dotan, @jondot http://twitter.com/jondot
On Fri, Nov 18, 2011 at 2:48 PM, Rustam Aliyev rus...@code.az wrote:
It's pleasing to see interest out there. We'll try to do some cleanups and
push it to github this weekend.
You can follow us on twitter: @elasticinbox
Regards,
On Fri, Nov 18, 2011 at 1:53 AM, Todd Burruss bburr...@expedia.com wrote:
I'm using cassandra 1.0. Been doing some testing on using cass's cache.
When I turn it on (using the CLI) I see ParNew jump from 3-4ms to
200-300ms. This really screws with response times, which jump from ~25-30ms
to
I they are not limited to repeating values but the Datastax docs[1] on
secondary indexes certainly seem to indicate they would be a poor fit for this
case (high read load, many unique values).
[1] http://www.datastax.com/docs/1.0/ddl/indexes
Dan
From: Maciej Miklas
On Fri, Nov 18, 2011 at 6:39 AM, Sylvain Lebresne sylv...@datastax.com wrote:
On Fri, Nov 18, 2011 at 1:53 AM, Todd Burruss bburr...@expedia.com wrote:
I'm using cassandra 1.0. Been doing some testing on using cass's cache.
When I turn it on (using the CLI) I see ParNew jump from 3-4ms to
On Fri, Nov 18, 2011 at 4:23 PM, Mohit Anchlia mohitanch...@gmail.com wrote:
On Fri, Nov 18, 2011 at 6:39 AM, Sylvain Lebresne sylv...@datastax.com
wrote:
On Fri, Nov 18, 2011 at 1:53 AM, Todd Burruss bburr...@expedia.com wrote:
I'm using cassandra 1.0. Been doing some testing on using
Thanks for the info Brandon. I'll do the upgrade once 0.8.8 is released.
On Wed, Nov 16, 2011 at 2:43 PM, Brandon Williams dri...@gmail.com wrote:
On Mon, Nov 14, 2011 at 2:49 PM, Giannis Neokleous
gian...@generalsentiment.com wrote:
Hello everyone,
We're using the bulk loader to load
The Cassandra team is pleased to announce the release of Apache Cassandra
version 1.0.3.
Cassandra is a highly scalable second-generation distributed database,
bringing together Dynamo's fully distributed design and Bigtable's
ColumnFamily-based data model. You can read more here:
I messed up the link to the changelog in my previous, sorry about that.
The correct link is http://goo.gl/u0MMV.
--
Sylvain
On Fri, Nov 18, 2011 at 5:21 PM, Sylvain Lebresne sylv...@datastax.com wrote:
The Cassandra team is pleased to announce the release of Apache Cassandra
version 1.0.3.
On Fri, Nov 18, 2011 at 7:47 AM, Sylvain Lebresne sylv...@datastax.com wrote:
On Fri, Nov 18, 2011 at 4:23 PM, Mohit Anchlia mohitanch...@gmail.com wrote:
On Fri, Nov 18, 2011 at 6:39 AM, Sylvain Lebresne sylv...@datastax.com
wrote:
On Fri, Nov 18, 2011 at 1:53 AM, Todd Burruss
On Fri, Nov 18, 2011 at 6:31 PM, Mohit Anchlia mohitanch...@gmail.com wrote:
On Fri, Nov 18, 2011 at 7:47 AM, Sylvain Lebresne sylv...@datastax.com
wrote:
On Fri, Nov 18, 2011 at 4:23 PM, Mohit Anchlia mohitanch...@gmail.com
wrote:
On Fri, Nov 18, 2011 at 6:39 AM, Sylvain Lebresne
On Fri, Nov 18, 2011 at 9:42 AM, Sylvain Lebresne sylv...@datastax.com wrote:
On Fri, Nov 18, 2011 at 6:31 PM, Mohit Anchlia mohitanch...@gmail.com wrote:
On Fri, Nov 18, 2011 at 7:47 AM, Sylvain Lebresne sylv...@datastax.com
wrote:
On Fri, Nov 18, 2011 at 4:23 PM, Mohit Anchlia
Hello,
Sorry,It is right that you say so.
Checking data is very difficult.
But, If the writing of data is returned correctly,
one or more data is written certainly on Cassandra.
Therefore,
If you didn't set read_repair_chance lowered,
I think that it is the right way that you count on Read
My understanding is that support for super columns will remain within the
thrift API for the foreseeable future (perhaps indefinitely?) but under the
covers, super column families will get transitioned to regular column
families with composite column names (
We should be able to:
- find all time records from all users within a given project (with
optionally a certain date range)
- find total time per task
- find all time records from user X (with optionally a certain date range)
As I understand from your answer this would require atleast 3 (or 5?)
On Thu, Nov 17, 2011 at 1:08 PM, Maciej Miklas mac.mik...@googlemail.comwrote:
A) Skinny rows
- row key contains login name - this is the main search criteria
- login data is replicated - each possible login is stored as single row
which contains all user data - 10 logins for
single
Ok, I figured something like that. Switching to
ConcurrentLinkedHashCacheProvider I see it is a lot better, but still
instead of the 25-30ms response times I enjoyed with no caching, I'm
seeing 500ms at 100% hit rate on the cache. No old gen pressure at all,
just ParNew crazy.
More info on my
On Fri, Nov 18, 2011 at 1:46 PM, Todd Burruss bburr...@expedia.com wrote:
Ok, I figured something like that. Switching to
ConcurrentLinkedHashCacheProvider I see it is a lot better, but still
instead of the 25-30ms response times I enjoyed with no caching, I'm
seeing 500ms at 100% hit rate on
This is the setup:
Cassandra 0.8.6
3 nodes
Keyspace: NetworkTopologyStrategy, 1DC, RF=2
1 node goes down and we cannot read from the ring.
My expectation is that LOCAL_QUORUM dictates that it will return a record once
a majority (N/2 +1) of replicas reports back.
2/2 + 1 = 2
I originally
Keyspace: NetworkTopologyStrategy, 1DC, RF=2
1 node goes down and we cannot read from the ring.
My expectation is that LOCAL_QUORUM dictates that it will return a record
once a majority (N/2 +1) of replicas reports back.
Yes, the RF and the number of hosts that are up within the replica
My expectation is that LOCAL_QUORUM dictates that it will return a record
once a majority (N/2 +1) of replicas reports back.
Yes, the RF and the number of hosts that are up within the replica set
of the row in question is what matters.
And note that this is for fundamental reasons. A node
After re-reading my post, what I meant to say is that I switched from
Serializing cache provider to ConcurrentLinkedHash cache provider and then
saw better performance, but still far worse than no caching at all:
- no caching at all : 25-30ms
- with Serializing provider : 1300+ms
- with
No i/o? No sstable counts going up in cfhistograms?
Is the heap so full you're experiencing GC pressure that way?
On Fri, Nov 18, 2011 at 3:46 PM, Todd Burruss bburr...@expedia.com wrote:
Ok, I figured something like that. Switching to
ConcurrentLinkedHashCacheProvider I see it is a lot
2011/11/18 Todd Burruss bburr...@expedia.com:
After re-reading my post, what I meant to say is that I switched from
Serializing cache provider to ConcurrentLinkedHash cache provider and then
saw better performance, but still far worse than no caching at all:
- no caching at all : 25-30ms
-
Running on cassandra 0.8.(6|7), I have issued two moves in the same cluster
at the same time, on two different nodes. There are no writes being issued
to the cluster.
I saw a mailing post mentioning doing moves one node at a time.
Did I just trash my cluster ?
Thanks
Re: Cassandra 0.8.7
Where will I find what the first part of the Cassandra-cli prompt means?
I've turned on SimpleAuthenticator/SimpleAuthority.
I connect via the Cassandra-cli
[default@unknown] connect localhost/9160 dilbert 'nomoovertime'
... ;
Connected to: Test Cluster on
No it's not just the cli tool, our app has the same issue coming back with read
issues.
Sent from my iPhone
On 18/11/2011, at 15:04, Peter Schuller peter.schul...@infidyne.com wrote:
Keyspace: NetworkTopologyStrategy, 1DC, RF=2
1 node goes down and we cannot read from the ring.
My
On Fri, Nov 18, 2011 at 4:23 PM, Anthony Ikeda
anthony.ikeda@gmail.com wrote:
This is the setup:
Cassandra 0.8.6
3 nodes
Keyspace: NetworkTopologyStrategy, 1DC, RF=2
1 node goes down and we cannot read from the ring.
My expectation is that LOCAL_QUORUM dictates that it will return a
No it's not just the cli tool, our app has the same issue coming back with
read issues.
You are supposed to not be able to read it. But you should be getting
a proper error, not an empty result.
--
/ Peter Schuller (@scode, http://worldmodscode.wordpress.com)
On Fri, Nov 18, 2011 at 1:59 PM, RobinUs2 ro...@us2.nl wrote:
We should be able to:
- find all time records from all users within a given project (with
optionally a certain date range)
You'll need a timeline per project. I would use one row per day, week, or
month, depending on the size.
32 matches
Mail list logo