Closed BrandonHicks-msr closed 3 weeks ago
update fully and reload both front and backend (web and consumers). After that, does it persist?
this has nothing to do with AJ jobs. It's related to karafka jobs and this looks like a partial upgrade. Once front and backend is upgraded this should go away.
I was able to reproduce it:
My initial recommendation resolves the problem, and this behavior is consistent with the docs. Closing.
If you attempt to deploy the updated Web UI before the Karafka consumer processes, you may encounter errors. This could range from 500 Internal Server errors to incorrect or missing offset-related data displays.
Expected behavior
While using v0.9.1 it works as expected, karafka is able to consume and produce topic messages as expected. It is not used as an ActiveJob replacement (we have sidekiq for this). We are using karafka as a message bus to pass topic messages between applications
Actual behavior
When upgrading to
v0.10
this seems to no longer be the case, with0.10
when accessing the karafka-web uikey not found :jobs
is immediately thrown.Your setup details
The karafka config is setup and very basic: