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 <e...@nextbigsound.com> wrote: > 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 <aa...@thelastpickle.com> > wrote: > > 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 wrote: > > > >> You should start with scrub. > >> > >> On Mon, Sep 19, 2011 at 1:04 PM, Eric Czech <e...@nextbigsound.com> > 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 > >>> currently running version 0.8.4 but this is data that was carried over > >>> from much earlier versions. Should I try to run scrub or are there > >>> any other general guidelines for dealing with this sort of error? > >>> > >>> Thanks everyone! > >>> > >> > >> > >> > >> -- > >> Jonathan Ellis > >> Project Chair, Apache Cassandra > >> co-founder of DataStax, the source for professional Cassandra support > >> http://www.datastax.com > > > > >
