-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Floating point exception (core dumped) #13
Comments
[truncated... Moved to Issue #15 ..] Also, is it normal that I get only 200 writes per seconds (this is VirtualBox on regular HDD, not SSD)? Even in bulk mode? |
@slava-vishnyakov -- we've seen the end-of-file bug before, but it was quite rare and we didn't pin it down. It's definitely a different issue, could you open a new one? (Also, thanks for reporting these, it's immensely helpful!) As far as 200 writes per second -- see limitations in https://github.com/rethinkdb/rethinkdb/blob/rethinkdb-next/NOTES -- currently we flush on every write with almost no batching, so we get really poor hdd write performance. This should be resolved in the coming release. |
I should probably mention that the extproc end-of-file error is most likely just the result of a rethinkdb process shutting down improperly. The real error is elsewhere. |
End of file messages is really just java script being overly chatty about On Saturday, November 10, 2012, Tryneus wrote:
|
@slava-vishnyakov: Do you happen to have a core dump from any of these crashes? |
@mlucy: Sadly, no, tried to recraete it today with core dumps enabled, but not luck. |
@mlucy: Sent to your email |
@slava-vishnyakov -- thanks, we'll look at it tomorrow. Really appreciate your patience! |
@slava-vishnyakov -- Do you remember what version of RethinkDB you were running? In particular, did you download it with apt-get or did you build it from source? If the former, what ubuntu distro are you on, or if the latter, do you know the commit hash? (We had a small problem where we weren't properly generating the RethinkDB version string that we put in the binary, so we're having some trouble matching core dumps with symbol files.) Thanks! |
@mlucy It was the apt-get version, released on the day you got to Hacker News.
:) |
@slava-vishnyakov -- Thanks! (And thanks for providing so much info). As far as I can tell the core files don't match any of the symbols we have on launchpad. I talked to @frank-trampe and he said that the very first versions we released on launch day didn't have associated symbol packages. So there's really no good way forward on this unless it crops up again with a version that we have symbols for (i.e. anything not released on the first day). |
@slava-vishnyakov -- thanks so much for the bug report. I'm going to close it as jammed because unfortunately we can't proceed on it unless it's reproduced on latest rethink version. It's totally our fault that the early build didn't have debugging symbols -- unfortunately we didn't line up all the pins for the release. We're also working on #41 to make the report process much more smooth and streamlined. |
Cool database, guys! (And I believe this is the first time I say this in my life, like "cool database!" 👍 )
But it crashed within 15 minutes of playing with it :(
Well, basically I've created a table (tv_shows), added a second server, sharded table into two tables. I've started inserting as much data as possible, then I Ctrl+C'ed the second server. Declared it dead from dashboard. Then I started the second server again. It said to stop the "dead" server. I stopped it. And got this:
Here I start the second machine and slightly later Ctrl+C'ed it.
Still, RethinkDB is awesome!
The text was updated successfully, but these errors were encountered: