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

Add FLUENT_ELASTICSEARCH_RELOAD_ON_FAILURE envvar to suppress unstable sniffering #282

Conversation

cosmo0920
Copy link
Contributor

This is reported in
uken/fluent-plugin-elasticsearch#525.

Invalid sniffer information is obtained by default, but we can avoid
the following configuration:

reload_connections false
reconnect_on_error true
reload_on_failure true

To specify reload_on_failure on fluentd-kubernetes-daemonset,
we should introduce a new envver to specify it.

Signed-off-by: Hiroshi Hatake hatake@clear-code.com

@cosmo0920 cosmo0920 changed the title Add FLUENT_ELASTICSEARCH_RELOAD_ON_FAILURE envvar to suppress sniffering Add FLUENT_ELASTICSEARCH_RELOAD_ON_FAILURE envvar to suppress unstable sniffering Mar 22, 2019
…e sniffering

This is reported in
uken/fluent-plugin-elasticsearch#525.

Invalid sniffer information is obtained by default, but we can avoid
the following configuration:

```aconf
reload_connections false
reconnect_on_error true
reload_on_failure true
```

To specify reload_on_failure on fluentd-kubernetes-daemonset,
we should introduce a new envver to specify it.

Signed-off-by: Hiroshi Hatake <hatake@clear-code.com>
@cosmo0920 cosmo0920 force-pushed the add-an-envvar-to-specify-reload_on_failure-parameter branch from 7cf883b to b9430c0 Compare March 22, 2019 08:13
@repeatedly repeatedly merged commit 6fa634a into fluent:master Mar 25, 2019
@repeatedly
Copy link
Member

Thx!

@cosmo0920 cosmo0920 deleted the add-an-envvar-to-specify-reload_on_failure-parameter branch March 25, 2019 10:18
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