-
Notifications
You must be signed in to change notification settings - Fork 97
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
tokumx crash #1219
Comments
its very sad to see tokumx just crashed, it should handle the error instead of crashing. i ran into same issue and in my case i found out the reason i.e. my code tries to build an index on very large collection and after 98% it just crashed with same error exception: i tried to increase ulimit , upgrade hardware. but its looks like its the issue with tokumx even in my updated version. Fri Mar 27 05:01:28.561 Crash reason: i am using 2.0.1. you can see my issue logged here: #1228 |
we bit the bullet and moved back to mongodb (and upgraded to 3.0 with On 06/04/2015 04:14 PM, Adeel Ahmad wrote:
|
Thank you very much, i am also trying to test my DB with Mongo 3.0. i think now is the time to move again from TokuMX to MongoDB :-) |
Hello Adeel, cacheSize: 5368709120 which smaller that cachetable: size current: 5486165566 your virtual memory is set to ~7G
Thank you very much, i am also trying to test my DB with Mongo 3.0. i think now is the time to move again from TokuMX to MongoDB :-)— |
Thank you for replying, i spend last 18 hour and i can reproduce it anywhere and i know its the bug and tokumx should handle that instead of crashing. i can not provide you the data farm but i can help you in providing stats. i upgraded my hardware , even changed my OS to CentoS 6.6. below are my test result. i tried with 30 GB Physical Memory and with 150GB SWAP and it failed, so i guess its not the virtual memory issue. 1st Test Run for index building Hard Ware: Amazon Linux , R3.xlarge(4vCPU with 32GB RAM + 150GB SWAP) Disk Space more than 200GB free Space. 2nd Test Run for index building CentOS 6.6, R3.xlarge(4vCPU with 32GB RAM + 150GB SWAP) Disk: More than 500 GB Free Space. |
@ aerrami: i tested it further its a bug in tokumx. now i use Server with 120GB RAM and 500GB HDD. i didn't specify cache size which means that line is comment in tokumx.conf. i tried to build the index and it crashed. what i found is:
i am expecting more from tokumx, crashing is not the option, it should throw some kind of error instead of crashing. |
We have a replica set with 2 replicas + arbiter; this morning one of the replicas started crashing (it's gotten to the point where it's immediately after start-up, but initially it did work for a few minutes between crashes)
incoming crash logs:
first crash, the machine was primary at the moment:
last crash, after I saw the notifications, found it dead and attempted to start it:
The text was updated successfully, but these errors were encountered: