-
Notifications
You must be signed in to change notification settings - Fork 137
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
error: Local: Queue full, msg: couldn't produce massage in kafka #90
Comments
Hi @golangav, thanks for opening this issue. What do you recommend us to do when the queue is full? |
Hello, can you add a queue or batch.size linger.ms |
@palmerabollo Hello, can you add a queue queue. buffering. Max.kbytes to specify how much information can be cached. The default is 400MB, and the maximum can be increased to 2097151kb, that is, about 2GB (because the cache is not 100% of your messages, but also has key or other meta information, so the actual available can not reach 2GB). queue. buffering. Max.messages to specify how many messages can be cached. The default is 100000. That's enough. Errors such as buffererror: Local: queue full can be avoided by changing these two properties and optimizing the process control of the program. |
Stupid question, the above 2 recommendations should be adjusted on the adapter side or Kafka cluster side? |
Hello
This error is also an error report when the network is not available, which is easy to mislead.
Restart and return to normal
Can you distinguish it
confluentinc/confluent-kafka-go#346
The text was updated successfully, but these errors were encountered: