-
``` bash
$ sudo service logstash stop
Killing logstash (pid 10236) with SIGTERM
Waiting logstash (pid 10236) to die...
Waiting logstash (pid 10236) to die...
Waiting logstash (pid 10236) to die...
Wai…
-
Testing the 0.9 Kafka beta output plugin and running into the following exception which I can reproduce locally:
```
input{
generator{
count=>10
}
}
output{
kafka {
topic_id => "test"
compression_t…
-
Is this a known issue and what is the workaround/fix?
:exception=>java.lang.IllegalArgumentException: Missing Ruby class handling for full class name=org.jruby.java.proxies.ArrayJavaProxy, simple nam…
-
http://build-eu-1.elasticsearch.org/job/logstash_create_all_plugins_tar_artifact_23/jdk=JDK7,label=metal-pool/lastBuild/console
The build returned a **SUCCESS** but in fact encountered many errors in…
-
It looks like we will be reworking the logstash-input-kafka to support upcoming Kafka 0.9 release that has performance improvements for the consumer. This ticket is created to track our progress.
-
This is highly undesirable, the reason we are publishing data to kafka is to ensure the consumers can be taken down and can come back up in an asynchronous fashion. Is this a limitation of this plugin…
-
Hi. I believe this is an problem on all branches. This issue is raised after testing on the master branch. When trying to reference jruby-kafka and logstash-output-kafka as git repos in gemfile so…
-
I've been using logstash 1.4.2 on AIX (7.1) and hoping to get 1.5.0.beta1 going but I'm hitting the same problem others have reported on Solaris, FreeBSD...
bash-4.2$ ./bin/logstash -f config/basic.…
-
Currently, when reading from an lz4 compressed topic from Kafka 0.8.2 results in the following error:
```
Kafka::Consumer caught exception: Java::KafkaCommon::UnknownCodecException
3 is an unknown co…
-
(This issue was originally filed by @colinsurprenant at https://github.com/elastic/logstash/issues/2899)
---
I am creating this issue here so we can better track it for the 1.5.0 release process. If…