Closed GoogleCodeExporter closed 8 years ago
[deleted comment]
[deleted comment]
[deleted comment]
I turned off mvcc and tried again and it failed much faster (like in 15 minutes
or so). I'm going to try to produce a new trace file that you can look at.
Original comment by stamhan...@gmail.com
on 31 May 2012 at 9:01
Ugh. It failed, but the compressed trace file is about 64MB. This is with trace
level 2. I couldn't get trace level 3 to work properly (in that I wanted it to
roll over after 10GB, and it was rolling over after about 1.8GB... so I was
losing log files when I didn't catch the roll-over in time).
I may have some sensitive data in this dump file (as I did in the last one), so
I don't want to publish it for the world to see. I'll send Thomas a link and
hopefully this time it'll get a little attention (I've gotten no response in
the forums, e-mail, or this bug, and it's a little disheartening since I see
other forum posts do get attention).
Original comment by stamhan...@gmail.com
on 31 May 2012 at 11:20
I'm sorry, but I'm not able to analyze this problem.
I would need a much simpler test case.
Original comment by thomas.t...@gmail.com
on 4 Jun 2012 at 5:25
Argh... I've only seen this problem happen with two different data sets (both
of which were pretty large). Based on the error messages, and the fact that
this is not mvcc related, would it be possible for you to add extra logging in
parts of the code? I'd be very willing to try out h2.jar's to give you more
information. Thanks for taking a look at this.
Original comment by stamhan...@gmail.com
on 4 Jun 2012 at 10:22
Original issue reported on code.google.com by
stamhan...@gmail.com
on 11 May 2012 at 10:49