Read below for tips. If you still need help, you can:
- Ask your question in The Karafka official Slack channel
- Open a GitHub issue. (Don't be afraid to open an issue, even if it's not a Karafka bug. An issue is just a conversation, not an accusation!)
- Check our FAQ and the Pro FAQ
You should not email any Karafka committer privately.
Please respect our time and efforts by sticking to one of the options above.
Please consider buying the Pro subscription for additional priority Pro support and extra features.
When you encounter issues with Karafka, there are several things you can do:
- Feel free to open a Github issue
- Feel free to ask on our Slack channel
- Use our integration specs and example apps to create a reproduction code that you can then share with us.
Remember that Karafka uses the
info log level by default. If you assign it a logger with
debug, debug will be used.
Here are a few guidelines that you should follow when trying to create a reproduction script:
- Use as few non-default gems as possible to eliminate issues emerging from other libraries.
- Try setting the
1- this will simplify the processing flow.
- Use a single topic with a single partition (so Karafka does not create extensive concurrent jobs).
- If the issue is related to Active Job or Ruby on Rails, try using the latest stable release.
- Check the Versions Lifecycle and EOL page to make sure that your Ruby and Ruby on Rails (if used) combination is supported.
- Try disabling all Karafka components that may be irrelevant to the issue, like extensive listeners and other hooks.
- You can use
TTINsignal to print a backtrace of all the Karafka threads if Karafka appears to be hanging or dead. For this to work, the
LoggerListenerneeds to be enabled.