Troubleshooting #

This page tries to help you with what to do if you have issues with Redict. Part of the Redict project is helping people that are experiencing problems because we don’t like to leave people alone with their issues.

  • If you have latency problems with Redict, that in some way appears to be idle for some time, read our Redis latency troubleshooting guide.
  • Redis stable releases are usually very reliable, however in the rare event you are experiencing crashes the developers can help a lot more if you provide debugging information. Please read our Debugging Redis guide.
  • We have a long history of users experiencing crashes with Redis that actually turned out to be servers with broken RAM. Please test your RAM using redict-server –test-memory in case Redis is not stable in your system. Redis built-in memory test is fast and reasonably reliable, but if you can you should reboot your server and use memtest86.

For every other problem please drop a message in our Chat. See Community resources for details.

  • Ubuntu 10.04 and 10.10 contain bugs that can cause performance issues. The default kernels shipped with these distributions are not recommended. Bugs were reported as having affected EC2 instances, but some users also cited server impact.
  • Certain versions of the Xen hypervisor report poor fork() performance. See the latency page for more information.

Redict logo courtesy of @janWilejan, CC-BY-SA-4.0. Download SVG ⤑

Portions of this website courtesy of Salvatore Sanfilippo, CC-BY-SA-4.0.