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

Remove unnecessary config reload #2709

Merged
merged 7 commits into from
Dec 3, 2019

Conversation

ganmacs
Copy link
Member

@ganmacs ganmacs commented Nov 27, 2019

Which issue(s) this PR fixes:
ref #2624

What this PR does / why we need it:

Current implementation loads system_config parameters(rpc_endpoint,
enable_get_dump, counter_server) in Supervisor.load_config
which is called at ServerEngine creation time.
And it can also reload config dynamically via serverengine's
mechanism(sending signal USR2 to fluentd).

These parameters can be reloadable but it doesn't make any changes
to fluentd itself. fluentd document also doesn't mention about signal USR2.
so it's no need to load in Supervisor.load_config.
it's enough to pass the value at start time.

Docs Changes:

no need

Release Note:

no need

@ganmacs ganmacs requested a review from repeatedly November 27, 2019 23:06
@ganmacs ganmacs self-assigned this Nov 27, 2019
@ganmacs ganmacs force-pushed the remove-unnecessary-config-reload branch 2 times, most recently from a58a70c to 39c73f8 Compare November 30, 2019 02:06
Signed-off-by: Yuta Iwama <[email protected]>
Current implementation loads system_config parameters(rpc_endpoint,
enable_get_dump, counter_server) in Supervisor.load_config
which is called at ServerEngine creation time.
And it can also reload config dynamically via serverengine's
mechanism(sending signal USR2 to fluentd).

These parameters can be reloadable but it doesn't make any changes
to fluentd itself. fluentd document also doesn't mention about signal USR2.
so it's no need to load in Supervisor.load_config.
it's enough to pass the value at start time.

Signed-off-by: Yuta Iwama <[email protected]>
Signed-off-by: Yuta Iwama <[email protected]>
Signed-off-by: Yuta Iwama <[email protected]>
@ganmacs ganmacs force-pushed the remove-unnecessary-config-reload branch from 39c73f8 to c98b348 Compare December 2, 2019 20:31
@ganmacs ganmacs requested a review from cosmo0920 December 2, 2019 21:32
@ganmacs
Copy link
Member Author

ganmacs commented Dec 2, 2019

@ashie @cosmo0920 could you review this patch?

Copy link
Contributor

@cosmo0920 cosmo0920 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@cosmo0920
Copy link
Contributor

nits: Which issue will be fixed by this PR?
I didn't find the concrete issue number on the pull request's description:

Which issue(s) this PR fixes:
ref https://github.com/fluent/fluentd/issues

@ganmacs
Copy link
Member Author

ganmacs commented Dec 3, 2019

nits: Which issue will be fixed by this PR?

Good catch… this is related to light config reloading mechanism.

@ganmacs ganmacs merged commit 29ad441 into fluent:master Dec 3, 2019
@ganmacs ganmacs deleted the remove-unnecessary-config-reload branch December 3, 2019 19:41
daipom added a commit to daipom/fluentd that referenced this pull request Mar 9, 2023
It does not load the config anymore since fluent#2709, so it should
simply returns the config for ServerEngine.

Signed-off-by: Daijiro Fukuda <[email protected]>
kenhys added a commit to kenhys/fluentd-kubernetes-daemonset that referenced this pull request Jul 12, 2024
Closes: fluent#1479

Feedback from @mszyzdek
ref. fluent#1479 (comment)

* graylog flavour of fluentd-kubernetes-daemonset uses gelf 3.0.0 and
  this version of gelf gem has Fixnum in code,
  graylog-labs/gelf-rb@7cc3cbb
* in ruby 3.2 Fixnum was removed after previous deprecation in version 2.4
  https://www.ruby-lang.org/en/news/2022/12/25/ruby-3-2-0-released/
* ruby in newest fluentd was upgraded to 3.2
  fluent/fluentd-docker-image@4f1d5e8
  so it also happened in fluentd-kubernetes-daemonset
* gelf 3.0.0 cannot work with ruby 3.2+ so we can see sad error on container start

NOTE: Even though gelf was updated to 3.1.0, still it has problem with
reloading Fluentd configuration with SIGUSR2. This is known issue
since Fluentd 1.8.0.
ref. fluent/fluentd#2709

Signed-off-by: Kentaro Hayashi <[email protected]>
kenhys added a commit to kenhys/fluentd-kubernetes-daemonset that referenced this pull request Jul 12, 2024
Closes: fluent#1479

Feedback from @mszyzdek
ref. fluent#1479 (comment)

* graylog flavour of fluentd-kubernetes-daemonset uses gelf 3.0.0 and
  this version of gelf gem has Fixnum in code,
  graylog-labs/gelf-rb@7cc3cbb
* in ruby 3.2 Fixnum was removed after previous deprecation in version 2.4
  https://www.ruby-lang.org/en/news/2022/12/25/ruby-3-2-0-released/
* ruby in newest fluentd was upgraded to 3.2
  fluent/fluentd-docker-image@4f1d5e8
  so it also happened in fluentd-kubernetes-daemonset
* gelf 3.0.0 cannot work with ruby 3.2+ so we can see sad error on container start

NOTE: Even though gelf was updated to 3.1.0, still it has problem with
reloading Fluentd configuration with SIGUSR2. This is known issue
since Fluentd 1.8.0.
ref.  fluent/fluentd#2709

Signed-off-by: Kentaro Hayashi <[email protected]>
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

Successfully merging this pull request may close these issues.

2 participants