3 ms·

The only time I used Kafka, it was involuntarily (included for the sake of fashion in some complicated IBM product, where it hid among WebSphere, DB2 and other

The only time I used Kafka, it was involuntarily (included for the sake of fashion in some complicated IBM product, where it hid among WebSphere, DB2 and other bigger elephants) and it ran my server out of disk space because due to a bug ridiculously massive temporary files weren't erased. Needless to say, I wasn't impressed: just one more hazard to worry about.

kitd 5y ago
due to a bug Data retention time is Kafka config 101. Are you sure it was a bug?
- geodel 5y ago
  Considering how half-assed Kafka is in general, that it needs all clients code changes when Kafka servers are upgraded. It is very likely that user hit Kafka bug.
  - kitd 5y ago
    Citation needed. New server versions are protocol backwards compatible so I'm not sure what you're referring to. Ofc, if you downgraded a server without changing the client, that may cause problems, but tbh that's hardly Kafka's fault.
  - deleted 5y ago
    [deleted]
  - EdwardDiego 5y ago
    > it needs all clients code changes when Kafka servers are upgraded It absolutely doesn't. Message formats predating Kafka 0.11 are only just being deprecated as of Kafka 3.0, and won't be dropped until Kafka 4.0. Now, if you want to use new shiny features (like cooperative sticky assignors to minimise consumer group stop the world rebalance pauses), then yes, you might need to upgrade clients. But otherwise, you can still happily use 0.8 clients with your upgraded brokers. https://cwiki.apache.org/confluence/display/KAFKA/KIP-724%3A+Drop+support+for+message+formats+v0+and+v1 https://cwiki.apache.org/confluence/display/KAFKA/KIP-724%3A...
EdwardDiego 5y ago
What was the bug, out of curiosity?