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

Where is files location when kafka service down? #181

Open
TiaraH opened this issue Mar 7, 2018 · 2 comments
Open

Where is files location when kafka service down? #181

TiaraH opened this issue Mar 7, 2018 · 2 comments

Comments

@TiaraH
Copy link

TiaraH commented Mar 7, 2018

  • Version:6.2.2
  • Operating System:Linux

That logstash failed to send file to kafka will retry till send success. But when logstash retrying, where are the files? Is there any path queue in logstash or just in memory? If we enable Persistent Queues the files will in the queue or not?

@jordansissel
Copy link
Contributor

jordansissel commented Mar 7, 2018

There are no files specific to the Kafka output. It will retry until successful or until the configured (infinity, by default) retry count is exceeded.

If Kafka is down, Logstash will begin congestion control processes which will stall the pipeline much like a traffic jam with cars on roads -- no cars are lost in a traffic jam, they just get stuck for a while as the transit channel is congested waiting for things to exit the highway (the pipeline, in the case of Logstash).

@TiaraH
Copy link
Author

TiaraH commented Mar 7, 2018

Thanks for your explanation.
And another questions, when kafka failed that logstash will retry until successful, but if there kafka status was normal just get some error like:"[WARN ][org.apache.kafka.clients.NetworkClient] [Producer clientId=producer-1] Error while fetching metadata with correlation id 4984 : {XXXX=UNKNOWN_TOPIC_OR_PARTITION} (kafka truly doesn't have this topic)
", if this error message, where can I move this error file? or it will retry again and again?

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