If I correctly understand the answers, the solution to your ordering
question is to use clustering keys.
I'm agree, but I just wanted to warn you about one limitation : the values
of keys can't be updated, unless by using a delete and then an insert.
(In the case of your song "example", putting
Hi Json,
I'm not familiar enough with Cassandra 3, but it might be snapshots.
Snapshots are usually hardlinks to sstable directories.
Try this :
nodetool clearsnapshot
Does it change anything?
--
Nicolas
Le sam. 8 oct. 2016 à 21:26, Jason Kania a écrit :
> Hi
Oki, have fun :)
Le jeu. 22 sept. 2016 à 18:39, Joseph Tech <jaalex.t...@gmail.com> a écrit :
> Thanks!. I was just trying with default cqlsh ; now realize that its only
> ONE CL
>
> On 22 Sep 2016 16:16, "Nicolas Douillet" <nicolas.douil...@gma
2016-09-15 04:17:55.408000 | IP.1 |
>910
>
>
> Enqueuing response to
> /IP.coord [SharedPool-Worker-1] | 2016-09-15 04:17:55.408000 | IP.1 |
> 1051
>
>
> Sending REQUEST_RESPONSE message to /I
Hi Pranay,
I'll try to answer the more precisely as I can.
Note that what I'm going to explain is valid only for reads, write requests
work differently.
I'm assuming you have only one DC.
1. The coordinator gets a list of sorted live replicas. Replicas are
sorted by proximity.
(I'm not
Hi Jaydeep,
Yes, dealing with tombstones in Cassandra is very tricky.
Cassandra keeps tombstones to mark deleted columns and distribute (hinted
handoff, full repair, read repair ...) to the other nodes that missed the
initial remove request. But Cassandra can't afford to keep those tombstones
Hi Erza,
Have you a dead node in your cluster?
Because the coordinator stores a hint about dead replicas in the local
system.hints when a node is dead or didn't respond to a write request.
--
Nicolas
Le sam. 17 sept. 2016 à 00:12, Ezra Stuetzel a
écrit :
> What
Hi,
In my opinion the guaranty provided by Cassandra is :
if your write request in Quorum *succeed*, then the next (after the
write response) read requests in Quorum (that succeed too) will be
consistent
(actually CL.Write + CL.Read > RF)
Of course while you haven't received a valid