-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Fix dry run mode #2651
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
Merged
Merged
Fix dry run mode #2651
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
repeatedly
reviewed
Oct 16, 2019
lib/fluent/supervisor.rb
Outdated
| ensure | ||
| Fluent::Engine.dry_run_mode = false | ||
| end | ||
| def configure_supervise |
Member
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
configure_supervisor?
3309da9 to
fa21b1b
Compare
This change had been introduced since https://github.com/fluent/fluentd/pull/1580/files . but even if dry-run mode, config need to show itself Signed-off-by: Yuta Iwama <[email protected]>
and if supervisor_mode, worker_id returns -1 because we need to identify worker0 and supervisor Signed-off-by: Yuta Iwama <[email protected]>
Signed-off-by: Yuta Iwama <[email protected]>
Signed-off-by: Yuta Iwama <[email protected]>
fa21b1b to
1089d34
Compare
Signed-off-by: Yuta Iwama <[email protected]>
Signed-off-by: Yuta Iwama <[email protected]>
Member
Author
|
I changed to fix #1576 at the same time. Could you take a look at this again? @repeatedly |
Signed-off-by: Yuta Iwama <[email protected]>
repeatedly
approved these changes
Nov 1, 2019
7 tasks
daipom
added a commit
that referenced
this pull request
Mar 7, 2025
Adds error handling similar to worker process. Fluent::Engine.run_configure calls Fluent::Registry#search. It can run Kernel.require. It can raise LoadError, ConflictError and others. Without this error handling, Fluentd cannot log those errors. This makes a situation where Fluentd fails to start, but there is no error log in the log file. This solves that problem. This appears to be an oversight of the following fix: * #2651 Signed-off-by: Daijiro Fukuda <[email protected]>
daipom
added a commit
that referenced
this pull request
Mar 7, 2025
Adds error handling similar to worker process. https://github.com/fluent/fluentd/blob/master/lib/fluent/supervisor.rb#L1149-L1164 `Fluent::Engine.run_configure` calls `Fluent::Registry#search`. It can run `Kernel.require`. It can raise `LoadError`, `ConflictError` and others. Without this error handling, Fluentd cannot log those errors. This makes a situation where Fluentd fails to start, but there is no error log in the log file. This solves that problem. This appears to be an oversight of the following fix: * #2651 Signed-off-by: Daijiro Fukuda <[email protected]>
daipom
added a commit
that referenced
this pull request
Mar 10, 2025
Adds error handling similar to worker process. https://github.com/fluent/fluentd/blob/master/lib/fluent/supervisor.rb#L1149-L1164 `Fluent::Engine.run_configure` calls `Fluent::Registry#search`. It can run `Kernel.require`. It can raise `LoadError`, `ConflictError` and others. Without this error handling, Fluentd cannot log those errors. This makes a situation where Fluentd fails to start, but there is no error log in the log file. This solves that problem. This appears to be an oversight of the following fix: * #2651 Signed-off-by: Daijiro Fukuda <[email protected]>
daipom
added a commit
that referenced
this pull request
Mar 11, 2025
**Which issue(s) this PR fixes**: None. **What this PR does / why we need it**: Adds error handling similar to worker process. https://github.com/fluent/fluentd/blob/8df10863769da32459aba2a1408134d0b8e7d9f4/lib/fluent/supervisor.rb#L1149-L1164 `Fluent::Engine.run_configure` calls `Fluent::Registry#search`. It can run `Kernel.require`. It can raise `LoadError`, `ConflictError` and others. Without this error handling, Fluentd cannot log those errors. This makes a situation where Fluentd fails to start, but there is no error log in the log file. This solves that problem. This appears to be an oversight of the following fix: * #2651 **Docs Changes**: Not needed. **Release Note**: The same as the title. Signed-off-by: Daijiro Fukuda <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Which issue(s) this PR fixes:
ref #2624
What this PR does / why we need it:
Show better log
Details
Example config
normal mode
Before (supervisor and worker show same log about
@type fake)After(Removed duplicated log)
dry-run mode
Before
After(show config)
when config has an error
Details
Example configBefore
After(be able to detect an error when dry-run)
Docs Changes:
no need
Release Note:
Make starting log better and seal dumped config