Probably those without suffix were created by previous Cassandra version
(somewhere in 2.x series)
Best regards, Vladimir Yudovin,
Winguzone - Hosted Cloud Cassandra on Azure and SoftLayer.
Launch your cluster in minutes.
On Sun, 09 Oct 2016 01:58:07 -0400 Jason Kania
The biggest problem with pread was the issue of over reading (reading 64k
where 4k would suffice), which was significantly improved in 2.2 iirc. I
don't think the penalty is very significant anymore, and if you are
experiencing time to safe point issues it's very likely a worthwhile switch
to flip.
Potentially relevant reading
https://issues.apache.org/jira/browse/CASSANDRA-10249
From: Benedict Elliott Smith
Reply-To: "user@cassandra.apache.org"
Date: Sunday, October 9, 2016 at 2:39 AM
To: "user@cassandra.apache.org"
Subject: Re: JVM safepoints, mmap, and slow disks
The biggest
Hi,
Even with memory mapped IO the kernel is going to do read ahead. It
seems like if the issue is reading to much from the device it isn't
going to help to use memory mapped files or smaller buffered reads.
Maybe helps by some percentage, but it's still going to read quite a
bit extra.
Arie
Well, you seem to be assuming:
1) read ahead is done unconditionally, with an equal claim to disk resources
2) read ahead is actually enabled (tuning recommendations are that it be
disabled, or at least drastically reduced, to my knowledge)
3) read ahead happens synchronously (even if you burn som
Hello,
I have running a sstableloader job.
Unfortunately some of nodes restarted since beginnig streaming.
I see streaming stop for those nodes.
Can I restart those streaming somehow?
Or if I restart sstableloader job, will it start from beginning?
Regards,
Osman
This e-mail message, including
It'll start over from the beginning.
On Sunday, October 9, 2016, Osman YOZGATLIOGLU <
osman.yozgatlio...@krontech.com> wrote:
> Hello,
>
> I have running a sstableloader job.
> Unfortunately some of nodes restarted since beginnig streaming.
> I see streaming stop for those nodes.
> Can I restart