I am running Cassandra 1.2.12 on CentOS 5.10.
Was running 1.1.15 previously without any issues as well.
-Arindam
From: Donald Smith [mailto:donald.sm...@audiencescience.com]
Sent: Tuesday, February 25, 2014 3:40 PM
To: user@cassandra.apache.org
Subject: RE: Supported Cassandra version for CentOS
As an update - finally got the node to join the ring.
Restarting all the nodes in the cluster, followed by a clean bootstrap of the
node that was stuck did the trick.
-Arindam
From: Arindam Barua [mailto:aba...@247-inc.com]
Sent: Monday, February 24, 2014 5:04 PM
To: user@cassandra.apache.org
Did not help finally.
So I enabled logging at debug level.
The log files tell me that the node being added is communicating with the other
nodes (that are seed nodes). Still nothing seems to be returning to that node.
The log files on the other nodes are detecting the shadow request, but no othe
Hi
I have two separated clusters consist of 4 nodes. One cluster is running on
1.2.12 and the other one on 2.0.5. I loaded data from first cluster
(1.2.12) to the second one (2.0.5) by copying snapshots between
corresponding nodes. I removed commitlogs, started second cluster and run
nodetool upgr
You may need to bit shift if that is the case
Sent from my iPhone
> On Feb 26, 2014, at 2:53 AM, Ben Hood <0x6e6...@gmail.com> wrote:
>
> Hey Colin,
>
>> On Tue, Feb 25, 2014 at 10:26 PM, Colin Blower wrote:
>> It looks like you are trying to implement the Decimal type. You might want
>> to s
go uses 'zig-zag' encoding, perhaps that is the difference?
On Wed, Feb 26, 2014 at 6:52 AM, Peter Lin wrote:
>
> You may need to bit shift if that is the case
>
> Sent from my iPhone
>
> > On Feb 26, 2014, at 2:53 AM, Ben Hood <0x6e6...@gmail.com> wrote:
> >
> > Hey Colin,
> >
> >> On Tue, Feb
And one last clarification. Where I said "stored procedure" earlier, I
meant "prepared statement". Sorry for the confusion. Too much typing while
tired.
-Tupshin
On Tue, Feb 25, 2014 at 10:36 PM, Tupshin Harper wrote:
> I failed to address the matter of not knowing the families in advance.
>
>
Hi,
is the DataStax "Java Driver for Apache Cassandra" (
https://github.com/datastax/java-driver) the official/recommended Java
Client to use for accessing Cassandra from Java?
Does Cassandra itself (i.e. the apache-cassandra-* jars) not contain any
CQL clients?
Thanks!
Short answer : yes
Long anwser: depending on whether you want to access Cassandra using
Thrift of the native CQL3 protocole, different options are available. For
Thrift access, lots of choices (Hector, Astyanax...). For CQL3 right now
the only Java client so far is the one provided by Datastax
"
It is probably ok to have redundant songs in playlists, cassandra is about
denormalization.
Dealing with this issue is going to be hard since the only way to dwal with
this would be scanning through the firsr cf and procing counts then using
that information to delete in the second table. However
Hello,
That's a large variation between the old and new cluster. Are you sure
you pulled over all the SSTables for your keyspaces? Also, did you run a
repair after the data move? Do you have a lot of tombstone data in the old
cluster that was removed during the migration process? Are you usi
Kundera does support CQL3. Work for supporting datastax java driver is
under development.
https://github.com/impetus-opensource/Kundera/issues/385
-Vivek
On Wed, Feb 26, 2014 at 6:34 PM, DuyHai Doan wrote:
> Short answer : yes
>
> Long anwser: depending on whether you want to access Cassandr
Hi,
I'm trying to truncate data on a single node 2.0.5 instance and I'm
noticing that using either TRUNCATE or DROP/CREATE in cqlsh appear to
leave the underlying data behind.
So I was wondering what nodetool operation I should use to completely
nuke the old data, short of dropping the entire key
"I'm noticing that using either TRUNCATE or DROP/CREATE in cqlsh appear to
leave the underlying data behind."
--> What do you mean by "underlying data" ? Are you talking about
"snapshots" ?
If yes, you can wipe them using nodetool clearsnapshots command
On Wed, Feb 26, 2014 at 4:14 PM, Ben Ho
Edward,
Thanks for your insight.
One other thought I had was to store a reference count with the "song". When
the last "playlist" referencing the "song" is deleted the "song" will also be
deleted because the reference count decrements to zero. However, this would
create some nastiness when
On Wed, Feb 26, 2014 at 3:17 PM, DuyHai Doan wrote:
> "I'm noticing that using either TRUNCATE or DROP/CREATE in cqlsh appear to
> leave the underlying data behind."
>
> --> What do you mean by "underlying data" ? Are you talking about
> "snapshots" ?
I was referring to all of the state related
Try truncate foo instead of drop table foo.
About the nodetool clearsnapshot, I've experienced the same behavior also
before. Snapshots cleaning is not immediate
On Wed, Feb 26, 2014 at 4:53 PM, Ben Hood <0x6e6...@gmail.com> wrote:
> On Wed, Feb 26, 2014 at 3:17 PM, DuyHai Doan wrote:
> > "I'm
This is a known issue that is fixed in 2.1beta1.
https://issues.apache.org/jira/browse/CASSANDRA-5202
Until 2.1, we do not recommend relying on the recycling of tables through
drop/create or truncate.
However, on a single node cluster, I suspect that truncate will work far
more reliably than drop
I've played with it using a 2 nodes cluster with auto_snapshot = false in
cassandra.yaml and by deactivating durable write (no commitlog). In my
case, truncating tables allows cleaning up data.
With "nodetool status", I can see the data payload decreasing from Gb to
some kbytes
On Wed, Feb 26,
Right the problem with building a list of counts in a batch is what happens
if song added as you are building the counts.
On Wed, Feb 26, 2014 at 10:32 AM, Green, John M (HP Education) <
john.gr...@hp.com> wrote:
> Edward,
>
>
> Thanks for your insight.
>
>
>
> One other thought I had was to st
On Wed, Feb 26, 2014 at 3:58 PM, DuyHai Doan wrote:
> Try truncate foo instead of drop table foo.
>
> About the nodetool clearsnapshot, I've experienced the same behavior also
> before. Snapshots cleaning is not immediate
I get the same behavior with truncate as well.
On Wed, Feb 26, 2014 at 3:59 PM, Tupshin Harper wrote:
> This is a known issue that is fixed in 2.1beta1.
> https://issues.apache.org/jira/browse/CASSANDRA-5202
>
> Until 2.1, we do not recommend relying on the recycling of tables through
> drop/create or truncate.
>
> However, on a single node cl
Oh, I should add that I was trying to use Cassandra 2.0.X on CentOS and it
needed CentOS 6.2+.
Don
From: Arindam Barua [mailto:aba...@247-inc.com]
Sent: Wednesday, February 26, 2014 1:52 AM
To: user@cassandra.apache.org
Subject: RE: Supported Cassandra version for CentOS 5.5
I am running Cassa
I am running Cassandra 2.0.5 on CentOS 5.9 without issue. Getting
CassandraPDO to work with with PHP... well that's another matter entirely.
I haven't had any luck there at all. I may have to move to Centos 6.x for
that reason alone!
Tim
On Wed, Feb 26, 2014 at 11:55 AM, Donald Smith <
donald.sm
I use truncate between my test cases. Never had a problem with one test
case inheriting the data from the previous one. I¹m using a single node,
so that may be why.
On 2/26/14, 9:27 AM, "Ben Hood" <0x6e6...@gmail.com> wrote:
>On Wed, Feb 26, 2014 at 3:58 PM, DuyHai Doan wrote:
>> Try truncate fo
We're running 2.0.5, recently upgraded from 1.2.14.
Sometimes we are seeing CommitLogs starting to build up.
Is this a potential bug? Or a symptom of something else we can easily
address?
We have
commitlog_sync: periodic
commitlog_sync_period_in_ms:1
commitlog_segment_size_in_m
One way to handle this is that both tables should be de-normalized. Take
this:
SongsAndPlaylists
PlaylistsAndSongs
In this way your client software is charged with keeping data in sync.
When you remove a song from a PlaylistsAndSongs you do a read for that song
in SongsAnyPlaylists. If the numbe
Thanks for your help everyone.
Sylvain, as I understand it, the scenario I described above is not resolved
by CASSANDRA-6561, correct?
(This scenario may not matter to most folks, which is totally fine, I just
want to make sure that I understand.)
Should I instead look into using the Thrift API
Hi all,
Is there any way to use the DataStax Java driver to combine multiple SELECT
statements into a single RPC? I assume not (I could not find anything
about this in the documentation), but I just wanted to check.
Thanks!
Best regards,
Clint
On Wed, Feb 26, 2014 at 12:10 PM, Laing, Michael
wrote:
> go uses 'zig-zag' encoding, perhaps that is the difference?
>
>
> On Wed, Feb 26, 2014 at 6:52 AM, Peter Lin wrote:
>>
>>
>> You may need to bit shift if that is the case
Thanks for everybody's help, I've managed to solve the issue: the
u
On Thu, Feb 27, 2014 at 12:01 AM, Ben Hood <0x6e6...@gmail.com> wrote:
> Hopefully the gocql team can code review this soon and if that's good
> to go, we'll have another CQL driver that can deal with decimals.
BTW thanks and kudos go to Theo and Tyler (of the cql-rb and the
datastax python driver
On Thu, Feb 27, 2014 at 12:05 AM, Ben Hood <0x6e6...@gmail.com> wrote:
> BTW thanks and kudos go to Theo and Tyler (of the cql-rb and the
> datastax python drivers respectively) for publishing encoding test
> cases for the decimal type - that was quite helpful :-)
Sorry, I forgot to mention the in
Hi,
Using Cassandra 2.0.5 we seem to be running into an issue with a
continuous flush of a column family that has no current data ingress.
After disconnecting all clients from the node, the Cassandra instance
seems to continuously flushing a specific column family with this line
appearing all over
33 matches
Mail list logo
