Cassandra JBOD has a bunch of issues, so I don't recommend it for production:
1) disks fill up with load (data) unevenly, meaning you can run out on a disk
while some are half-full2) one bad disk can take out the whole node3) instead
of a small failure probability on an LVM/RAID volume, with JBOD
Yeah I meant 2.2. Keep telling myself it was 3.0 for some reason.
On 20 August 2018 at 19:29, Oleksandr Shulgin
wrote:
> On Mon, Aug 13, 2018 at 1:31 PM kurt greaves wrote:
>
>> No flag currently exists. Probably a good idea considering the serious
>> issues with incremental repairs since forev
Is there a JMX property somewhere that I could monitor to see how old the
oldest row cache item is?
I want to see how much churn there is.
Thanks in advance,
John...
Hi Pratchi,
Incremental has been the default since C* 2.2.
You can run a full repair by adding the "--full" flag to your nodetool
command.
Cheers,
Le lun. 20 août 2018 à 19:50, Prachi Rath a écrit :
> Hi Community,
>
> I am currently creating a new cluster with cassandra 3.11.2 ,while
> enab
Hi Community,
I am currently creating a new cluster with cassandra 3.11.2 ,while enabling
repair noticed that incremental repair is true in logfile.
(parallelism: parallel, primary range: true, incremental: true, job
threads: 1, ColumnFamilies: [], dataCenters: [], hosts: [], # of ranges:
20, pu
On Thu, Aug 9, 2018 at 3:46 AM srinivasarao daruna
wrote:
> Hi All,
>
> We have built Cassandra on AWS EC2 instances. Initially when creating
> cluster we have not considered multi-region deployment and we have used AWS
> EC2Snitch.
>
> We have used EBS Volumes to save our data and each of those
On Mon, Aug 13, 2018 at 3:50 PM Vitali Dyachuk wrote:
> Hello,
> I'm going to follow this documentation to add a new datacenter to the C*
> cluster
>
> https://docs.datastax.com/en/cassandra/3.0/cassandra/operations/opsAddDCToCluster.html
>
> The main step is to run nodetool rebuild which will sy
On Mon, Aug 13, 2018 at 1:31 PM kurt greaves wrote:
> No flag currently exists. Probably a good idea considering the serious
> issues with incremental repairs since forever, and the change of defaults
> since 3.0.
>
Hi Kurt,
Did you mean since 2.2 (when incremental became the default one)? Or
Hi Maxim.
Assuming all your update operations are successful and that you only delete
data by TTL in that table, then you shouldn’t have to do repairs on it.
You may also consider to lower the gc_grace_seconds value on that table, but
you should be aware of how this impacts hints and logged bat
