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

Unexpected behavior by fluentd-collector from one Elastic search index to kafka #81

Open
phanitejak opened this issue Oct 11, 2022 · 0 comments

Comments

@phanitejak
Copy link

We have implemented fluentd-kafka plugin to collect information from kafka topics and post the formatted data to Elastic search database.
However, recently, after upgrading from kafka-6.0.0-1090 to kafka-7.0.0-1250 (these RPMs are part of our organization's internal packaging), we have observed that the custom micro-service alarm-collector build using fluentd-kafka plugin 0.16.0 version, was able to process many indexes but one of them - alarmhistoryindex - keeps failing to connect to kafka.
But after restarting the micro-service pods, the connection was successful.
We request a possible explanation for this.
This feels some bug to us - if true, may we know the possible fix please?
Thank you all in advance.

Here is the log from our microservice...
alarm-collector-belk-fluentd-statefulset-0(1).log

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

1 participant