Hello Shrikar,
Yes primary key is (studentID, subjectID). I had dropped the test table,
recreating and populating it post which will share the cfhistogram. In such
case is there any practical limit on the rows I should fetch, for e.g.
should I do
select * form marks_table where studentID =
I'm writing a Java client to a Cassandra db.
One of the main primary keys is a timeuuid.
I plan to do INSERTs using now() and have Cassandra generate the value of
the timeuuid.
After the INSERT, I need the Cassandra-generated timeuuid value. Is there
an easy wsay to get it, without having to re-
Hi Apoorva,
I assume this is the table with studentId and subjectId as primary keys
and not other like like marks in that.
create table marks_table(studentId int, subjectId int, marks int, PRIMARY
KEY(studentId,subjectId));
Also could you give the cfhistogram stats?
nodetool cfhistograms mark
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 driv
Another thing to keep in mind is that if you are hitting the issue I
described, waiting 60 seconds will not absolutely solve your problem, it
will only make it less likely to occur. If a memtable has been partially
flushed at the 60 second mark you will end up with the same corrupt sstable.
On F
+1 for tablesnap
On Fri, Mar 28, 2014 at 4:28 PM, Jonathan Haddad wrote:
> I will +1 the recommendation on using tablesnap over EBS. S3 is at least
> predictable.
>
> Additionally, from a practical standpoint, you may want to back up your
> sstables somewhere. If you use S3, it's easy to pull
As I tried to say, EBS snapshots require much care or you get corruption
such as you have encountered.
Does Cassandra quiesce the file system after a snapshot using fsfreeze or
xfs_freeze? Somehow I doubt it...
On Fri, Mar 28, 2014 at 4:17 PM, Jonathan Haddad wrote:
> I have a nagging memory o
I will +1 the recommendation on using tablesnap over EBS. S3 is at least
predictable.
Additionally, from a practical standpoint, you may want to back up your
sstables somewhere. If you use S3, it's easy to pull just the new tables
out via aws-cli tools (s3 sync), to your remote, non-aws server,
I have a nagging memory of reading about issues with virtualization and not
actually having durable versions of your data even after an fsync (within
the VM). Googling around lead me to this post:
http://petercai.com/virtualization-is-bad-for-database-integrity/
It's possible you're hitting this
Hi,
In my cassandra logs, I see a lot of "StatusLogger" output lines. I'm
trying to understand why this is logged, and how to interpret the output.
Maybe someone can point me to some documentation on this particular logging
aspect?
I would like to know what is triggering the StatusLogger.java to
Robert,
That is what I thought as well. But apparently something is happening. The
only way I can get away with doing this is adding a sleep 60 right after the
nodetool snapshot is executed. I can reproduce this 100% of the time by not
issuing a sleep after nodetool snapshot.
This is the er
On Fri, Mar 28, 2014 at 12:21 PM, Russ Lavoie wrote:
> Thank you for your quick response.
>
> Is there a way to tell when a snapshot is completely done?
>
IIRC, the JMX call blocks until the snapshot completes. It should be done
when nodetool returns.
=Rob
In your step 4, be sure you create a consistent EBS snapshot. You may have
pieces of your sstables that have not actually been flushed all the way to
EBS.
See https://github.com/alestic/ec2-consistent-snapshot
ml
On Fri, Mar 28, 2014 at 3:21 PM, Russ Lavoie wrote:
> Thank you for your quick r
Thank you for your quick response.
Is there a way to tell when a snapshot is completely done?
On Friday, March 28, 2014 1:30 PM, Robert Coli wrote:
On Fri, Mar 28, 2014 at 11:15 AM, Russ Lavoie wrote:
We are using cassandra 1.2.10 (With JNA installed) on ubuntu 12.04.3 and are
running our
We are using version 1.2.4 and it is difficult to shutdown the embedded
version. But you don't have to. Just check in each test setup method if
embedded Cassandra is already running and start it if necessary. Than
create keyspaces/tables in setup methods and drop them in teardown methods.
For us th
DevCenter 1.0 is the Java driver 1.0 to connect to your cluster. This
version of the driver doesn't support C* 2.0 with its latest CQL version.
Now you'll still be able to connect to a C* 2.0 cluster, but your queries
will actually need to be compatible with C* 1.2 (basically none of the
new CQL fe
On Fri, Mar 28, 2014 at 11:15 AM, Russ Lavoie wrote:
> We are using cassandra 1.2.10 (With JNA installed) on ubuntu 12.04.3 and
> are running our instances in Amazon Web Services.
>
> Our cassandra systems data is on an EBS volume
>
Best practice for Cassandra on AWS is to run on ephemeral str
We are using cassandra 1.2.10 (With JNA installed) on ubuntu 12.04.3 and are
running our instances in Amazon Web Services.
What I am trying to do.
Our cassandra systems data is on an EBS volume so we can take snapshots of the
data and create volumes based on those snapshots and restore them whe
On Mar 27, 2014, at 2:16 PM, Michael Dykman wrote:
> Java on linux has *always* been a hassle. Recently, installing ant via
> apt-get on an active ubuntu still want to yank in components of GCJ
> . Back to the tar-ball.
For Ubuntu and Debian, I use the webupd8team packages, these download the
Within DevCenter, I'm getting an error: [feature] is introduced in CQL
3.1.0, you're running CQL 3.0.5.
This doesn't make sense as I'm using the absolute latest version of
Cassandra (2.0.6); connecting through cqlsh shows it's using 3.1.1:
Connected to Test Cluster at localhost:9160.
[cql
In a previous message I described my guess at
what was causing the Datastax Cassandra installation
to require OpenJDK. Using the method I describe below,
I'm now able to install the Datastax Cassandra rpm.
Note that I have no idea (yet) whether Cassandra actually
runs, but at least it installs.
T
All,
I have a question about how to use the EmbeddedCassandraService in unit
tests. I wrote a short collection of unit tests here:
https://github.com/wibiclint/cassandra-java-driver-keyspaces
I'm trying to start up a new EmbeddedCassandraService for each unit test.
I looked at the Cassandra sou
On Fri, Mar 28, 2014 at 11:48 AM, Colin wrote:
> OpenJDK will crash under load whilst running Cassandra.
That's definitely the case for OpenJDK 6, but 7 *should* be okay. However,
most people are running the Oracle JRE (even for 7), so there's not a ton
of evidence out there for OpenJDK 7.
-
OpenJDK will crash under load whilst running Cassandra.
--
Colin
+1 320 221 9531
> On Mar 28, 2014, at 4:11 PM, Jon Forrest wrote:
>
> In a previous message I described my guess at
> what was causing the Datastax Cassandra installation
> to require OpenJDK. Using the method I describe bel
On 3/28/2014 8:20 AM, Michael Shuler wrote:
# rpm -iv cassandra12-1.2.15-1.noarch.rpm
error: Failed dependencies:
java >= 1.6.0 is needed by cassandra12-1.2.15-1.noarch
This properly indicates the missing dependency, which is not installed,
nor provided by a package in your 'rpm -i
Caveat: I am not super strong on rpm-based distros.
On 03/27/2014 06:57 PM, Jon Forrest wrote:
I've done a little more research on this problem.
I'm now convinced that this is a Cassandra problem,
but not the problem I had originally thought.
For example, I downloaded cassandra12-1.2.15-1.noarc
cassandra*.noarch.rpm -> Install Cassandra Only
dsc*.noarch.rpm -> DSC stands for DataStax Community. Install Cassandra +
OpsCenter
Donald Smith a écrit sur 27/03/2014
20:36:57 :
> De : Donald Smith
> A : "'user@cassandra.apache.org'" ,
> Date : 27/03/2014 20:37
> Objet : Question about rpms
Hello,
DS JD
On 03/27/2014 01:06 PM, DE VITO Dominique wrote:
Hi,
-Message d'origine-
De : ssiv...@gmail.com [mailto:ssiv...@gmail.com]
Envoyé : jeudi 27 mars 2014 10:41
À : user@cassandra.apache.org
Objet : Re: Which hector version is suitable for cassandra 2.0.6 ?
On 03/27/2014 12:
28 matches
Mail list logo