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

Plugin incompatible with new fluentd release 0.14 #70

Closed
comtef opened this issue Jun 1, 2016 · 2 comments · Fixed by #72
Closed

Plugin incompatible with new fluentd release 0.14 #70

comtef opened this issue Jun 1, 2016 · 2 comments · Fixed by #72
Labels
Milestone

Comments

@comtef
Copy link

comtef commented Jun 1, 2016

The kinesis plugin is not compatible with the new release of fluentd (0.14).
Startup fail with the following message :

2016-06-01 09:37:04 +0000 [error]: unexpected error error="uninitialized constant Fluent::DetachMultiProcessMixin"
2016-06-01 09:37:04 +0000 [error]: /opt/td-agent/embedded/lib/ruby/gems/2.1.0/gems/fluent-plugin-kinesis-1.0.1/lib/fluent/plugin/kinesis_helper.rb:23:in `module:KinesisHelper'

The use of detach_process in an output plugin was pointed as a bad practice from fluentd developper tagomoris and will be deprecated in future release.

output plugins using detach_process looks very curious from viewpoint of fluentd core developer...

@riywo riywo added the bug label Jun 1, 2016
@riywo
Copy link
Contributor

riywo commented Jun 1, 2016

Hi @comtef ,

Thank you for reporting. I think some require statements has been got rid of in v0.14 so that this plugin is facing the missing of module. I'll fix it soon.

To stop using detach_process in this plugin, we need more investigation to get high throughput with a thread model in MRI. This is a separate topic for this issue. I'll open an issue.

@riywo
Copy link
Contributor

riywo commented Jun 13, 2016

Hi @comtef ,

I've released v1.1.0 to fix this issue and more. Please check it out and let me know if anything.
https://rubygems.org/gems/fluent-plugin-kinesis/versions/1.1.0

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

Successfully merging a pull request may close this issue.

2 participants