Managing multiple plugin versions, staying current.

[Christian Hedegaard]

Just restarted fluentd on one of my testing servers and noticed this:

 

2014-05-16 00:08:17 +0000 [info]: gem 'fluent-mixin-config-placeholders' version '0.2.3'

2014-05-16 00:08:17 +0000 [info]: gem 'fluent-mixin-plaintextformatter' version '0.2.4'

2014-05-16 00:08:17 +0000 [info]: gem 'fluent-plugin-elasticsearch' version '0.3.0'

2014-05-16 00:08:17 +0000 [info]: gem 'fluent-plugin-elasticsearch' version '0.2.0'

2014-05-16 00:08:17 +0000 [info]: gem 'fluent-plugin-file-alternative' version '0.1.5'

2014-05-16 00:08:17 +0000 [info]: gem 'fluent-plugin-flume' version '0.1.1'

2014-05-16 00:08:17 +0000 [info]: gem 'fluent-plugin-forest' version '0.2.4'

2014-05-16 00:08:17 +0000 [info]: gem 'fluent-plugin-forest' version '0.2.3'

2014-05-16 00:08:17 +0000 [info]: gem 'fluent-plugin-mongo' version '0.7.1'

2014-05-16 00:08:17 +0000 [info]: gem 'fluent-plugin-record-reformer' version '0.2.8'

2014-05-16 00:08:17 +0000 [info]: gem 'fluent-plugin-rewrite' version '0.0.12'

2014-05-16 00:08:17 +0000 [info]: gem 'fluent-plugin-rewrite-tag-filter' version '1.3.1'

2014-05-16 00:08:17 +0000 [info]: gem 'fluent-plugin-route' version '0.1.2'

2014-05-16 00:08:17 +0000 [info]: gem 'fluent-plugin-s3' version '0.3.7'

2014-05-16 00:08:17 +0000 [info]: gem 'fluent-plugin-s3' version '0.3.6'

2014-05-16 00:08:17 +0000 [info]: gem 'fluent-plugin-s3' version '0.3.5'

2014-05-16 00:08:17 +0000 [info]: gem 'fluent-plugin-scribe' version '0.10.10'

2014-05-16 00:08:17 +0000 [info]: gem 'fluent-plugin-td' version '0.10.17'

2014-05-16 00:08:17 +0000 [info]: gem 'fluent-plugin-td-monitoring' version '0.1.0'

2014-05-16 00:08:17 +0000 [info]: gem 'fluent-plugin-webhdfs' version '0.2.1'

2014-05-16 00:08:17 +0000 [info]: gem 'fluentd' version '0.10.41'

 

Notice there are several plugins that have multiple versions. So I’ve got a couple questions:

 

1.)    How does fluentd determine which plugin version to use? Will it always default to the most recent?

2.)    Are there any issues caused by having multiple versions around?

3.)    Is it wise to periodically clean up old versions?

4.)    Is there an easy way to not install/upgrade the plugin unless it’s not already installed? Would that even be wise?

 

We deploy our infrastructure using chef, including all of our fluentd infrastructure. Each time chef-client runs, it will execute a “fluent-gem-install blah” for the various plugins that we use. It looks like if there is a newer version of the gem, it’s automatically installing the newest rather than saying “Hey, you’ve got this gem already – exit”. I just want to make sure there won’t be any issues over time of accumulating a history of older plugins, as machines will be re-chef’ed fairly often to update various configuration options.

 

Thanks guys!

[Kiyoto Tamura]

Hey Christian,

As long as you are loading your gems from Fluentd, Fluentd always loads the newer version of the plugin.

Kiyoto

--
You received this message because you are subscribed to the Google Groups "Fluentd Google Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fluentd+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Check out Fluentd, the open source data collector for high-volume data streams

[Kiyoto Tamura]

correction: I meant to say, "As long as you are loading your plugins from Rubygems, Fluentd always loads the newer version of the plugin."

[Christian Hedegaard]

Well, I guess that’s all I really need to know then!

 

Thanks! J

[Kiyoto Tamura]

np. we should document this behavior. I will get on it.

Kiyoto