Skip to content
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

Got core dump while running a benchmark test #988

Closed
cnbscience opened this issue Feb 12, 2016 · 4 comments
Closed

Got core dump while running a benchmark test #988

cnbscience opened this issue Feb 12, 2016 · 4 comments

Comments

@cnbscience
Copy link

terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc.

Received signal 6 (Aborted)
#0 /lib64/libc.so.6(gsignal+0x35) [0x7eff70feb625]
#1 /lib64/libc.so.6(abort+0x175) [0x7eff70fece05]
#2 /usr/lib64/libstdc++.so.6(_ZN9__gnu_cxx27__verbose_terminate_handlerEv+0x12d) [0x7eff718a5a5d]
#3 /usr/lib64/libstdc++.so.6(+0xbcbe6) [0x7eff718a3be6]
#4 /usr/lib64/libstdc++.so.6(+0xbcc13) [0x7eff718a3c13]
#5 /usr/lib64/libstdc++.so.6(+0xbcd0e) [0x7eff718a3d0e]
#6 /usr/lib64/libstdc++.so.6(_Znwm+0x7d) [0x7eff718a40fd]
#7 ./db_bench() [0x5620a2]
#8 ./db_bench() [0x58b785]
#9 ./db_bench() [0x565faa]
#10 ./db_bench() [0x548416]
#11 ./db_bench() [0x47dcb7]
#12 ./db_bench() [0x4ea630]
#13 ./db_bench() [0x4ed23d]
#14 ./db_bench() [0x4b6b10]
#15 ./db_bench() [0x4b735a]
#16 ./db_bench() [0x4cc578]
#17 ./db_bench() [0x5950ae]
#18 /lib64/libpthread.so.0(+0x79d1) [0x7eff725429d1]
#19 /lib64/libc.so.6(clone+0x6d) [0x7eff710a18fd]

could anyone let me know what exactly is happening.

Regards

@ajkr
Copy link
Contributor

ajkr commented Feb 12, 2016

Which benchmark are you running? Could you please provide the db_bench options you're using, if any?

@cnbscience
Copy link
Author

I have used bulk random fill for this purpose and had modified the script a little to store 5 billion hashes with key size 10 and value size 20.

@mdcallag
Copy link
Contributor

std::bad_alloc is raised when malloc fails and that happens when RocksDB is configured to use more memory than your server provides -- http://www.cplusplus.com/reference/new/bad_alloc/

You probably need to change the configuration.

@gfosco
Copy link
Contributor

gfosco commented Jan 10, 2018

Closing this via automation due to lack of activity. If discussion is still needed here, please re-open or create a new/updated issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants