Hi,
We are taking daily snapshots for backing up our cassandra data and then
use our backups to restore in a different environment. I would like to
verify that the data is consistent and all the data during the time backup
was taken is actually restored.
Currently I just count the number of rows
I have installed Cassandra on EC2 using Bitnami,
I would like to connect to the Cassandra database using a Java
application on AWS
How do I do that,
Thanks in Advance
-
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.o
Ah cool, I didn't realize reaper did that.
On October 30, 2017 at 1:29:26 PM, Paulo Motta (pauloricard...@gmail.com) wrote:
> This is also the case for full repairs, if I'm not mistaken. Assuming I'm not
> missing something here, that should mean that he shouldn't need to mark
> sstables as unr
> This is also the case for full repairs, if I'm not mistaken. Assuming I'm not
> missing something here, that should mean that he shouldn't need to mark
> sstables as unrepaired?
That's right, but he mentioned that he is using reaper which uses
subrange repair if I'm not mistaken, which doesn't
Yes, should be possible .. u will need to set ur keyspaces accordingly to
create replicas on each cass cluster ..
Thanks
Suraj
On Mon, Oct 30, 2017 at 1:11 PM Rahul Neelakantan wrote:
> Why wouldnt you set it up as a single cluster that spans 2 DCs?
>
> On Mon, Oct 30, 2017 at 4:09 PM, Vincent
Why wouldnt you set it up as a single cluster that spans 2 DCs?
On Mon, Oct 30, 2017 at 4:09 PM, Vincent Lee wrote:
> For high availability in a single DC region, I would like to install one
> Cassandra cluster on one AZ and a second cluster on a different AZ.
> The data between them needs to be
For high availability in a single DC region, I would like to install one
Cassandra cluster on one AZ and a second cluster on a different AZ.
The data between them needs to be synchronized. Is this possible?
Note that this is for a single DC (region).
Currently I am using GossipingPropertyFileSnitc
Hi DuyHai,
Thank you for providing your feedback to our question.
Just to elaborate on the 2 factors that you have provided above.
1) Collection cardinality e.g. the number of elements in the collection. A
maximum of 64,000 elements can be stored.
2) the size of each element in the collection. T
Kurt,
I apreciate your answer but I don't believe CompletedTasks count the
"validation compactions". These are compactions that occur from repair
operations. I am running tests on 10 cluster nodes in the same physical
rack, with Cassandra Stress Tool and I didn't make any Repair commands. The
tabl
Hi,
I run repair, then I see that anticompaction started on all nodes.Does it mean
that all data is already repaired. Actually I increased RF, so can I already
use database?
Thanks.
> Once you run incremental repair, your data is permanently marked as repaired
This is also the case for full repairs, if I'm not mistaken. I'll admit I'm not
as familiar with the quirks of repair in 2.2, but prior to 4.0/CASSANDRA-9143,
any global repair ends with an anticompaction that marks s
I believe (may be wrong) that CompletedTasks counts Validation compactions
while TotalCompactionsCompleted does not. Considering a lot of validation
compactions can be created every repair it might explain the difference.
I'm not sure why they are named that way or work the way they do. There
appea
Hello Bill
First if you don't care about insertion order it's better to use Set rather
than list. List implementation requires read before write for some
operations.
Second, the read performance of the collection itself depends on 2 factors :
1) collection cardinality e.g. the number of elements
13 matches
Mail list logo
