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

logs getting duplicated with foward as input #1375

Closed
sonirahul opened this issue Jun 10, 2019 · 6 comments
Closed

logs getting duplicated with foward as input #1375

sonirahul opened this issue Jun 10, 2019 · 6 comments
Assignees

Comments

@sonirahul
Copy link

sonirahul commented Jun 10, 2019

I am noticing a weird behavior with fluent bit with input mode as forward. The problem is whenever I send a log to fluent bit on forward mode it gets cumulated sort of like
log0
log0
log1
log0
log1
log2

i have a way to replicate the issue as well.

  1. docker run -p "24224:24224" fluent/fluent-bit:latest /fluent-bit/bin/fluent-bit -i forward -o stdout
  2. docker run -t -i --log-driver=fluentd --log-opt fluentd-address=my-ip:24224 ubuntu
  3. then enter this command multiple times "echo 'hi' >> /dev/null"
  4. you will notice that on the fluent bit logs the log for the command at 3 command are getting repeated the way i have mentioned at top. e.g. log0, log 0, log1, log0, log1, log2

I have seen the same issue when I hit the fluent bit using a java program using the fluentd-logger. I think its a bug. Any help on this would be helpful.

@edsiper edsiper self-assigned this Jun 10, 2019
edsiper added a commit that referenced this issue Jun 10, 2019
Signed-off-by: Eduardo Silva <eduardo@treasure-data.com>
@edsiper
Copy link
Member

edsiper commented Jun 10, 2019

thanks for reporting the issue, It has been fixed on 18fea1a

@sonirahul
Copy link
Author

any expected date when it would be released?

@okdas
Copy link

okdas commented Jun 11, 2019

I thought I was mad when tried to troubleshoot that issue. :)
Thanks for the fix. Seems like a serious enough bug for a quick release?

@sonirahul
Copy link
Author

I thought I was mad when tried to troubleshoot that issue. :)
Thanks for the fix. Seems like a serious enough bug for a quick release?

yupp i also spent 2 plus days over it before raising it.

@sonirahul
Copy link
Author

Anyways any tentative date of release.

edsiper added a commit that referenced this issue Jun 13, 2019
Signed-off-by: Eduardo Silva <eduardo@treasure-data.com>
@edsiper
Copy link
Member

edsiper commented Jun 13, 2019

Today release v1.1.3 is going out with the fix.

Closing as fixed.

@edsiper edsiper closed this as completed Jun 13, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants