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

Fix log messages and its conditions #1227

Merged
merged 4 commits into from
Sep 28, 2016
Merged

Fix log messages and its conditions #1227

merged 4 commits into from
Sep 28, 2016

Conversation

repeatedly
Copy link
Member

No description provided.

@tagomoris
Copy link
Member

Tests are not fixed with modified log messages.

@repeatedly
Copy link
Member Author

Yes because I want feedback for more better message.

@tagomoris tagomoris added enhancement Feature request or improve operations v0.14 labels Sep 12, 2016
@@ -56,7 +56,7 @@ def configure(conf)
elsif @path
# ok
else # @_plugin_id_configured is true
raise NotImplementedError, "implement this feature later with system_config"
raise NotImplementedError, "implement this feature later with system_config. Add <storage> section for file store or remove @id for memory store temporary"
Copy link
Member

Choose a reason for hiding this comment

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

This block is for "Make root path for buffers and storages" (root path is based on @id) described in wiki. So it's wrong to tell users to remove @id.
https://github.com/fluent/fluentd/wiki/Changes-proposed-for-v0.14.x#multi-processes--cpu-cores

Copy link
Member Author

Choose a reason for hiding this comment

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

Yeah, I know. The problem is users now hard to use without file because storage plugin doesn't have store type option.
Currently, existing users hit this error because they use following configuration for v0.12.

<source>
  @type dummy
  @id input_dummy
  # ...
</source>

I think this configuration should work with v0.14 without error. My change is temporary. Better way is fallback to on memory store, not raising NotImplementedError.

Copy link
Member Author

Choose a reason for hiding this comment

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

There are 2 ways for in_dummy.

  • Add store_type like option to specify file or on-memory and log message in this line
  • Fallback to on-memory storage, not raising NotImplementedError

Copy link
Member

Choose a reason for hiding this comment

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

IMO, falling back to on-memory storage is better than adding configuration parameters for temporal issue.

"worse performance" is bad for user impression. Several users misread
"Why this plugin makes fluentd performance slower?"
Perfomance is same as before without optimization, so
log message should be changed.
@repeatedly repeatedly changed the title Fix log messages Fix log messages and its conditions Sep 26, 2016
@repeatedly
Copy link
Member Author

Update test for EventRouter.

@repeatedly
Copy link
Member Author

Test passed excluding unstable test. Re-run test.

@repeatedly
Copy link
Member Author

Test are passed.

@repeatedly
Copy link
Member Author

If no concern, I will merge it.

@repeatedly repeatedly merged commit 1122182 into master Sep 28, 2016
@repeatedly repeatedly deleted the fix-log-messages branch March 9, 2018 23:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Feature request or improve operations v0.14
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants