I watched the logs pretty carefully as scrub ran and it definitely
skipped/deleted some problematic rows so perhaps that would explain the tmp
sstables but I'm not sure. Either way, they weren't still being written to
and after casting my restart spell, everything is totally fine and the tmp
table
tmp files are temporary in nature, if they fail to live up to their name then
they are against nature.
If they are still been written to then something is happening, either a flush
or a compaction. Check nodetool compactstats
They may indicate errors during the scrub (or compact), check the lo
Scrub seems to have worked. Thanks again!
Will a major compaction delete the "tmp" sstables genereated though? Scrub
seems to have generated a lot of them and they're taking up an unnerving
amount of disk space.
On Mon, Sep 19, 2011 at 5:34 PM, Eric Czech wrote:
> Ok then I'll shutdown the se
Ok then I'll shutdown the server, change the access mode, restart, and
run scrub (and then change the access mode back).
Thanks for the pointers and I'll let you know how it goes one way or the other.
On Tue, Sep 20, 2011 at 12:29 AM, aaron morton wrote:
> I've also found it useful to disable me
I've also found it useful to disable memmapped file access until the scrub is
complete by adding this to the yaml
disk_access_mode: standard
Cheers
-
Aaron Morton
Freelance Cassandra Developer
@aaronmorton
http://www.thelastpickle.com
On 20/09/2011, at 6:55 AM, Jonathan Ellis w
You should start with scrub.
On Mon, Sep 19, 2011 at 1:04 PM, Eric Czech wrote:
> I'm getting a lot of errors that look something like "java.io.IOError:
> java.io.IOException: mmap segment underflow; remaining is 348268797
> but 892417075 requested" on one node in a 10 node cluster. I'm
> curren
My guess would be CASSANDRA-2675. Upgrade to the latest version in
your release series, if you haven't.
On Sat, Aug 27, 2011 at 9:53 AM, Chad Johnson wrote:
> Hi,
>
> We periodically get the following exception in our Cassandra cluster. What I
> mean by periodically is once or twice a week. It
Try the patch at https://issues.apache.org/jira/browse/CASSANDRA-2417
On Mon, Apr 4, 2011 at 11:18 AM, Or Yanay wrote:
> Hi All,
>
>
>
> I have upgraded from 0.7.0 to 0.7.4, and while running scrub I get the
> following exception quite a lot:
>
>
>
> java.lang.AssertionError: mmap segment underfl
I am considering treating the node as a dead node, delete it's data files and
bootstrap from scratch.
Is that a reasonable approach? Is there a way for me to identify the bad file/s
and remove it/them?
From: Or Yanay [mailto:o...@peer39.com]
Sent: Monday, April 04, 2011 7:19 PM
To: user@cassandr
