Hello Shrikar,
We are still facing read latency issue, here is the histogram
http://pastebin.com/yEvMuHYh
On Sat, Mar 29, 2014 at 8:11 AM, Apoorva Gaurav
apoorva.gau...@myntra.comwrote:
Hello Shrikar,
Yes primary key is (studentID, subjectID). I had dropped the test table,
recreating
,
Shrikar
On Wed, Apr 2, 2014 at 11:30 PM, Apoorva Gaurav apoorva.gau...@myntra.com
wrote:
Hello Shrikar,
We are still facing read latency issue, here is the histogram
http://pastebin.com/yEvMuHYh
On Sat, Mar 29, 2014 at 8:11 AM, Apoorva Gaurav
apoorva.gau...@myntra.com wrote:
Hello
level?
~Shrikar
On Thu, Apr 3, 2014 at 12:20 AM, Apoorva Gaurav apoorva.gau...@myntra.com
wrote:
At the client side we are getting a latency of ~350ms, we are using
datastax driver 2.0.0 and have kept the fetch size as 500. And these are
coming while reading rows having ~200 columns
the results
:)
On Wed, Apr 2, 2014 at 8:45 AM, Apoorva Gaurav
apoorva.gau...@myntra.comwrote:
Thanks Sourabh,
I've modelled my table as studentID int, subjectID int, marks int,
PRIMARY KEY(studentID, subjectID) as primarily I'll be querying using
studentID and sometime using studentID
Hello All,
We have a schema which can be modelled as *(studentID int, subjectID int,
marks int, PRIMARY KEY(studentID, subjectID)*. There can be ~1M studentIDs
and for each studentID there can be ~10K subjectIDs. The queries can be
using studentID and studentID-subjectID We have a 3 node (each
Hello All,
We had a 4 node cassandra 2.0.4 cluster ( lets call them host1, host2,
host3 and host4), out of which we've removed one node (host4) using
nodetool removenode command. Now using nodetool status or nodetool ring we
no longer see host4. It's also not appearing in Datastax opscenter. But
Hello Sylvian,
Queried system.peers on three live nodes and host4 is appearing on two of
these.
On Tue, Apr 1, 2014 at 5:06 PM, Sylvain Lebresne sylv...@datastax.comwrote:
On Tue, Apr 1, 2014 at 12:50 PM, Apoorva Gaurav apoorva.gau...@myntra.com
wrote:
Hello All,
We had a 4 node
Did that and I actually see a significant reduction in write latency.
On Tue, Apr 1, 2014 at 5:35 PM, Sylvain Lebresne sylv...@datastax.comwrote:
On Tue, Apr 1, 2014 at 1:49 PM, Apoorva Gaurav
apoorva.gau...@myntra.comwrote:
Hello Sylvian,
Queried system.peers on three live nodes
of).
--
Sylvain
On Tue, Apr 1, 2014 at 2:44 PM, Apoorva Gaurav
apoorva.gau...@myntra.comwrote:
Did that and I actually see a significant reduction in write latency.
On Tue, Apr 1, 2014 at 5:35 PM, Sylvain Lebresne sylv...@datastax.comwrote:
On Tue, Apr 1, 2014 at 1:49 PM, Apoorva
than fetch size in studentID int, subjectID int, marks
int, PRIMARY KEY(studentID, subjectID)
On Wed, Apr 2, 2014 at 2:20 AM, Robert Coli rc...@eventbrite.com wrote:
On Mon, Mar 31, 2014 at 9:13 PM, Apoorva Gaurav
apoorva.gau...@myntra.com wrote:
Thanks Robert, Is there a workaround
Thanks Robert, Is there a workaround, as in our test setups we keep
dropping and recreating tables.
On Mon, Mar 31, 2014 at 11:51 PM, Robert Coli rc...@eventbrite.com wrote:
On Fri, Mar 28, 2014 at 7:41 PM, Apoorva Gaurav apoorva.gau...@myntra.com
wrote:
Yes primary key is (studentID
querying large number
of rows efficient.
http://www.datastax.com/dev/blog/client-side-improvements-in-cassandra-2-0
On Sat, Mar 29, 2014 at 8:11 AM, Apoorva Gaurav apoorva.gau...@myntra.com
wrote:
Hello Shrikar,
Yes primary key is (studentID, subjectID). I had dropped the test table
Hello All,
We've a schema which can be modeled as (studentID, subjectID, marks) where
combination of studentID and subjectID is unique. Number of studentID can
go up to 100 million and for each studentID we can have up to 10k
subjectIDs.
We are using apahce cassandra 2.0.4 and datastax java
table marks_table(studentId int, subjectId int, marks int, PRIMARY
KEY(studentId,subjectId));
Also could you give the cfhistogram stats?
nodetool cfhistograms your keyspace marks_table;
Thanks,
Shrikar
On Fri, Mar 28, 2014 at 3:53 PM, Apoorva Gaurav apoorva.gau...@myntra.com
wrote
14 matches
Mail list logo
