-
Notifications
You must be signed in to change notification settings - Fork 350
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
predixy crashed with SIGABRT #35
Comments
Can you reproduce this bug everytime? which commands be used in testing? Is custom commands be used? what's means of the custom command redis_lock_lock.acquire/redis_lock.release/cl.throttle |
Not every time. (then we couldn't use predixy if predixy crashed every time...)
I'll check and post commands used in test later. |
We used the same approach too! and we too switched to 1.0.5-pre. but I'm wondering if the spot in which predixy crashes is same as #29 , regardless of supporting custom command. I'm going to use predixy latency monitor to get the exact command list that our service uses. |
They modified the predixy source code then result in predixy crash, are you modified predixy source code too? |
No. we don't. (for now, at least when we got SIGABRT error) but we get the same results, that makes me embarrassed. |
Can you help to upload the predixy.log? |
Sorry for late reply. We applied latest patch of branch 'issue32', and ran the load test multiple times. So far so good! I'm looking at the logs continuously, no SIGABRT, no hang with SIGSEGV (11). Many thanks! |
We're using predixy 1.0.5-pre on Ubuntu 16.04, which is built from latest master.
configuration attached.
predixy.conf.txt
I think we're experiencing basically same issue as #29.
We're performing load testing on redis cluster, A predixy instance is processing 10K requests per sec. predixy doesn't crash so often, but when it crashes, it is critical.
The text was updated successfully, but these errors were encountered: