Skip to content
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

Open
golangav opened this issue Mar 26, 2022 · 3 comments
Open

error: Local: Queue full, msg: couldn't produce massage in kafka #90

golangav opened this issue Mar 26, 2022 · 3 comments

Comments

@golangav
Copy link

golangav commented Mar 26, 2022

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

image

image

@palmerabollo palmerabollo changed the title error: Loacl: Queue full couldn't produce massage in kafka error: Local: Queue full, msg: couldn't produce massage in kafka Mar 27, 2022
@palmerabollo
Copy link
Member

Hi @golangav, thanks for opening this issue. What do you recommend us to do when the queue is full?

@golangav
Copy link
Author

golangav commented Mar 29, 2022

Hello, can you add a queue

or batch.size linger.ms

@golangav
Copy link
Author

golangav commented Mar 29, 2022

@palmerabollo Hello, can you add a queue
confluentinc/confluent-kafka-dotnet#703
image

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants