logstash-output-kinesis 2.0.1-java → 2.1.0-java

checksums.yaml

@@ -1,15 +1,15 @@
 ---
 !binary "U0hBMQ==":
   metadata.gz: !binary |-
-    NWYxZmNmMWM3MjYxNjczM2JiMjRjZTQ3MDZlOTJkMWU1MzcyYzVmMw==
+    N2E1OTI0M2E4ODlmNjNmMDRhYWRjOThhNmZkMzI2M2NjOGU2Njc5YQ==
   data.tar.gz: !binary |-
-    NzczNzJlMzQ3NTU2Y2YxNTI4MDY5OWU3YWVlY2QyYmYxZjQ3OTZjOQ==
+    YzczY2JjZWVjMzc0OThkYmNjYzAyZDk5NzUyYTQzMWE5NTgwZWNkNw==
 SHA512:
   metadata.gz: !binary |-
-    NDUwNTBjZDFjNmM5NjI3NjBhZjRmYWUxMDVmMWExMWY2ODAxZDc2ODljYzBl
-    MzA0Njc5Mzc4NDY5ZTI3MjFiOTU1ODRkMDBiODNkYTFiYzFhMjZhNjEzNGMy
-    NTMyZWU4MTU1MzQxMjE3NWVhMjgyNTQ0YmUwNjFhZGQ4ODk4Yzc=
+    YzI4Mzk3ZWQxZTdjZDBlNDhjMTk4YWY1ZmM0NDA4ODdkYmFhNmVjMTEzYzZm
+    YjI4NjIyYjE2NjQ5MzkyNmUxMmYwMjRmMzAwZGMxZTNjZWZjYjUzNDU1Yjgz
+    ZTA3OTQyYWI2OGRkYTRhNDRlODZhYWMzYzMwNmE1OTIzZTJjMjA=
   data.tar.gz: !binary |-
-    NWE4NDA2NzZkN2NjNTUzMzc3MmE2NDJhMTNmZmFhZmY3MGE4ZGJlNGU4MjBm
-    MTM2ODE0Mzg1NGY1OGMxZDcxMzE5YWU0OWM4NWZkMTMyNDE3NmFlZGUzMjM5
-    NTA2ODYzNWExZmFhMWZlMWU2NGMxMzVhZjhmNzZhZjFhMWY2ZWY=
+    ZTJjODczYTVmOGRlNDk2MzkwZDI4MDIzODY5ZmQzOGMyN2IxOTQ3YmQ4OGFm
+    MjRmZWY4MmExYzljZGM2OWJhYzVjYjJhNGM5OTlhNDc2MWJiNzYzMTQ0Y2Yy
+    MWQxNDI0M2ZlYmNhYTdkNjE0YjBiZTZhZDg2NWJlZTViOGZhNTI=

data/README.md

@@ -132,6 +132,19 @@ output {
 }
 ```
 
+### Backpressure
+
+The KPL library does not force any backpressure. This means if Kinesis is unavailable or throttling, KPL will happily accept records until it chews up all available memory on your machine. This plugin has a default backpressure mechanism - if there's more than 1000 pending records to be written to Kinesis, then further log records will block. This will cause Logstash to block further processing until everything is flushed out to Kinesis. I know that sounds lame, but it's better than the Linux OOM killer stepping in and breaking all your shit, no?
+
+Anyway, if you want to throw more memory / CPU cycles at buffering lots of stuff before it makes it to Kinesis, you can control the high-watermark:
+
+```nginx
+output {
+  kinesis {
+    max_pending_records => 10000 # I sure as hell hope you know what you're doing.
+  }
+}
+```
 
 ## Known Issues
 

data/lib/logstash-output-kinesis/version.rb

@@ -1,3 +1,3 @@
 module LogstashOutputKinesis
-  VERSION = "2.0.1"
+  VERSION = "2.1.0"
 end

data/lib/logstash/outputs/kinesis.rb

@@ -20,6 +20,9 @@ class LogStash::Outputs::Kinesis < LogStash::Outputs::Base
   config :event_partition_keys, :validate => :array, :default => []
   # If true, a random partition key will be assigned to each log record
   config :randomized_partition_key, :validate => :boolean, :default => false
+  # If the number of records pending being written to Kinesis exceeds this number, then block
+  # Logstash processing until they're all written.
+  config :max_pending_records, :validate => :number, :default => 1000
 
   # An AWS access key to use for authentication to Kinesis and CloudWatch
   config :access_key, :validate => :string
@@ -190,6 +193,13 @@ class LogStash::Outputs::Kinesis < LogStash::Outputs::Base
     rescue => e
       @logger.warn("Error writing event to Kinesis", :exception => e)
     end
+
+    num = @producer.getOutstandingRecordsCount()
+    if num > @max_pending_records
+      @logger.warn("Kinesis is too busy - blocking until things have cleared up")
+      @producer.flushSync()
+      @logger.info("Okay - I've stopped blocking now")
+    end
   end
 end
 

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: logstash-output-kinesis
 version: !ruby/object:Gem::Version
-  version: 2.0.1
+  version: 2.1.0
 platform: java
 authors:
 - Sam Day
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2015-11-06 00:00:00.000000000 Z
+date: 2015-12-05 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: logstash-core