When the filter workers crash Logstash will stop consuming any events,
Since we don't have a dead letter queue yet, we can't restart the
workers.
Fixes#3983Fixes#3990
This patch requires the use of the latest version of `jruby-openssl`
which support TLSv1.2. This PRs changes the monkeypatch to specify to
set the `ssl_version` to `TLS` which allow support of TLSv1, TLSv1.1 and
TLSv1.2.
Fixes#3955, #3991
An obsolete setting is one that will cause a configuration error if it
is used.
The purpose of `:obsolete` is to help inform users when a setting has
been completely removed. The lifecycle of a plugin setting is now 4
phases: available, deprecated, obsolete, deleted.
"Available" is the default, and deprecated remains the same as it was
(logging a warning). The new obsolete will cause a configuration error
if such a setting is used. Then later, we can finally delete the config
setting after it's been obsolete for some time.
Fixes#3977Fixes#3978
Currently, during shutdown, the pipeline loops through input workers
and calls Thread.raise on each input thread. Plugins rescue that
exception to exit the `run` loop. Afterwards, `teardown` is called for
any additional bookkeeping.
This proposal exposes a `stop` call on the input plugin class to alert
an input that it should shutdown. It is the plugin job to frequently
poll an internal `stop?` method to know if it's time to exit and
terminate if so.
The `teardown` method remains to do the additional bookkeeping, and it
will be called by the inputworker when `run` terminates.
add concurrent-ruby as logstash-core dependency
make Plugins::Input#stop? public
In some scenarios it's necessary for the inputworker or the pipeline
to know that the plugin is in a shutdown mode
document why inputworker sleeps on StandardError
better debug message when input plugin raises exception during shutdown
Remove related files for compiling the treetop grammar we have refactored the
makefile using rake. If you want to generate a new parser you can use
this command.
`rake compile:all`
Fixes#3941
This PR fix a problem when doing the interpolation with a string that
did not end with a fieldref but with a character. The interpolation was
ignoring the last character.
Example:
```
"%{type}|" => "syslog"
```
Fixes#3931Fixes#3937
Concurrent-ruby is throwing warning when running under jdk7,
we have decided to silence theses errors unless you run logstash with
the `--debug` flag.
Fixes#3869
