Re: migrating from 0.6 to 0.8, "java.io.IOError: ... cannot extend file to required size"

2011-08-11 Thread aaron morton
I did a test upgrade first and ran the scrub as part of that process to make sure everything was working. Cheers - Aaron Morton Freelance Cassandra Developer @aaronmorton http://www.thelastpickle.com On 11 Aug 2011, at 21:47, Zhu Han wrote: > > > On Wed, Aug 10, 2011 at 5:24

Re: migrating from 0.6 to 0.8, "java.io.IOError: ... cannot extend file to required size"

2011-08-11 Thread Zhu Han
On Wed, Aug 10, 2011 at 5:24 PM, aaron morton wrote: > I remember seeing this once before upgrading a system from 0.6 to 0.7 on a > Ubuntu EC2 (non data stax build) with EBS disks. I did the same thing and > just assumed it was an EBS or 0.6 bug. From memory after the upgrade that > node had some

Re: migrating from 0.6 to 0.8, "java.io.IOError: ... cannot extend file to required size"

2011-08-10 Thread Ian Douglas
Ubuntu 11.04 On 8/9/2011 6:09 PM, Jonathan Ellis wrote: What OS was this? On Tue, Aug 9, 2011 at 6:32 PM, ian douglas wrote: Thanks to 'driftx' in IRC, adding this line to my cassandra.yaml file seems to have fixed the problem: disk_access_mode: standard On 08/09/2011 04:06 PM, ian doug

Re: migrating from 0.6 to 0.8, "java.io.IOError: ... cannot extend file to required size"

2011-08-10 Thread aaron morton
I remember seeing this once before upgrading a system from 0.6 to 0.7 on a Ubuntu EC2 (non data stax build) with EBS disks. I did the same thing and just assumed it was an EBS or 0.6 bug. From memory after the upgrade that node had some serialisation issues with a few SSTables that I had to even

Re: migrating from 0.6 to 0.8, "java.io.IOError: ... cannot extend file to required size"

2011-08-09 Thread Jonathan Ellis
What OS was this? On Tue, Aug 9, 2011 at 6:32 PM, ian douglas wrote: > Thanks to 'driftx' in IRC, adding this line to my cassandra.yaml file seems > to have fixed the problem: > > disk_access_mode: standard > > > > > On 08/09/2011 04:06 PM, ian douglas wrote: > > updated stack trace after fixing

Re: migrating from 0.6 to 0.8, "java.io.IOError: ... cannot extend file to required size"

2011-08-09 Thread Brandon Williams
On Tue, Aug 9, 2011 at 6:43 PM, ian douglas wrote: > Driftx on IRC: > "follow up on the list saying that disabling mmap fixed it" Which is my code for "I have no idea why this is happening, maybe someone else does" :) -Brandon

Re: migrating from 0.6 to 0.8, "java.io.IOError: ... cannot extend file to required size"

2011-08-09 Thread ian douglas
Driftx on IRC: "follow up on the list saying that disabling mmap fixed it" On 08/09/2011 04:32 PM, ian douglas wrote: Thanks to 'driftx' in IRC, adding this line to my cassandra.yaml file seems to have fixed the problem: disk_access_mode: standard On 08/09/2011 04:06 PM, ian douglas wrot

Re: migrating from 0.6 to 0.8, "java.io.IOError: ... cannot extend file to required size"

2011-08-09 Thread ian douglas
Thanks to 'driftx' in IRC, adding this line to my cassandra.yaml file seems to have fixed the problem: disk_access_mode: standard On 08/09/2011 04:06 PM, ian douglas wrote: updated stack trace after fixing the corrupted GameSave2 tables: INFO 16:05:20,314 Logging initialized INFO 16:05

Re: migrating from 0.6 to 0.8, "java.io.IOError: ... cannot extend file to required size"

2011-08-09 Thread ian douglas
updated stack trace after fixing the corrupted GameSave2 tables: INFO 16:05:20,314 Logging initialized INFO 16:05:20,330 Heap size: 6290407424/6291456000 INFO 16:05:20,336 JNA not found. Native methods will be disabled. INFO 16:05:20,344 Loading settings from file:/data/apache-cassandra-0.

migrating from 0.6 to 0.8, "java.io.IOError: ... cannot extend file to required size"

2011-08-09 Thread ian douglas
Hey all, Thanks to thobbs_ patience in IRC this morning, I got the last of my questions answered about migrating from v0.6 to v0.8. My cassandra.yaml is mostly stock out of the box other than IP's, ports (I'm running v0.6 on my workstation at the same time as v0.8), and our cluster name. I u